Example workflow

Skill lakarpusky/claude-skills-toolkit/templates/example-workflow

Example skill demonstrating all skill patterns and best practices. Use when user asks for "skill examples", "skill patterns", or wants to learn about skill development.From its SKILL.md

Install

npx -y skills add lakarpusky/claude-skills-toolkit --skill example-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, 513 tokens by cl100k_base, as published. Nobody here has run it

Example Workflow Skill

This skill demonstrates proper structure and common patterns for building skills.

Instructions

Step 1: Understand the Request

Analyze user input to determine:

What outcome they want
What tools/data are needed
Any constraints or preferences

Step 2: Execute Workflow

Based on analysis:

For document creation:

Gather required information
Apply template from assets/
Generate content
Run quality checks

For MCP operations:

Verify MCP connection
Make API calls in sequence
Validate each response
Handle errors gracefully

Step 3: Deliver Results

Summarize what was done
Provide output/links
Suggest next steps if applicable

Examples

Example 1: Simple Task

User says: "Create a project checklist"

Actions:

Ask for project name and key milestones
Generate checklist from template
Format as markdown

Result: Formatted checklist ready for use

Example 2: Multi-Step Workflow

User says: "Set up a new client workspace"

Actions:

Create project folder (Phase 1)
Generate standard documents (Phase 2)
Set up tracking (Phase 3)
Send notification (Phase 4)

Result: Complete workspace with all components linked

Error Handling

Error: Missing Required Input

Cause: User didn't provide necessary information

Solution:

Identify missing fields
Ask user for specific missing items
Provide examples of expected format

Error: Validation Failed

Cause: Generated content didn't meet quality threshold

Solution:

Log specific validation failures
Attempt automated fix if possible
Request user guidance if needed

References

See references/patterns.md for detailed pattern documentation
See references/yaml-frontmatter.md for YAML field reference
See scripts/validate_skill.py for validation logic

Best Practices Demonstrated

Clear structure - Organized with headers and sections
Specific examples - Shows actual user phrases and outcomes
Error handling - Covers common failure cases
References linked - Points to additional resources
Actionable steps - Each instruction is clear and specific

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most automation workflows skills give in 513 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

Write conventional commit messagesin 36 of 745, across 35 files
Delete branches after mergein 30 of 745, across 21 files
Make atomic commitsin 25 of 745, across 15 files
Write minimal code to pass testsin 22 of 745, across 10 files
Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
Use try-catch for error handlingin 20 of 745, across 8 files
Run tests before committingin 20 of 745, across 12 files
Write tests before implementationin 20 of 745, across 8 files
Configure branch protection rulesin 19 of 745, across 5 files
Explain the why in commit messagesin 19 of 745, across 9 files
Refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

analyze user input for desired outcome
gather required information for document creation
apply template for document creation
run quality checks for document creation
make api calls in sequence
validate each api response

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.