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

job-resume

Skill0 starsChanged 23 days agoMITView on GitHub

Review career evidence and peer feedback, select or tailor a resume, and verify reusable application materials. Use directly for resumes, bios and career stories or as supporting work during an authorized application; submission belongs to job-application.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. rockbenben/ai-job-search-cn★ 48same name

    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 repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask only for missing evidence that materially affects a claim.

    line 21
  2. Distinctive:

    Treat peer feedback as attributed evidence to review, not automatic factual authority.

    line 22
  3. Distinctive:

    Keep a compact claim-to-source map for materially new or changed claims.

    line 23

≈ “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

Resume and career evidence

Turn the candidate's actual experience into accurate, useful materials. Reuse a suitable current document before creating another variant. Accept handoffs from application or coaching work without requiring the user to invoke this skill separately; return the verified artifact and unresolved claims to the requesting workflow.

Find the authoritative evidence

Use the private workspace selected by the user or task. Read its AGENTS.md and roles/INDEX.md for source mappings; never look for candidate records inside the installed skill. Defaults beneath the private workspace are references/profile.md, references/preferences.md and resumes/INVENTORY.md. Read corrections first, relevant source evidence second, and the exact role only when tailoring. Preserve existing filenames, storage services and ownership.

Work directly from supplied materials if there is no workspace. Do not require setup for an edit. If persistent storage is requested without a destination, resolve the private location; job-search-setup can help when installed.

Separate confirmed facts, candidate recollections awaiting clarification, peer observations and your editorial suggestions. Keep dates, titles, actual responsibilities, team outcomes and individual contribution distinct. Career duration does not establish equal specialization tenure; a project, course or experiment does not establish professional employment. Old resume wording does not override a later correction.

Review the substance

  • Identify the audience and requested material. For a specific role, use its actual duties and advertised level to select relevant evidence. Do not upgrade past titles, proficiency or ownership to match a vacancy.
  • Ask only for missing evidence that materially affects a claim. Never invent metrics, team sizes, credentials, clients, technologies or causality. A precise qualitative result is useful when a number is unavailable.
  • Treat peer feedback as attributed evidence to review, not automatic factual authority. Record whether the candidate accepts, rejects or defers it; reconcile disputed observations with available sources. Do not copy confidential employer material or reveal peer identities in outward-facing documents without authorization.
  • Keep a compact claim-to-source map for materially new or changed claims. Use the optional evidence review template when several claims or conflicts need review; keep it in the private workspace. Do not create a duplicate biography merely to rewrite a bullet.
  • Draft for clarity: what the candidate did, relevant context, supported outcome and ownership. Retain distinctions between contributing, leading and managing. Surface unresolved assertions outside the deliverable instead of presenting them as established facts.

Choose, produce and verify

Read the resume inventory and any resume-specific instructions before choosing a file. Reuse an approved template and suitable verified variant. Tailor only when the target or evidence calls for a material change; a new company name alone does not require a new resume. A requested draft needs no separate approval, but label it as a draft until reviewed.

Use available document/PDF tools for the requested format; PDF is a useful default when no format is specified. Inspect rendered pages for clipping, spacing, page breaks, readable links and consistent typography. Check extracted text and reading order against the source, including contact fields and current claims. Do not promise ATS scores or parsing success. If rendering is unavailable, provide the editable artifact and state that visual verification remains incomplete.

Record the actual output path, source revision, format, review status and intended use in the private inventory when maintaining that workspace. Preserve exact submitted versions; corrections affect future materials and never silently replace files linked to past applications. Remove unintended comments, revision history and document metadata from an outward-facing copy while preserving useful private sources.

Finish with the reviewed artifact, substantive changes and any unresolved claim. Sharing, uploading and applying require their own authorization; use job-application for an authorized application when available.

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.