CtrlK
BlogDocsLog inGet started
Tessl Logo

deck-guizang-editorial

OpenDesign's FY26 marketing plan: brand-to-pipeline — audience, offer, channel mix, and the launch calendar that ties creative to growth. Built as a decision-grade marketing & GTM deck for CMO, growth lead, founder.

61

Quality

72%

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/deck-guizang-editorial/SKILL.md

The canonical home for this skill is deck-guizang-editorial in nexu-io/open-design

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a compact, well-structured design spec with concrete, executable guidance (exact colors, sizes, fonts, prohibitions) and clean sectioning that needs no external references. Its only soft spot is the absence of an explicit in-body production workflow with validation checkpoints.

DimensionReasoningScore

Conciseness

A lean spec sheet of hex codes, layout dimensions, and prohibitions that assumes Claude's competence; only minor asides (e.g., "Inspired by op7418/guizang-ppt-skill Style A") could be trimmed.

4 / 5

Actionability

Highly concrete guidance — exact hex values, 8.5-10vw headline sizes, 3x2/26vh grids, named fonts (Playfair Display, Noto Serif SC) and explicit prohibitions — leaving only minor gaps such as no inline HTML/CSS skeleton.

4 / 5

Workflow Clarity

Content is clearly sectioned (template, palette, layout, design details) and the single deck-build task is unambiguous, though no explicit multi-step production sequence or validation checkpoint appears in the body itself (those live in the frontmatter prompt).

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references; the body is well-organized into clearly headed sections, meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

66%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 is specific and well-keyworded for its marketing/GTM niche but lacks an explicit "Use when..." trigger clause, capping completeness. It names concrete deck components and a clear audience rather than framing Claude's actions.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants an annual marketing plan, GTM deck, or launch/pipeline planning slides') to lift completeness above 3.

Include natural synonyms users actually say ('campaign', 'go-to-market strategy', 'marketing strategy') to broaden trigger-term coverage.

Reframe around concrete actions Claude performs ('Builds... organizes... runs a critic pass') rather than only describing the deck's subject matter.

DimensionReasoningScore

Specificity

Lists several concrete deck components — "audience, offer, channel mix, and the launch calendar that ties creative to growth" — plus the deliverable frame "decision-grade marketing & GTM deck", though these are content areas more than explicit actions.

4 / 5

Completeness

The "what" is clear (a marketing & GTM deck covering audience/offer/channel/launch calendar), but there is no explicit "Use when..." trigger clause; the audience mention ("for CMO, growth lead, founder") only weakly implies when, so completeness is capped at 3 per the missing-trigger-clause guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("marketing plan", "brand-to-pipeline", "GTM deck", "launch calendar", "CMO", "growth lead"), but misses common synonyms like "campaign", "go-to-market strategy", or "marketing strategy".

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (editorial-style marketing/GTM plan deck) with specific framing, with only minor overlap risk against generic deck or presentation skills.

4 / 5

Total

15

/

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