deploy
/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.
- Author
- hamzafer ↗
- Repository
- claude-routines ↗
- Licence
- MIT
- Last repository change
- 18.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Triggers from the description
Original author description
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.
How it works
- Procedure
- Pre-deploy nudges
- Snippet expansion happens in create/update
- See also
SKILL.md preview
---
name: deploy
description: 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.
---
# claude-routines:deploy
Smart router. Reads the file, decides if it needs `create` or `update`, then delegates.
## Procedure
1. Read the routine file at `<file>`.
2. Parse its YAML frontmatter.
3. If `trigger_id` is present in frontmatter -> use the `update` skill with `<file>`.
4. If `trigger_id` is absent -> use the `create` skill 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 rules
- `dry-run deploy <file>` to see the exact API body
- `diff <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
- `create` for the create-side mechanics
- `update` for the update-side mechanics (especially read-modify-write)
- `bulk` for "deploy all" or "deploy everything in <dir>"
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · hamzafer/claude-routines | 90 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| microsoft/power-platform-skills | 100 | MIT |
| friendlyinternet/nuxt-crouton | 100 | MIT |
| wraith-proxy/wraith-skills | 100 | MIT |
| jikig-ai/soleur | 100 | Apache-2.0 |
| curiositech/windags-skills | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version c9efe2317744 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100create
Create a new Claude Code routine from a local .md file. Invoke when the user says "create <file>" or when called as a sub-skill of deploy. The file's frontmatter must NOT contain a trigger_id. - 100get
Fetch a single Claude Code routine by its trigger_id and write it to a local .md file. Invoke when the user says "get <trigger_id>" or asks to download/inspect one specific routine from the cloud. - 100do-deploy
Deploy popoto: run tests, bump version, tag release, publish to PyPI, deploy docs. Triggered by 'deploy', 'do-deploy', or any request to publish a new version. - 95commit-push-deploy
Commit, push, then deploy only if allowlisted infra already exists. Use for /commit-push-deploy, "commit push deploy", "deploy this". Must push. Never force-push. Never invent infra. - 100vercel-deploy
Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\". - 100vercel-deploy
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".