CtrlK
BlogDocsLog inGet started
Tessl Logo

punkt-elements-dev

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

82

1.44x
Quality

73%

Does it follow best practices?

Impact

97%

1.44x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/punkt-elements-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 excels as a concise, well-organized table of contents with excellent progressive disclosure across 14 referenced files. However, it provides zero actionable content in the body itself — no quick-start guidance, no code snippets, no key commands — making it entirely dependent on the referenced files. Without bundle files to verify, the skill body alone is essentially an index page with no standalone value.

Suggestions

Add a 'Quick Start' section with 2-3 essential commands (e.g., how to create a new component, run tests, start dev server) so the SKILL.md is actionable on its own.

Include a brief workflow summary (e.g., 'To add a new component: 1. scaffold → 2. implement → 3. test → 4. export') with a pointer to the full checklist, giving Claude immediate orientation.

Add at minimum one concrete code example showing the basic structure of a Punkt Lit component so Claude can act without needing to read referenced files first.

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 examples. It is purely a table of contents with links to other files, providing no executable or actionable content on its own.

1 / 3

Workflow Clarity

The numbered section list implies a logical progression from architecture through implementation to testing and checklists, and the final item is a checklist for adding new elements. However, there are no explicit workflow steps, validation checkpoints, or sequencing instructions in the body itself.

2 / 3

Progressive Disclosure

The skill is structured as a clear overview with well-signaled, one-level-deep references to 14 topic-specific files. Navigation is straightforward and topics are logically organized from foundational concepts to specific concerns.

3 / 3

Total

9

/

12

Passed

Description

89%

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 skill description that clearly identifies its niche (Punkt design system Lit web components), provides an explicit 'Use when' clause, and includes distinctive identifiers like the package name and file path. The main weakness is that the capability actions (creating, modifying, testing) are somewhat generic and could be more specific about what kinds of operations are supported.

Suggestions

Consider listing more specific concrete actions such as 'define custom element properties, add slots, configure styles, write unit tests' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (Lit web components, Punkt design system) and some actions (creating, modifying, testing components), but doesn't list deeply specific concrete actions like 'add slots', 'define properties', 'write unit tests', etc.

2 / 3

Completeness

Clearly answers both 'what' (developing Lit web components, creating/modifying/testing components) and 'when' ('Use when working on Punkt Elements source code'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Lit', 'web components', 'Punkt', '@oslokommune/punkt-elements', 'Punkt Elements', '/packages/elements/src/components/', 'design system'. These cover both package names and technology terms a developer would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with specific package name (@oslokommune/punkt-elements), specific path (/packages/elements/src/components/), and specific technology (Lit). Very unlikely to conflict with other skills.

3 / 3

Total

11

/

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.