maceytest/testytesty
test
19
Does it follow best practices?
Validation for skill structure
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 value. It provides zero information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Replace 'test' with a description of what the skill actually does using specific action verbs (e.g., 'Extracts data from...', 'Generates reports for...', 'Converts files between...')
Add an explicit 'Use when...' clause that specifies the conditions or user requests that should trigger this skill
Include natural keywords and file types/formats that users would mention when they need this skill's functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 'test' provides no concrete actions whatsoever - it's a single word with no indication of what the skill does. | 1 / 3 |
Completeness | The description answers neither 'what does this do' nor 'when should Claude use it' - it provides no useful information at all. | 1 / 3 |
Trigger Term Quality | The word 'test' is overly generic and not a natural keyword users would say when seeking a specific skill; it could apply to anything. | 1 / 3 |
Distinctiveness Conflict Risk | The word 'test' is maximally generic and would conflict with virtually any skill; it provides no distinguishing characteristics. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is an empty placeholder with no actual instructions. It fails all dimensions as it provides no actionable guidance, no workflow, no structure, and no useful content. The skill needs to be completely written from scratch.
Suggestions
Replace the TODO placeholder with actual instructions describing what the skill does and how to execute it
Add concrete, executable code examples or specific commands that Claude can follow
Define clear steps or workflow if the skill involves multiple actions
Include at least one practical example showing expected input and output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is a placeholder TODO with no actual instructions. While technically brief, it provides zero value and wastes tokens on a non-functional template. | 1 / 3 |
Actionability | No concrete guidance, code, commands, or examples are provided. The TODO placeholder offers no actionable instructions whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. The content is entirely empty of any procedural guidance. | 1 / 3 |
Progressive Disclosure | No structure, organization, or references to other materials. The content is a single placeholder line with no navigation or content hierarchy. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_field | 'description' is very short (4 chars), consider making it more detailed | Warning |
Total | 10 / 11 Passed | |
Install with Tessl CLI
npx tessl i maceytest/testytestyReviewed
Table of Contents