Frameworks for technical interviews and salary negotiation. Use for behavioral interview prep (STAR method), technical interview communication, offer evaluation, and compensation negotiation strategies.
Provides frameworks for technical interviews and salary negotiation. Use for STAR method behavioral prep, technical interview communication, offer evaluation, and compensation negotiation.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install soft-skills@melodic-softwareThis skill is limited to using the following tools:
references/salary-negotiation.mdreferences/star-method.mdThis skill provides frameworks for excelling in technical interviews and negotiating job offers effectively.
Structure answers to behavioral questions ("Tell me about a time when...") using STAR:
| Component | % of Answer | Purpose |
|---|---|---|
| Situation | 10% | Set the context |
| Task | 10% | Your specific responsibility |
| Action | 60% | What you did (the meat) |
| Result | 20% | Outcomes with metrics |
Example Structure:
"Tell me about a time you resolved a conflict on your team."
SITUATION (10%): "On my last project, two senior engineers disagreed
about the database architecture - one wanted PostgreSQL, the other MongoDB."
TASK (10%): "As the tech lead, I needed to help them reach a decision
that the whole team could support without damaging their relationship."
ACTION (60%): "First, I scheduled a meeting where each could present
their case with specific criteria: performance requirements, team expertise,
and maintenance burden. Then I created a decision matrix we could score together.
When scores were close, I facilitated a discussion about what mattered most
for THIS project specifically. I made sure both felt heard by summarizing
their key points before moving on."
RESULT (20%): "We chose PostgreSQL based on the team's existing expertise.
Both engineers felt the process was fair - one even said it was the best
technical decision process he'd experienced. The project launched on time
and we haven't had database issues in 18 months."
Full reference with 5 example stories: references/star-method.md
Beyond coding ability, how you communicate matters:
Negotiation is expected and professional. Most offers have room to negotiate.
Research market rates
Know your BATNA
Wait for the formal offer
| Tactic | Example |
|---|---|
| Use email | Written negotiation is documented and thoughtful |
| State a range | "$150K-$160K based on my research" |
| Cite specifics | "Based on levels.fyi data for this role..." |
| Negotiate holistically | Salary, equity, sign-on, PTO, remote work |
| Express enthusiasm | "I'm excited about this role" + negotiation |
Full reference with scripts and tactics: references/salary-negotiation.md
When an offer is below expectations:
Prepare 3-5 versatile stories that can answer multiple question types:
| Story Theme | Can Answer Questions About |
|---|---|
| Technical challenge | Problem-solving, learning, complexity |
| Team conflict | Conflict resolution, communication, leadership |
| Project under pressure | Stress, prioritization, delivery |
| Mistake/failure | Learning, humility, growth |
| Cross-team collaboration | Influence, stakeholder management |
Each story should include:
references/star-method.md - Full STAR examples for common questionsreferences/salary-negotiation.md - Detailed negotiation tactics and scripts/soft-skills:prep-interview command - Structure your interview storiesprofessional-communication skill - General communication frameworksDate: 2025-12-26 Model: claude-opus-4-5-20251101
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 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 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.