CtrlK
BlogDocsLog inGet started
Tessl Logo

baoyu-design

Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks (a.k.a. PPT / PowerPoint presentations), documents and résumés, animations, 3D objects, research reports, HTML email, diagrams, fliers, and visual explorations. Use whenever the user asks to design, mock up, prototype, wireframe, visualize, explore, or make a PPT/deck for an interface, product screen, user flow, content layout, visual artifact, or pitch/deck concept, even if they do not say "design". Also use to export a deck built with this skill to PowerPoint (PPT/PPTX) — but only decks authored here (deck-stage / this skill's slide-structured HTML), NOT arbitrary HTML, so confirm the target is such a deck first. Also use for setting up, importing, or authoring reusable design systems, UI kits, brand tokens, or component libraries. Harness-agnostic for Claude Code, Cursor, Codex Agent, and similar file-capable agents.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/baoyu-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

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 well-structured orchestration entry point with a clear numbered workflow, but it is dense and verbose for an overview and, critically, most of the files and directories it routes to (system-prompt.md, built-in-skills/, agents/, project-types.json, starter-components/) are absent from the bundle, undermining both actionability and navigation.

Suggestions

Tighten the long inline caveats in steps 3 and 5 into shorter conditional bullets to reduce token load while preserving the routing logic.

Ensure the referenced bundle exists: ship system-prompt.md, built-in-skills/, agents/, project-types.json, and starter-components/, or remove the dead links so progressive disclosure routes resolve.

Add at least one copy-paste-ready concrete command or snippet (beyond the one glob pattern) so the entry flow is actionable without first opening another file.

DimensionReasoningScore

Conciseness

It avoids explaining concepts Claude already knows and functions as an index, but several sentences are very long and dense (e.g. step 3's built-in-skills routing and step 5) with repeated inline caveats that could be tightened.

2 / 3

Actionability

It gives concrete signals (e.g. 'glob designs/*/_ds_manifest.json', 'agents/import-design-system.mjs') and a numbered routing table, but most actionable content is 'read this file' pointers with little copy-paste-ready code, and many of those target files are absent from the bundle.

2 / 3

Workflow Clarity

A clear numbered 1–6 entry sequence exists with a verify step (step 6: preview, confirm it loads cleanly, fix errors before finishing), but several branches route to files that are not present, leaving some sequences incomplete rather than fully self-contained.

2 / 3

Progressive Disclosure

References are well-signaled and conceptually one-level-deep, but the actual bundle contradicts them: system-prompt.md, built-in-skills/, agents/, project-types.json, and starter-components/ are all referenced yet missing, so navigation lands on dead links.

2 / 3

Total

8

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that names concrete capabilities, includes natural trigger terms, explicitly states when to use it, and draws clear scope boundaries. It is somewhat long but the length is earned by breadth of artifact types rather than fluff.

DimensionReasoningScore

Specificity

Lists many specific concrete actions: 'Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks... animations, 3D objects, research reports, HTML email, diagrams, fliers'.

3 / 3

Completeness

Clearly answers both what (the enumerated artifact types) and when via the explicit 'Use whenever the user asks to...' trigger clause.

3 / 3

Trigger Term Quality

Excellent coverage of natural user terms: 'design, mock up, prototype, wireframe, visualize, explore, or make a PPT/deck' plus 'even if they do not say "design"', covering common phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche (HTML design artifacts) with distinct triggers and an explicit scope boundary ('NOT arbitrary HTML, so confirm the target is such a deck first'), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

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

relative_links

Relative link issues: 25 missing

Warning

Total

15

/

16

Passed

Repository
JimLiu/baoyu-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.