Name: ork-implement
Author: yonatangross

Imported from yonatangross/orchestkit (plugins/ork-codex/skills/ork-implement/SKILL.md). Install upstream with npx skills add yonatangross/orchestkit --skill ork-implement. Copyright stays with the author.

Ork Implement

Implement only the agreed scope. Read repository instructions first and use an isolated worktree whenever a shared primary checkout may be active.

Before writing against an unfamiliar third-party API, confirm its current surface through the context7 MCP server (call resolve-library-id, then query-docs) rather than recalling it.

Keep the diff small. Add focused tests when behavior changes, and report the exact verification output. Do not self-certify a high-impact change: request $ork-verify (or ork_verifier when installed) after implementation.

Prefer ork_implementer when installed; otherwise implement in this context. Delegate only independent, bounded units; keep integration in one place.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install ork-implement and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "yonatangross-orchestkit-ork-implement", "kind": "skill", "name": "ork-implement", "description": "Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches.", "publisher": "yonatangross", "version": "1.0.0", "capabilities": { "domains": [ "math" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/yonatangross/orchestkit", "path": "plugins/ork-codex/skills/ork-implement/SKILL.md", "ref": "HEAD", "url": "https://github.com/yonatangross/orchestkit/blob/HEAD/plugins/ork-codex/skills/ork-implement/SKILL.md", "key": "yonatangross/orchestkit/plugins/ork-codex/skills/ork-implement/SKILL.md" } }, "instructions": "# Ork Implement\n\nImplement only the agreed scope. Read repository instructions first and use an isolated worktree whenever a shared primary checkout may be active.\n\nBefore writing against an unfamiliar third-party API, confirm its current surface through the context7 MCP server (call `resolve-library-id`, then `query-docs`) rather than recalling it.\n\nKeep the diff small. Add focused tests when behavior changes, and report the exact verification output. Do not self-certify a high-impact change: request `$ork-verify` (or `ork_verifier` when installed) after implementation.\n\nPrefer `ork_implement", "cost": { "context_tokens": 182 } }

ork-implement

About

Ork Implement

Use it

Install ork-implement and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews