CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

decider

Load to create, search, or supersede an architecture decision record.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/decider/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 dense, token-efficient overview with concrete commands, explicit binding-semantics rules, and a clear approval gate — genuinely actionable instruction-only guidance. Its weaknesses are over-compressed sentences that cost clarity, no example invocation or sample record, validation via "check" never wired into a workflow step, and references to five bundle files that do not exist in the bundle.

Suggestions

Add the referenced files to the bundle (workflows/create-decision.md, workflows/update-decision.md, schemas/decision-format.md, templates/decision-entry.md, templates/index-row.md) or inline minimal versions, since the body's navigation chain currently dead-ends at five missing paths.

Decompress the status-semantics rules (e.g. the removed-record rationale sentence) into a short status → binding-effect table; the current prose is token-efficient but requires multiple reads.

Include one example CLI invocation (e.g. a sample search and its output shape) and add an explicit step to run "decisions check" after creating or updating a record so validation is part of the workflow.

DimensionReasoningScore

Conciseness

The body is highly lean — it never explains what an ADR is, assumes competence throughout, and packs every sentence with project-specific rules — but several sentences are compressed to the point of needing re-reads (e.g. "A removed record's reason lives where its Rationale cell names it, the comment at the code or the principle doc's section"), and removal/withdrawal rules appear in both the "A record is short" paragraph and the workflow triggers. Brevity that does not fully preserve clarity fits the 4 anchor rather than the 5.

4 / 5

Actionability

Guidance is concrete: an exact CLI invocation (".agents/skills/decider/scripts/decisions <command> [options]"), named actions ("search, search --issue, list, next-id, get, check"), named environment variables, explicit workflow paths, and an exact approval phrasing to say to the user. It stops short of the 5 anchor because no example command invocation (e.g. a sample search) or inline sample record is given — the worked example is delegated to another skill's file and to --help.

4 / 5

Workflow Clarity

The reading sequence is explicit ("Read a hit's INDEX row first. Read an active or superseded record's document before treating it as binding"), the trigger-to-workflow table clearly routes create/update paths, and the approval gate is an explicit checkpoint ("Never create a decision document without explicit user approval"). The 5 anchor is not reached because the "check" action is listed but never prescribed as a validation step after create/update, and the actual step sequences are delegated to workflow files.

4 / 5

Progressive Disclosure

The SKILL.md itself is a well-organized ~50-line overview delegating detail to "decisions --help" and clearly signaled one-level references, which would merit a 4-5 — but the referenced bundle files (workflows/create-decision.md, workflows/update-decision.md, schemas/decision-format.md, templates/decision-entry.md, templates/index-row.md) are absent from the actual bundle, which contains only scripts/decisions and scripts/lib/kendex-env.sh. Scoring against the real bundle structure, the broken reference chain leaves navigation incomplete, fitting the 3 anchor better than the 4 ("minor organization gaps").

3 / 5

Total

15

/

20

Passed

Description

78%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 concise, specific description that names a distinct artifact and three concrete operations, with "Load to..." providing explicit trigger guidance. Its main gaps are missing common synonyms ("ADR", "decision log") and the absence of an explicit user-side "Use when..." clause, which keep it just short of exemplary.

DimensionReasoningScore

Specificity

"Load to create, search, or supersede an architecture decision record" names the artifact and lists three concrete actions ("create, search, or supersede"), matching the anchor for several specific actions with minor gaps; it is not comprehensive (list/get/check and INDEX management are unmentioned) so not a 5, and it exceeds the 1-2 actions of the 3 anchor.

4 / 5

Completeness

The 'what' is clear (create, search, supersede decision records) and "Load to create..." functions as equivalent explicit trigger guidance stating when to load the skill, so the missing-'Use when' cap does not apply; however the trigger could be more explicit with user-side phrases (e.g. "Use when the user asks to record or revisit an architectural decision"), matching the 4 anchor rather than the 5.

4 / 5

Trigger Term Quality

The terms "architecture decision record", "create", "search", and "supersede" are natural phrases a user would say, giving good keyword coverage, but common variations are missing — most notably the abbreviation "ADR" and "decision log" — so it falls short of the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"architecture decision record" is a distinct niche term with operations (create, search, supersede) unlikely to fire for unrelated skills; it is more distinct than the 4 anchor's example ("Works with PDF and Word document files") and fits the clear-niche, minimal-conflict 5 anchor.

5 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/decider/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.