openspec-onboard

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/openspec-onboard/SKILL.md

Quality

Content

65%

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

The skill is highly actionable with a well-sequenced, checkpointed onboarding workflow, but it is verbose and monolithic with no external references and a missing verification gate before archiving. Splitting reference material into bundle files and adding a verify step would raise the weaker dimensions.

Suggestions

Add a verification checkpoint (e.g. run '/opsx:verify' or re-check tasks.md) before the 'openspec archive' step in Phase 10.

Move the command reference table and the proposal/spec/design/tasks templates into a references/ file (e.g. references/templates.md) linked one level deep, reducing the main body.

De-duplicate the command reference (it appears in Phase 11 and again in the Graceful Exit section) and trim scripted dialogue to reduce token weight.

Dimension	Reasoning	Score
Conciseness	The body is mostly task-specific instruction rather than generic concept padding, so it avoids the worst verbosity trap; however, at ~550 lines it carries heavy scripted dialogue and repeats the command reference twice, so it could be tightened without losing clarity.	2 / 3
Actionability	It provides concrete, executable commands ('openspec status --json', 'openspec new change', 'openspec archive'), real file-structure diagrams, and copy-paste-ready templates with clearly parameterized placeholders, so guidance is fully actionable.	3 / 3
Workflow Clarity	Phases 1-11 are clearly sequenced with explicit PAUSE checkpoints and a preflight validation, and strong sequencing alone would warrant 3; however, there is no verification step before the destructive 'openspec archive' move despite '/opsx:verify' existing, and the missing validate-before-archive feedback loop for a destructive operation triggers the rubric cap of 2.	2 / 3
Progressive Disclosure	No bundle files exist and the entire ~550-line skill is a single monolithic file; the command reference table and artifact templates are inline content that would be better split into one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 conveys the skill's purpose at a high level but stays abstract and omits explicit invocation triggers. Adding a 'Use when...' clause with concrete trigger terms would lift specificity, completeness, and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when onboarding to OpenSpec, learning the OpenSpec workflow, or running a first change cycle.'

Replace the abstract 'workflow cycle' phrasing with concrete actions the skill performs (e.g. 'create a change, draft proposal/specs/design/tasks, implement, and archive').

Include natural trigger variations users would actually say ('teach me OpenSpec', 'walk me through my first OpenSpec change').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Guided onboarding for OpenSpec') and an action ('walk through a complete workflow cycle with narration and real codebase work'), but 'workflow cycle' is abstract rather than a list of multiple concrete actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It states what the skill does (guided onboarding, walkthrough) but provides no 'Use when...' clause or equivalent explicit trigger for when to invoke it, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	It includes some relevant natural terms ('onboarding', 'OpenSpec', 'workflow cycle') a user might say, but lacks common variations and has no explicit trigger phrasing, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	Tying it to 'OpenSpec' gives it a niche, but 'workflow cycle with narration and real codebase work' is generic enough to overlap with sibling OpenSpec skills (explore, new, apply), so it is not fully distinct.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (550 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-onboard/SKILL.md
Commit: be872c1

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.