write-skill
Use when creating, editing, evaluating, testing, or verifying ANY skill or skill-related file (SKILL.md, skill resources, skill scripts, or skill assets). If you're asked to evaluate or test a skill's effectiveness, use this skill.
What this skill does
## Understand Requirements First When asked to create or edit a skill: 1. If helpful, **ask clarifying questions** about the skill's purpose: - What specific problem does this skill solve? - What should the output/outcome be? - What context or inputs will the skill work with? - What are the key behaviors or patterns it should enforce? 2. **Summarize your understanding** and get user confirmation: - "Let me confirm: this skill should [summary]. Is this correct?" - Wait for user approval before proceeding **You cannot create a good skill without understanding what you're building.** ## Testing After writing a skill, ask the user: "Would you like me to test the skill?" (Skills are often manually tested by the user, or can't be tested in an automated way, so you should ask before proceeding.) If the user opts for the agent to test the skill: 1. **Design a scenario** that exercises the skill's core purpose. Describe it to the user and get approval before running it. 2. **Run the scenario** with a subagent. Document exactly what the agent did—what choices it made, what worked, what didn't. 3. **If the agent failed or rationalized away the skill's intent**, identify the gap, add an explicit counter to the skill, and re-test. 4. **Repeat** until the skill reliably produces the intended behavior. ## Scripts When a skill includes executable scripts, **REQUIRED:** Use the `script` skill for language selection and conventions. ## Interactive File Editing If a script you're writing would benefit from the user interactively editing and saving a file, add to the SKILL.md: **REQUIRED:** Invoke the `neovim` skill. Have the script call `edit-and-wait.sh`. ## Required Reading **STOP. Read these documents NOW. Not later. Not "as you go." Right now.** - [Format Guide](references/format-guide.md) - [Getting Agents to Follow Instructions](references/getting-agents-to-follow-instructions.md) - [Agent Skills](https://code.claude.com/docs/en/skills.md) - [Skill Specification](https://raw.githubusercontent.com/agentskills/agentskills/main/docs/specification.mdx) - [Skill Authoring Best Practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices.md) - [Persuasion Principles](https://raw.githubusercontent.com/obra/superpowers/main/skills/writing-skills/persuasion-principles.md)
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.