openspec-onboard

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

Quality

69%

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 ./eval/local/skills/benchmarks/dependency/openspec/openspec-onboard/SKILL.md

Quality

Content

77%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 highly actionable, well-sequenced tutorial with concrete commands, templates, validation checkpoints, and graceful exit handling. Its weaknesses are redundancy (duplicated command reference tables, padded narration) and the absence of any progressive disclosure — everything is inlined in a single long file.

Suggestions

Deduplicate the command reference tables: define them once and reference them from the Graceful Exit section instead of repeating them verbatim.

Move the full command reference and artifact templates into a references/ file and link to it, keeping SKILL.md as a lean orchestration guide.

Trim celebratory narration ('Congratulations!', recap text) to reduce token overhead without losing the teaching flow.

Dimension	Reasoning	Score
Conciseness	The verbatim display templates mostly earn their place in a tutorial skill, but the command reference tables are duplicated in full in both Phase 11 and the Graceful Exit section, and the recap/congratulations narration adds padding that could be tightened.	3 / 5
Actionability	Commands are copy-paste ready ('openspec --version', 'openspec new change "<derived-name>"', 'openspec archive "<name>"', mkdir with platform variants) and full artifact templates with concrete save paths cover the common cases; placeholders are appropriately dynamic for user-specific content.	5 / 5
Workflow Clarity	Eleven numbered phases are clearly sequenced with explicit PAUSE checkpoints, a preflight CLI validation step, a scope guardrail with fallback options, and graceful exit handling with resume paths — feedback loops and checkpoints are explicit throughout.	5 / 5
Progressive Disclosure	Section headers organize the phases well, but there are no bundle files at all: roughly 550 lines are fully inlined, and the duplicated command reference tables are content that belongs in a single dedicated section or separate reference file.	3 / 5
	Total	16 / 20 Passed

Description

61%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 communicates what the skill does and uses fairly natural trigger language, but it lacks an explicit 'when to use' clause and does not enumerate the concrete workflow steps. It is distinctive within the OpenSpec ecosystem though not fully conflict-free against sibling commands.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user is new to OpenSpec, asks for a tutorial, or wants to be walked through their first change cycle.'

Enumerate the concrete cycle steps (e.g. 'create a change, draft proposal, specs, design, and tasks, implement, then archive') to raise specificity.

Include natural synonyms such as 'tutorial', 'getting started', or 'first change' to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (OpenSpec onboarding) and 1-2 concrete actions ('walk through a complete workflow cycle', 'real codebase work') but does not enumerate the specific cycle steps (proposal, specs, design, tasks, archive), so coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clear (guided onboarding walking a complete workflow cycle with narration and real codebase work), but there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	'Guided onboarding', 'walk through', and 'workflow cycle' are natural phrases a user would say, giving good keyword coverage, though common variations like 'tutorial', 'getting started', or 'first change' are missing.	4 / 5
Distinctiveness Conflict Risk	The OpenSpec onboarding niche is mostly distinct with clear triggers, but it has minor overlap risk with closely related sibling commands (/opsx:propose, /opsx:new) that run the same cycle for experienced users.	4 / 5
	Total	14 / 20 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 (555 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: rpamis/comet
Path: eval/local/skills/benchmarks/dependency/openspec/openspec-onboard/SKILL.md
Commit: 899d1fb

Reviewed: 7 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.