CtrlK
BlogDocsLog inGet started
Tessl Logo

openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

62

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-new-change/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a tight, actionable workflow with concrete commands, an explicit stop checkpoint, and clear guardrails, well-organized into navigable sections. Minor gains are possible in tightening prose and making the first-artifact resolution fully copy-paste ready.

DimensionReasoningScore

Conciseness

Largely efficient with concrete commands and no over-explanation of concepts Claude knows, though a few sentences (e.g., "This creates a scaffolded change..." and the dense store-selection paragraph) could be trimmed slightly.

4 / 5

Actionability

Provides mostly executable bash commands with JSON fields to parse, but the first-artifact-id resolution ("check the status output to find the first artifact") leaves a minor copy-paste gap rather than a fully ready path.

4 / 5

Workflow Clarity

A clear numbered 1-6 sequence with an explicit STOP checkpoint and guardrails covering error cases; no validate-fix-retry loop is present, but the workflow is non-destructive scaffolding so the destructive-ops cap does not bind.

4 / 5

Progressive Disclosure

No bundle files exist; the body is a flat, well-organized set of sections (Store selection, Input, Steps, Output, Guardrails) with no nested references, satisfying the simple-skill exception for well-organized content.

5 / 5

Total

17

/

20

Passed

Description

66%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 clearly states the skill's purpose and includes an explicit use-trigger, with a distinctive OpenSpec-specific niche. It is held back by thin action coverage and generic trigger phrasing rather than comprehensive user-natural synonyms.

Suggestions

Expand the action list beyond "Start" to mention concrete outcomes like scaffold the change directory, show artifact status, and fetch the first artifact template.

Add user-natural synonyms such as "change request", "spec change", or "proposal" alongside "feature, fix, or modification" to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("OpenSpec change") and one concrete action ("Start a new OpenSpec change") but offers no comprehensive list of specific actions, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

Provides both a clear "what" ("Start a new OpenSpec change using the experimental artifact workflow") and an explicit "when" clause, though the trigger ("structured step-by-step approach") is somewhat generic rather than fully concrete.

4 / 5

Trigger Term Quality

Includes relevant terms ("new feature, fix, or modification", "new OpenSpec change") but lacks common user synonyms like "change request", "spec", or "proposal", fitting the missing-variation anchor.

3 / 5

Distinctiveness Conflict Risk

A clear niche tied to the OpenSpec artifact workflow with distinct, product-specific triggers means minimal conflict risk with unrelated skills.

5 / 5

Total

15

/

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
Fission-AI/OpenSpec
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.