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 ./.agent/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 body is a well-sequenced, actionable onboarding workflow with concrete commands and templates and good checkpointing, but it is monolithic and verbose for a single SKILL.md with no progressive disclosure via separate files.

Suggestions

Move the command-reference table and the artifact templates (proposal/spec/design/tasks skeletons) into reference files under ./references/ and link to them, reducing the SKILL.md to an overview plus phase sequence.

De-duplicate the command-reference table (it appears in both the Recap and the Quick-exit section) into a single shared reference.

Add an explicit verification feedback loop before the Archive phase (e.g. run /opsx:verify and only archive when it passes) to push workflow_clarity toward 5.

DimensionReasoningScore

Conciseness

Mostly actionable scripted material rather than concept over-explanation, but ~540 lines with heavy display templates and a duplicated command-reference table that could be tightened.

3 / 5

Actionability

Provides concrete executable openspec/git commands and concrete artifact templates (Why/What Changes, WHEN/THEN/AND scenarios, Goals/Non-Goals); placeholders and heuristic codebase scanning leave minor gaps.

4 / 5

Workflow Clarity

Clear 11-phase sequence with explicit PAUSE checkpoints, a preflight init-validation gate, guardrails, and a task checklist, but lacks an in-skill verify-before-archive feedback loop.

4 / 5

Progressive Disclosure

Single monolithic ~540-line file with no bundle files and no references; command reference, artifact templates, and exit scripts are all inlined and could be split out.

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 (guided onboarding through a full OpenSpec workflow cycle) but omits any explicit "Use when..." trigger guidance, capping its completeness. It is reasonably distinct and specific but light on natural trigger terms.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when the user wants to learn OpenSpec, get started with OpenSpec, or be onboarded to the OpenSpec workflow."

Broaden trigger terms with user-natural synonyms like "get started", "learn", or "walk me through" alongside "onboarding".

List 1-2 more concrete capabilities (e.g. "creates proposal, specs, design, and tasks artifacts") to raise specificity from 3 toward 4-5.

DimensionReasoningScore

Specificity

Names the OpenSpec-onboarding domain plus 2-3 actions ("walk through a complete workflow cycle", "with narration", "real codebase work") but is not a comprehensive action list.

3 / 5

Completeness

Has a clear "what" but no explicit "Use when..." trigger clause; the "when" is only weakly implied, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

"onboarding" is a natural user term, but coverage is thin and missing common variations like "get started" or "learn OpenSpec".

3 / 5

Distinctiveness Conflict Risk

"Guided onboarding for OpenSpec" is a clear niche with only minor overlap risk against sibling /opsx workflow skills, though it lacks a distinct trigger phrase.

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 (550 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
Draculabo/AntigravityManager
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.