If you find yourself re-explaining the same deployment process, the same client-report format, or the same code-review checklist at the start of every new project, that's the exact signal a Skill is worth building. Write it once as a Skill, and Claude Code loads it on demand whenever it's relevant — no re-briefing required.
CLAUDE.md is always-on context for one specific project — it loads automatically every session and describes that project's conventions. A Skill is different: it's loaded on demand, and it isn't tied to a single project at all. A "write a client status report" Skill is exactly as useful on client A's project as client B's — it's the workflow that's reusable, not the project-specific detail.
---
name: client-deploy-checklist
description: Use when deploying a finished feature to a client's production site.
---
# Client Deploy Checklist
1. Run the full test suite — do not skip on a "small" change.
2. Check the diff for any leftover console.log or debug code.
3. Confirm the CLAUDE.md "do not touch" list wasn't violated.
4. Deploy, then verify the live URL matches the intended change.
5. Update the client changelog with what shipped and why.The exact frontmatter fields and file-discovery rules can change between Claude Code versions — check your installed version's Skills documentation for the current format. What stays constant is the idea: a short, specific brief for a workflow you'll repeat, written the way you'd brief a freelancer joining partway through a project, not as a generic tutorial.
If every client project on this stack gets deployed to Cloudflare Pages the same way, that deployment process is worth writing as a Skill once — the real commands, the real order of operations, the specific thing that trips people up (like a cache header that needs bumping). Every future project gets the same careful deploy without you re-typing the steps from memory each time.
Agencies that send a recurring client status update can package the real format — what sections it has, what tone it's written in, what data points always need pulling — as a Skill, so producing next month's report starts from the established format instead of reconstructing it from an old email you have to go dig up.
A workflow you'll only do once doesn't need the overhead of a formal Skill file — just do it directly in the conversation. Skills pay off specifically because the setup cost is spread across many future uses; for something genuinely one-off, that math doesn't work out.
Skills, hooks, subagents, and MCP all solve different problems — the free guide covers the fundamentals first if you're still getting oriented.
Get the Free Guide →A Skill is a folder-based instruction pack — a directory containing a SKILL.md file plus optional helper scripts and assets — that Claude Code loads on demand to turn it into a specialist for a specific workflow, rather than re-explaining the same process every time.
CLAUDE.md is always-on context for one project — it loads every session automatically. A Skill is loaded on demand for a specific task and can be shared across multiple projects, since it's not tied to any one codebase.
A clear description of when to use the skill, the steps of the workflow it covers, and any specific conventions or gotchas — written the way you'd brief a competent freelancer joining partway through, not as a generic tutorial.
No — Skills earn their setup cost on workflows you repeat across multiple projects or multiple clients. A one-off task is usually faster handled directly in the conversation.