CtrlK
BlogDocsLog inGet started
Tessl Logo

guide-authoring

Authoring OR reviewing a learn/ guide (learn/benefits/*.md, learn/agentos/*.md). Enforces the grounding discipline (memory-mine + use-the-subsystem's-tools before writing), the rich-narrative + benefits + lived-voice content bar, render-verified TD Mermaid, conceptual-vs-reference separation, the never-hand-edit-generated-files rule, and a no-rubber-stamp reviewer gate.

69

Quality

83%

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 is an exemplar pointer skill — lean, concrete, and unambiguous — that defers all substantive detail to a single well-signaled reference file that is present in the bundle.

DimensionReasoningScore

Conciseness

The body is a lean pointer: a single concrete instruction plus a terse rationale; it does not explain concepts Claude already knows and every line earns its place, matching the lean/efficient anchor.

3 / 3

Actionability

Gives a concrete, executable instruction — 'use the view_file tool to read ... guide-authoring-bar.md before writing the first sentence or posting a review verdict' — with a specific tool, exact path, and explicit timing.

3 / 3

Workflow Clarity

For this simple pointer skill the single action (trigger -> read and adhere to the bar file before acting) is unambiguous, which the simple-skills note allows to score 3; the reviewer-gate validation concept is also flagged.

3 / 3

Progressive Disclosure

Textbook one-level-deep disclosure: a concise overview body signaling a single detailed reference (guide-authoring-bar.md) that exists in the bundle, with easy navigation and no nested references.

3 / 3

Total

12

/

12

Passed

Description

67%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 and well-scoped to learn/ guide authoring/reviewing, but leans heavily on internal jargon and lacks an explicit natural 'Use when...' trigger, capping its trigger-term quality and completeness.

Suggestions

Add an explicit natural 'Use when...' trigger clause (e.g., 'Use when writing or reviewing a learn/ guide') to lift completeness and trigger clarity.

Replace internal jargon ('lived-voice content bar', 'no-rubber-stamp reviewer gate') in the description with natural terms a user would actually say.

Include common natural variations ('write a guide', 'review a guide', 'documentation') alongside the path globs to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions/bar it enforces — 'grounding discipline (memory-mine + use-the-subsystem's-tools)', 'render-verified TD Mermaid', 'conceptual-vs-reference separation', 'never-hand-edit-generated-files rule', 'no-rubber-stamp reviewer gate' — matching the anchor for listing several specific actions.

3 / 3

Completeness

Clearly answers WHAT (the disciplines it enforces) and states a trigger condition ('Authoring OR reviewing a learn/ guide'), but lacks an explicit 'Use when...' clause and the trigger is phrased as a gerund headline wrapped in jargon rather than a crisp natural trigger, so it does not reach the anchor-3 bar.

2 / 3

Trigger Term Quality

Contains some natural terms ('Authoring OR reviewing a learn/ guide', 'guide', 'learn/benefits') but is dominated by internal jargon ('lived-voice content bar', 'no-rubber-stamp reviewer gate', 'render-verified TD Mermaid') a user would not naturally say, missing common variations like 'write a guide' or 'documentation'.

2 / 3

Distinctiveness Conflict Risk

Scoped tightly to 'learn/ guides' with explicit file globs (learn/benefits/*.md, learn/agentos/*.md), giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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.