Development skill from everything-claude-code
19
Quality
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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/cc-skill-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 information about what the skill does, when to use it, or how to distinguish it from other skills. It appears to be a placeholder or metadata fragment rather than a functional description.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Creates Python scripts, debugs code, writes unit tests').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to write code, debug errors, or create scripts').
Specify the domain or technology focus to distinguish from other development skills (e.g., 'Python development', 'web frontend', 'API integration').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 'Development skill from everything-claude-code' contains no concrete actions whatsoever - it doesn't describe what the skill actually does, only vaguely references 'development' and a source. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'development' which is extremely generic. There are no natural keywords users would say when needing this skill - 'everything-claude-code' is not a user-facing term. | 1 / 3 |
Distinctiveness Conflict Risk | 'Development skill' is extremely generic and would conflict with virtually any coding, programming, or software-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 effectively empty and non-functional. It contains only a title and a nonsensical placeholder sentence ('Development skill skill') that provides no actual instruction, guidance, or value. This fails every dimension of the rubric as it teaches Claude nothing about how to perform any task.
Suggestions
Define what specific task or capability this skill should teach Claude to perform
Add concrete, executable code examples or specific step-by-step instructions for the intended task
Include at least a quick-start section with copy-paste ready commands or code
If this is meant to be a strategic/compact development skill, specify what 'strategic' and 'compact' mean in terms of actual behaviors and outputs
| 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 process is described. There is nothing for Claude 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 | |
20ba150
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.