CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

architecture-deepener

Identifica melhorias estruturais e fronteiras arquiteturais. Trigger em: "deepening", "deep module", "shallow module", "refactor architecture", "improve architecture", "consolidate modules", "agent-friendly codebase", "AI-navigable", "module depth", "melhorar a arquitetura", "fronteiras de domínio", "estado compartilhado".

Quality

70%

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/38-architecture-deepener/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 delivers a well-structured, genuinely domain-specific process with concrete heuristics, an output template, and a YAML gate format — strong actionability and workflow clarity for an instruction-only skill. Its weaknesses are verbosity in re-explaining familiar architecture concepts and a monolithic single-file layout with inlined glossary/lens content and dangling references to files that don't exist in the bundle.

Suggestions

Move the glossary and 'Lentes Adicionais' sections into a references/ file (e.g. references/language.md, the acknowledged equivalent of LANGUAGE.md) and link to it one level deep, keeping SKILL.md as a lean overview — this also fixes the dangling docs/skill-guides references.

Trim the Lenses section to only the skill-specific reframing (depth/deletion test/locality mappings) and cut re-explanations of REST vs messaging vs RPC, HATEOAS, SRP, and layer-vs-tier that Claude already knows.

Add an explicit mid-process checkpoint in Fase 1/Grilling (e.g., what to confirm with the user before writing candidates or before adding terms to CONTEXT.md) to complement the existing post-implementation test checkpoint.

DimensionReasoningScore

Conciseness

Much of the ~315-line body is genuinely additive (custom glossary with 'use exatamente — consistencia e o ponto', detection-heuristics table, output template), but the 'Lenses Adicionais' section re-explains concepts Claude already knows — SRP ('uma razao para mudar'), REST vs messaging vs RPC trade-offs, a full HATEOAS paragraph, layer-vs-tier definitions — matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'. Not a 2 because these are explicitly reframed through the skill's own vocabulary rather than being pure padding.

3 / 5

Actionability

Guidance is largely executable: a canonical fitness-functions YAML schema with a concrete dep-cruiser example, a copy-paste output template for candidates, and a symptom→suspeita→acao heuristics table, matching 'Mostly executable guidance; concrete code or commands with minor gaps'. Not a 5 because several steps remain abstract — 'explore organicamente e anote onde voce sente friccao' and the grilling loop give direction but no concrete procedure, and referenced guides (docs/skill-guides/architecture-deepening.md) do not exist in the bundle.

4 / 5

Workflow Clarity

The three phases (Explore → Apresentar candidatos → Grilling loop) are clearly sequenced with inputs, outputs, pre-requisites, and an explicit post-implementation checkpoint ('execute os testes dos contratos preservados… Uma falha pede investigação') that includes failure triage, matching 'Clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because the Explore and Grilling phases lack internal checkpoints, and several handoff/integration steps (skills 23/28/33/37) depend on external skills without verification of their availability.

4 / 5

Progressive Disclosure

Section structure is good (headers, tables, clear navigation), but no bundle files exist while the body references external paths (docs/skill-guides/*.md, policies/*.md, examples/architecture-decisions.md) that are not resolvable within the skill, and ~100 lines of glossary + lenses are inlined that clearly belong in a separate reference file — the skill itself admits this ('docs/skill-guides/architecture-language.md (a criar conforme demanda) — glossario completo'). This matches 'Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

65%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 pairs a clear, bilingual trigger list with a well-defined architecture niche, giving it solid 'when' guidance and distinctiveness. Its main weakness is a vague 'what' — 'identifica melhorias estruturais' names no concrete actions or outputs, leaving the skill's actual deliverables unstated.

Suggestions

Replace 'Identifica melhorias estruturais e fronteiras arquiteturais' with concrete actions and outputs, e.g. 'Identifica módulos shallow via deletion test e propõe candidatos de deepening priorizados em _architecture_review/, com handoff para Migration & Refactor'.

Trim insider jargon from the trigger list ('deepening', 'AI-navigable', 'deep module') in favor of phrases users naturally say, keeping the natural bilingual terms like 'melhorar a arquitetura' and 'consolidate modules'.

DimensionReasoningScore

Specificity

The description only states "Identifica melhorias estruturais e fronteiras arquiteturais" — it names the architecture-improvement domain but the single action ('identifica melhorias') is generic, matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete actions (e.g., applies deletion test, proposes prioritized candidates, generates fitness-functions.yml) are listed, and not a 1 because the domain is clearly named.

2 / 5

Completeness

It has an explicit 'when' ("Trigger em: …" with concrete trigger phrases, satisfying the equivalent-trigger-guidance requirement) and a 'what' ("Identifica melhorias estruturais e fronteiras arquiteturais"), matching 'Has both what and when' but above the anchor-4 example because the when is more explicit. It is not a 5 because the 'what' is terse and high-level — it does not concretely state what the skill produces (candidate list, fitness-functions.yml, ADR handoff).

4 / 5

Trigger Term Quality

The trigger list has good natural-term coverage in two languages — "refactor architecture", "improve architecture", "consolidate modules", "melhorar a arquitetura", "estado compartilhado" — matching 'Good keyword coverage; a few natural terms missing'. It is not a 5 because several triggers ("deep module", "shallow module", "AI-navigable", "deepening") are insider jargon a user would rarely say spontaneously.

4 / 5

Distinctiveness Conflict Risk

Triggers like "deep module", "shallow module", "module depth", "fronteiras de domínio" carve a fairly distinct architecture-deepening niche with minimal conflict risk, matching 'Mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because generic triggers ("refactor architecture", "improve architecture") could fire for general refactoring or code-review skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/38-architecture-deepener/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.