CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

85%

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

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.

A well-structured, actionable architecture skill: concrete copy-paste code, an explicit context-detection rule, and clean delegation to sibling skills for layer details. Its main defect is an internal inconsistency between the ".ts/.tsx in every src prop" rule and the ".js in all import paths" rule/examples, which slightly undermines both actionability and trust in the guidance.

Suggestions

Resolve the src-prop extension contradiction: the RULE section requires `src={"/extensions/lead/src/index.ts"}` (`.ts`/`.tsx`) while all examples use `.js` paths and the checklist mandates ".js extensions in all import paths" — pick one convention or state explicitly when each applies.

Trim the cross-section redundancy (entry-point rule in RULE + Checklist + Quick Reference; BuildParam read guidance in both the section and Quick Reference) to move conciseness toward lean.

Move the full value-object example and/or BuildParam deep-dive into a references/ bundle file to keep SKILL.md a tighter overview.

DimensionReasoningScore

Conciseness

Efficient and dense — comparison table, tight rules, executable snippets — with no explanations of concepts Claude already knows. Not a 5 because the entry-point rule and BuildParam reading guidance are each restated across the RULE section, Checklist, and Quick Reference, so some redundancy could be trimmed.

4 / 5

Actionability

Mostly executable: complete TSX for the top-level component, a full value-object example, BuildParam declaration and consumption, and a package tree. Not a 5 due to an internal contradiction — the RULE mandates `src={"/extensions/lead/src/index.ts"}` ("`.ts` or `.tsx` extension in every `src` prop") while every code example uses `"/api/Extension.js"` and the checklist mandates ".js extensions in all import paths".

4 / 5

Workflow Clarity

The 6-step Checklist plus explicit context detection ("checking the file path: `extensions/` → extension mode, `packages/` → core mode") gives a clear sequence, and failure consequences are stated ("Omitting the file extension will cause a build failure"). Not a 5 because there are no verification checkpoints after the create/declare steps, though this non-destructive pattern skill needs few.

4 / 5

Progressive Disclosure

A single well-sectioned SKILL.md that appropriately delegates layer-specific detail to clearly signaled sibling skills (bold mentions inline plus a Related Skills section), keeping references one level deep. Not a 5 because sizable inline material (the ~30-line value-object example, the BuildParam sections) could arguably live in separate bundle files.

4 / 5

Total

16

/

20

Passed

Description

87%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.

A strong description: it clearly states what the skill covers, gives an explicit and natural "Use when" trigger for the full-stack (API + Admin) extension niche, and cleanly delineates itself from related layer-specific skills. The only minor weaknesses are single-phrasing trigger terms and structural-noun rather than action-oriented specifics.

DimensionReasoningScore

Specificity

Lists several concrete elements — "top-level component with Api.Extension and Admin.Extension entry points, shared domain layer, BuildParam declarations, and package structure" — with minor gaps (the registration mechanism itself is only implied by "registration pattern"). Not a 5 because the specifics are structural nouns rather than a comprehensive list of actions the skill performs.

4 / 5

Completeness

Explicitly answers both: what ("Full-stack extension skeleton and registration pattern" with enumerated components) and when ("Use this skill when creating an extension that spans both API and Admin") with a concrete trigger phrase. Anchor 4's caveat that "when could be more explicit" does not apply here.

5 / 5

Trigger Term Quality

"Use this skill when creating an extension that spans both API and Admin" plus "full-stack" are natural phrases for this domain, giving good keyword coverage. Not a 5 because only one phrasing is offered — no synonyms or variations (e.g., "backend and frontend", "both sides") are included.

4 / 5

Distinctiveness Conflict Risk

"Spans both API and Admin" is a precise niche trigger that cleanly separates this skill from the layer-specific siblings, and it explicitly delegates ("References webiny-api-architect and webiny-admin-architect for layer-specific details"). Minimal conflict risk with closely related skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

webiny/webiny-js

Path

skills/user-skills/full-stack-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.