CtrlK
BlogDocsLog inGet started
Tessl Logo

sdd-design

Create the SDD technical design and architecture approach. Trigger: orchestrator launches design for a change.

56

Quality

65%

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 ./internal/assets/skills/sdd-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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-organized, actionable design-phase workflow with a concrete document template, explicit persistence contract, and a properly gated threat-matrix reference. It is efficient and clearly sequenced, with only minor conciseness and validation-loop gaps.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, with a focused design template and tight rules; minor boilerplate repetition (e.g., persistence contract restated across steps) could be trimmed.

4 / 5

Actionability

Provides a concrete, copy-paste-ready design document template, explicit file paths, persistence topic keys, and a return-envelope format; minor gaps come from references to shared docs not bundled here.

4 / 5

Workflow Clarity

Clear five-step sequence with a mandatory persistence checkpoint, applicability-gated threat matrix, and explicit blocking-question handling; lacks a formal validate->fix->retry loop but gates progression well.

4 / 5

Progressive Disclosure

Well-structured body with a single one-level-deep reference (references/threat-matrix.md, confirmed to exist) that is clearly signaled and conditionally loaded; minor organization gaps from reliance on external shared docs.

4 / 5

Total

16

/

20

Passed

Description

55%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 the skill's purpose and includes an explicit trigger, but the trigger is orchestration-internal jargon rather than natural user language and the capability list is thin. It is distinguishable but would benefit from concrete artifact outputs and user-natural phrasing.

Suggestions

Add concrete artifact outputs to the description (e.g., 'produce a design.md capturing architecture decisions, data flow, file changes, and testing strategy').

Replace the mechanical trigger with natural trigger phrases a user or orchestrator would actually say (e.g., 'Use when producing the technical design for an SDD change').

Mention key deliverables (design document, architecture decisions, threat matrix) to improve specificity and completeness.

DimensionReasoningScore

Specificity

Names the SDD design domain and one-to-two concrete actions ('Create the SDD technical design and architecture approach'), but coverage is not comprehensive — no enumeration of the design artifacts produced.

3 / 5

Completeness

States both what it does (create technical design and architecture approach) and when it runs (the explicit Trigger clause), but the 'when' is an internal launch condition rather than a natural user-facing trigger.

4 / 5

Trigger Term Quality

The trigger ('orchestrator launches design for a change') is mechanical orchestration jargon, not natural phrases a user would say; only one or two generic keywords are present.

2 / 5

Distinctiveness Conflict Risk

The SDD technical-design sub-agent niche is fairly distinct; minor overlap risk with sibling sdd-* phase skills but unlikely to trigger for the wrong skill.

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
Gentleman-Programming/gentle-ai
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.