CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-decision-discipline

Right-size, ground, and gate SDLC decisions with SNC-sized depth, said-vs-assumed write-back, an evidence ledger, honest option cards, recorded approval, and self-review. Use when running brainstorm-feature, plan-feature, design-solution, or system-design-session.

Quality

80%

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/common/common-decision-discipline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-built instruction-only skill: dense, jargon-free of padding, with concrete formats, thresholds, and enums, a clear sectioned workflow with genuine validation gates, and clean one-level-deep referencing from the entry file. The main deficits are moderate redundancy between the policy sections and the Anti-Patterns/Red Flags sections, and bundle hygiene — orphaned reference files, an orphaned assets directory, and broken cross-bundle links.

Suggestions

Link the four orphaned reference files (brainstorm-evaluation.md, direction-quality-evaluation.md, explore-mode.md, research-spike.md) and the cost-record assets from SKILL.md's References section so they are discoverable from the entry point.

Fix or remove the broken cross-bundle links in decision-evidence-fidelity.md pointing at ../../common-tdd/references/quality-contract.md and ../../common-code-review/references/orchestration.md, which do not resolve in this bundle.

Consolidate the Anti-Patterns and Red Flags sections, which restate rules already stated in sections 1-6, to remove redundancy and recover token budget.

DimensionReasoningScore

Conciseness

The body is extremely dense with zero concept over-explanation and every line carrying a rule, but the Anti-Patterns and Red Flags sections largely restate constraints already given in sections 1-6 ("No unlabeled claims" restates the evidence-tagging rule; "No pending approval leakage" restates section 6), which is trimmable redundancy rather than the every-token-earns-its-place of anchor 5.

4 / 5

Actionability

For an instruction-only skill the guidance is mostly executable: a concrete SNC tier table, exact evidence tags ("confirmed(<path>)", "assumed", "unknown"), an approval enum ("approval: pending | approved(<who>, <YYYY-MM-DD>) | assumed-autonomous"), hard limits ("Review card ≤250 words", "batch max 3"), an exact reply phrase, and file pointers. It falls short of anchor 5 only because much of the guidance is policy constraints whose full copy-ready formats live in reference files rather than inline.

4 / 5

Workflow Clarity

Sections 1-7 form a coherent sequence (size → shared understanding → evidence → questions → options → approval → publication) with real checkpoints (pre-approval placeholder/contradiction/ambiguity check, "NOT RUN/not assessed is never PASS", "Deep requires independent check"). It sits below anchor 5 because the numbered sections read as policy areas more than an explicitly ordered procedure, and the correction loop after "Reply ok or corrections" is implicit.

4 / 5

Progressive Disclosure

The body links six one-level-deep reference files at their point of use plus a References section, and SKILL.md itself is a lean overview. However, scoring against the actual bundle reveals gaps beyond "minor": four of ten reference files (brainstorm-evaluation.md, direction-quality-evaluation.md, explore-mode.md, research-spike.md) are never linked from SKILL.md, the assets/ directory is reachable only through an unlinked file, and decision-evidence-fidelity.md contains broken cross-bundle links (../../common-tdd/…, ../../common-code-review/…).

4 / 5

Total

16

/

20

Passed

Description

80%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 strong description that explicitly states what the skill does and when to use it, with concrete mechanisms and precise, low-conflict triggers. Its main weakness is trigger-term coverage: it relies solely on sibling skill names rather than natural user phrasing, and its jargon-heavy mechanism list slightly limits how concrete the capabilities read.

Suggestions

Add natural-language trigger phrases users would actually say — e.g., "compare approaches", "weigh option trade-offs", "shape a design direction", "write a decision brief" — alongside the four skill names so the description matches requests that don't invoke those skills verbatim.

Soften or briefly gloss internal jargon such as "SNC-sized depth" and "said-vs-assumed write-back" (e.g., "complexity-tiered depth" and "restating what was said vs. what was assumed") so the named capabilities read concretely without bundle context.

DimensionReasoningScore

Specificity

Lists several concrete process actions — "Right-size, ground, and gate SDLC decisions" plus named mechanisms ("said-vs-assumed write-back", "an evidence ledger", "honest option cards", "recorded approval, and self-review") — but jargon like "SNC-sized depth" and "said-vs-assumed write-back" leaves minor gaps in concrete, self-describing coverage, placing it just below the comprehensive anchor 5.

4 / 5

Completeness

Clearly answers both parts: the "what" is explicit (right-size, ground, and gate decisions with the enumerated mechanisms) and the "when" is an explicit trigger clause naming four concrete invocation contexts, matching the anchor for both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

The only trigger terms are the four sibling skill names ("brainstorm-feature, plan-feature, design-solution, or system-design-session"), which are relevant but skip the natural phrases a user would say when needing decision discipline (e.g., "compare approaches", "trade-offs", "design brief", "decide between options"), matching the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear decision-governance niche (sizing, evidence, approval gating) and triggers on four precisely named skills, giving it distinct triggers with minimal conflict risk against generic skills.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-decision-discipline/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.