Development skill from everything-agent-code
19
0%
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 ./.agent/skills/agent-strategic-compact/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 critically deficient across all dimensions. It provides no actionable information about what the skill does, contains no natural trigger terms, and would be impossible for Claude to correctly select from a pool of skills. The description appears to be a placeholder or metadata fragment rather than a functional skill description.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Writes unit tests, refactors code, implements features' instead of 'Development skill').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to write code, debug issues, create functions, or implement features').
Specify the domain or technology stack to distinguish from other development skills (e.g., 'Python backend development' or 'React frontend components').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 'Development skill from everything-agent-code' contains no concrete actions whatsoever - it doesn't describe what the skill actually does, only vaguely references 'development' and a source name. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it' - there is no explanation of capabilities and no 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'development' which is extremely generic. 'everything-agent-code' appears to be an internal identifier, not a natural keyword users would say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'development skill' is extremely generic and would conflict with virtually any coding, programming, or software development related skill. There are no distinct triggers to differentiate it. | 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 essentially a placeholder with no actual instructional value. It contains only a title and a nonsensical description ('Development skill skill') that provides no guidance on what the skill does or how to use it. The content fails on all dimensions as it teaches Claude nothing.
Suggestions
Define what 'agent-strategic-compact' actually does - what specific task or capability should this skill enable?
Add concrete, executable code examples or specific step-by-step instructions for the skill's intended purpose
Include at least a quick start section with actionable guidance that Claude can immediately apply
If this skill involves multi-step processes, document the workflow with clear sequencing and validation checkpoints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is essentially empty - just a title and a single vague sentence. While brevity is valued, this provides no actual content to be concise about. | 1 / 3 |
Actionability | No concrete guidance, code, commands, or examples are provided. The phrase 'Development skill skill' is meaningless and provides zero actionable instruction. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. There is nothing to follow or execute. | 1 / 3 |
Progressive Disclosure | No structure, no references, no organization. The content is a single meaningless 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
332e58b
Table of Contents
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.