Name: punkt-css
Rating: 76.8 (1 reviews)
Author: oslokommune

punkt-css

Using Punkt CSS (@oslokommune/punkt-css) in projects. Covers setup, layout, typography, colors, grid, spacing, and utility classes for building websites and applications with the Oslo kommune design system. Use when building pages or layouts with Punkt CSS classes.

1.65x

Quality

72%

Does it follow best practices?

Impact

96%

1.65x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/punkt-css/SKILL.md

Quality

Content

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

The body is an efficient, well-organized index that follows the progressive-disclosure shape, but it delegates everything to section files that are not present in this bundle, leaving the SKILL.md itself with no actionable content. Adding a minimal quick-start snippet and confirming the referenced files exist would substantially strengthen it.

Suggestions

Add a minimal executable quick-start to the body (e.g. the install command and one small HTML/class example) so the skill is actionable even before loading a section file.

Verify and ship the 9 linked section files (getting-started.md, colors.md, etc.) — currently none exist in the bundle, so every body link is broken.

Give brief one-line descriptions per section link or a rule for choosing among them (e.g. "start with getting-started.md for setup; jump to colors.md when styling") to turn the TOC into a navigable workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero concept explanations, but the opening sentence ("Skill for using Punkt CSS... Covers setup, layout, typography, colors, grid, spacing, and utility classes...") duplicates the frontmatter description almost verbatim and could be trimmed. Not the 5 anchor's "every token earns its place", but well above the verbose anchors.	4 / 5
Actionability	The only guidance is a high-level "Key principle: Focus on CSS classes and CSS custom properties" — no code, commands, class names, or concrete steps anywhere in the body. This matches anchor 2 ("high-level hints but missing the specific steps to execute") rather than 1, since the principle does steer which API surface to use.	2 / 5
Workflow Clarity	The numbered section list beginning with "Getting Started" implies a rough order, but no explicit workflow, checkpoints, or selection guidance is given for navigating to the right section. Fits anchor 3 (sequence implicit, checkpoints missing) better than 2 (a TOC structure is present) and below 4 (no explicit checkpoints or feedback loops).	3 / 5
Progressive Disclosure	The body is a clean, one-level-deep table of contents with descriptively labeled links (Getting Started, Typography & Layout, Colors, ...) — structurally the 5-anchor shape. However, none of the 9 linked files exist in the bundle (no references/ directory), so the claimed split cannot be verified as real, holding this at 4.	4 / 5
	Total	13 / 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 strong description: third-person, specific about capability areas, with an explicit 'Use when' trigger and a clearly distinct niche. The trigger clause is narrow (one phrase) and could add synonyms like "Oslo design system" or "brand styles" for broader natural-language matching.

Dimension	Reasoning	Score
Specificity	"Covers setup, layout, typography, colors, grid, spacing, and utility classes" names the domain plus several concrete capability areas with only minor gaps. It lists topics rather than the multiple specific concrete actions of the 5 anchor, but is far beyond the generic domain-only naming of anchors 1-2.	4 / 5
Completeness	The 'what' is explicit ("Covers setup, layout, typography, colors, grid, spacing, and utility classes...") and the 'when' is explicit ("Use when building pages or layouts with Punkt CSS classes"). The when-clause is a single narrow trigger, fitting anchor 4 ("'when' could be more explicit or specific") better than 5's multiple concrete trigger phrases, and clearly above 3 where 'when' is only weakly implied.	4 / 5
Trigger Term Quality	Natural phrases users would say are present: "building pages or layouts", "Punkt CSS classes", "typography", "colors", "grid", "spacing". Missing common synonyms and broader design-system phrasings (e.g. "Oslo design system", "brand styles"), so it falls short of the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Oslo kommune design system" and "@oslokommune/punkt-css" establish a clear niche with distinct triggers. Conflict risk with generic CSS or design-system skills is minimal, matching the 5 anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 9 missing	Warning

	Total	15 / 16 Passed

Repository: oslokommune/punkt-skills
Path: skills/punkt-css/SKILL.md
Commit: 2ba2eb2

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.