CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-full-stack-architect

Full-stack extension skeleton and registration pattern. Use this skill when creating an extension that spans both API and Admin — the top-level component with Api.Extension and Admin.Extension entry points, shared domain layer, BuildParam declarations, and package structure. References webiny-api-architect and webiny-admin-architect for layer-specific details.

65

Quality

78%

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

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body with concrete code and clean cross-skill navigation. It loses points only on minor redundancy and the absence of explicit validation checkpoints in its construction workflow.

Suggestions

Tighten the BuildParam and Quick Reference sections to remove overlap with the Checklist and earlier code blocks, keeping the body leaner.

Add an explicit verification step to the Checklist (e.g., 'Confirm the extension builds and both entry points resolve with .js extensions') so the construction workflow has a concrete validation checkpoint.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code and no padding of concepts Claude already knows, but the BuildParam section and the Quick Reference repeat content already covered in the Checklist and code blocks, leaving room to tighten.

2 / 3

Actionability

Provides fully executable TSX/TS throughout — top-level component, BuildParam declaration, webiny.config.tsx consumption, and a shared domain class — with CORRECT/WRONG contrasts and bolded MUST rules that are copy-paste ready.

3 / 3

Workflow Clarity

A clear checklist sequences the build steps and bolded build-failure warnings act as implicit checkpoints, but there are no explicit validation or verification steps despite the scaffolding involving multiple coordinated files.

2 / 3

Progressive Disclosure

Well-organized into TL;DR, RULE, structure, component, shared layer, BuildParams, checklist, and quick reference, deferring layer-specific detail to sibling skills via consistently signaled one-level-deep '→ see webiny-X-architect' references.

3 / 3

Total

10

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both purpose and trigger while listing concrete structural components. The main gap is trigger-term naturalness, which leans on framework jargon over user-facing phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete structural elements — 'Api.Extension and Admin.Extension entry points, shared domain layer, BuildParam declarations, and package structure' — naming specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (full-stack extension skeleton and registration pattern) and 'when' (the 'Use this skill when creating...' clause), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Has a relevant natural trigger ('Use this skill when creating an extension that spans both API and Admin') but leans on specialized jargon (Api.Extension, BuildParam) rather than covering common natural variations a user would say.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — extensions spanning both API and Admin — and explicitly defers layer-specific detail to sibling skills, making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
webiny/webiny-js
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.