CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-continuous-learning

Development skill from everything-claude-code

43

1.54x
Quality

13%

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-claude/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 effectively a stub: a duplicated filler line and a "When to Use" sentence that points to a nonexistent overview, with no actionable guidance, workflow, or supporting references. It is concise only because it is nearly empty.

Suggestions

Add a concrete "How it works" section with the actual capture/organize/apply steps instead of the placeholder "Development skill skill." line.

Provide at least one executable example (e.g. a command or snippet that records a learning) so the skill is actionable rather than descriptive.

Either implement the referenced "overview" content inline or remove the dangling reference to it, and split any detailed material into a references/ file with a clear link.

DimensionReasoningScore

Conciseness

The body is brief and not padded with over-explanation, but tokens like the stuttering "Development skill skill." and the vacuous "execute the workflow or actions described in the overview" do not earn their place, so it lands at the "mostly efficient but could be tightened" anchor rather than 4-5.

3 / 5

Actionability

There is no concrete code, command, or specific instruction anywhere in the body; it only vaguely describes intent ("applicable to execute the workflow"), matching the "entirely vague or abstract; no concrete guidance" anchor.

1 / 5

Workflow Clarity

No steps, sequence, or validation checkpoints are present, and the skill's actual action is never defined, matching the "steps missing or incoherent" anchor; it does not qualify for the simple-skill exception because the single action is not unambiguous.

1 / 5

Progressive Disclosure

Structure is minimal (a title and one heading) and the body references an "overview" that does not exist in the file or any bundle, a dangling/buried reference; no references/scripts/assets bundle exists, so it sits below the well-organized threshold.

2 / 5

Total

7

/

20

Passed

Description

8%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 vacuous label rather than a capability statement: it names a broad domain, includes no concrete actions, no natural trigger terms, and no use-when guidance, making it indistinguishable from countless other development skills.

Suggestions

Replace the label with concrete capabilities, e.g. "Captures, organizes, and reuses lessons learned across coding sessions to improve future recommendations."

Add an explicit trigger clause such as "Use when the user wants to record insights from a task or apply past learnings to a new problem."

Include natural trigger keywords users would actually say (e.g. "lessons learned", "retrospective", "continuous learning", "knowledge capture") to distinguish it from sibling skills.

DimensionReasoningScore

Specificity

The description "Development skill from everything-claude-code" is a noun phrase that names a broad domain but states zero concrete actions, matching the "entirely vague; no concrete actions" anchor rather than score 2 (which requires at least minimal/generic actions).

1 / 5

Completeness

It offers only a vague "what" ("Development skill") and no "when"/trigger guidance at all, matching the score 2 anchor; it is not a 1 only because a domain is at least named, but it cannot reach 3 without any explicit use-when clause.

2 / 5

Trigger Term Quality

A user needing this skill would never naturally say "development skill from everything-claude-code"; it contains only the generic word "development" and a source label, with no recognizable trigger phrases, fitting the "no natural keywords; entirely generic language" anchor.

1 / 5

Distinctiveness Conflict Risk

"Development skill" is entirely generic and would collide with virtually any other development-oriented skill, matching the score 1 anchor; nothing in the description carves out a distinct niche.

1 / 5

Total

5

/

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.