CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

punkt-components

Using Punkt design system components (React and Elements/Web Components). Covers component APIs, props, events, slots, and usage patterns for all Punkt UI components. Use when building UIs with Punkt components.

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

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

An exemplary overview document: copy-paste-ready setup for all three integration methods, genuinely non-obvious operational guidance (CSP, Next.js tree-shaking, form-attribute support), and a clean one-level-deep reference structure for per-component details. Minor room to improve by trimming explanations of standard HTML behavior and adding a quick way to verify a setup works.

DimensionReasoningScore

Conciseness

Most content is non-obvious, Punkt-specific guidance that earns its tokens (CSP origins, optimizePackageImports for Next.js, slot-change behavior, inputSize semantics), matching the 'efficient; minor instances of over-explanation' anchor. Not 5 because it explains standard HTML behavior Claude already knows — "the browser submits the field with that form, wherever it is on the page", whitespace showing "like in plain HTML", and radio buttons forming "one group" — and the Elements slot paragraph is long enough to belong in a reference.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance covering the common cases: "npm add @oslokommune/punkt-react", complete import and render examples for all three setup methods (React NPM, Elements NPM, Elements CDN), a full next.config.mjs snippet, and a complete CSP directive block. Not below 5 because no gaps or pseudocode were found in any setup path.

5 / 5

Workflow Clarity

Each setup path is an unambiguous install → import → render → configure-CSP sequence, with a troubleshooting checkpoint ("Missing CSP configuration is a common cause of broken fonts, missing icons, and invisible components"), matching the 'clear sequence with most checkpoints present' anchor. Not 5 because there are no explicit validation or verification steps (e.g. how to confirm the setup renders correctly); not 3 because the sequences have no real gaps and there are no risky operations requiring feedback loops.

4 / 5

Progressive Disclosure

The body is a clean overview with well-signaled, one-level-deep references: a numbered Components index of 35 per-component files, contextual pointers ("See [header.md](header.md) ... for details and for the server-side data workaround", "See [Strings and overrides](strings.md)"), and a clear hand-off to the punkt-css skill — matching the 5 anchor exactly. Note: no bundle files were present in the evaluation workspace, so the existence of the referenced .md files could not be verified on disk; the score reflects the structure as written.

5 / 5

Total

18

/

20

Passed

Description

78%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 concise, well-scoped description that clearly states what the skill covers and when to use it, in third person with no padding. Its main gaps are a single trigger phrase and the absence of package names and Pkt-prefixed component names that users would naturally mention.

Suggestions

Broaden the trigger clause to cover natural variations, e.g. "Use when building UIs with Punkt components or when the user mentions Pkt-prefixed components (PktButton, PktInput), @oslokommune/punkt-react, or @oslokommune/punkt-elements."

Add a boundary sentence distinguishing this skill from the sibling punkt-css skill (e.g. "For CSS classes, colors, typography, and spacing, use the punkt-css skill") to reduce overlap on generic 'Punkt' queries.

Replace the generic verb 'Covers' with concrete actions such as "Build UIs with Punkt React and Elements components: configure props, handle events, use slots, and follow usage patterns."

DimensionReasoningScore

Specificity

"Covers component APIs, props, events, slots, and usage patterns for all Punkt UI components" lists several specific coverage areas plus the two concrete package flavors ("React and Elements/Web Components"), matching the 'several specific actions; minor gaps' anchor. Not 5 because the verbs are 'Using/Covers' rather than multiple concrete actions; not 3 because it enumerates more than 1-2 specifics with comprehensive scope.

4 / 5

Completeness

Both parts are present: a clear what ("Covers component APIs, props, events, slots, and usage patterns") and an explicit when ("Use when building UIs with Punkt components"), so no missing-trigger cap applies. Not 5 because the 'when' is a single trigger phrase, while the 5 anchor expects multiple concrete trigger phrases with synonyms.

4 / 5

Trigger Term Quality

Good natural keywords — "Punkt", "design system", "React", "Elements/Web Components", "UI", "building UIs" — that a user needing this skill would plausibly say. Falls short of 5 because package names (@oslokommune/punkt-react) and Pkt-prefixed component names (PktButton, PktInput) that users would naturally paste are absent.

4 / 5

Distinctiveness Conflict Risk

"Punkt design system components (React and Elements/Web Components)" is a clear proprietary niche with component-scoped triggers, giving minimal conflict risk with generic UI skills. The closely related punkt-css skill is implicitly disambiguated by the explicit components/APIs/props scope, so the 4 anchor's 'minor overlap risk with closely related skills' fits less well than the 5 anchor's 'clear niche with distinct triggers'.

5 / 5

Total

17

/

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

relative_links

Relative link issues: 40 missing

Warning

Total

15

/

16

Passed

Repository

oslokommune/punkt-skills

Path

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