CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

self-evolving-single-agent

Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or improve itself over time without becoming a multi-agent team.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A terse, well-structured instruction skill that respects the token budget and specifies concrete deliverables with genuine checkpoints (interview-research gate, approval receipts). Its gaps are execution detail for referenced mechanisms (Memory Tickets, host capabilities, the contracts gate file) and an unsignaled reference to a file that does not exist in the bundle.

Suggestions

Clarify the status of `contracts/builder-interview-research-gate.md` — either bundle it under references/ and link it, or state where it lives and what it contains.

Add one line each defining the opaque mechanisms (Memory Ticket format, what a valid 'one-use owner approval receipt' is, how to detect revision-v1/evolution-v2 host capabilities) so the guidance is fully executable.

DimensionReasoningScore

Conciseness

The ~45-line body is dense and lean with zero padding and no explanation of concepts Claude already knows — every step adds novel, project-specific requirements ("Memory Events and Memory Tickets for durable updates", "8-12 only if that many gaps remain"). This matches 'lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

The guidance is largely concrete for an instruction-only skill: exact files to create (`.agentlas/memory-map.json`, `docs/prompt-performance-contract.md`, `.agentlas/global-commands.json`), a pre-generation gate to run, and defined outputs. It stops short of a 5 because key mechanisms are referenced without any execution detail — how to run the gate, what a Memory Ticket or 'one-use owner approval receipt' looks like, or what 'revision-v1/evolution-v2 host capabilities' concretely means.

4 / 5

Workflow Clarity

The 7-step procedure is clearly sequenced with real checkpoints: a mandatory pre-generation gate (step 2), an approval checkpoint before any self-evolution changes (step 6), and the File revision approval checklist ('real staged multi-file diff, current source evidence, and an exact one-use owner approval receipt'). It is not a 5 because there is no error-recovery/feedback loop and the `verification` output is named but never described.

4 / 5

Progressive Disclosure

The body is under 50 lines with clean sections (Procedure, Output, File revision approval), which per the simple-skill note could merit a 5. It drops to 4 because `contracts/builder-interview-research-gate.md` is referenced as a path to run but is not a bundle file here and is not clearly signaled (no link or location guidance), leaving a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

75%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.

A solidly above-average description with an explicit trigger clause, multiple domain-specific actions, and a clear single-vs-multi-agent boundary. Its main weaknesses are that the 'what' is only implied inside the 'when' clause and the trigger vocabulary could cover more user-natural synonyms.

Suggestions

State the 'what' independently of the trigger, e.g. 'Generates a single installable agent package with memory architecture, research-refresh loop, and proposal-first self-evolution. Use when...' so both halves are explicit.

Add natural synonyms users would say, such as 'self-improving', 'self-updating', or 'agent that learns from experience', to broaden trigger coverage.

Mention the concrete deliverables (memory contract, refresh loop, approval gate, global commands) in the description to sharpen what the skill produces.

DimensionReasoningScore

Specificity

The description lists several distinct actions for the domain — "keep learning, track sources, refresh research, propose repairs, or improve itself over time" — which matches the 'several specific actions; minor gaps' anchor. It falls short of a 5 because the actions remain abstract (no concrete artifacts or examples of what 'improve itself' entails), and above a 3 because it goes well beyond 1-2 generic actions.

4 / 5

Completeness

It has an explicit "Use when..." trigger clause, and a 'what' ("generating a single installable agent") is present, but the what is embedded inside the when-condition rather than stated independently, and it never says what the skill actually produces (memory architecture, approval gates, global commands). This matches 'both what and when; when could be more explicit or specific' rather than the fully explicit two-part structure of a 5.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present — "generating a single installable agent", "keep learning", "refresh research", "propose repairs", "improve itself", "multi-agent team" — giving good keyword coverage. A 5 is not warranted because common synonyms like "self-improving", "self-updating", or "autonomous agent" are missing; it clearly exceeds the 'some relevant keywords but missing variations' level.

4 / 5

Distinctiveness Conflict Risk

The niche is well-delineated by "single installable agent" and the explicit exclusion "without becoming a multi-agent team", giving mostly distinct triggers. It is not a 5 because it could still overlap with a generic agent-generation skill (nothing in the trigger phrases excludes plain agent-building requests).

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agentlas-ai/Agentlas-OS

Path

skills/self-evolving-single-agent/SKILL.md

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.