Deploy
Deploy a Claude Code routine from a local .md file. Routes to create or update based on whether the file's frontmatter has a trigger_id. Invoke when the user says "deploy <file>", "push <file>", "ship <file>", or asks to publish a routine to the cloud.From its SKILL.md
npx -y skills add hamzafer/claude-routines --skill deployAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 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.
SKILL.md
1.4 KB, as published. Nobody here has run it
claude-routines:deploy
Smart router. Reads the file, decides if it needs create or update, then delegates.
Procedure
- Read the routine file at
<file>. - Parse its YAML frontmatter.
- If
trigger_idis present in frontmatter -> use theupdateskill with<file>. - If
trigger_idis absent -> use thecreateskill with<file>.
That's it. Both create and update handle their own snippet expansion, validation, API calls, and result reporting.
Pre-deploy nudges
If the user hasn't validated the file recently, suggest:
validate <file>to lint frontmatter and cron rulesdry-run deploy <file>to see the exact API bodydiff <file>to preview field-by-field changes (UPDATE path only)
Don't block on these. The user can skip them if they're confident.
Snippet expansion happens in create/update
Both downstream skills handle {{include <path>}} expansion. You don't need to expand here; just route.
See also
createfor the create-side mechanicsupdatefor the update-side mechanics (especially read-modify-write)bulkfor "deploy all" or "deploy everything in <dir>"