glossary

How to add entries to the glossary

1.22x

Quality

—

Does it follow best practices?

Impact

66%

1.22x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is admirably concise and provides some concrete link syntax, but the guidance is incomplete and the workflow mechanics are underspecified. The single external glossary reference also points to a path that does not exist.

Suggestions

Add a short worked example of a complete glossary entry so the guidance is copy-paste ready.

Specify where entries go in the glossary file (e.g., alphabetical placement) to make the workflow unambiguous.

Fix or clarify the ../../docs/glossary.md reference (it does not resolve) or describe the expected glossary file location.

Dimension	Reasoning	Score
Conciseness	The body is lean—short intro plus three bullets—with no padding and no re-explanation of what a glossary is; every token earns its place.	3 / 3
Actionability	It gives concrete link syntax (`[term](../path/to/file.ts)`, `[term](#term)`) but is incomplete—no example of a full glossary entry and hedged phrasing ("consider adding")—so it is not fully copy-paste ready.	2 / 3
Workflow Clarity	The bullets give a loose checklist but no clear sequence or mechanics (e.g., where in the glossary file to place an entry), so the single action is not fully unambiguous.	2 / 3
Progressive Disclosure	The content is organized as bullets in a simple short skill, but it relies on an external reference (../../docs/glossary.md) that does not resolve, and there are no section headers to aid navigation.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 identifies a clear niche and a concrete action but lacks any usage trigger, limiting its completeness and trigger-term quality. It is serviceable but would be meaningfully improved by a "Use when..." clause.

Suggestions

Add an explicit trigger clause such as "Use when introducing a new term or finding an existing term lacking a glossary entry".

Expand the action list (e.g., "add, update, and cross-reference glossary entries") to raise specificity.

Include common user phrasings ("define a term", "glossary entry") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and action ("add entries to the glossary") but lists only one action rather than multiple specific concrete actions, so it stops short of the top anchor.	2 / 3
Completeness	It states what the skill does (add glossary entries) but gives no explicit "when to use it" guidance; per the guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	"glossary" is a relevant keyword a user might say, but there are no common variations or a "Use when..." trigger phrase, leaving coverage incomplete.	2 / 3
Distinctiveness Conflict Risk	The glossary niche is somewhat specific, but without explicit triggers it could still overlap with documentation or term-management skills.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: MetaMask/ocap-kernel
Commit: 03b6a62

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.