CtrlK
BlogDocsLog inGet started
Tessl Logo

rate-complexity

Use when an issue needs its complexity declared — proposing a rating from the issue body alone and getting the owner to confirm or amend it, or backfilling a rating onto an existing unrated issue. Invoked by new-feat at issue-creation time; also the backfill path for issues opened before the label existed.

71

Quality

86%

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

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.

Excellent actionability and structure: executable gh commands for every path, a clear two-mode workflow with confirmation and pre-filter checkpoints, and clean single-file organization. The only trimmable fat is the rationale section's editorializing, and the batch backfill mode would benefit from a post-apply verification step.

Suggestions

Tighten the 'Why the timing is the whole point' section — the contamination argument can be stated in 2–3 sentences without the motivated-reasoning aside, saving ~10 lines.

Add a post-apply verification step to Mode B's batch pass (e.g., re-run the gh issue list filter after labeling to confirm no unrated issues remain), closing the workflow's one validation gap.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no generic-knowledge padding, every command shown once — but the 'Why the timing is the whole point' rationale and asides like 'That is motivated reasoning' could be tightened further. Not 5 because a few sentences of editorializing do not strictly earn their place; not 3 because there is no unnecessary concept explanation.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: 'gh issue edit … --add-label "complexity:3"', the dual-label backfill command, the 'gh issue list … --jq' pre-filter for unrated issues, and the exclusion query. Mode A steps are concrete down to 'one sentence of justification naming the rubric row'.

5 / 5

Workflow Clarity

Two clearly sequenced modes with real checkpoints — the owner confirm-or-amend loop in Mode A and the jq label pre-filter in Mode B — plus explicit handling of the unreachable-owner case. Not 5 because the batch backfill pass has no post-apply verification that labels actually landed; not 3 because validation is present (pre-filter, confirmation loop, unconfirmed marker), not absent.

4 / 5

Progressive Disclosure

A self-contained single-file skill with well-organized sections (rationale, rubric, Mode A, Mode B, labels, consumers); nothing that belongs in a separate file is inlined, and the external pointers ('wiki/conventions/session-metrics.md', '@tools/pr-metrics') are one level deep and clearly contextualized as consumers rather than nested references.

5 / 5

Total

18

/

20

Passed

Description

87%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 with an explicit 'Use when…' trigger clause, concrete actions, and a distinct niche. Its only weakness is that it never mentions the Fibonacci scale, the actual labels, or the repos involved, which slightly limits keyword coverage and specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'proposing a rating from the issue body alone', 'getting the owner to confirm or amend it', 'backfilling a rating onto an existing unrated issue' — but the rating scale (1/2/3/5/8) and the label mechanism are never stated, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both: the what (propose a rating from the issue body, get owner confirmation, or backfill an unrated issue) and the when ('Use when an issue needs its complexity declared', plus concrete invocation contexts — issue-creation time and pre-label issues). Not 4 because the when clause is explicit and scenario-specific rather than merely present.

5 / 5

Trigger Term Quality

Natural keywords like 'complexity', 'rating', 'unrated', and 'backfill' are present and would be said by a user needing this skill, but common synonyms such as 'difficulty', 'estimate', or 'label' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — declaring issue complexity ratings with owner confirmation — with triggers (complexity declaration, unrated issues, backfill) that are unlikely to fire for any other skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

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
englishstreetventures/osn
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.