From cowork-job-search
Help answer job application questions tailored to a specific role
How this skill is triggered — by the user, by Claude, or both
Slash command
/cowork-job-search:app-questionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Priority hierarchy**: See `shared/references/priority-hierarchy.md` for conflict resolution.
Priority hierarchy: See
shared/references/priority-hierarchy.mdfor conflict resolution.
Help answer job application questions by saving each question to the job folder and generating a tailored answer based on your resume, work history, and the specific job posting.
/cowork:app-questions - Start the flow (will ask for a job URL or use most recent)/cowork:app-questions https://... - Answer questions for a specific job posting/cowork:app-questions last - Use the most recent job folderResolve the data directory using shared/references/data-directory.md.
Resolve the data directory, then check prerequisites per shared/references/prerequisites.md. Resume is required; profile is recommended but not blocking.
If $ARGUMENTS is "last" or empty:
DATA_DIR/jobs/ for the most recently modified folderIf $ARGUMENTS is a URL:
DATA_DIR/jobs/shared/references/browser-setup.mdDATA_DIR/jobs/[company-slug]-[date]/posting.mdLoad these files for context:
posting.md — the job description (required)resume.md — the tailored resume for this role (if available)DATA_DIR/resume/* — original resumeDATA_DIR/profile.md — work history (if available)questions.md — previously answered questions for this job (if exists)Ask the user to paste or type the application questions. Common types include:
The user can provide:
For each question, write a tailored answer that:
For behavioral questions (STAR format):
For salary questions: Reference the salary range from the job posting if available. If the user has a target in DATA_DIR/preferences.md, use that. If unsure, draft a flexible response and flag it for user review.
For "why this company" questions: Pull from the job posting, company description, and any details in the posting about mission/values. Connect to the candidate's career arc from the profile.
Save all questions and answers to DATA_DIR/jobs/[company-slug]-[date]/questions.md:
# Application Questions — [Company] [Role]
*Generated: [DATE]*
*Job posting: [URL]*
---
## Q1: [Question text]
**Character limit**: [N] (if specified)
[Answer]
---
## Q2: [Question text]
[Answer]
---
Present each answer to the user with:
After presenting answers, ask:
"Want to adjust any of these? I can change the tone, swap in different examples, or shorten/lengthen answers."
For each revision:
questions.mdThe user may also:
When answering questions, check if similar questions have been answered for previous jobs in other DATA_DIR/jobs/*/questions.md files. If so:
This builds a growing bank of application answers that get better over time.
Structure user-facing output with these sections:
Add to ~/.claude/settings.json:
{
"permissions": {
"allow": [
"Read(~/.claude/skills/**)",
"Read(~/.cowork/**)",
"Write(~/.cowork/**)",
"Edit(~/.cowork/**)",
"mcp__claude-in-chrome__*"
]
}
}
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub whyuascii/cowork-job-search --plugin cowork-job-search