CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-components-engineering

Guide writing or changing Web Components so they fit the project and work for every consumer: learn its browser targets, consuming frameworks and versions, component library and conventions first, then design a stable public contract (tag, attributes, properties, events, slots, parts) and implement it with idempotent lifecycle and cleanup, shadow or light DOM as fits, accessibility across shadow boundaries, native form association, server-rendered roots reused, and a real-browser check. Use whenever you create or edit a custom element, a shadow root, a Lit, FAST or Stencil component, a form-associated control, or a component library's registration, types or docs, even when the user doesn't say Web Components. It adds no library, base class or TypeScript migration unless asked. Not for reviewing components already written (the knackpack:web-components-code-reviewer agent, started only on request), CSS layout and cascade (the css-engineering skill), or React's own semantics (the React reviewer).

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, expert-level engineering skill: nearly every rule is stated with its concrete failure mode, exact API, or executable snippet, and the nine-step workflow is clearly sequenced with a real verification section. The main gaps are modest: a little re-explanation of platform basics Claude already knows, no explicit error-recovery loop after verification, and a monolithic structure that could offload framework-interop detail to reference files.

Suggestions

Trim passages that restate platform fundamentals Claude already knows (e.g., 'call super() first', the naming-convention table, slot-assignment basics) and keep only the project-specific or failure-mode-driven rules.

Add an explicit feedback loop to the Verify section: what to do when type check, lint, or the browser test fails (fix without auto-fix modes, re-run, and only then proceed), so error recovery is not left implicit.

Consider moving the per-framework consumer details (React 18/19, Vue, Angular, Svelte 5) into a references/ file with a clear pointer from section 7, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, failure-mode-driven guidance (upgrade-order constructor bugs, per-connection AbortController, own-property shadowing before definition, `:host-context()` removal) and mostly avoids padding, matching the efficient score-4 anchor. It falls short of 5 because some passages re-state platform fundamentals Claude already knows — "call `super()` first", the kebab-case/PascalCase naming table, "Only the host's direct children are slotted" — which could be trimmed.

4 / 5

Actionability

Guidance is fully concrete and executable throughout: copy-paste-ready snippets (`this.dispatchEvent(new CustomEvent('item-select', { bubbles: true, detail }))`, the `attachInternals().shadowRoot ?? this.attachShadow(...)` reuse, the `Object.hasOwn(this, name)` upgrade fix), exact API calls (`setFormValue(value, state)`, `toggleAttribute(name, Boolean(value))`, `internals.states`), and specific tools and checks (Web Test Runner, Playwright, webstatus.dev, eslint-plugin-wc). Per the code_vs_instruction note, this instruction-heavy skill meets the score-5 bar: specific examples cover the common cases.

5 / 5

Workflow Clarity

The body is an explicitly numbered sequence in execution order (Learn the project → Design the contract → Implement → Shadow DOM → Accessibility → Forms/SSR → Framework consumers → Security → Verify) with a validation section that names checks and a coverage checklist (reinsertion, reflection of `false`, events outside the host, form reset, keyboard operation). It stops short of 5 because no fix-and-re-validate feedback loop is stated in the Verify step — validation outcomes are listed but error recovery is left implicit.

4 / 5

Progressive Disclosure

With no bundle files present, the single ~110-line file is well organized: numbered sections, a contract-convention table, and clearly delineated domains, and the size is within single-file norms. It matches the good-structure score-4 anchor rather than 5 because there are no well-signaled one-level-deep references at all — sections like the per-framework interop details (section 7) are the kind of material that could be split into reference files — and the cross-skill pointers ("the css-engineering skill") are plain text rather than navigable links.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: dense with concrete capabilities, an explicit and richly phrase-triggered use clause, and explicit exclusions that separate it from sibling skills and agents. The only flaw is second-person phrasing in the trigger clause, which costs it a point on specificity under the rubric's voice rule.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions — "learn its browser targets, consuming frameworks and versions", "design a stable public contract (tag, attributes, properties, events, slots, parts)", "idempotent lifecycle and cleanup", "native form association, server-rendered roots reused, and a real-browser check" — comprehensive and near the score-5 anchor. However, the trigger clause "Use whenever you create or edit a custom element" uses second-person voice, which the judging guidelines penalize by reducing specificity by 1.

4 / 5

Completeness

Both halves are explicit: the "what" lists concrete capabilities (contract design, lifecycle implementation, accessibility, form association, real-browser verification) and the "when" is an explicit "Use whenever you create or edit..." clause with concrete trigger phrases plus negative triggers ("Not for reviewing components already written..."). This clearly matches the score-5 anchor; it is not the score-4 anchor because the when-clause is specific rather than merely present.

5 / 5

Trigger Term Quality

Natural user phrases are covered comprehensively with synonyms: "custom element", "a shadow root", "a Lit, FAST or Stencil component", "a form-associated control", "a component library's registration, types or docs", and "Web Components", explicitly firing "even when the user doesn't say Web Components". This matches the comprehensive-coverage anchor; no common variation a user would actually say is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous (Web Components engineering) and the description actively disambiguates the three nearest neighbors — "the knackpack:web-components-code-reviewer agent", "the css-engineering skill", "the React reviewer" — giving minimal conflict risk. This fits the clear-niche-with-distinct-triggers anchor better than the score-4 anchor, whose minor overlap risk is not present given the explicit exclusions.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

bezmoradi/knackpack

Path

skills/web-components-engineering/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.