CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fs-electric-studio

OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/examples/fs-electric-studio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly written, highly concrete design-system spec that a model could largely build from directly, weakened by a missing production workflow (no sequenced steps or validation checkpoints in the body) and by references to seed files (example.html, STYLE_PRESETS.md, LICENSE) that are not shipped in the bundle. The repeated lock rules could also be consolidated for token efficiency.

Suggestions

Ship the referenced files (example.html, STYLE_PRESETS.md, LICENSE) in the bundle — or inline the essential seed CSS/JS and preset definition — so the "keep verbatim" instructions are executable.

Add a short numbered workflow in the body: ask for missing essentials → produce slide plan → write slides from masters → run a self-check (contrast, overflow, single-idea-per-slide, forwardable-without-rewriting critic pass).

Consolidate the three repeated color/typeface lock statements into one "Locked constraints" list to trim redundant tokens.

DimensionReasoningScore

Conciseness

The body is a dense design spec — exact :root tokens, a master-page table, a scaling formula, and a nav key list — with no padding and no explanation of concepts Claude already knows. Not 5: the lock rules are repeated three times ("do not introduce any color or font outside this spec", "Forbidden: any other hue…", "Never substitute … any second typeface") and could be consolidated.

4 / 5

Actionability

Provides concrete, executable guidance: the full :root CSS block, the split-panel HTML shell, "factor = min(innerWidth/1920, innerHeight/1080)", master split ratios, and a precise output contract. Not 5 because the pivotal instruction to keep "example.html" and its SlidePresentation controller "verbatim" cannot be executed — no example.html ships in the bundle, and the seed CSS/JS is not inlined.

4 / 5

Workflow Clarity

The sequence is only implied (start from the seed → compose masters → emit a single self-contained HTML), with no ordered steps for the actual production process and no validation checkpoints — "No scrolling, no overflow" is stated as a constraint rather than a check. Matches anchor 3 (sequence present but implicit, checkpoints missing); the ask-essentials → plan → write → critic-pass flow lives only in the frontmatter example prompt.

3 / 5

Progressive Disclosure

Section headers are clear (tokens, typography, layout, masters, stage, motion, output, attribution), but the referenced files — example.html, STYLE_PRESETS.md, and the LICENSE — do not exist in the bundle (no references/, scripts/, or assets/ directories), so the references do not resolve. Good signaling but broken structure lands at 3 rather than 4, and above 2 because organization within the file is solid.

3 / 5

Total

14

/

20

Passed

Description

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

The description clearly names a niche deliverable (buyer-forwardable B2B sales deck) with audience roles and structural components, but reads more like a product brief than a capability statement: the hard-coded subject "OpenDesign as an enterprise design platform" narrows it, and there is no "Use when…" trigger clause. Keyword coverage is good though missing common synonyms like "pitch deck".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a sales proposal, pitch deck, quote, or buyer-facing B2B presentation."

Remove the hard-coded example subject "OpenDesign as an enterprise design platform" from the description and state the capability generally: writes buyer-forwardable B2B SaaS sales proposals covering pain, value, ROI, and rollout for an economic buyer.

List concrete actions/outcomes (e.g. "produces a single-file HTML deck with slide plan, speaker-ready structure, and a forwardable-without-rewriting critic pass") to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ("a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout") but the only concrete action is writing one proposal/deck; the listed items are deck sections rather than capabilities. It falls below 4 (which requires several specific actions) and above 2 because the domain and deliverable structure are concrete.

3 / 5

Completeness

The "what" is clear — "a buyer-forwardable proposal … Built as a decision-grade B2B sales deck" — but there is no "Use when…" clause or equivalent trigger guidance in the description, capping completeness at 3. Not 4 because "when" is only weakly implied by naming the audience.

3 / 5

Trigger Term Quality

Contains natural user phrases like "B2B sales deck", "proposal", "ROI", "economic buyer", "procurement". Not 5 because common synonyms ("pitch deck", "quote", "pricing proposal") are missing and terms like "buyer-forwardable" and "decision-grade" are jargon users would not say; clearly above 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The niche "B2B SaaS sales proposal for economic buyer, design VP, procurement" is mostly distinct with clear triggers. Not 5 due to overlap risk with generic presentation/deck-creation skills (and broad tags like "sales", "renewal", "customer"); above 3 because the proposal niche is clearly staked.

4 / 5

Total

14

/

20

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.

Validation — 15 / 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

nexu-io/open-design

Path

plugins/_official/examples/fs-electric-studio/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.