answer-questionslisted

Draft the free-text answers a job application asks for - "why do you want to work here", "why are you a fit for this role", "tell us about a project you are proud of", "anything else we should know" - grounded strictly in the user's real resume and the job posting, and written so they do not read as AI output. Use whenever the user is filling in an application form and needs the written portions, pastes application questions, asks "how should I answer this", wants a cover-letter box filled, or reaches that stage of apply-to-job after their resume is tailored. Also use for a recruiter's written screening questions. Do NOT use it for a cold outreach email to a company that has not asked anything (that is a different task), and do NOT use it to answer salary or work-authorization questions, which the skill deliberately hands back to the user.
DhruvPrajapati4/apply-kit · ★ 0 · AI & Automation · score 70

Install: claude install-skill DhruvPrajapati4/apply-kit

# answer-questions An application's text boxes are read by a human, usually right after they have skimmed forty near-identical answers. What survives that is specificity: real numbers, real systems, and a point of view about this particular company. Everything here rests on one rule inherited from the rest of the kit: **the answers may only contain things the user has actually done.** A resume that has been tailored honestly and then paired with an invented answer is worse than either alone, because the invention is the part that gets probed in the interview. ## Inputs Read whatever exists in the scratchpad. Each one makes the answers sharper: | File | What it gives you | |---|---| | `master.tex` | the only legitimate source of achievements and numbers | | `jd-brief.md` | what the company says it wants, in its own words | | `fit-report.md` | the honest gaps, which are answer material, not shameful | | `job-leads.md` | company context if discovery ran | One input is not a file: the repeat answers the user has already given once (self-identification, notice period) are remembered across sessions rather than stored in the project, so check what is already known before asking again. If the questions came from a form the user is looking at, ask them to paste the questions verbatim, along with any word or character limits. Limits are not decoration; an answer truncated mid-sentence by the form reads as carelessness. ## Procedure 1. **Sort the questions.** Some you can answ