setup
Skill1 starsChanged 3 months agoMITView on GitHub
Build the candidate profile from scratch through a guided interview. Run this first, before any other skill. Populates profile/*.md and career_facts.yaml.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- openstory-so/openstorytheir own version, first seen Nov 16, 2026
- furkandvrc/conductortheir own version, first seen Nov 16, 2026
- futorio/red-greentheir own version, first seen Nov 16, 2026
- JCodesMore/jobs-for-ai-agentstheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
Used with
Projects with it also use add-atomic-chat-tool, add-dashboard and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-atomic-chat-tool
Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
Also in 8 projects that use this
MicrosoftSkilladd-dashboard
Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
Also in 8 projects that use this
- +10 more from microsoft
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- anthropics/knowledge-work-plugins★ 36ksame name
- garrytan/gbrain★ 33ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.4ksame name
- pytorch/executorch★ 5.2ksame name
- aws/agent-toolkit-for-aws★ 3.5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- company-researchSkill
- cover-letterSkill
- cv-tailorSkill
- interview-coachSkill
- job-scoutSkill
- learnSkill
- negotiatorSkill
- network-mapperSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- outreach-drafterSkill
- submitSkill
- trackerSkill
- upskillSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not rush to fill everything in one pass.
- Distinctive: line 14
Ask the user to gather, if they have them (none are required to begin):
- Distinctive: line 29
Ask directly: what energized you, what drained you, what you want more of, what you won't do again.
- Distinctive: line 34
Ask for 1-2 paragraphs of their real writing.
- Very specific: line 48
Never fabricate on the user's behalf: If they can't substantiate a metric or skill, leave it out.
- Distinctive: line 50
Write incrementally to the files as facts are confirmed.
“Common” is measured: kept by at least 6 in 10 of the 169 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/setup — build your profile from scratch
The user has no materials yet. Your job is to interview them and produce their profile files. Do not rush to fill everything in one pass; a rich profile is the highest-leverage thing in this whole system, so it is worth several sessions.
Before you start
Ask the user to gather, if they have them (none are required to begin):
- Their current CV / resume (any format)
- LinkedIn "Data Export → Connections" CSV → drop in
data/connections/(feeds the network layer later; also gitignored as personal data) - Any past cover letters, reference letters, diplomas
The interview — run in this order, one theme at a time
- Career spine →
profile/01-candidate-profile.mdandcareer_facts.yamlFor each role: company, title, dates, real scope, specific projects, tools, and only defensible metrics. Push gently for numbers, but never invent one — if they can't defend it, it doesn't go in the facts. As you confirm each hard fact, write it tocareer_facts.yaml(this is the frozen truth the honesty gate uses). - Energy audit →
profile/02-behavioral-profile.mdAsk directly: what energized you, what drained you, what you want more of, what you won't do again. This shapes fit scoring more than the resume does. Suggest a free DISC or 16Personalities if they want a working-style section. - Voice →
profile/03-writing-style.mdAsk for 1-2 paragraphs of their real writing. Extract do's/don'ts. This is what stops later drafts sounding like a language model. - Rubric →
profile/04-job-evaluation.mdWalk them through the knobs. Enforce the two design rules: mostly penalties, andmin_senioritydrops below Senior (inverted from the usual junior filter). Fill the YAML block with their real constraints (location, comp floor, exclusions). - CV source + STAR bank →
profile/05-cv-source.md,profile/07-interview-prep.mdThe uncut CV content, and 6-10 real STAR stories covering the Staff/Group-level probes (direction-setting, influence without authority, a hard trade-off, an owned failure, a cross-team decision, an AI/tech-depth story).
Rules
- Never fabricate on the user's behalf. If they can't substantiate a metric or skill,
leave it out. The whole system's integrity rests on
career_facts.yamlbeing true. - Write incrementally to the files as facts are confirmed; don't hold everything in context.
- End each session by telling the user which files are still thin and what to bring next.
Optional: Lenny's Product Skills (read-and-distill, don't bulk-install)
A subset of https://github.com/RefoundAI/lenny-skills is useful as source material for the profile — read them once, distill into the user's own words, don't leave 86 PM-operating skills installed and polluting agent triggering. Relevant ones for a Senior/Lead/Staff/Group
- AI-builder target:
career-transitions,written-communication,defining-product-vision,stakeholder-alignment,systems-thinking,evaluating-trade-offs,ai-product-strategy,building-with-llms,ai-evals. The hiring-side ones (evaluating-candidates,conducting-interviews,writing-job-descriptions) are installed as active skills for the Interview Coach — see that skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

