CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-admin-architect

Admin-side architecture patterns for Webiny extensions. Use this skill when building frontend features with headless features (UseCase/Repository/Gateway), presentation features (Presenter/ViewModel/hooks/components), MobX-based presenters, RegisterFeature, value objects for domain values, and Admin BuildParams. Covers the admin/ directory structure for both features/ and presentation/ layers.

Quality

83%

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

71%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-organized, highly actionable patterns reference with near copy-paste-ready code and clear decision guidance. Its main weaknesses are repetition of key rules, a monolithic single-file structure where substantial implementation guides belong in references/ files, and a couple of code examples with missing context.

Suggestions

Split the Repository, Gateway, Observable Service, and Value Objects implementation sections into references/ files (e.g. references/implementations.md), keeping SKILL.md as an overview with clearly signaled one-level-deep pointers — the skill is ~690 lines with no bundle files.

Consolidate the 'resolve is mandatory' rule (currently stated in TL;DR, Feature Registration, Core APIs, and Key Rules) and the createReactiveComponent rule (stated in the Working Context table and React Component Rules) into single authoritative sections to trim duplicated tokens.

Complete the partial examples: add imports to the useIdentity hook example and either define or explicitly stub the GetThing use case abstraction referenced by CurrentThingPresenter.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific with no explanation of concepts Claude already knows, but the 'resolve is mandatory' rule is repeated four times (TL;DR, Feature Registration, Core APIs, Key Rules) and the createReactiveComponent rule three times, and the ~90-line Gateway GraphQL example could be trimmed — minor over-explanation that could be tightened rather than the fully lean level-5.

4 / 5

Actionability

Mostly executable, copy-paste-ready TypeScript/TSX with imports, a full directory tree, and explicit rules; minor gaps keep it from 5 — the useIdentity example omits its imports, and the Presenter example references a GetThing/abstractions.js that is never defined in this skill.

4 / 5

Workflow Clarity

Sections follow the actual build order (abstractions → feature registration → useFeature hook → presenter → components) with explicit decision checkpoints ('Detect which context you're in by checking the file path', typical vs. one-off pattern choice); not 5 because no explicit end-to-end numbered sequence is given, though no destructive or batch operations require validation loops.

4 / 5

Progressive Disclosure

No bundle files exist; all ~690 lines live in SKILL.md. Self-contained sections (Repository Implementation, Gateway Implementation, Observable Service, Value Objects) are prime candidates for references/ files, matching 'content that should be separate is inline'; not 4 because the structure and cross-skill pointers, while clear, don't offset the absence of any file-level splitting in a document this long.

3 / 5

Total

15

/

20

Passed

Description

88%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 explicitly states what the skill covers and when to use it, with a comprehensive enumeration of concrete Webiny-specific capabilities. Trigger terms are natural for the domain, and only minor improvements (synonyms, tighter separation from sibling Webiny admin skills) are available.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'headless features (UseCase/Repository/Gateway), presentation features (Presenter/ViewModel/hooks/components), MobX-based presenters, RegisterFeature, value objects for domain values, and Admin BuildParams' — with comprehensive coverage of the skill's scope and no notable gaps, matching the top anchor rather than the 'minor gaps' level-4 anchor.

5 / 5

Completeness

Explicitly answers both: 'what' ('Admin-side architecture patterns for Webiny extensions') and 'when' ('Use this skill when building frontend features with...') with concrete trigger phrases — a direct match for the top anchor; not 4 because the when-clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Webiny extensions', 'admin', 'MobX-based presenters', 'value objects', 'BuildParams', 'headless features') that users in this codebase would say, but common variations like 'admin UI', 'admin app', 'React components', or 'screens/pages' are missing, so it falls short of the comprehensive synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Webiny admin-side architecture layering) that is mostly distinct, but the body lists closely related sibling skills (webiny-admin-ui-extensions, webiny-full-stack-architect, webiny-dependency-injection) covering adjacent admin territory, so minor overlap risk with closely related skills remains — not 5, not 3 since the core triggers are clearly architecture-pattern-specific.

4 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (693 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

webiny/webiny-js

Path

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