Name: ork-assess
Author: yonatangross

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

Ork Assess

State the decision, scope, and criteria before scoring. Choose criteria appropriate to the task—normally correctness, maintainability, security, operability, testability, cost, and reversibility—and omit criteria that have no bearing on the decision.

Collect evidence from the code, repository guidance, tests, or authoritative documentation. For a third-party library, framework, or service, the authoritative source is the context7 MCP server: call resolve-library-id, then query-docs. Separate facts, assumptions, and unknowns. Do not invent numeric precision: use a score only when it makes the comparison clearer, and attach the evidence and confidence to it.

For high-impact choices, ask an independent read-only ork_reviewer or built-in reviewer to challenge the leading conclusion. End with a recommendation, conditions for approval, and concrete follow-up actions. Do not edit the target.

# 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-assess 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-assess", "kind": "skill", "name": "ork-assess", "description": "Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen solution.", "publisher": "yonatangross", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen solution." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/yonatangross/orchestkit", "path": "plugins/ork-codex/skills/ork-assess/SKILL.md", "ref": "HEAD", "url": "https://github.com/yonatangross/orchestkit/blob/HEAD/plugins/ork-codex/skills/ork-assess/SKILL.md", "key": "yonatangross/orchestkit/plugins/ork-codex/skills/ork-assess/SKILL.md" } }, "instructions": "# Ork Assess\n\nState the decision, scope, and criteria before scoring. Choose criteria appropriate to the task—normally correctness, maintainability, security, operability, testability, cost, and reversibility—and omit criteria that have no bearing on the decision.\n\nCollect evidence from the code, repository guidance, tests, or authoritative documentation. For a third-party library, framework, or service, the authoritative source is the context7 MCP server: call `resolve-library-id`, then `query-docs`. Separate facts, assumptions, and unknowns. Do not invent numeric precision: use a score only ", "cost": { "context_tokens": 229 } }

ork-assess

About

Ork Assess

Use it

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

Manifest

Reviews