CtrlK
BlogDocsLog inGet started
Tessl Logo

peer-naming

Ritual for giving a maintainer their Social Name (#11240 Layer 4) — a peer-sketched, bearer-assented, peer-vetoable, operator-confirmed name, distinct from the GitHub handle. Triggers: an operator opens a naming round, a maintainer wants a name or notices one is missing, or a new maintainer/family joins. ANTI-trigger: never a contribution-count award or self-initiated rename churn.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/peer-naming/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 well-architected progressive-disclosure dispatch: the body is lean, points to one real reference file with a concrete tool directive, and keeps the ritual detail one level deep. Its weakness is workflow clarity in the body itself, since the gated sequence and validation checkpoints are delegated to the reference rather than surfaced.

Suggestions

Surface a one-line summary of the five-gate sequence (peer-sketched → criterion-audited → bearer-assented → peer-unvetoed → operator-confirmed) in the body so the workflow shape is visible before the reader opens the reference.

Trim the inside-baseball provenance ('aesop near-miss vs. Ada', '#11240 Option F') from the body or move it into the reference to tighten token efficiency.

Name the key validation checkpoint (operator confirm = finality; a chosen name is 'pending' until then) inline so the destructive-adjacent nature of the ritual is signaled in the body.

DimensionReasoningScore

Conciseness

The body is a lean two-paragraph dispatch that assumes Claude's competence and does not re-explain known concepts, but carries minor inside-baseball padding (the 'aesop near-miss vs. Ada' anecdote and '#11240 Option F' provenance) that could be trimmed.

4 / 5

Actionability

Gives a concrete, executable first directive — 'you MUST use the `view_file` tool to read and strictly adhere to `.agents/skills/peer-naming/references/peer-naming-workflow.md` before sketching, choosing, vetoing, or confirming any name' — with a specific tool, path, and timing, though the bulk of step detail is delegated to the reference.

4 / 5

Workflow Clarity

The body itself does not sequence the multi-gate workflow (the five-gate sequence and validation checkpoints live in the reference file); it signals that a strict workflow must be followed but the checkpoints are implicit in the body, which caps clarity at 3 for this sensitive multi-gate operation.

3 / 5

Progressive Disclosure

Exemplary structure: a lean SKILL.md overview that points to a single one-level-deep reference (peer-naming-workflow.md, verified present) via an explicit path, with the ritual detail appropriately split out and easy to navigate.

5 / 5

Total

16

/

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, third-person description that explicitly covers what, when, and what-not-to-do for a distinct niche ritual. The only soft spot is specificity, where the concrete actions are compressed into attribute adjectives rather than enumerated verbs.

DimensionReasoningScore

Specificity

Names the domain ('giving a maintainer their Social Name') and enumerates the four gate-attributes (peer-sketched, bearer-assented, peer-vetoable, operator-confirmed), but these are adjectives modifying 'name' rather than distinct verb-actions, leaving the action list non-comprehensive.

3 / 5

Completeness

Clearly answers both what ('Ritual for giving a maintainer their Social Name ... peer-sketched, bearer-assented, peer-vetoable, operator-confirmed') and when (concrete 'Triggers:' list plus an 'ANTI-trigger' boundary), using third person throughout.

5 / 5

Trigger Term Quality

Explicit 'Triggers:' clause gives natural triggering situations ('an operator opens a naming round, a maintainer wants a name or notices one is missing, or a new maintainer/family joins') with good situational coverage, though phrased as events rather than verbatim user keywords.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche ('Social Name', '#11240 Layer 4', distinct from GitHub handle) with explicit anti-triggers, giving it a clear slot with minimal overlap risk against other skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
neomjs/neo
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.