CtrlK
BlogDocsLog inGet started
Tessl Logo

punkt-react-dev

Developing React components in the Punkt design system (@oslokommune/punkt-react). Covers creating, modifying, and testing components in /packages/react/src/components/. Use when working on Punkt React source code.

78

1.13x
Quality

66%

Does it follow best practices?

Impact

98%

1.13x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/punkt-react-dev/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

This SKILL.md is an excellent table of contents with strong progressive disclosure and conciseness, but it provides zero actionable content in the body itself. It relies entirely on referenced files for all substance, meaning if those files are missing or incomplete, the skill provides no value. The body would benefit from at least a quick-start snippet or key workflow summary to be useful on its own.

Suggestions

Add a 'Quick Start' section with a minimal concrete example (e.g., the command to scaffold a new component or a brief code snippet showing the standard component pattern) so the SKILL.md is actionable even before reading sub-files.

Include a brief high-level workflow summary (e.g., 3-5 steps: create files → implement → test → lint → add to exports) with validation checkpoints directly in the SKILL.md body.

Add a short 'Key Rules' or 'Critical Constraints' section summarizing the most important do's/don'ts so Claude gets essential guidance without needing to read all 14 referenced files.

DimensionReasoningScore

Conciseness

The content is extremely lean — just a title, one-sentence description, and a numbered table of contents. Every token serves a purpose with zero unnecessary explanation.

3 / 3

Actionability

The SKILL.md itself contains no concrete guidance, code, commands, or executable instructions. It is purely a table of contents with no actionable content in the body.

1 / 3

Workflow Clarity

The numbered list implies a logical sequence (architecture → specs → implementation → testing → checklist), and item 13 is a checklist for adding new components. However, there are no explicit workflow steps, validation checkpoints, or feedback loops in the body itself.

2 / 3

Progressive Disclosure

The content is a well-organized overview with 14 clearly signaled, one-level-deep references to separate topic files. Navigation is easy and topics are logically grouped. Without bundle files to verify, the structure itself is exemplary progressive disclosure.

3 / 3

Total

9

/

12

Passed

Description

75%

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

This is a solid, focused description that clearly identifies its niche (Punkt design system React components) and includes an explicit 'Use when' clause. Its main weakness is that the capability actions are somewhat generic (creating, modifying, testing) rather than listing more specific concrete tasks, and the trigger terms could include a few more natural variations.

Suggestions

Expand the specific actions beyond 'creating, modifying, and testing' to include more concrete tasks like 'adding props, writing stories, implementing accessibility patterns, styling with design tokens'.

Add more natural trigger term variations such as 'design system component', 'punkt-react', 'UI library', or 'Storybook' to improve keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (React components in Punkt design system) and some actions (creating, modifying, testing), but doesn't list deeply specific actions like 'writing unit tests', 'adding props', 'implementing accessibility patterns', etc.

2 / 3

Completeness

Clearly answers both 'what' (developing React components in the Punkt design system, covering creating/modifying/testing) and 'when' (explicit 'Use when working on Punkt React source code' clause).

3 / 3

Trigger Term Quality

Includes relevant terms like 'React components', 'Punkt design system', '@oslokommune/punkt-react', and the file path, but misses common variations users might say such as 'design system component', 'UI component', 'storybook', or 'punkt-react'.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific package name (@oslokommune/punkt-react), the exact file path (/packages/react/src/components/), and the named design system (Punkt). Very unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

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