CtrlK
BlogDocsLog inGet started
Tessl Logo

add-block-preview

Gate a block's visibility — ship an unreleased block as a preview (hidden until revealed via AppConfig/env), reveal it to admins/orgs, GA it, or kill-switch a shipped block

68

Quality

83%

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

100%

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

The content is tight, highly actionable, and well-sequenced, with concrete config payloads, exact file paths, and named test files as verification checkpoints. Organization is clean with no nested-reference overhead.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it jumps straight into the three-lever model, lifecycle, invariants, and named test files with no pedagogical padding about what blocks are, so every token earns its place.

3 / 3

Actionability

It gives concrete, copy-paste-ready guidance: an exact JSONc AppConfig rule shape, the PREVIEW_BLOCKS env var, specific file paths, the ' (Preview)' suffix, and a named deploy command with the 'sim-<env>-fast' strategy.

3 / 3

Workflow Clarity

The lifecycle is a clearly sequenced five-step process (Author -> Local dev -> Merge/deploy -> Hosted preview -> GA cleanup) with explicit confirmation feedback (suffix disappears within ~30s) and named test files serving as verification checkpoints.

3 / 3

Progressive Disclosure

A single well-organized SKILL.md with clear sections (model, lifecycle, kill switch, invariants, tests); its path references point into the existing codebase rather than nesting skill-bundle files, so structure is clean and one level deep.

3 / 3

Total

12

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, naming four concrete lifecycle operations in a clear niche. It is held back by the absence of an explicit 'Use when...' trigger clause and by technical-jargon trigger terms.

Suggestions

Append an explicit 'Use when...' trigger clause, e.g. 'Use when shipping, revealing, GA-ing, or kill-switching a Sim block's visibility.'

Soften jargon with user-natural phrasings such as 'preview a block', 'make a block GA', or 'pull a block from discovery' alongside the technical terms.

DimensionReasoningScore

Specificity

Lists multiple distinct concrete actions — 'ship an unreleased block as a preview', 'reveal it to admins/orgs', 'GA it', 'kill-switch a shipped block' — matching the anchor for listing several specific actions.

3 / 3

Completeness

It clearly answers what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'preview', 'kill-switch', and 'GA' are natural within this niche, but coverage leans technical ('AppConfig/env') and lacks common user-spoken variations, matching 'some relevant keywords but missing common variations' rather than the full-coverage anchor.

2 / 3

Distinctiveness Conflict Risk

The block-visibility gating lifecycle (preview/GA/kill-switch) is a clear, narrow niche unlikely to fire for any other skill, matching the distinct-trigger anchor; it also uses third person voice ('Gate a block's visibility').

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
simstudioai/sim
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.