cc-skill-strategic-compact
Development skill from everything-claude-code
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill cc-skill-strategic-compactOverall
score
16%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 critically deficient across all dimensions. It provides no information about what the skill actually does, contains no useful 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 reference rather than an actual functional description.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Creates Python scripts, debugs code, writes unit tests, refactors functions').
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, create scripts, or work with programming languages').
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 explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 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 term users would use. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'development skill' is extremely 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 content is effectively empty and provides no value. It contains only a title and a nonsensical placeholder sentence ('Development skill skill') with no actual instructions, examples, code, or guidance. 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, describe the specific development patterns, workflows, or techniques it should cover
| 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 information or guidance whatsoever. | 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
56%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 9 / 16 Passed | |
- 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.