CtrlK
BlogDocsLog inGet started
Tessl Logo

peer-role

Switch into evidence-backed convergence-pressure mindset when reviewing a peer's design proposal. Suspends Auto Mode "ack-and-move-on" bias for the duration. Triggers: Use this skill IMMEDIATELY when reviewing an Ideation Sandbox discussion / architectural proposal, an epic shape, a skill shape, a roadmap or milestone proposal, or a `/lead-role` convergence artifact. Do NOT auto-fire on ordinary status broadcasts where the right action is mark-read or "no collision".

70

Quality

85%

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

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 deliberately minimal SKILL.md body that acts as a clean pointer to a single one-level-deep reference, with a copy-paste-ready activation declaration. It is highly token-efficient; the only gaps are the lack of an inline validation checkpoint and reference signaling via plain path rather than a link.

DimensionReasoningScore

Conciseness

Lean and efficient: the body is a ~10-line pointer plus one verbatim required declaration, with no padding and full assumption of Claude's competence.

5 / 5

Actionability

Concrete executable guidance (exact view_file path + copy-paste verbatim declaration line), but the substantive action detail is delegated to the reference file rather than covered inline.

4 / 5

Workflow Clarity

A single unambiguous gate sequence (read reference, then declare, only then draft), but no explicit validation checkpoint for the mode-activation step.

4 / 5

Progressive Disclosure

Appropriate overview-to-detail split with a clearly signaled one-level-deep reference loaded via view_file; the reference is named inline rather than as a clickable markdown link, a minor organization gap.

4 / 5

Total

17

/

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, well-scoped description that clearly states both capability and trigger conditions with an explicit negative boundary to avoid misfiring. Trigger term coverage is good but could add a few more natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Switch into evidence-backed convergence-pressure mindset', 'Suspends Auto Mode "ack-and-move-on" bias') plus a list of concrete trigger targets, with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (convergence-pressure mindset, suspends ack-and-move-on bias) and when ('Use this skill IMMEDIATELY when reviewing...') with concrete trigger phrases and a negative boundary.

5 / 5

Trigger Term Quality

Good coverage of natural terms a user would say ('reviewing a peer's design proposal', 'architectural proposal', 'roadmap or milestone proposal', '/lead-role convergence artifact'), missing a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

Clear niche (peer-role convergence pressure) with distinct triggers and an explicit 'Do NOT auto-fire on ordinary status broadcasts' boundary, giving minimal conflict risk.

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.

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.