CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-continuous-learning

Development skill from everything-claude-code

15

Quality

0%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cc-skill-continuous-learning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an empty shell skill with only a title and generic boilerplate sections. It contains no actual skill content—no instructions, no examples, no workflows, and no references. It fails on every dimension because there is literally nothing of substance to evaluate.

Suggestions

Define what 'continuous learning' means in this context and add concrete, actionable instructions describing the specific workflow or process Claude should follow.

Add executable code examples or specific commands that demonstrate the skill's core task.

Replace the generic 'When to Use' and 'Limitations' boilerplate with skill-specific scope, constraints, and trigger conditions.

If the skill involves multi-step processes, add a numbered workflow with explicit validation checkpoints.

DimensionReasoningScore

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—'execute the workflow or actions described in the overview' is circular and vacuous since no overview content exists.

1 / 3

Workflow Clarity

No workflow, steps, or process are described at all. The skill name suggests 'continuous learning' but no sequence, validation, or any operational detail is provided.

1 / 3

Progressive Disclosure

No bundle files exist, no references to external resources, and the content itself is a stub with no meaningful structure or navigation. There is nothing to disclose progressively.

1 / 3

Total

4

/

12

Passed

Description

0%Scale 1-3

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 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 reduce conflict risk with other skills.

DimensionReasoningScore

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.

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 or development-related skill. There is nothing to distinguish it from other skills.

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
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.