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 is an extremely poor skill description that provides essentially no useful information. It fails on every dimension: it names no concrete actions, includes no trigger terms, lacks both 'what' and 'when' guidance, 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 development environments, configures build tools, manages dependencies').
Add an explicit 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user asks about project setup, build configuration, or dependency management').
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 a placeholder stub with no meaningful content whatsoever. It contains only a title, a generic boilerplate description, and a circular 'When to Use' section that references a non-existent overview. It fails on every dimension of the rubric.
Suggestions
Define the actual purpose and scope of the skill — what is 'continuous learning' in this context, and what specific actions should Claude take?
Add concrete, executable guidance: specific commands, code examples, or step-by-step workflows that Claude can follow.
Include a real 'When to Use' section with specific trigger conditions (e.g., 'When the user asks to update learning notes after a code review').
If the skill involves multi-step processes, add a clear workflow with validation checkpoints and error recovery steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is essentially empty — it contains no substantive instructions, yet what little is there is filler text ('Development skill skill', 'applicable to execute the workflow or actions described in the overview') that adds zero value. | 1 / 3 |
Actionability | There is no concrete guidance, no code, no commands, no examples, and no specific instructions of any kind. The skill provides absolutely nothing actionable. | 1 / 3 |
Workflow Clarity | No workflow, steps, sequence, or validation checkpoints are present. The 'When to Use' section is a circular, meaningless placeholder. | 1 / 3 |
Progressive Disclosure | There is no structure, no references to other files, and no organized content. The entire skill is a near-empty stub 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
6a07b83
- 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.