CtrlK
BlogDocsLog inGet started
Tessl Logo

spec-driven-development/agent-registry

Coordina multipli agenti AI CLI (Kimi, Claude, Gemini, OpenAI, ecc.) che lavorano contemporaneamente sullo stesso progetto e mantiene una memoria collettiva (wiki) di tutte le sessioni passate. Usa questa skill SEMPRE quando lavori in parallelo con altre AI CLI, quando devi salvare lo stato di una sessione condivisa, quando vuoi evitare sovrascritture su file toccati da altri agenti, quando devi chiedere "questo lavoro è già stato fatto? questo bug si è già visto?", o quando l'utente parla di "multi-tap", "registry agenti", "coordination", "lock file", "handoff condiviso", "wiki delle sessioni", "chi sta lavorando su cosa" o "evitare che le AI si pestino i piedi".

72

Quality

90%

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

Overview
Quality
Evals
Security
Files

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced body with strong validation feedback loops and copy-paste commands throughout. Its main weaknesses are length/redundancy and progressive disclosure: detailed reference material is kept inline and the documented directory structure references folders that are absent from the actual bundle.

Suggestions

Remove the duplicated command syntax — either keep the inline examples in the flow OR the 'Riferimento comandi' reference, not both — and consolidate the directory layout (shown at lines ~36 and ~496) into a single occurrence to tighten conciseness.

Split dense reference material out of SKILL.md into one-level-deep files (e.g. REFERENCE.md for command syntax/env vars, GIT-SYNC.md for sync principles, DASHBOARD.md for API endpoints) so SKILL.md stays an overview with clearly signaled links.

Reconcile the 'Struttura della skill' listing with the actual bundle: either create the missing references/registry-schema.yaml, templates/registry-template.md, and evals/evals.json files, or remove those entries so the documented structure matches what is shipped.

DimensionReasoningScore

Conciseness

The body is reference-dense with no concept-explanation fluff, but it is ~520 lines with redundancy: the 'Riferimento comandi' section repeats syntax already shown inline, the directory layout appears twice, and the Docker/WhatsApp section is heavy — matching 'mostly efficient but could be tightened' rather than fully lean.

2 / 3

Actionability

Every step ships copy-paste-ready commands with realistic values (e.g. 'python ... registry_manager.py register "kimi-$(date +%s)" "Kimi" "2.7" "Refactoring modulo auth" --space ...'), and the full command-reference section lists exact syntax, matching 'Fully executable code/commands; copy-paste ready'.

3 / 3

Workflow Clarity

The numbered 'Flusso di sessione (obbligatorio)' sequences read→register→query→work→lock→end→finish, with an explicit LoopVerifyContext feedback loop (re-read, verify, re-verify on new prompt) and validation on destructive ops (kill cmdline/anti-PID-reuse check, cleanup preserving fresh-lock sessions), matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

Sections are well-organized and the referenced scripts/ bundle genuinely exists, but all reference material (command reference, env-var table, git-sync principles, dashboard API) stays inline in SKILL.md rather than being split out, and the documented 'Struttura della skill' lists references/, templates/, and evals/ directories that do not exist in the actual bundle — matching 'some structure but content that should be separate is inline'.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 strong, concrete description that states multiple specific capabilities and pairs them with an explicit 'Use when...' clause carrying a wide range of natural trigger phrases. It is distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Coordina multipli agenti AI CLI' working concurrently, 'mantiene una memoria collettiva (wiki)', saving shared session state, avoiding overwrites, and querying past work/bugs — matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (coordinate parallel agents + shared wiki memory) and when via an explicit 'Usa questa skill SEMPRE quando...' clause with many triggers, satisfying the 'clearly answers both what AND when' anchor; the explicit trigger clause avoids the completeness cap of 2.

3 / 3

Trigger Term Quality

Provides broad natural-language coverage with quoted triggers a user would actually say: 'multi-tap', 'registry agenti', 'coordination', 'lock file', 'handoff condiviso', 'wiki delle sessioni', 'chi sta lavorando su cosa', matching the 'Good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (multi-agent CLI coordination + shared wiki memory) with distinctive triggers like 'registry agenti' and 'lock file', making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

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

skill_md_line_count

SKILL.md is long (536 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents