create-skill
Workflow
Follow these 9 steps in order. Copy this checklist into your response and check off each step as you complete it:
Task Progress:
- [ ] Step 1: Understand the skill with concrete examples
- [ ] Step 2: Choose skill name
- [ ] Step 3: Write description
- [ ] Step 4: Write frontmatter
- [ ] Step 5: Write SKILL.md body
- [ ] Step 6: Decide on progressive disclosure
- [ ] Step 7: Create bundled resources
- [ ] Step 8: Validate
- [ ] Step 9: Iterate
Step 1: Understand the Skill with Concrete Examples
More from hyf0/skills
optimize-skill
Analyzes and optimizes an existing agent skill for conciseness, discoverability, and adherence to best practices. Use when a skill needs improvement, is too verbose, has poor activation rates, or fails to follow progressive disclosure patterns. Do NOT use for creating a new skill from scratch — use create-skill instead.
18code
Open the current working directory or a specified folder in Visual Studio Code.
11dev-announce
Generates developer tool feature announcement tweets in an understated, data-driven style. Use when drafting tweets to announce new features, performance improvements, or API additions for projects like Rolldown. Do NOT use for general social media posts, blog writing, or non-technical announcements.
6resolve-pr-comments
Review and resolve GitHub PR review comments. Use when the user wants to address, fix, or resolve unresolved review comments on a pull request. TRIGGER when: user says \"resolve PR comments\", \"fix PR comments\", \"address review comments\", \"handle PR feedback\", or provides a PR URL with instructions about unresolved comments. Do NOT use for: creating PRs, reviewing code yourself, or general PR operations that don't involve resolving existing review comments.
4