Open Terminal and Start Claude Code
Open a terminal in the trusted skills repository and start Claude Code there. Confirm the current path, visible skills, pending Git changes, and permissions before asking it to create anything.
Use Claude Code inside a local skills repository to generate a task-specific skill, inspect and validate the files it creates, then test the skill on representative input and improve the reusable instructions.


Source episode · 18:37
Claude Skills Explained: My Workflow for Creating Reusable AI Agents with Cursor and Claude Codewith Claire Vo
Claire starts Claude Code inside her local skills folder, invokes the create-skill skill to build a changelog-to-newsletter skill, runs its validator, and tests it with an actual changelog.
A task-specific Claude skill that Claude Code can discover, validate, and apply consistently to representative inputs.
Anthropic AI assistant
Claude for coding tasks
Step by step
Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.
4 steps
Open a terminal in the trusted skills repository and start Claude Code there. Confirm the current path, visible skills, pending Git changes, and permissions before asking it to create anything.
Invoke the create-skill skill with one recurring task. Supply the real input shape, output format, tone or policy constraints, and examples that show when the skill should and should not run.
Use the create-skill skill to create [skill-name] for [recurring task]. Inputs look like: [representative input]. Produce: [exact output]. Follow: [constraints]. Trigger on: [matching examples]. Do not trigger on: [non-matching examples].
Review the proposed folder and diff before running scripts. Check the metadata, instructions, referenced files, trigger description, output contract, and read-only validation behavior.
Show the generated file tree and summarize the purpose of each file. Run only the read-only validation checks defined in the trusted create-skill folder. Report warnings and do not modify unrelated files.
Test the new skill with representative input in a fresh turn, then try an ambiguous input and an unrelated request. Move recurring corrections into the skill and keep the improved example with it.
Here is the latest [input type]: [input] Apply the appropriate skill. Preserve source facts, follow the required format, and label missing information instead of inventing it.
If the output isn't perfect, you can easily open the `SKILL.md` file for the new skill in a text editor and tweak the instructions to refine the tone, format, or logic.
Turn an idea into a PRD, user stories, and a plan.
After the steps
How to recover when the loop fails and where human judgment helps.
Recover
Keep building

Design a weekly meta-workflow that analyzes your interactions with your AI assistant to make it smarter. This system learns your writing style from edits, suggests new automations for repetitive tasks, and helps you filter valuable AI techniques from hype.

Create a daily AI workflow that summarizes yesterday's meetings, identifies urgent tasks, and proactively learns internal company terms it doesn't understand. This keeps your AI assistant's knowledge current and highly relevant to your work.

Build a recurring AI task that automatically gathers updates from your calendar, Slack, and notes to suggest weekly priorities and prepare you for upcoming meetings. Start every Monday with a clear, comprehensive plan without the manual effort.
Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.