CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-continuous-learning

Development skill from everything-agent-code

19

Quality

0%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/agent-continuous-learning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 description is critically deficient across all dimensions. It provides no actionable information about what the skill does, contains no natural trigger terms, and would be impossible for Claude to correctly select from a pool of skills. The description appears to be a placeholder or metadata fragment rather than a functional skill description.

Suggestions

Replace the entire description with concrete actions the skill performs (e.g., 'Writes unit tests, refactors code, implements features' instead of 'Development skill').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to write code, debug issues, create functions, or implement features').

Specify the domain or technology stack to distinguish from other development skills (e.g., 'Python backend development' or 'React frontend components').

DimensionReasoningScore

Specificity

The description 'Development skill from everything-agent-code' contains no concrete actions whatsoever - it doesn't describe what the skill actually does, only vaguely references 'development' and a source name.

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 'Use when...' clause or equivalent guidance.

1 / 3

Trigger Term Quality

The only potential trigger term is 'development' which is extremely generic. 'everything-agent-code' appears to be an internal identifier, not a natural keyword users would say.

1 / 3

Distinctiveness Conflict Risk

The term 'development skill' is extremely generic and would conflict with virtually any coding, programming, or software development related skill. There are no distinct triggers to differentiate it.

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 content is effectively a placeholder with no substantive information. It consists only of a title and a nonsensical description ('Development skill skill') that provides no guidance on what 'agent-continuous-learning' means or how to implement it. The skill fails on all dimensions as it contains no actionable content whatsoever.

Suggestions

Define what 'agent-continuous-learning' actually means and what specific tasks or behaviors this skill should enable

Add concrete, executable code examples or specific commands that demonstrate the continuous learning workflow

Include a clear multi-step process with validation checkpoints if this involves iterative learning or feedback loops

Structure the content with sections (e.g., Quick Start, Core Workflow, Examples) and reference external files for detailed documentation if needed

DimensionReasoningScore

Conciseness

The content is essentially empty - just a title and a single vague sentence. While brief, it provides no actual value or information, making it inefficient in a different way: it wastes the skill file entirely.

1 / 3

Actionability

No concrete guidance whatsoever. No code, no commands, no examples, no specific instructions. The phrase 'Development skill skill' is meaningless and provides zero actionable direction.

1 / 3

Workflow Clarity

No workflow is defined. There are no steps, no processes, no validation checkpoints - nothing that could guide Claude through any task related to continuous learning.

1 / 3

Progressive Disclosure

No structure exists. There are no sections, no references to other files, no organization of any kind. The content is a single line that fails to disclose anything progressively or otherwise.

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.

Validation10 / 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
Dokhacgiakhoa/antigravity-ide
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.