CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

architect

Settle types and module shape before cross-boundary code — competing designs explored in parallel, compared on API surface and invariants, decision recorded with rejected alternatives and an accepted-deviations register.

Quality

75%

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 ./skills/architect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an exemplary lean, directive instruction skill with a clear when-to-use/not-to-use split and a well-sequenced five-step workflow. Its main defects are an unlinked bundle — both reference files would go undiscovered by a reader of SKILL.md alone — and implicit rather than explicit checkpoints in the workflow.

Suggestions

Link the bundle files at their point of use: in step 3 cite [design-red-flags.md](references/design-red-flags.md) for comparison criteria and in step 4 cite [rationale-template.md](references/rationale-template.md) as the record format.

Make checkpoints explicit in the workflow, e.g. 'Each design must state how every named invariant is preserved; if it cannot, it is rejected' as a gate in step 3.

Clarify the 'oh-my-claudecode:architect' subagent dispatch with a fallback (e.g. plain parallel subagents) so the workflow is executable in environments without that specific agent.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout ('Design before steel', 'Types before wiring; data shapes before functions that move them') with zero padding and no explanation of concepts Claude already knows — every token earns its place, matching anchor 5 rather than the 'minor trims' of anchor 4.

5 / 5

Actionability

Guidance is concrete for an instruction-only skill: dispatch named subagents, each producing 'the core types, the module boundary, the API surface', with enumerated comparison criteria and specified decision-record contents. Minor gaps keep it at anchor 4 rather than 5 — the body never points to the actual rationale template, and 'dispatch oh-my-claudecode:architect subagents' presumes a specific agent setup without fallback guidance.

4 / 5

Workflow Clarity

The five Workflow steps are clearly sequenced with named deliverables and a tie-break rule, and the operation is not destructive or batch, so no validation cap applies. It sits at anchor 4 rather than 5 because checkpoints are implicit (e.g. comparison criteria in step 3, the deviations register in step 4) rather than explicit validation steps with feedback loops.

4 / 5

Progressive Disclosure

The body itself is short and well-sectioned, but scoring against the actual bundle: references/design-red-flags.md ('Use during comparison of competing designs') and references/rationale-template.md ('Fill during the decision phase') are orphaned — neither path is mentioned anywhere in the body, so navigation to them is missing. This matches anchor 3 ('references present but not clearly signaled'); the under-50-lines exception for a 5 does not apply because external references exist and are clearly needed.

3 / 5

Total

16

/

20

Passed

Description

63%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 is highly specific and third-person, laying out the full design-exploration workflow in concrete terms, and it occupies a distinct niche. Its weakness is trigger guidance: there is no 'Use when...' clause and the vocabulary is designer jargon rather than the natural phrases a user would say, so both completeness and trigger-term quality are capped.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a change adds a module, changes a signature other files call, or the user asks for a design before implementation.'

Add natural-language synonyms users actually say — 'design this', 'architecture', 'API design', 'module structure' — alongside the current jargon terms like 'invariants' and 'accepted-deviations register'.

Soften insider terminology ('accepted-deviations register', 'cross-boundary code') or pair each with a plain-language equivalent so the description reads naturally to non-expert users.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'Settle types and module shape', 'competing designs explored in parallel', 'compared on API surface and invariants', 'decision recorded with rejected alternatives' — covering the workflow comprehensively, matching the anchor for comprehensive concrete actions rather than the 'minor gaps' of 4.

5 / 5

Completeness

The 'what' is explicit and concrete, but the only 'when' is 'before cross-boundary code' — a temporal position in the workflow rather than an explicit trigger clause. Per the judging guidelines, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3; anchor 4 requires both what and when with the when merely imprecise.

3 / 5

Trigger Term Quality

Keywords like 'types', 'module shape', 'competing designs', and 'API surface' are relevant but lean toward design jargon; natural user phrasings such as 'design this', 'architecture', or 'before you build' are missing, fitting the anchor for some relevant keywords missing common variations. Anchor 4 would require noticeably fuller natural-term coverage, which is absent.

3 / 5

Distinctiveness Conflict Risk

The pre-implementation design-exploration niche with rejected-alternative decision records is mostly distinct from other skills, with only minor overlap risk against a generic review or planning skill — matching anchor 4. Anchor 5 would require trigger phrases that make the niche unmistakable, which the jargon-tilted description does not fully supply.

4 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/architect/SKILL.md

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.