cc-skill-continuous-learning
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-continuous-learning/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 a label rather than a functional description. It provides no concrete actions, no trigger terms, no 'when to use' guidance, and no distinguishing characteristics. It would be nearly useless for Claude to select this skill appropriately from a pool of available skills.
Suggestions
Replace the entire description with specific concrete actions this 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 reduce conflict risk 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 explanation of capabilities and no trigger guidance whatsoever. | 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 could 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 template with no actual content. It contains only generic boilerplate sections ('When to Use', 'Limitations') that are self-referential and provide no skill-specific guidance whatsoever. The title suggests 'continuous learning' but nothing in the body teaches Claude how to do anything.
Suggestions
Define what 'continuous learning' means in this context and add concrete, actionable instructions for the specific workflow or task Claude should perform.
Add executable code examples or specific commands that demonstrate the skill's core functionality.
Replace the generic 'When to Use' and 'Limitations' boilerplate with skill-specific scope, constraints, and at least one concrete example input/output.
If this skill involves a multi-step process, outline the steps with explicit 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, wasting tokens on content that adds no value. | 1 / 3 |
Actionability | There are no concrete instructions, code, commands, or examples. The skill describes nothing actionable—it references an 'overview' and 'workflow' that don't exist in the content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process are described at all. The content is entirely meta-description with no actual task sequence or validation checkpoints. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to external files, and no structure beyond empty boilerplate section headers. The skill body is a hollow template. | 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
93c57b2
- 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.