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.

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 executable commands, clear sequencing, an explicit stop point, and guardrails for error recovery. It respects Claude's competence and needs no external bundle files.

DimensionReasoningScore

Conciseness

The body is lean and procedural: numbered steps with executable commands and only OpenSpec-specific clarifications, with no padding explaining concepts Claude already knows.

3 / 3

Actionability

Provides concrete, executable commands (`openspec new change`, `openspec status`, `openspec instructions`) with exact flags and quoted arguments, ready to run.

3 / 3

Workflow Clarity

A clearly sequenced six-step process with an explicit STOP checkpoint, a status-verification step, and guardrails that serve as error-recovery feedback (invalid name, existing change).

3 / 3

Progressive Disclosure

Self-contained single-purpose skill with well-organized sections (Input, Steps, Output, Guardrails) and no need for external reference files; no nested references.

3 / 3

Total

12

/

12

Passed

Description

90%

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 concise, uses third-person voice, and clearly pairs a what-statement with an explicit 'Use when' trigger. Its only weakness is listing a single broad action rather than multiple concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('OpenSpec change', 'experimental artifact workflow') and a concrete action ('Start a new change') but does not enumerate multiple distinct concrete actions, matching the 'Names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

Clearly answers what it does ('Start a new OpenSpec change using the experimental artifact workflow') and when to use it via an explicit 'Use when the user wants to create a new feature, fix, or modification...' clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('create a new feature, fix, or modification') alongside the domain term, giving good coverage of phrasings users actually use.

3 / 3

Distinctiveness Conflict Risk

The 'OpenSpec change' and 'experimental artifact workflow' framing carves a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

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
PBH-BTN/PeerBanHelper
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.