demo-profile
Demo skill for the SkillToolProfile example.
28
18%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skilltoolprofile/skills/demo-profile/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no functional content. It fails on every dimension: it describes no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when', and provides no distinguishing characteristics that would help Claude select it appropriately.
Suggestions
Replace the placeholder text with a concrete description of what the skill actually does, listing specific actions (e.g., 'Generates reports, processes data, creates visualizations').
Add an explicit 'Use when...' clause with natural trigger terms that users would actually say when they need this skill.
Define a clear domain niche so the skill is distinguishable from others in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Demo skill for the SkillToolProfile example' is entirely abstract and does not describe any capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of functionality. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'SkillToolProfile' is internal jargon, and 'demo skill' is not something a user would request. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic and vague that it provides no distinguishing characteristics. It could conflict with anything or nothing since it describes no actual domain. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a minimal demo skill that provides one concrete command but lacks meaningful workflow guidance, validation steps, and clear references to supporting documentation. The content is brief but not efficiently structured—it spends tokens on meta-explanation ('This skill exists only to demonstrate...') rather than actionable instruction. It would benefit significantly from specifying what the script does, what the expected output looks like, and what 'the docs' refers to.
Suggestions
Add a brief description of what `scripts/write_profile.sh` does and what the expected output in `out/profile.txt` looks like.
Replace the vague 'use the docs for reasoning' with specific file references or inline guidance for knowledge-only mode.
Add a validation step after running the script (e.g., 'Verify output: check that out/profile.txt contains...').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is short but includes some unnecessary framing ('This skill exists only to demonstrate...') that doesn't add actionable value. The distinction between 'full mode' and 'knowledge-only mode' is somewhat useful but could be tighter. | 2 / 3 |
Actionability | It provides one concrete command (`sh scripts/write_profile.sh out/profile.txt`), but the guidance for 'knowledge-only mode' is vague ('use the docs for reasoning instead of executing it') with no specifics on what docs or what reasoning steps to take. | 2 / 3 |
Workflow Clarity | There is no clear workflow, no sequencing of steps, and no validation or verification. The skill presents a single command with no context on what happens before or after, and the two modes are not clearly delineated as a process. | 1 / 3 |
Progressive Disclosure | The content is brief enough that a monolithic structure isn't a major problem, but it references 'the docs' without specifying which docs or linking to them, making navigation unclear. No bundle files are provided to support the reference. | 2 / 3 |
Total | 7 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- trpc-group/trpc-agent-go
- Commit
b3a84a7
- 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.