CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-continuous-learning

Development skill from everything-claude-code

22

Quality

11%

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

22%

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 skeleton: it contains a broken filler line, a 'When to Use' section that defers to a non-existent overview, and generic limitation boilerplate, with no actionable guidance or real workflow. It reads as an unpopulated template rather than a usable skill.

Suggestions

Replace the filler 'Development skill skill.' and the deferring 'When to Use' text with the actual overview of what the skill does and the concrete steps to perform it.

Add executable, specific guidance — e.g. the exact file path/format to write lessons to and a sample entry — so the skill is actionable rather than abstract.

Either provide the referenced 'overview'/'workflow' content inline or link to a real reference file so the document is self-contained.

DimensionReasoningScore

Conciseness

The body is short, but 'Development skill skill.' is broken filler and the Limitations are generic caveats that do not earn their place, fitting the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor rather than the lean level-3 anchor.

2 / 3

Actionability

It provides no concrete code, commands, or steps — 'execute the workflow or actions described in the overview' is purely abstract and describes rather than instructs, matching the level-1 anchor.

1 / 3

Workflow Clarity

No workflow is actually present; the body references 'the workflow or actions described in the overview' but no such overview exists, matching the 'steps unclear or missing; no sequence' anchor. The simple-skill exception does not apply because the content is not clear and well-organized.

1 / 3

Progressive Disclosure

Sections are labeled and the skill is under 50 lines with no bundle files, but it points to an 'overview' that is missing, so organization is only partial, fitting the 'some structure but could be better organized' anchor rather than a clean level-3.

2 / 3

Total

6

/

12

Passed

Description

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.

The description is essentially a placeholder: it conveys no concrete capability, no trigger terms, and no usage guidance, so it would neither help a user discover the skill nor distinguish it from others. Every dimension scores at the floor.

Suggestions

Replace 'Development skill from everything-claude-code' with concrete actions the skill performs, e.g. 'Capture lessons learned from a coding session into a persistent knowledge file'.

Add an explicit 'Use when...' clause naming natural trigger terms users would say, such as 'learning', 'lessons learned', or 'continuous improvement'.

Make the scope distinctive enough that it does not collide with general development skills by naming the specific artifact it produces or updates.

DimensionReasoningScore

Specificity

The description 'Development skill from everything-claude-code' names no concrete actions whatsoever, matching the 'vague or no actions; abstract language' anchor rather than the level-2 anchor that names a domain and some actions.

1 / 3

Completeness

It barely states what the skill does ('Development skill') and includes no 'Use when...' trigger guidance, so both what and when are very weak, matching the level-1 'Missing what OR when, or both very weak' anchor.

1 / 3

Trigger Term Quality

It contains no natural keywords a user would actually say; 'Development skill from everything-claude-code' is overly generic jargon-free filler, matching the 'no natural keywords; overly generic' anchor.

1 / 3

Distinctiveness Conflict Risk

'Development skill' is so generic it would conflict with countless other skills, matching the 'very generic; would conflict with many skills' anchor rather than the level-2 'somewhat specific' anchor.

1 / 3

Total

4

/

12

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
sickn33/antigravity-awesome-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.