CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orchestrate

Use when driving one or more tasks end to end from the local bare repo's `main` worktree — a feature designed with the user first when its scope is open, or a ready list of tasks — ordering them, cutting a worktree per task, handing each to a subagent that runs new-feat, running prep-pr with every finding fixed rather than reported, and shepherding each pull request to a squash merge and worktree teardown. Also the route for a request to review and fix an open pull request another tool or session wrote, through review-pr. Not for a one-file change, and not outside the bare repo.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, well-sequenced orchestration procedure with validation and recovery paths for every failure mode. Its weaknesses are length — rationale prose and time-sensitive statistics mixed into the instructions — and a monolithic body that keeps procedures the main loop rarely needs (stack merging, workflow stage splitting) inline instead of in reference files.

Suggestions

Move the self-contained sub-procedures — "A frontend stack", the Workflow stage-splitting stages, "Adopting an open pull request", and "Every wait ends" — into files under references/ (like gotchas.md) and keep one-line pointers plus the triggering condition in SKILL.md.

Cut the rationale narratives and repo statistics (e.g. "64% of this repository's recorded token spend", "85.8% of subagent spend today") or move them to a metrics reference; they are time-sensitive and do not change what the agent does.

State the load-bearing rules (TASK-BRANCH marker, premise checks, wait terminal states) as terse imperative checklists at each step, leaving the why to at most one clause, to cut token cost without losing actionability.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and most of its length is genuine operational detail, but there is noticeable fat: rationale prose ("what survives a compaction is what was written down, not what you were holding in context"), time-sensitive repo statistics outside any deprecated section ("64% of this repository's recorded token spend currently sits in that anonymous HEAD pool", "It is 85.8% of subagent spend today"), and long narrative passages that could be cut to imperative rules. Mostly efficient with tightening needed fits 3; it is above 2 because the verbosity is occasional digression, not pervasive padding.

3 / 5

Actionability

Fully executable throughout: exact commands with expected outputs (the precondition checks, the fetch refspec, `bun install --frozen-lockfile`), precise `gh api` calls with `--jq` filters, marker formats (`TASK-BRANCH: <branch>`, `CLAIMED: <repo>#<n>`), wait-script exit codes, and a `test -e` check on every named path. This is copy-paste-ready guidance covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Steps 00, 0, and 1–5 are explicitly sequenced with validation checkpoints everywhere: precondition commands with expected outputs, premise verification before every brief, mechanical checks before trusting a subagent's report, the CI-started count check, and terminal states plus deadlines for every wait. Each failure mode (red check, DIRTY, BEHIND, flake, dead subagent, blocked CI) has an explicit recovery path — a clear match to the 5 anchor's feedback loops and checklists.

5 / 5

Progressive Disclosure

The step structure is clear and the one bundle reference is real and well signaled ("The full table, with the reason behind each, is `references/gotchas.md`" — top six inline, full table in the file, one level deep). But the ~540-line body inlines several large, self-contained subsections — "A frontend stack", the Workflow stage-splitting procedure, "Adopting an open pull request", "Every wait ends" — that belong in reference files like gotchas.md, which is the anchor-3 pattern of content that should be separate staying inline; it reaches 4 only if most content is appropriately placed, which it is not.

3 / 5

Total

16

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, highly specific description that answers both what and when with concrete triggers and useful negative boundaries. Its only weaknesses are heavy reliance on repo-internal jargon for triggers and direct overlap with the review-pr skill's trigger phrase.

DimensionReasoningScore

Specificity

The description enumerates the full workflow concretely: "ordering them, cutting a worktree per task, handing each to a subagent that runs new-feat, running prep-pr with every finding fixed rather than reported, and shepherding each pull request to a squash merge and worktree teardown", plus the review-and-fix route "through review-pr". Coverage is comprehensive rather than having minor gaps, so it matches the 5 anchor, not 4.

5 / 5

Completeness

It explicitly answers when ("Use when driving one or more tasks end to end... a feature... or a ready list of tasks") and what (the ordering/worktree/subagent/prep-pr/merge/teardown chain), and adds negative triggers ("Not for a one-file change, and not outside the bare repo"). This clearly matches the 5 anchor with concrete trigger phrases; 4 would require the when to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present ("driving one or more tasks end to end", "review and fix an open pull request", "a ready list of tasks"), but it leans on internal jargon (bare repo, worktree, `new-feat`, `prep-pr`) and misses common synonyms like "orchestrate", "backlog", or "work through the task list". Good coverage with a few natural terms missing fits 4; it is above 3 (relevant natural phrases exist) but below 5 (no synonym variation).

4 / 5

Distinctiveness Conflict Risk

A clear niche (end-to-end orchestration from the local bare repo's `main` worktree) with explicit exclusions, but "the route for a request to review and fix an open pull request another tool or session wrote, through review-pr" overlaps with the `review-pr` skill itself, which it names. Mostly distinct with minor overlap risk against a closely related skill fits 4; the explicit boundaries keep it above 3.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (546 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 3 possibly missing (scripts/queue-sim.sh, scripts/review-scope.ts, scripts/wait-pr.sh)

Warning

Total

14

/

16

Passed

Repository

englishstreetventures/osn

Path

.claude/skills/orchestrate/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.