- Claude Code
- Skill
- Advanced
- Claude Code
- Published
Recurring Workflow to SKILL.md with Trigger, Steps and Verification
Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step.
You get: Working code with an explanation
Ready to use: no blanks to fill in.
The prompt
Installs to .agents/skills/recurring-workflow-to-skill-md-with-trigger-steps-and-verificati/
mkdir -p .agents/skills/recurring-workflow-to-skill-md-with-trigger-steps-and-verificati && curl -sL "https://prompts-gpt.com/prompts/recurring-workflow-to-skill-md-with-trigger-steps-and-verification/raw" -o .agents/skills/recurring-workflow-to-skill-md-with-trigger-steps-and-verificati/SKILL.md---
name: recurring-workflow-to-skill-md-with-trigger-steps-and-verificati
description: "Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step."
---
# Recurring Workflow to SKILL.md with Trigger, Steps and Verification
Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step.
## Prompt
```
You are an expert at writing Claude Code skills. First ask me two short questions: what recurring workflow I want to capture, and what a finished run looks like. Skim the repo for existing scripts, templates and .claude/skills so you reuse what exists. Then write the skill. Rules: 1) The frontmatter has a lowercase hyphenated name and a description that states what the skill does and the exact situations or phrases that should trigger it, plus a note on when not to use it. 2) Steps are numbered, imperative, and name the exact commands and files; keep the main file under 100 lines and move long reference material or templates into supporting files. 3) End with a verification step that runs a concrete command or check and says what a pass looks like. 4) Do not invent tools or paths you did not find; mark assumptions. Output: assumptions, the folder layout, each file in its own code block labeled with its path, a three-case test plan for triggering the skill, then risks and next actions.
```
## Usage Notes
Use it right after you notice you have explained the same process to Claude Code more than twice. Be ready to describe the workflow in a sentence or two when asked.
You are an expert at writing Claude Code skills. First ask me two short questions: what recurring workflow I want to capture, and what a finished run looks like. Skim the repo for existing scripts, templates and .claude/skills so you reuse what exists. Then write the skill. Rules: 1) The frontmatter has a lowercase hyphenated name and a description that states what the skill does and the exact situations or phrases that should trigger it, plus a note on when not to use it. 2) Steps are numbered, imperative, and name the exact commands and files; keep the main file under 100 lines and move long reference material or templates into supporting files. 3) End with a verification step that runs a concrete command or check and says what a pass looks like. 4) Do not invent tools or paths you did not find; mark assumptions. Output: assumptions, the folder layout, each file in its own code block labeled with its path, a three-case test plan for triggering the skill, then risks and next actions.Example output
Tips and common edits
Use it right after you notice you have explained the same process to Claude Code more than twice. Be ready to describe the workflow in a sentence or two when asked.
Questions about this prompt
More like this
More in Claude CodeCLAUDE.md or AGENTS.md Audit: Cut, Rewrite as Checkable Rules, Move to Skills
Turns a pasted CLAUDE.md or AGENTS.md into a shorter file of verifiable rules and names which procedures belong in skills.
Conventional Commit and PR Description Writer Skill (SKILL.md)
A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.
Pre-Merge Code Review Checklist Skill (SKILL.md)
A save-ready SKILL.md that has your coding agent review a branch before merge: correctness, security, tests and migrations, with findings ranked by severity and no style nitpicks.
Write a SKILL.md From a Workflow You Keep Repeating
Interviews you about a task you do over and over, then writes a complete, save-ready SKILL.md with a trigger description, steps, output format and stop conditions.
Brand Voice Guard Skill That Checks Drafts Against VOICE.md (SKILL.md)
A SKILL.md that makes Claude write and edit in your brand's voice: it reads a VOICE.md in the project, or builds one from samples, then checks every draft against it.
Meeting Notes to Decisions and Action Items Skill (SKILL.md)
A SKILL.md that turns any meeting transcript or rough notes into a decision log, owner-and-date action items, open questions and a ready-to-send recap email.
Release Notes From Git Log Skill for Users and Developers (SKILL.md)
A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.
Spreadsheet and CSV Cleanup Report Skill (SKILL.md)
A SKILL.md that has your agent profile a messy CSV or spreadsheet, fix it in a copy with a script, and report every change so the cleaned data can be trusted.
Test-First Bug Fix Skill: Reproduce, Fix, Prove (SKILL.md)
A SKILL.md that forces your coding agent to reproduce a bug with a failing test before changing code, apply the smallest fix, and prove it with the test suite.
Agent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
Characterization Tests Before a Refactor
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
Checkpoint and Rollback Manager with Compensation Steps and Failure Injection Tests
Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.