CtrlK
BlogDocsLog inGet started
Tessl Logo

openspec-propose

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

85

1.04x
Quality

88%

Does it follow best practices?

Impact

69%

1.04x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 highly actionable with executable commands, a well-sequenced workflow including explicit validation checkpoints, and clean self-contained organization. Its only weakness is minor repetition of the context/rules guidance and a slightly redundant intro.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and no padding of concepts Claude already knows, but repeats the context/rules warning across two sections and includes a slightly redundant artifact-listing intro that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready bash commands (openspec new/status/instructions) with JSON field names, specific tool usage (AskUserQuestion, TodoWrite), and concrete output guidance covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sequence with sub-steps, explicit validation loop (re-run status until applyRequires done, verify file exists before proceeding), and a Guardrails section with feedback for the batch artifact-generation operation.

5 / 5

Progressive Disclosure

Self-contained single-purpose skill with no bundle files and well-organized section headers (Input, Steps, Output, Artifact Creation Guidelines, Guardrails), so the simple-skill exception applies.

5 / 5

Total

19

/

20

Passed

Description

83%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, complete, and uses natural trigger language with explicit 'Use when' guidance and concrete deliverables. It is slightly under maximal distinctiveness and trigger synonym coverage.

DimensionReasoningScore

Specificity

Names concrete deliverables ('design, specs, and tasks ready for implementation') and a clear action ('Propose a new change with all artifacts generated in one step'), listing several specific actions with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (propose a change generating all artifacts in one step) and 'when' ('Use when the user wants to quickly describe what they want to build and get a complete proposal').

5 / 5

Trigger Term Quality

Includes natural phrasings users would say ('describe what they want to build', 'proposal', 'design', 'specs', 'tasks') with good keyword coverage, though missing some common synonyms like 'spec out' or 'plan a feature'.

4 / 5

Distinctiveness Conflict Risk

The proposal/design/specs/tasks niche tied to implementation readiness is mostly distinct with only minor overlap risk against general planning skills, rather than a razor-sharp clear niche.

4 / 5

Total

17

/

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
arm/mlia
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.