demo-profile
Demo skill for the SkillToolProfile example.
35
18%
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 information 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, formats tables, creates summaries').
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 or any indication of functionality or triggers. | 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
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 a single bash command but lacks meaningful workflow guidance, validation steps, and clear references. The content is brief but not efficiently structured—it spends tokens explaining its own purpose as a demo rather than providing actionable instructions. The two operational modes (full vs knowledge-only) are mentioned but insufficiently defined.
Suggestions
Add explicit steps for what to do before and after running the script, including any validation of the output file.
Link to the specific 'docs' referenced for knowledge-only mode rather than vaguely mentioning them.
Clarify the two modes (full vs knowledge-only) with concrete guidance for each, or remove the distinction if it's not actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is short but includes some unnecessary explanation ('This skill exists only to demonstrate...') and the 'knowledge-only mode' paragraph adds context that could be tighter. However, it's not overly verbose. | 2 / 3 |
Actionability | It provides one concrete bash command, but the guidance is minimal and incomplete—there's no context on what the script does, what inputs it expects, or what the expected output looks like. The 'knowledge-only mode' instruction is vague ('use the docs for reasoning'). | 2 / 3 |
Workflow Clarity | There is no clear workflow, no sequencing of steps, and no validation or verification. The skill mentions two modes (full and knowledge-only) but doesn't clearly define when each applies or what steps to follow in either case. | 1 / 3 |
Progressive Disclosure | The skill is very short so a monolithic structure isn't a major issue, but it references 'docs' for reasoning in knowledge-only mode without linking to any specific documentation, making navigation unclear. | 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
0c1ec2b
- 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.