Agent skill
example-workflow
Use when demonstrating plugin workflow features - shows how skills can guide multi-step processes
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/example-workflow
SKILL.md
Example Workflow Skill
Overview
This skill demonstrates how to create a workflow-based skill that guides Claude through a multi-step process. It serves as a reference implementation for plugin developers.
When to Use
This is an example skill for learning purposes. In a real plugin, you would:
- Use when specific conditions match the skill's domain
- Provide clear triggering criteria
- Guide through complex multi-step workflows
Example Workflow
When invoked, this skill would guide through these steps:
- Gather requirements - Ask clarifying questions
- Plan approach - Create a structured plan using TodoWrite
- Execute systematically - Follow the plan step-by-step
- Verify results - Confirm the outcome matches requirements
Integration with Other Components
This skill demonstrates how skills can:
- Reference bundled documentation in
references/ - Call executable scripts in
scripts/ - Use MCP server tools provided by the plugin
- Trigger or respond to plugin hooks
For Plugin Developers
Key points this example demonstrates:
- Clear YAML frontmatter with name and description
- Structured workflow with numbered steps
- Integration points with other plugin components
- Documentation of when/how to use the skill
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?