get
/get
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.
- 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
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.
Triggers from the description
Original author description
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.
How it works
- Procedure
- File format
- Pull caveat
- Common errors
- See also
SKILL.md preview
---
name: get
description: 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.
---
# claude-routines:get
Fetch one routine and write it as a local `.md` file the user can edit.
## Procedure
1. Call `RemoteTrigger` with `action: "get"` and `trigger_id: <id>`.
2. Strip read-only fields from the response: `id`, `created_at`, `updated_at`, `next_run_at`, `creator`, `ended_reason`, `api_token_hint`, `persist_session`, `last_fired_at`, `enabled_plugins`, `extra_marketplaces`, and `job_config.ccr.session_context.outcomes`.
3. Build YAML frontmatter from the remaining fields: `trigger_id`, `name`, `cron` (or `run_once_at`), `enabled`, `env_id` (from `job_config.ccr.environment_id`), `allowed_tools` (from `job_config.ccr.session_context.allowed_tools`), optional `model` (from `job_config.ccr.session_context.model` if present), optional `sources` (from `job_config.ccr.session_context.sources` if present), optional `mcp_connections`.
4. The prompt body comes from `job_config.ccr.events[0].data.message.content`.
5. Derive a kebab-case slug from `name`. Write to `routines/<slug>.md` (or wherever the user prefers; default `routines/`).
## File format
```yaml
---
trigger_id: trig_01ABC...
name: "Morning Brain Digest"
cron: "0 7 * * *"
enabled: true
env_id: env_01...
allowed_tools: [Bash, Read, Write, Edit, WebFetch]
model: claude-opus-4-7
---
(prompt body verbatim)
```
## Pull caveat
If you fetched the body of a routine that originally used `{{include <path>}}` directives, the cloud has the FULLY EXPANDED body. The `get` skill writes that expanded body verbatim. The user accepts that pull-after-deploy loses snippet references; this is by design.
## Common errors
- HTTP 404: the `trigger_id` doesn't exist. Maybe it was deleted via the web UI. Suggest `list` to confirm.
## See also
- `pull` for fetching all routines at once
- `list` to find a `trigger_id` if the user only knows the routine's name
Versions
The database has no other skills named get.
Database snapshot: 13.11.2026 · package version 3a0dc0b68f35 (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
- 90pull
Fetch all Claude Code routines from the cloud and write each one to a local .md file. Invoke when the user says "pull", "pull all", "sync from cloud", or asks to download everything to local files. - 90deploy
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. - 90get-task
Get details of a specific task by ID or name. Use when the user wants to view or look up a task. - 100code-mate-claude-code
Run Claude Code non-interactively for coding tasks. Use when the user asks to delegate work to Claude Code. - 90routine-memory
Carry state between runs of a scheduled routine using Hindsight memory. Use when creating or editing a routine, to write the recall and retain steps into the routine's own instructions, and at the start and end of every scheduled or event-triggered routine run. - 100routine
Routine — repeated bundles of Practices. Use when the user invokes /routine, wants recurring agent behavior, asks to compose Practices on a trigger, or when Otto should mine/propose a Routine from repeated work. Recurring activation belongs to the human.