Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles.
Provides software engineering resume guidance for ATS optimization, achievement bullet formulas, and job-targeted tailoring. Use when reviewing resumes or crafting impact-driven content from work experience.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install soft-skills@melodic-softwareThis skill is limited to using the following tools:
references/achievement-formula.mdreferences/ats-keywords.mdreferences/resume-structure.mdreferences/tailoring-guide.mdComprehensive guidance for creating effective software engineering resumes that pass ATS systems and resonate with hiring managers.
A resume is a marketing document, not a job history. Its purpose is to:
Software engineering resumes should emphasize:
| Experience Level | Recommended Length |
|---|---|
| 0-5 years | 1 page |
| 5-10 years | 1-2 pages |
| 10+ years | 2 pages max |
FirstName_LastName_Resume.pdf[Strong Action Verb] [specific task/project] using [tools/methods], resulting in [quantified outcome].
| Category | Verbs |
|---|---|
| Technical | Architected, Built, Deployed, Engineered, Implemented, Integrated, Migrated, Optimized, Refactored, Scaled |
| Design | Analyzed, Designed, Documented, Modeled, Prototyped, Researched, Specified |
| Leadership | Championed, Coached, Led, Mentored, Pioneered, Spearheaded |
| Impact | Achieved, Boosted, Delivered, Improved, Increased, Reduced, Saved, Streamlined |
When tailoring for a job description:
For detailed guidance on specific topics:
achievement-bullet output style - Format for achievement bullets/soft-skills:craft-achievement command - Transform descriptions into bullets/soft-skills:tailor-resume command - Adapt resume for specific jobresume-coach agent - Interactive resume improvementThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.