CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-continuous-learning

Development skill from everything-claude-code

40

1.54x
Quality

9%

Does it follow best practices?

Impact

99%

1.54x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/cc-skill-continuous-learning/SKILL.md

The canonical home for this skill is cc-skill-continuous-learning in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

18%Weight 40%Scale 1-5

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

The body is a near-empty placeholder with a duplicated word and a circular pointer to an overview that does not exist. It offers no actionable guidance, no workflow, and no meaningful structure.

Suggestions

Replace the filler 'Development skill skill.' line with the actual concrete steps or commands the skill should perform.

Either add the referenced 'overview' content or remove the dangling pointer to 'the workflow or actions described in the overview.'

Provide real 'When to Use' trigger conditions instead of the generic 'applicable to execute the workflow' sentence.

DimensionReasoningScore

Conciseness

The body is very short, so it is not token-heavy, but the few tokens present are wasted: 'Development skill skill' is a stuttered duplicate and 'described in the overview' references an overview that does not exist, so it is mostly efficient with some unnecessary padding.

3 / 5

Actionability

There is no concrete code, command, or specific guidance; 'execute the workflow or actions described in the overview' only describes and points at a nonexistent overview rather than instructing.

1 / 5

Workflow Clarity

No steps or sequence are present, and the lone reference to 'the workflow or actions described in the overview' has no corresponding overview, so the process is incoherent.

1 / 5

Progressive Disclosure

There is minimal structure (a single '## When to Use' header) but no real organization, no bundle files, and a reference to a nonexistent overview; the content is too empty to qualify as well-organized.

2 / 5

Total

7

/

20

Passed

Description

0%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a content-free placeholder: a generic domain label plus a source attribution, with no actions, triggers, or use-conditions. It fails every dimension and is indistinguishable from countless other skills.

Suggestions

Replace the description with concrete capabilities (e.g., specific actions the skill performs) written in third person.

Add an explicit 'Use when...' clause naming the natural trigger phrases a user would say.

Drop the source-repo attribution and instead state the distinct niche that separates this skill from general development skills.

DimensionReasoningScore

Specificity

The phrase 'Development skill from everything-claude-code' is entirely abstract with no concrete actions; it does not even reach the minimal 'Processes PDF files' level because it names no verb or capability at all.

1 / 5

Completeness

Both the 'what' and the 'when' are missing or extremely vague; there is no 'Use when...' trigger clause and no concrete statement of capability.

1 / 5

Trigger Term Quality

'Development skill' is entirely generic and 'everything-claude-code' is a source-repo label (technical jargon), not a natural phrase a user would say when needing this skill.

1 / 5

Distinctiveness Conflict Risk

'Development skill' is entirely generic and would overlap with virtually any development-oriented skill, giving it no distinguishable niche.

1 / 5

Total

4

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.