CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-lifecycle-promotion

Use when adding or auditing Agentlas skill lifecycle metadata, skill-registry.json, trial evidence, Curator promotion decisions, or first-class skill promotion gates.

66

Quality

78%

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 ./.agents/skills/skill-lifecycle-promotion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise and well-structured with concrete, sequenced governance directives and a blocking promotion gate plus reporting checklist. Its only gaps are the lack of example artifact schemas and an explicit retry/feedback loop on the promotion gate.

Suggestions

Add a brief example of the expected structure for `.agentlas/skill-registry.json` (a few JSON lines) so the directives are copy-paste ready.

Turn the step-8 promotion gate into an explicit feedback loop (e.g. 'Block promotion; remediate the missing evidence; re-check before proceeding').

DimensionReasoningScore

Conciseness

The body is lean: a short orienting line plus nine terse directives and a compact output checklist, with no over-explanation of concepts Claude already knows and no padding, so every token earns its place.

5 / 5

Actionability

Directives are concrete and specific (named paths like `.agentlas/skill-registry.json`, field values like `tier: candidate`, and flag `runtimeFirstClassRecallEnabled: false`), but no example schemas or sample file contents are given, leaving a minor gap for an instruction-only skill.

4 / 5

Workflow Clarity

A clear nine-step sequence is present with a promotion-blocking gate (step 8) and an output section that reports evidence gaps and rollback status, but there is no explicit validate-then-fix-then-retry feedback loop, which keeps it below a 5.

4 / 5

Progressive Disclosure

The skill is well under 50 lines, has no external bundle files, and is cleanly organized into a Procedure section and an Output section, satisfying the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

71%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 specific, distinct, and uses an explicit Use-when trigger covering several concrete governance artifacts. Its main weaknesses are jargon-heavy trigger terms lacking synonyms and a fused what/when structure rather than separate statements.

Suggestions

Add a short separate capability statement before the 'Use when' clause so the 'what' is stated independently of the 'when' (e.g. 'Governs Agentlas skill promotion metadata. Use when...').

Include natural-language synonyms and file extensions alongside the jargon (e.g. 'skill registry, .agentlas/skill-registry.json, promotion trials, curator decisions') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names two concrete actions ("adding or auditing") applied to several specific artifacts ("skill-registry.json", "trial evidence", "Curator promotion decisions", "first-class skill promotion gates"), which exceeds the 1-2 action bar but stops short of the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

It has an explicit "Use when..." trigger clause and embeds the "what" (adding/auditing lifecycle metadata) inside it, but the what and when are fused into a single sentence rather than a separately stated capability plus concrete triggers, so it falls just below a 5.

4 / 5

Trigger Term Quality

Relevant domain keywords like "skill-registry.json", "Curator promotion decisions", and "first-class skill promotion gates" are present, but they are specialized jargon with no common synonyms, variations, or file-extension alternatives, so coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

The niche is highly specific (Agentlas skill lifecycle governance with named registry/trial/curator artifacts), giving it distinct triggers and minimal overlap risk with generic skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentlas-ai/Agentlas-OS
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.