CtrlK
BlogDocsLog inGet started
Tessl Logo

openspec-onboard

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

52

Quality

58%

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-onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is a well-sequenced, actionable guided tutorial with clear phase checkpoints and concrete commands. Its main weaknesses are verbosity from duplicated reference tables and the absence of any progressive disclosure via bundled reference files despite its length.

Suggestions

Extract the command reference tables (duplicated in the Recap and Graceful Exit sections) into a single REFERENCES.md and link to it from both places to remove duplication.

Add an explicit verification checkpoint in Phase 9 (e.g. run `openspec validate --change <name>` or invoke `/openspec-verify-change`) before archiving.

Move the large displayed monologue templates into a bundled templates file referenced one level deep, keeping SKILL.md as a lean overview of the phase rhythm.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but it repeats content (the command reference table appears twice) and some displayed templates could be tightened, so it is not fully lean.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready commands with --store handling, JSON parsing, and resolvedOutputPath usage; minor gaps remain in placeholder-filled template strings.

4 / 5

Workflow Clarity

A clear 11-phase sequence uses an explicit EXPLAIN/DO/SHOW/PAUSE pattern with checkpoint pauses and a preflight install check; a minor gap is the lack of an explicit verification step after the implementation phase.

4 / 5

Progressive Disclosure

The skill is a single ~550-line monolithic file with no external references; while section headers provide structure, content that could live in separate files (e.g. command reference, templates) is fully inlined.

3 / 5

Total

14

/

20

Passed

Description

53%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 what the skill does but omits any explicit trigger guidance for when Claude should invoke it. Adding a 'Use when...' clause with natural trigger phrases would materially raise completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user is new to OpenSpec, wants a walkthrough of the workflow, or asks to learn/onboard to OpenSpec.'

Include common synonyms and natural phrasings users might say ('learn OpenSpec', 'first time with OpenSpec', 'walk me through a change').

List a couple more concrete actions (e.g. 'create a change, draft proposal/specs/design/tasks, implement, and archive') to broaden specificity coverage.

DimensionReasoningScore

Specificity

Names the OpenSpec onboarding domain and 1-2 concrete actions ('walk through a complete workflow cycle', 'narration', 'real codebase work'), but coverage is not comprehensive.

3 / 5

Completeness

Has a clear 'what' (guided onboarding walking through a workflow cycle) but no explicit 'when'/'Use when...' clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Contains relevant keywords like 'onboarding', 'OpenSpec', and 'workflow cycle' but lacks the natural trigger phrases a user would actually say and misses common synonyms.

3 / 5

Distinctiveness Conflict Risk

Targets a distinct niche (OpenSpec onboarding) with minimal conflict risk, though it could overlap slightly with other OpenSpec workflow skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (561 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.