agentleFS
shashu10shashu10/job-search-skills/skills/job-search-setup/SKILL.md

job-search-setup

Skill0 starsChanged 23 days agoMITView on GitHub

Set up a private job-search workspace or connect an existing search to these skills. Use for onboarding and source mapping.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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
  1. Distinctive:

    Call supporting skills when needed.

    line 19
  2. Distinctive:

    Use the user's chosen private folder, outside the public package and installed skill folders.

    line 23
  3. Very specific:

    Keep sourced, dated facts and corrections in references/profile.md.

    line 31
  4. Distinctive:

    Start with one application tracker and one outreach record.

    line 37
  5. Distinctive:

    Check links, ownership and corrections, then report what's ready and the next useful action.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Set up a job search

Give the search a home, then get to work. Standalone coaching can start from supplied context without a workspace, interview invitation or offer.

Start with a request

Let users ask naturally:

  • Find and Apply to Jobs — job-research
  • Find and Request Referrals — recruiting-outreach
  • Interview Coach — job-interview
  • Offer Negotiator — job-offer

Call supporting skills when needed. Resume tailoring belongs inside the application workflow; users need not manage every handoff.

Choose the workspace

Use the user's chosen private folder, outside the public package and installed skill folders. For an existing search, read its instructions and map its sources. Preserve names, storage services, records and owners; don't create a competing tracker.

For a new search, use ordinary file tools to copy the blank workspace from assets/workspace/ into that folder, preserving subfolders. Rename gitignore.template to .gitignore. Check destination paths first; never overwrite existing files. No installation script is required.

Learn what matters

Reuse the resume and confirmed answers. Ask only for missing targets, level, locations/work rights, working languages, constraints and immediate priorities. Optional unknowns can wait. Collect sensitive identifiers or legal declarations only when an authorized application needs them.

Keep sourced, dated facts and corrections in references/profile.md; keep choices and workflow limits in references/preferences.md. Confirm the scheduling timezone when needed. Don't infer work rights from residence or timezone, or generalize an employer-specific declaration. Leave permissions unset unless granted.

Keep one source for each thing

Adapt the private AGENTS.md to map installed skills and sources. The template routes all ten skills; load only what's needed. Follow recordkeeping when choosing fields and owners.

Start with one application tracker and one outreach record. Keep shortlist choices separate from employer stages; “pursue” alone doesn't authorize submission. Reuse valid grants within scope. Add separate lanes only when needed, with clear ownership.

Reuse resume templates and inventory; preserve submitted versions and receipts. Interview, offer, inbox and schedule notes support the live records. Leave unused templates blank. Dashboards read these sources rather than duplicating stages.

Check links, ownership and corrections, then report what's ready and the next useful action. Keep personal data out of the distributable package. Setup sends no messages, submits no applications and schedules nothing.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.