demo-skill

A tiny skill used by the skill isolation example.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

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

The content is a deliberately minimal diagnostic canary: extremely concise but not actionable as skill guidance, with only an implicit single-step detection and no section structure. It works as a leak detector but scores low on delivering executable skill behavior.

Suggestions

If this skill is meant to do more than detect leaks, add concrete, executable instructions or commands.

Add a short section header to organize the content and lift progressive disclosure structure.

State explicitly what should happen once a leak is detected so the workflow has a clear follow-up step.

Dimension	Reasoning	Score
Conciseness	The two-sentence body is lean with no padding and does not explain concepts Claude already knows, so every token is purposeful.	3 / 3
Actionability	The body offers no concrete, executable guidance or commands; it is a passive diagnostic statement rather than an instruction.	1 / 3
Workflow Clarity	The single detection purpose ('If this body shows up ... it indicates a skill state leak') is unambiguous, but there is no structured sequence or follow-up action, so it stops short of a clear workflow.	2 / 3
Progressive Disclosure	The body is tiny with no external references needed, but it has no organized sections to qualify for the simple-skill full mark.	2 / 3
	Total	8 / 12 Passed

Description

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 a minimal meta label rather than a capability description: it conveys no actions, no user-facing triggers, and no usage guidance. It uses correct third-person voice but is otherwise uninformative.

Suggestions

Rewrite the description to name concrete actions the skill performs (e.g., 'Detects and reports ...').

Add an explicit 'Use when ...' trigger clause with natural terms a user would actually say.

Make the purpose specific enough to distinguish it from other skills and avoid trigger conflicts.

Dimension	Reasoning	Score
Specificity	The description 'A tiny skill used by the skill isolation example' names no concrete actions at all, only a meta-purpose, matching the vague/abstract anchor.	1 / 3
Completeness	It states neither what the skill does (no actions) nor when to use it (no 'Use when...' trigger), so both what and when are missing.	1 / 3
Trigger Term Quality	It contains no natural keywords a user would say; 'skill isolation example' is internal jargon, matching the no-natural-keywords anchor.	1 / 3
Distinctiveness Conflict Risk	The phrasing is generic and meta with no distinct trigger niche, so it would not reliably distinguish this skill from others.	1 / 3
	Total	4 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: trpc-group/trpc-agent-go
Commit: 737835b

Reviewed: 3 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.