sdd-onboard

Walk users through the SDD workflow on the real codebase. Trigger: orchestrator launches onboarding for the full SDD cycle.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./internal/assets/skills/sdd-onboard/SKILL.md

Quality

Content

77%

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 ten-phase walkthrough with explicit validation checkpoints and ready-to-use narration scripts. Its main weakness is token efficiency and the lack of progressive disclosure, since everything lives inline in one long file with no bundled detail references.

Suggestions

Tighten the repeated narration quote blocks into a compact template (e.g. one reusable "narration pattern" with per-phase one-liners) to cut length without losing the teaching cues.

Move the per-phase detail (proposal/spec/design/tasks formats and the criteria checklist) into bundled reference files and link to them one level deep from a lean overview, improving progressive disclosure.

Inline or bundle the referenced sdd-phase-common.md "Section D" envelope so the skill is self-contained rather than depending on an external shared file.

Dimension	Reasoning	Score
Conciseness	The ~220-line body is mostly efficient and avoids explaining concepts Claude already knows, but the repeated narrated quote blocks add length that could be tightened, fitting the level-2 anchor.	2 / 3
Actionability	It gives concrete phase-by-phase narration scripts, an explicit criteria checklist for choosing a change, and points to specific formats (sdd-propose, sdd-spec, sdd-design, sdd-tasks), matching the fully-actionable level-3 anchor.	3 / 3
Workflow Clarity	The ten phases are clearly sequenced with explicit checkpoints (ask before continuing past Phase 3, STOP on failure, a dedicated Verify phase), matching the level-3 anchor with validation steps and error-recovery feedback.	3 / 3
Progressive Disclosure	It is a single monolithic file over 50 lines with all per-phase detail inline and no bundled reference files, and its references to sdd-* skills and _shared/sdd-phase-common.md are external rather than clearly signaled one-level-deep bundle links.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 cleanly answers both what and when via an explicit Trigger clause, but its capability list is thin and its trigger terms are jargon-heavy rather than natural user phrasing. It is distinct enough to avoid most conflicts but overlaps with the broader SDD skill family.

Suggestions

Expand the action list beyond "walk users through" to concrete capabilities (e.g., scans the codebase for a small improvement, drafts proposal/specs/design/tasks, implements, verifies, and archives the change).

Soften trigger terms toward phrasing users/orchestrators naturally say, e.g. "Use when onboarding to SDD or running a guided first SDD cycle on a real codebase."

Add a disambiguating clause that separates this onboarding walkthrough from the individual sdd-explore/propose/spec/etc. skills it invokes.

Dimension	Reasoning	Score
Specificity	"Walk users through the SDD workflow on the real codebase" names the domain and the onboarding action, but does not list multiple specific concrete actions, matching the level-2 anchor rather than the multi-action level-3 example.	2 / 3
Completeness	It states both what it does (walk users through the SDD workflow on the real codebase) and an explicit when via the "Trigger:" clause, which is equivalent explicit trigger guidance and therefore not capped at 2.	3 / 3
Trigger Term Quality	"orchestrator launches onboarding for the full SDD cycle" supplies relevant keywords but leans on jargon (orchestrator, SDD cycle) and misses common natural variations, fitting the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The onboarding trigger carves out a niche, but it sits within a family of sdd-* skills (explore, propose, spec, etc.) with which it could still overlap, matching the level-2 anchor.	2 / 3
	Total	9 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: Gentleman-Programming/gentle-ai
Path: internal/assets/skills/sdd-onboard/SKILL.md
Commit: e01b114

Reviewed: about 14 hours 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.