CtrlK
BlogDocsLog inGet started
Tessl Logo

punkt-css-dev

Developing component and utility styles in the Punkt design system (@oslokommune/punkt-css). Covers creating, modifying, and maintaining SCSS in /packages/css/src/scss/. Use when working on Punkt CSS source code.

80

2.72x
Quality

70%

Does it follow best practices?

Impact

98%

2.72x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

50%

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 essentially a pure table of contents with no substantive content in the body itself. While the organization and reference structure are reasonable, the complete absence of any actionable guidance, quick-start content, or concrete examples in the main file makes it ineffective as a standalone skill. The value depends entirely on the referenced files, none of which were provided for verification.

Suggestions

Add a 'Quick Start' section with a concrete example of creating a basic component SCSS file, including the key patterns and naming conventions inline.

Include a brief architecture overview (3-5 lines) summarizing the SCSS structure so Claude has immediate context without needing to read architecture-overview.md first.

Add at least one executable code example showing a typical component SCSS pattern (e.g., a minimal component with BEM naming, dark mode, and responsive breakpoints).

Include a condensed version of the new-component checklist directly in SKILL.md, since this is the most common workflow and should be immediately accessible.

DimensionReasoningScore

Conciseness

The content is extremely lean — just a title, one-sentence description, and a numbered list of references. 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 no actionable content in the body. All substance is deferred to external files.

1 / 3

Workflow Clarity

The numbered list implies a logical progression from architecture through to checklists and dev pages, and item 15 ('Checklist: Adding Component Styles') suggests a workflow exists. However, no actual workflow steps, validation checkpoints, or sequencing are present in this file.

2 / 3

Progressive Disclosure

The structure is well-organized with clear one-level-deep references to 16 topic files, which is good progressive disclosure design. However, no bundle files were provided, so we cannot verify the referenced files exist, and the SKILL.md provides zero quick-start content — it's entirely an index with no inline overview or getting-started guidance to orient the reader before diving into sub-files.

2 / 3

Total

8

/

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 SCSS development) with explicit trigger guidance and distinctive identifiers. Its main weakness is that the capability actions are somewhat general ('creating, modifying, maintaining') rather than listing specific concrete tasks within SCSS development.

Suggestions

Add more specific concrete actions, e.g., 'writing component mixins, defining design tokens, creating utility classes, managing SCSS variables and partials' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (Punkt design system, SCSS) and some actions (creating, modifying, maintaining), but doesn't list specific concrete actions like 'write mixins', 'define variables', 'create responsive breakpoints', etc.

2 / 3

Completeness

Clearly answers both what ('Developing component and utility styles in the Punkt design system, covers creating, modifying, and maintaining SCSS') and when ('Use when working on Punkt CSS source code'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes strong natural keywords: 'Punkt', 'punkt-css', '@oslokommune/punkt-css', 'SCSS', 'design system', 'component styles', 'utility styles', and the specific file path. These are terms a user working on this system would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific package name (@oslokommune/punkt-css), the specific file path (/packages/css/src/scss/), and the named design system (Punkt). 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.