CtrlK
BlogDocsLog inGet started
Tessl Logo

demo-profile

Demo skill for the SkillToolProfile example.

50

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is concise, actionable, and well-structured for a simple demo skill, providing an executable command and clearly distinguishing its two operating modes. It appropriately leverages a real bundle script rather than restating its contents.

DimensionReasoningScore

Conciseness

The body is a lean handful of lines that assumes Claude's competence and explains nothing Claude already knows; every token earns its place, matching the score-3 'lean and efficient' anchor.

3 / 3

Actionability

It gives a fully executable, copy-paste-ready command `sh scripts/write_profile.sh out/profile.txt` backed by a real script, matching the score-3 anchor for concrete executable guidance.

3 / 3

Workflow Clarity

This is a simple single-task skill under 50 lines, and the single action is unambiguous with two clearly distinguished modes (full vs knowledge-only), so per the simple-skills note workflow clarity scores 3.

3 / 3

Progressive Disclosure

The body is well-organized with a real one-level reference to scripts/write_profile.sh (verified present), and for a skill this small that structure satisfies the score-3 anchor without needing deeper references.

3 / 3

Total

12

/

12

Passed

Description

7%

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 placeholder-quality one-liner that states a demo purpose but provides no concrete actions, no natural trigger terms, and no usage guidance. It is barely distinguishable and would rarely be selected on its own merits.

Suggestions

Rewrite the description to name the concrete actions the skill performs (e.g., 'Writes a demo profile file via a shell script') instead of the abstract 'Demo skill for the SkillToolProfile example.'

Add an explicit 'Use when...' trigger clause stating when Claude should invoke this skill (e.g., 'Use when demonstrating the SkillToolProfile tool-profile behavior or testing full vs knowledge-only modes').

Include natural user-facing keywords (e.g., 'skill tool profile', 'demo output', 'profile file') so the description contains terms a user would actually say.

DimensionReasoningScore

Specificity

The phrase "Demo skill for the SkillToolProfile example" names no concrete actions at all, only an abstract purpose, matching the 'vague or no actions' anchor rather than the score-2 anchor which requires naming some actions.

1 / 3

Completeness

It weakly states what the skill is (a demo) and entirely omits any "Use when..." trigger for when to invoke it; per the guidelines a missing trigger clause with a weak 'what' falls at the bottom of the scale.

1 / 3

Trigger Term Quality

"SkillToolProfile" is internal API jargon that no user would naturally say when they need this skill; there are no natural trigger terms, matching the score-1 anchor for technical jargon.

1 / 3

Distinctiveness Conflict Risk

It names a specific niche (the SkillToolProfile example) so it is somewhat distinct, but the description is too vague and trigger-less to clearly avoid overlap, matching the score-2 'somewhat specific but could overlap' anchor rather than the distinct-trigger score-3 anchor.

2 / 3

Total

5

/

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
trpc-group/trpc-agent-go
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.