CtrlK
BlogDocsLog inGet started
Tessl Logo

lead-role

Switch into relaxed-planning + dialogue-first mindset when delegated lead role for coordination. Suspends Auto Mode velocity-bias for the duration. Triggers: Use this skill IMMEDIATELY when the user delegates lead with explicit phrases ("you take the lead", "coordinate the team", "lead this phase", "drive the next planning step", "chief-architect" when scope is swarm/substrate/roadmap/multi-ticket), OR when the Mailbox Check Protocol surfaces a valid `lead-role-baton`, OR when you have just authored a substrate-shaped ticket about to enter implementation, OR via direct /lead-role invocation.

80

Quality

100%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body exemplifies progressive disclosure: a minimal overview that defers all detail to a single, well-structured reference file and mandates one concrete payload line. It is concise, actionable, and unambiguous, scoring the top anchor on every dimension.

DimensionReasoningScore

Conciseness

The ~12-line body is lean and assumes Claude's competence, giving only a redirect directive plus a literal first-payload line rather than explaining what lead-role is. It is not level 2 because it contains no unnecessary explanation or padding to tighten.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: a named tool (`view_file`), an exact reference path, an enumeration of artifact types to gate, and a literal string to declare as the first payload line. Not level 2, which would be pseudocode or missing key details.

3 / 3

Workflow Clarity

A single unambiguous directive — read the reference file before producing artifacts, then declare the payload line — which the rubric permits to score 3 for simple single-action skills. No destructive/batch operation lives in the body that would require validation checkpoints, so it is not capped at 2.

3 / 3

Progressive Disclosure

The body is a concise overview pointing to one real, well-organized reference file (lead-role-mode.md, verified present in ./references/) clearly signaled via 'read and strictly adhere to'. It is one level deep with easy navigation, matching the top anchor; not level 2, which leaves content that should be separate inline.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, uses natural trigger language, explicitly states both capability and trigger conditions, and is narrowly scoped to avoid conflicts. Written in third person with no fluff, it hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions/conditions — 'Switch into relaxed-planning + dialogue-first mindset', 'Suspend Auto Mode velocity-bias for the duration' — rather than vague language. It is not the level below because it goes well beyond naming a single domain and a couple of actions.

3 / 3

Completeness

Clearly answers both 'what' (switch to planning/dialogue mindset, suspend velocity bias) and 'when' via an explicit 'Triggers:' clause with multiple named conditions. It meets the anchor for explicit triggers rather than only implying when (level 2).

3 / 3

Trigger Term Quality

Includes natural phrasings a user would actually say — 'you take the lead', 'coordinate the team', 'lead this phase', 'drive the next planning step', 'chief-architect' — plus a baton and invocation path. Good coverage of natural terms; not the level below, which only has some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Distinct niche (lead-role coordination handoff) with specific trigger phrases and a baton/invocation path unlikely to fire for unrelated skills. Not level 2, which still overlaps with similar skills — these triggers are narrowly scoped to a lead delegation event.

3 / 3

Total

12

/

12

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.