Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, well-structured procedural skill: an explicit 8-step workflow with genuine human-in-the-loop checkpoints (draft approval before filing, ask-and-wait on ambiguity), lean prose that assumes competence, and clean one-level-deep references to the ticket-writing doc and sibling skills. The only gap is that issue-creation mechanics and draft format live entirely in the referenced doc, leaving minor executable detail out of the body. No bundle files (references/, scripts/, assets/) exist in this skill to further disclose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~48-line body is lean: terse numbered steps and rules with zero concept explanations, no padding, and no background Claude already knows (e.g. it never explains what Linear or an issue tracker is). Every token carries instruction — matching anchor 5's 'every token earns its place' rather than anchor 4's 'minor instances of over-explanation'. | 5 / 5 |
Actionability | Mostly executable guidance: a copy-paste-ready lookup command ("tessl api /v1/orgs/<org id>/integrations/linear/routes"), the exact env var (LINEAR_API_KEY), concrete state names (Todo, Backlog), per-case filing branches (no blockers / with blockers / park), and stop-work instructions. Minor gaps remain — the actual issue-creation call syntax and a sample issue draft are not shown, only delegated to the referenced ticket-writing doc — so it sits at anchor 4 ('minor gaps') rather than anchor 5's fully copy-paste-ready coverage. | 4 / 5 |
Workflow Clarity | The 8-step sequence is clearly ordered with explicit checkpoints and feedback loops: "Show the drafts and wait for the person's yes" before any batch write, "With neither, ask the person... and wait", "When more than one team fits, ask which", and error recovery in the rules ("When a call is refused, do not work around it: ask the person"). Because a validation checkpoint exists before filing, the batch-operation cap does not apply, and the content matches anchor 5. | 5 / 5 |
Progressive Disclosure | The body is a well-organized overview (Steps, Rules) with clearly signaled, one-level-deep references — [Writing a ticket for the factory](../../docs/writing-factory-tickets.md), [Regional setup](../factory-setup/references/region.md), and the create-github-issue skill link — and no bundle files of its own to inline. This matches anchor 5's clean overview-plus-clear-references pattern; there is no nesting, burying, or inlined bulk content that would justify anchor 4. | 5 / 5 |
Total | 19 / 20 Passed |