implement SKILL.md skillA
implement from trevhud/rote is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add trevhud/rote/implement@git:20261019.2704951Pins git:20261019.2704951 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- trevhud/rote
- Path
plugin/skills/implement/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261019.2704951, committed Oct 19, 2026
- First version recorded
- Oct 19, 2026
- Size
- 13,432 bytes
- Repository stars
- 8
- License
- Apache-2.0
Fill in the stub modules of a pipeline emitted by rote, so it actually runs. Use after `rote emit` or `rote compile` when the emitted app still has extracted/* stubs that raise a "[rote stub]" error or a bare NotImplementedError, or when the user says "implement the stubs", "fill in the extracted modules", "make the compiled pipeline run", "wire up the real API calls", or `rote run` fails on a stub. Reads each node's IR contract (inputs, declared output keys, constants, description, source…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Implement the stubs of an emitted pipeline `rote emit` and `rote compile` produce a runnable app whose deterministic steps are scaffolds: every `pure_function` and `external_call` node that has no real implementation yet gets a stub that fails on call. Your job is to replace those stubs with working code that honors each node's IR contract, then prove the pipeline runs end to end with `rote run`. You write code only in user-owned files. rote owns everything else and regenerates it on the next emit. The CLI ships on PyPI as `rote-cli`. Invoke it as `uvx --from rote-cli rote <args>`, which works on every release (the `uvx rote-cli` shorthand needs a release newer than 0.14.0). Running a Python app needs that runtime's extra in the same environment, because `rote run` executes it with its own interpreter: `uvx --from 'rote-cli[dbos]' rote run ...` for DBOS, `'rote-cli[temporal]'` for Temporal. If the user is inside a rote checkout with a `.venv`, `.venv/bin/rote` works too. ## 1. Locate the emitted dir and its IR The user names the directory, or it is the most recent `--out` in the conversation. Accept any of: …
Read the whole file at its exact version.
How to install
mdr add trevhud/rote/implement@sha256:50f6058a0308b214The line at the top of this page pins the label git:20261019.2704951, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_l5czxed6jtdclpoj)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, all committed on Oct 19, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.2704951 latest | 2026-10-19 | 2704951 | 13,432 B | A | view · diff |
| git:20261019.249ece1 | 2026-10-19 | 249ece1 | 13,067 B | A | view · diff |
| git:20261019.812ab6a | 2026-10-19 | 812ab6a | 12,807 B | A | view · diff |
| git:20261019.9d62bcb | 2026-10-19 | 9d62bcb | 12,650 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13432 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
trevhud/rote · 8 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l5czxed6jtdclpoj GET https://markdownregistry.com/api/v1/resolve?ref=trevhud/rote/implement GET https://markdownregistry.com/api/v1/blob/50f6058a0308b2143037e4f2611549239dd0943512fe688ac810d0139c162ec5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.