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.

89

1.04x
Quality

Does it follow best practices?

Impact

69%

1.04x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

An actionable, well-structured workflow skill with concrete commands and clear validation loops. Its main weakness is redundancy between the intro, the description, and the closing guidelines section, which costs some token efficiency.

Suggestions

Remove the opening paragraph (lines 12-19) since it restates the frontmatter description and the artifact list is covered later; let the Steps section carry the workflow.

Merge the "Artifact Creation Guidelines" section into step 4a or delete it, as it duplicates the context/rules/dependency/template guidance already specified there.

Drop the standalone "When ready to implement, run /opsx:apply" line and the mid-document horizontal rule, keeping only the final Output prompt that already mentions /opsx:apply.

DimensionReasoningScore

Conciseness

Mostly efficient procedural guidance, but the opening paragraph ("Propose a new change - create the change and generate all artifacts in one step. I'll create a change with artifacts:...") repeats the frontmatter description, and the "Artifact Creation Guidelines" section re-states the context/rules/dependency notes already given in step 4a.

2 / 3

Actionability

Fully executable commands throughout — `openspec new change`, `openspec status --change --json`, `openspec instructions <artifact-id> --change --json` — plus the specific JSON fields to parse, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

A clearly sequenced five-step process with an explicit feedback loop (re-run `openspec status --json` after each artifact) and validation checkpoints ("Verify each artifact file exists after writing before proceeding to next", check all applyRequires are done).

3 / 3

Progressive Disclosure

No bundle files exist and none are referenced; the body is a single self-contained doc organized into well-signaled sections (Input, Steps, Output, Artifact Creation Guidelines, Guardrails) with no nested references, which is appropriate for this skill.

3 / 3

Total

11

/

12

Passed

Description

100%

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 tight, third-person description that clearly states what the skill does and when to invoke it, listing concrete deliverables with natural trigger terms. It mirrors the strongest reference examples in the rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — "a complete proposal with design, specs, and tasks ready for implementation" — matching the score-3 anchor that enumerates specific actions/outcomes.

3 / 3

Completeness

Explicitly answers both what ("Propose a new change with all artifacts generated") and when via a "Use when the user wants to..." trigger clause, hitting the score-3 anchor.

3 / 3

Trigger Term Quality

Natural phrasing users would say — "describe what they want to build", "proposal", "design, specs, and tasks" — giving good coverage of common variations rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The openspec change-proposal niche with specific artifact vocabulary (proposal/design/specs/tasks, implementation) is distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.