agentleFS
wonderwhizwonderwhiz/offladder-claude/skills/answer-application-questions/SKILL.md

answer-application-questions

Skill0 starsChanged 4 days agoMITView on GitHub

Draft honest answers to job application form and screening questions, such as "Why do you want to work here?" or "Describe a time you…", from the job post and the person's CV. Use when someone pastes application questions or asks for help with a job application form.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Never invent experience, results or motivation.

    line 23
  2. Distinctive:

    Never tick consent boxes or submit anything on their behalf.

    line 24

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

Answer job application questions

Screening questions are often read, or filtered, before the CV. Answers should be short, specific and consistent with the CV, because one person may read both.

How to do it

  1. Sort the questions first.
    • Only they can answer: salary expectations, notice period, right to work or visa, start date, location, licences, criminal record, and equality questions (gender, ethnicity, disability, age). Don't draft these. Tell them what each one is for, and for salary, suggest researching a range for that role and area.
    • Eligibility yes/no: often knockout filters. They must answer exactly and truthfully; don't suggest stretching them.
    • Open questions: draft these.
  2. For each open question, use one example from their CV or from what they tell you: what happened, what they did, what changed. Aim for 50 to 150 words unless there's a word limit, and respect any limit exactly.
  3. "Why this company / role?" needs a real reason from them. Ask for one if you don't have it rather than inventing praise.
  4. Check consistency with the CV: same titles, dates and numbers.
  5. Suggest they keep a document of their best answers to adapt next time instead of starting from zero.

Rules

  • Never invent experience, results or motivation.
  • Never tick consent boxes or submit anything on their behalf; they review and send every answer themselves.

If the OffLadder tools are connected

find_career_guide with "screening questions" or "application forms faster" returns OffLadder's guides with sources. OffLadder CV, its free Chrome extension, can fill application forms with a tailored CV and draft open answers for the person to check, and never drafts questions only they can answer.

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.