CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 write-issue on every issue it opens and by new-feat on an unrated issue it picks up; also the backfill path for issues opened before the label existed.

Quality

90%

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

82%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.

A tight, highly actionable instruction skill: executable gh/jq commands, a concrete rating rubric, and clearly sequenced modes with a built-in confirm-or-mark-unconfirmed safety design. The gaps are minor — a missing post-apply verification step in the batch backfill pass and a few rhetorical passages that could be cut.

Suggestions

Add a verification step to Mode B's batch pass (e.g. re-run the listing filter after applying to confirm no issues remain unrated, or spot-check a sample of applied ratings) so the batch operation has an outcome check.

Trim the rhetorical explanations in 'Why the timing is the whole point' — e.g. the 'talked into agreeing with the spend' imagery and the motivated-reasoning aside — down to the bare rules they illustrate.

Signal the trailing 'The labels' and 'What consumes this' sections as reference material (or fold them into a short 'Reference' heading) so the operational core reads as Modes A and B first.

DimensionReasoningScore

Conciseness

Mostly lean and project-specific — the timing rationale, rubric table, and gh commands earn their tokens. Not 5: a few rhetorical passages could be trimmed, e.g. "the number gets talked into agreeing with the spend" and the aside explaining that self-rating is "motivated reasoning", a concept Claude already knows; not 3: no padded sections or teaching of background concepts.

4 / 5

Actionability

Fully executable throughout: copy-paste gh commands with exact label and repo arguments ("gh issue edit 412 --repo englishstreetventures/osn --add-label \"complexity:3,complexity:unconfirmed\""), a jq listing filter for unrated issues, and a concrete Fibonacci rubric with repository-shaped examples per row. Not 4: the commands and decision criteria cover the common cases with no gaps.

5 / 5

Workflow Clarity

Mode A is a numbered sequence with an explicit human checkpoint (owner confirm or amend, with neighbouring values offered) and a defined unattended fallback; Mode B pre-filters to unrated issues and carries the unconfirmed-marker safety design. Not 5: the batch backfill pass has no post-apply verification (e.g. re-checking that labels landed or spot-checking a sample); not 3: checkpoints are present and explicit — the jq select gates the batch and the unconfirmed label makes unattended output separable.

4 / 5

Progressive Disclosure

A single ~110-line file with clean section headers (rubric, Mode A, Mode B, labels, consumers) and no bundle files; everything is load-bearing and easy to navigate. Not 5: it exceeds the under-50-line simple-skill case and the trailing labels/consumer detail could be more clearly signaled as reference material; not 3: no content that clearly belongs in a separate file is inlined and nothing is buried.

4 / 5

Total

17

/

20

Passed

Description

92%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: explicit 'Use when' triggers, concrete third-person actions covering both the interactive and backfill modes, and clear delineation from sibling skills. The only weakness is keyword breadth — it covers its own vocabulary well but omits natural synonyms a user might reach for.

DimensionReasoningScore

Specificity

Concrete third-person actions cover the skill's full scope: "proposing a rating from the issue body alone", "getting the owner to confirm or amend it", and "backfilling a rating onto an existing unrated issue". Not 4: unlike 'minor gaps in coverage', these actions enumerate both modes completely; not lower because nothing is vague or generic.

5 / 5

Completeness

Both halves are explicit: what ("proposing a rating from the issue body alone and getting the owner to confirm or amend it, or backfilling a rating") and when ("Use when an issue needs its complexity declared... backfilling a rating onto an existing unrated issue"). Not 4: the 'when' is not merely present but concrete, naming the exact triggering scenarios.

5 / 5

Trigger Term Quality

Natural terms a user would say are present — "complexity", "rating", "unrated issue", "backfill", "confirm or amend" — plus the invoking skill names. Not 5: common synonyms like "difficulty", "estimate", or "size" are missing; not 3: several genuinely natural phrases appear, not just jargon.

4 / 5

Distinctiveness Conflict Risk

A clear niche — pre-work complexity declaration for issues — with explicit relationships to sibling skills ("Invoked by write-issue on every issue it opens and by new-feat on an unrated issue it picks up"), which removes ambiguity rather than adding conflict. Not 4: overlap risk with issue-related skills is addressed head-on, leaving minimal conflict.

5 / 5

Total

19

/

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

Path

.claude/skills/rate-complexity/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.