Create a project skill at .claude/skills/[skill-name]/SKILL.md for [the chore]. Frontmatter: name, a description that says when to use it, argument-hint, and disable-model-invocation: true so it only runs when I type /[skill-name]. Body: the steps as a numbered list ([steps]), the rules ([rules]), and a final step that shows me a summary of what changed and stops before any commit or deploy. Use $ARGUMENTS for the week's date. Keep it under 40 lines and show it to me before saving.
Build your first Claude Code skill for a repeated task
You ask the coding agent to do the same chore every week and keep retyping the same instructions.
- Claude Code
- Grok Build
For: Tech person, Owner · Updated October 25, 2026
A starting point: fill in the [brackets] with your own details, and check the answer before you use it. Tool screens change often, so yours may look a little different.
Video walkthrough
Video coming later: One Skill, Four Agents: Teach a Weekly Chore Once (P3-04). Until then, watch the free episodes that are out now.
The prompts
Copy the version for the tool you use, then replace every [bracket].
/skills (Confirm [skill-name] is listed, then run it:) /[skill-name] [week date]
Fill in these [brackets]
| Bracket | What to put there |
|---|---|
[skill-name] | Lowercase with hyphens. It becomes the slash command. e.g. weekly-specials |
[the chore] | e.g. update specials.html from specials.csv every Monday |
[steps] | The exact steps you'd tell a new hire. |
[rules] | e.g. keep the page layout, prices with two decimals, max 6 items, no deploy |
Docs note (checked Oct 17, 2026): Claude Code skills are folders with a SKILL.md: YAML frontmatter (description recommended) plus Markdown instructions. Project skills live in .claude/skills/<name>/SKILL.md; personal ones in ~/.claude/skills/. You run one with /name, and disable-model-invocation: true stops Claude from triggering it on its own. Claude Code skills follow the Agent Skills open standard. Grok Build’s docs say it reads Claude Code skills automatically.
Real example (Claude, free plan, tested Oct 25, 2026, drafted in a web chat as a stand-in for Claude Code):
--- name: weekly-specials description: Update the weekly specials page on the Lantern Row Kitchen website from specials.csv. Use when the user wants to publish a new week's specials. disable-model-invocation: true --- **Steps** 1. Read `specials.csv` and find the rows for the week of $ARGUMENTS. 4. Check that the built specials page shows exactly the items in the CSV for that week: no extras, none missing, and prices that match. 5. Show me a summary of what changed (items added, removed, or edited, and any price changes), then stop. Do not commit or deploy. **Rules** - Never change prices that aren't in the CSV. - If no rows match $ARGUMENTS, stop and tell me rather than guessing a week.A few things I added beyond your spec, so you can cut them if you’d rather not have them:
Answer given with our fictional inputs (Lantern Row Kitchen, a made-up restaurant). Excerpt trimmed; “…” marks cuts. AI answers vary, so yours will be different. Check it before you use it.
Watch for: It added rules you didn’t ask for (and said so). Keep only the ones you want, and test the skill once before you rely on it. Some lines are cut from this excerpt.
Check before you send
- The description says when to use it in words you'd actually type
- disable-model-invocation: true on anything that edits files on a schedule
- The last step stops for your review; no commit or deploy inside the skill
- You ran it once on a test branch and checked the page
Privacy note: what not to paste
Skills get committed with your project. No passwords, API keys, or customer data inside SKILL.md.