fan-out

Route work that crosses repositories by opening a labelled `factory` issue in each repository that must follow an upstream change, such as a new perihelion-protos release. Use as the action for a tag `push` trigger in perihelion-protos, or when an issue's work belongs in other repositories.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 exemplary lean skill body: precise steps, real commands, explicit dedupe/skip validation for a batch operation, and clear guardrails. The only improvement space is supplying the exact commands for the tag-diff comparison and issue creation, and a brief note on handling gh failures.

Suggestions

Add the concrete command for step 1's tag comparison (e.g. the git diff between the two tags) and the gh issue create invocation with title and body.

Add a brief failure-handling note for gh commands (e.g. what to do if search or issue creation fails or is rate-limited).

Dimension	Reasoning	Score
Conciseness	The ~26-line body is lean and every token earns its place: it opens with non-obvious domain knowledge ('A run only works in the repository whose event started it'), includes no padding, and explains nothing Claude already knows, matching anchor 5.	5 / 5
Actionability	Mostly executable guidance: a copy-paste-ready command ('gh search code --owner perihelionhq --filename demo.proto'), an exact issue title template, and concrete file paths. Minor gaps — no command for the tag-to-tag comparison in step 1 and no gh issue create invocation — keep it at anchor 4 rather than 5.	4 / 5
Workflow Clarity	A clear five-step sequence with explicit checkpoints for the batch operation: skip repositories already at the tag, check for existing issues before opening, a dedupe guard in 'Do not', and a final report step listing issues opened and skipped with reasons. It sits at anchor 4 rather than 5 because there is no error-recovery guidance if a gh command fails; the validation checkpoints are present, so the batch-operation cap at 3 does not apply.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references (no references/, scripts/, or assets/ files exist), and its sections (Inputs, Procedure, Do not) are cleanly organized, so it qualifies for anchor 5 under the rubric's simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

82%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 strong description: it explicitly states both what the skill does and when to use it, in a highly distinctive niche vocabulary. Its only weakness is that it describes a single routing action rather than enumerating several concrete actions, and it misses a few natural synonyms a user might say.

Suggestions

Enumerate the concrete sub-actions briefly (compare tags, find consumers via gh search code, open labelled issues) to raise specificity.

Add one or two natural synonyms users might say, such as 'fan out' or 'propagate an upstream release to dependent repos'.

Dimension	Reasoning	Score
Specificity	The description names the domain (cross-repository routing) and one precise concrete action — 'opening a labelled `factory` issue in each repository that must follow an upstream change' — but lists only one or two actions rather than several, matching anchor 3 rather than 4.	3 / 5
Completeness	Both what ('Route work that crosses repositories by opening a labelled `factory` issue in each repository') and when ('Use as the action for a tag `push` trigger in perihelion-protos, or when an issue's work belongs in other repositories') are answered explicitly with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('work that crosses repositories', 'tag `push` trigger', "when an issue's work belongs in other repositories") with good coverage of the realistic invocation contexts, but a few natural synonyms (e.g. 'fan out', 'propagate') are missing, so it fits anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The description occupies a clear niche — labelled `factory` issues for perihelion-protos release fan-out — with distinct trigger conditions and minimal overlap with any generic skill, matching anchor 5.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: perihelionhq/perihelion-platform-context
Path: plugins/canonical-workflow/skills/fan-out/SKILL.md
Commit: caafac3

Reviewed: 19 hours ago

Table of Contents

Discovery Implementation Validation

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.