sdd-onboard

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

Quality

57%

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

52%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 skill is well-sequenced with clear phase checkpoints and good section structure, but it is noticeably verbose due to scripted narration blocks and delegates concrete execution to sibling skills rather than inlining actionable steps. Tightening the narration and inlining key formats would materially raise quality.

Suggestions

Replace the scripted 'narration' code-fence blocks with short directives (e.g., 'In 1-3 sentences, explain the phase goal') instead of full suggested dialogue, cutting many tokens.

Inline a minimal concrete example of each phase artifact format (proposal/spec/design/tasks) or link to a single bundled reference, rather than only deferring to sibling skills' formats.

Trim concept restatements like 'This is the moment where specs pay off — they tell us exactly what to check' to one-line operational guidance.

Dimension	Reasoning	Score
Conciseness	The body is padded with scripted conversational narration in code fences ('Welcome to SDD! I'll walk you through...') and restates concepts Claude already knows ('This is the moment where specs pay off'), adding tokens that do not teach new behavior.	2 / 5
Actionability	The change-selection criteria are concrete, but each phase defers execution to sibling skills ('Run sdd-explore behavior inline', 'following sdd-propose format') without inlining the actual steps, formats, or commands needed to execute the phase.	3 / 5
Workflow Clarity	A clear 10-phase sequence is laid out with explicit checkpoints (ask before continuing past Phase 3, STOP if blocked) and a verify/archive step, though some validation guidance is implicit rather than enumerated.	4 / 5
Progressive Disclosure	No bundle files are present, but the body is sectioned into well-organized phases; cross-references to sibling skills and sdd-phase-common.md are clearly signaled, with only minor inlining of narration that could be trimmed.	4 / 5
	Total	13 / 20 Passed

Description

62%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 states a clear purpose and an explicit trigger, but the trigger is phrased for the orchestrator rather than as natural user language, and the capability list is generic rather than enumerated. It is competent but could be sharpened with concrete actions and user-facing trigger terms.

Suggestions

Enumerate concrete actions in the description (e.g., 'explore the codebase, write proposal/specs/design/tasks, implement, verify, and archive the change') instead of relying on 'the full SDD cycle'.

Add natural user-facing trigger language alongside the orchestrator trigger (e.g., 'Use when the user wants a guided first SDD cycle on their real codebase').

Name the artifact outputs (proposal.md, specs, design.md, tasks.md) so the capability is concrete and distinguishable from sibling SDD skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('SDD workflow on the real codebase') and one concrete action ('Walk users through') but does not enumerate the concrete actions the cycle performs, instead deferring to 'the full SDD cycle'.	3 / 5
Completeness	Clearly states what the skill does ('Walk users through the SDD workflow') and when it runs ('Trigger: orchestrator launches onboarding for the full SDD cycle'), though the 'when' is system-triggered rather than user-need phrasing.	4 / 5
Trigger Term Quality	Includes an explicit 'Trigger:' clause but it names a system actor ('orchestrator launches onboarding') rather than natural user phrases, and lacks synonyms or variations of SDD onboarding.	3 / 5
Distinctiveness Conflict Risk	The 'SDD onboarding' niche and 'full SDD cycle' framing are fairly distinct from other skills, with only minor overlap risk against sibling SDD skills.	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
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: a245f26

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