CtrlK
BlogDocsLog inGet started
Tessl Logo

studio-css-reset

Guidance for Remotion Studio UI changes where the global CSS reset affects nested elements. Use when editing packages/studio UI, especially when adding wrapper spans, inline icons, labels, buttons, compact rows, or any nested text whose typography, color, sizing, or truncation must stay stable.

76

Quality

93%

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

87%

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

A concise, actionable, well-organized instruction skill with concrete CSS prescriptions and an executable verification command. Its only gap is the absence of an explicit validate→fix→retry checkpoint around the verification step.

Suggestions

Add an explicit validation feedback loop after the turbo checks, e.g., 'If lint/test fails, fix the reported issues and re-run the focused checks before proceeding.'

Clarify the workflow ordering as numbered steps (style nested elements → preserve layout → recheck states → run checks) so the sequence reads as a checklist rather than a guidance list.

DimensionReasoningScore

Conciseness

The body is lean with no concept padding ('Remotion Studio applies a broad CSS reset... Treat every new nested element as reset-styled...') and every bullet carries specific, non-redundant guidance that assumes Claude's competence.

3 / 3

Actionability

Bullets prescribe exact CSS properties ('fontFamily, fontSize, lineHeight', 'flexShrink: 0', 'minWidth, overflow, textOverflow, whiteSpace') and the bash block ('bunx turbo run lint test --filter=...') is copy-paste ready and executable.

3 / 3

Workflow Clarity

A sequence of considerations and an explicit verification command block are present, but there is no validation checkpoint or feedback loop (e.g., 'if checks fail, fix and re-run'), leaving the checkpoint implicit rather than explicit.

2 / 3

Progressive Disclosure

The skill is self-contained and under 50 lines with no external references needed, organized into a clear intro, a bulleted 'When changing Studio UI' section, and a 'For Studio code changes' command block — well-organized sections suffice for a simple skill.

3 / 3

Total

11

/

12

Passed

Description

100%

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, niche-specific description with concrete capability coverage, natural trigger terms, an explicit 'Use when' clause, and low conflict risk. It is concise yet complete.

DimensionReasoningScore

Specificity

The description names the domain (Remotion Studio UI, global CSS reset affecting nested elements) and enumerates concrete triggering edit types such as 'wrapper spans, inline icons, labels, buttons, compact rows' — multiple specific concrete scenarios rather than vague language.

3 / 3

Completeness

It answers 'what' (guidance for Studio UI changes where the CSS reset affects nested elements) and 'when' via an explicit 'Use when editing packages/studio UI, especially when adding...' clause, satisfying both halves.

3 / 3

Trigger Term Quality

Terms like 'Remotion Studio', 'packages/studio UI', 'wrapper spans', 'compact rows', and 'truncation' are exactly the natural vocabulary a developer editing this subsystem would use, giving good coverage of relevant trigger terms.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to 'Remotion Studio UI' and the global CSS reset with distinct element-specific triggers, making it very unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
remotion-dev/remotion
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.