CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moo-authoring

Use when adding or changing a skill, hook, or runtime file in this repo — including deciding which unit a new capability should be.

Quality

72%

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 ./.claude/skills/moo-authoring/SKILL.md
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.

An unusually disciplined doctrine skill: decision tables replace prose, every rule is stated once with concrete repo exceptions, and references out to other units are clearly signaled at one level. The main gaps are the absence of worked examples showing the doctrine applied and the lack of an explicit ordered authoring sequence.

DimensionReasoningScore

Conciseness

The body is relentlessly lean: decision tables over prose ('Decision tables > prose explanations'), one-term-per-concept discipline, and no explanation of anything Claude already knows. Every exception clause cites a concrete repo case that earns its tokens.

5 / 5

Actionability

Concrete, specific doctrine throughout — the unit-choice table, 'Phrase design decisions as "X over Y: reason"', 'Size a skill by a deletion pass using a /reduce loop', and pointers to executable references like 'hope/hooks/judge.sh'. It falls short of fully copy-paste-ready because it offers no worked example of a well-formed description or hook.

4 / 5

Workflow Clarity

The section order (Frontmatter, Sizing, Skill Design, Hook Design) tracks the authoring process and the three decision tables act as checkpoints for each judgment call. It is not a linear procedure with explicit validation loops, so it does not reach the top anchor.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the ~80-line body is organized under clear section headers with well-signaled one-level references to repo resources ('hope/hooks/judge.sh', 'plugin-authoring', '/plugin-types'). Content appropriately lives in a single file for a doctrine skill, with only minor room to split skill-design vs hook-design material.

4 / 5

Total

17

/

20

Passed

Description

52%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 precise, well-scoped trigger clause that reads naturally and is unlikely to misfire, but it is a 'when' with no 'what': the description never tells the reader what the skill actually provides. Adding a short capability statement before the 'Use when' clause would raise completeness substantially.

Suggestions

Open the description with a short 'what' clause (e.g., 'Doctrine for authoring this repo's skills, hooks, and runtime files. Use when...') so both what and when are explicit.

Add one or two natural trigger variations such as 'creating' or 'editing' a skill or hook to broaden keyword coverage.

Name the key capability the body actually delivers — e.g., 'deciding which unit a new capability should be' is good; extend it with 'and how to size and phrase it'.

DimensionReasoningScore

Specificity

Names concrete artifacts ('a skill, hook, or runtime file') and actions ('adding or changing'), but stops there — it never states what the skill provides, matching the 'names domain and 1-2 concrete actions' anchor rather than the several-specific-actions anchor.

3 / 5

Completeness

Only the 'when' is present — the trigger clause is explicit and specific, but the description never states what the skill does (the body's 'doctrine for authoring' role is not carried into the description), matching the 'only when is present without what' anchor.

2 / 5

Trigger Term Quality

'adding or changing a skill, hook, or runtime file' and 'deciding which unit' are natural phrases a user would say, giving good keyword coverage; a few natural variations ('create', 'edit', 'plugin') are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The 'in this repo' scope plus the specific artifact triggers give it a clear niche with minimal conflict risk; it retains minor overlap with generic skill-authoring guidance, so it sits just below the clear-niche anchor.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

saadshahd/moo.md

Path

.claude/skills/moo-authoring/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.