demo-profile
Demo skill for the SkillToolProfile example.
40
25%
Does it follow best practices?
Impact
Pending
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 concrete actions describing what the skill actually does (e.g., 'Generates reports, processes data files, creates visualizations').
Add an explicit 'Use when...' clause with natural trigger terms that users would actually say when they need this skill.
Include domain-specific keywords and file types/formats to make the skill clearly distinguishable from others.
| 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 uninformative that it provides no distinguishing characteristics. It could not be reliably selected over any other skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
50%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 sufficient context, clear output expectations, and proper references. The dual-mode explanation adds ambiguity without enough guidance to be actionable. As a demo skill it serves its purpose, but as instructional content it falls short on actionability and clarity.
Suggestions
Clarify what 'the docs' refers to in knowledge-only mode by adding explicit links or file references.
Add expected output or success criteria for the `write_profile.sh` command so Claude knows what a successful execution looks like.
Either remove the meta-explanation about being a demo skill or replace it with actionable context about when and why to use this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is short but includes some unnecessary explanation ('This skill exists only to demonstrate...') that doesn't add actionable value. The 'In knowledge-only mode' sentence is somewhat verbose for what it conveys. | 2 / 3 |
Actionability | There is one concrete command provided, but the skill lacks context on what the command does, what inputs/outputs to expect, and the 'knowledge-only mode' guidance is vague ('use the docs for reasoning' — which docs?). | 2 / 3 |
Workflow Clarity | The skill describes two modes (full and knowledge-only) but doesn't clearly sequence steps or provide validation. For a simple single-command skill this could be acceptable, but the dual-mode distinction introduces ambiguity without clear guidance on when each applies. | 2 / 3 |
Progressive Disclosure | The skill is short enough that it doesn't need external references, but it mentions 'the docs' without linking to them, which is a missed navigation opportunity. The structure is minimal but adequate for the content size. | 2 / 3 |
Total | 8 / 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
09cce3e
- 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.