CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-browser-support

Recomputes Storybook browser support floors from Plausible /docs usage, writes pinned versions, and opens a PR. Use only when a human explicitly applies this skill.

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 unusually tight operational skill: every line is executable guidance, risky steps are gated by explicit operator approval and escalation rules, and the structure is cleanly sectioned for a self-contained workflow. The only meaningful gaps are the lack of a concrete request-body example and an explicit end-to-end step ordering with post-write verification.

DimensionReasoningScore

Conciseness

The body is dense imperative instruction — exact field values, file paths, and branch names — with zero explanation of concepts Claude already knows. The percentage-semantics paragraph ("Use metrics[1] as the share... The 0.5% cutoff means percentage >= 0.5, not 0.005") is domain-specific error prevention, not padding, so anchor 4's "minor over-explanation" does not fit.

5 / 5

Actionability

Gives the exact endpoint, field-by-field query spec (site_id, date_range, filters, dimensions, metrics, include), exact file paths, branch, labels, and PR template. It falls short of anchor 5's copy-paste-ready bar because there is no literal request-body example or a worked rolled-share computation showing the arithmetic in practice.

4 / 5

Workflow Clarity

A clear Auth → Query → Heuristic → Approve → Write → PR sequence with a hard pre-write checkpoint ("Do not... write new floors without explicit operator approval"), a feedback loop ("If browserslist cannot resolve the new pins, bump caniuse-lite"), and an escalation path ("stop and ask the Technical Architect"). It misses anchor 5 because the end-to-end order is implied by section order rather than explicit, and there is no post-write verification step.

4 / 5

Progressive Disclosure

A self-contained single-file skill (~62 lines) with well-organized sections (Auth, Query, Heuristic, Approve, Write, PR) and no inlined content that belongs in a separate file; the only external link (Plausible Stats API docs) is a legitimate one-level reference. No bundle files exist, and none are needed.

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 strong description: third-person voice, concrete three-action pipeline, and an explicit (if terse) when-clause appropriate for a manually-invoked skill. Its main limitation is the absence of richer trigger synonyms and any hint of the approval workflow that dominates the skill body.

DimensionReasoningScore

Specificity

"Recomputes Storybook browser support floors from Plausible /docs usage, writes pinned versions, and opens a PR" lists three specific concrete actions with named artifacts. It stops short of anchor 5's comprehensive coverage because the operator-approval gate and the write targets (browserslist, docs) are not mentioned, but it well exceeds the 1-2 actions of anchor 3.

4 / 5

Completeness

Both parts are explicit: the "what" is the recompute/write/PR pipeline and the "when" is "Use only when a human explicitly applies this skill". It does not reach anchor 5 because the when-clause is an invocation gate rather than concrete trigger phrases like "when the user mentions X".

4 / 5

Trigger Term Quality

Natural terms a user would say are present: "browser support", "floors", "Storybook", "Plausible", "pinned versions", "PR". A few common variations are missing ("browserslist", "caniuse", "supported browsers"), which keeps it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Storybook browser support floors from Plausible /docs usage" names a clear niche combining a specific product, data source, and artifact, making accidental triggering of another skill very unlikely.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

storybookjs/storybook

Path

.agents/skills/update-browser-support/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.