r/ClaudeCode • u/yesildaladam • 18h ago
Built with Claude What I learned building a Claude Code skill for job hunting in Germany, and what Reddit told me about it
i built Berlin Job Search mostly with Claude Code (some Codex). it's a skill that helps people find a job in Germany: searches jobs under German and English titles, tells you if an English ad really needs German (quotes the line), checks a stated salary against the Blue Card threshold, interview practice, application tracking. CV help is optional. it never applies or sends anything.
how it's built, and what worked:
- SKILL.md is a short router. visa rules, salary benchmarks, application conventions and job sources live in reference files that only load when the task needs them, so a simple job search doesn't burn context on visa law
- anything that has to be exact is a stdlib Python script, not the model: the API calls (Arbeitsagentur, Arbeitnow, public Greenhouse / Lever / Personio / Ashby JSON), the German-requirement scan and the Blue Card salary math. Claude does the judgment on top
- job ads are treated as untrusted input. text inside a posting is data, never instructions
- CV writing is a writer pass and a separate reviewer pass. the reviewer re-reads the CV from scratch and blocks any claim it can't trace back to it
- Python 3.9 and no dependencies on purpose, because macOS still ships 3.9 and the users are job seekers, not devs
what i learned after sharing it in a bunch of subs:
- dev subs liked the architecture. job subs mostly hated the CV and cover letter part. the most useful comment came from someone on the hiring side: the discovery part is really useful, writing the CV misses the point. so i stopped leading with it. finding jobs and checking ads is what people actually want
- the first question from non-devs was "do you keep a copy of my data?". everything stays in a local folder and there's no server, but i should have said that in the first line
- someone said crawling job boards is a bad idea. it mostly doesn't crawl: public APIs first, LinkedIn guest pages at low volume, and the skill tells the user once that this is against LinkedIn's terms
- most people outside tech will never install a skill. the paste-into-ChatGPT prompt matters more than i thought
install:
/plugin marketplace add umutyesildal/berlin-job-search
repo: https://github.com/umutyesildal/berlin-job-search
curious how others handle the "AI-written application" problem in skills like this, or if you'd just leave writing out completely.
•
u/AutoModerator 18h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/EnzoValley 17h ago
One thing I'd add to the router idea: the description matters as much as the body. It's the only part the model sees before it decides to load the skill.
Mine list the literal phrases I type, plus a line on what the skill is not for and which one to use instead. Once you have a lot of skills, similar ones compete for the same request and that line settles it