cc-skill-strategic-compact
Development skill from everything-claude-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 ./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 is an extremely poor description that provides essentially no useful information. It fails on every dimension: it names no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when,' and is so generic it would conflict with any development-related skill.
Suggestions
Replace the entire description with specific concrete actions the skill performs (e.g., 'Sets up project scaffolding, configures build tools, manages dependencies').
Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when the user asks about project setup, build configuration, or dependency management').
Remove the source attribution 'from everything-claude-code' as it provides no value for skill selection and replace it with domain-specific keywords users would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 'Development skill from everything-claude-code' is extremely vague. It names no concrete actions whatsoever—just a generic reference to 'development' with no indication of what it actually does. | 1 / 3 |
Completeness | Neither the 'what' nor the 'when' is meaningfully addressed. There is no explanation of what the skill does and no guidance on when Claude should select it. | 1 / 3 |
Trigger Term Quality | The only potentially relevant keyword is 'development,' which is overly generic. 'everything-claude-code' appears to be a source/package name rather than a natural trigger term a user would use. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'development skill' is maximally generic and would conflict with virtually any coding, programming, or software development skill. There is nothing distinctive about this description. | 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 is an empty template with no actual content. It contains only generic boilerplate headings and placeholder text that could apply to literally any skill. There is nothing specific, actionable, or useful for Claude to learn from this file.
Suggestions
Define what this skill actually does — replace the generic 'When to Use' section with a specific description of the task, including concrete triggers or scenarios.
Add actionable content: executable code examples, specific commands, or step-by-step instructions that Claude can follow to accomplish the skill's purpose.
Include at least one concrete input/output example so Claude knows what success looks like.
Remove or replace all generic boilerplate text (e.g., 'the workflow or actions described in the overview') with specific, substantive guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no substantive information. The 'When to Use' and 'Limitations' sections are generic filler that provide zero value — they describe nothing specific and waste tokens on platitudes Claude already understands. | 1 / 3 |
Actionability | There are no concrete instructions, code, commands, examples, or any actionable guidance whatsoever. The skill describes nothing about what to actually do — it's entirely abstract and self-referential. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process are described. The content references 'the workflow or actions described in the overview' but no overview with actual content exists. There is nothing to follow. | 1 / 3 |
Progressive Disclosure | No structure, no references to supporting files, and no meaningful organization. The sections that exist are empty shells with generic placeholder text and no bundle files to support them. | 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
1930a07
- 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.