cc-skill-strategic-compact
Development skill from everything-claude-code
15
0%
Does it follow best practices?
Impact
—
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 description is essentially non-functional. It provides no concrete actions, no trigger terms, no 'when to use' guidance, and no distinguishing characteristics. It would be impossible for Claude to reliably select this skill from a pool of available skills.
Suggestions
Replace the entire description with specific concrete actions the skill performs (e.g., 'Sets up development environments, configures build tools, manages dependencies').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about project setup, build configuration, dependency management, or development workflows').
Narrow the scope to a distinct niche rather than the overly broad 'development skill' to avoid conflicts with other coding-related skills.
| 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 skill' with no indication of what it actually does. | 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 meaningful explanation of capabilities. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'Development skill' and 'everything-claude-code' are not terms users would use when requesting help with a specific task. | 1 / 3 |
Distinctiveness Conflict Risk | 'Development skill' is maximally generic and would conflict with virtually any coding, programming, or software development skill. There is nothing to distinguish it from other skills. | 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 shell with no substantive content — just generic boilerplate headings and placeholder text. It provides absolutely no actionable guidance, no concrete examples, no workflow, and no references. It fails on every dimension of the rubric.
Suggestions
Define what this skill actually does and replace all placeholder text with specific, actionable instructions or code examples.
Add concrete steps, commands, or code snippets that Claude can execute — the current content has zero executable guidance.
Remove the generic 'When to Use' and 'Limitations' boilerplate and replace with skill-specific scope and constraints.
If the skill involves multi-step processes, add a clear numbered workflow with validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely boilerplate with no substantive information. The 'When to Use' and 'Limitations' sections are generic filler that provide zero skill-specific guidance and waste tokens on things Claude already knows. | 1 / 3 |
Actionability | There are no concrete instructions, code, commands, or examples. The content describes nothing actionable — it's entirely abstract placeholder text with no executable guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is described. The skill references 'the workflow or actions described in the overview' but no overview with actual content exists. | 1 / 3 |
Progressive Disclosure | No structure, no references to supporting files, and no meaningful content organization. The sections that exist are empty boilerplate with no navigational value. | 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
7ebecf2
- 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.