CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orange-clean-paper-saas

Create a clean paper-toned SaaS design system with warm neutrals, orange accent signals, rounded premium forms, and polished product illustration surfaces.

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 ./agent-skills/web-design/orange-clean-paper-saas/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 lean, well-sectioned design brief with unusually concrete styling direction for an instruction-only skill, and the "Avoid" and "Tuning knobs" sections add genuine calibration value. Its key defects are the entirely empty "Workflow" section and the verbatim duplication of the description under "Use When", which undermine both workflow clarity and organization.

Suggestions

Either delete the empty "## Workflow" section or populate it with an actual sequence (e.g. 1. choose paper tones, 2. establish orange signal usage, 3. build form panel, 4. build illustration panel, 5. check contrast against the Avoid list).

Replace the verbatim-repeated "Use When" bullet with genuinely additional trigger guidance (SaaS onboarding, landing pages, product mockups) instead of duplicating the frontmatter description.

Add a small set of concrete token-level anchors — a handful of hex values for the paper surfaces and orange, and a radius/shadow scale — so the guidance can be executed without further specification.

DimensionReasoningScore

Conciseness

The body is composed of terse, directive bullets ("Use orange as the primary signal and action color for steps, buttons, active states...") with no explanation of concepts Claude already knows. It is not a 5 because the "Use When" section duplicates the frontmatter description verbatim and the empty "Workflow" header wastes tokens.

4 / 5

Actionability

As an instruction-only design skill, the guidance is genuinely concrete: named surface tones ("warm off-white, cream, parchment, and pale stone"), specific application targets ("step markers, primary CTAs, highlight icons, link text, micro-badges"), and recommended layouts ("Split onboarding card with a form panel on one side..."). It is not a 5 because nothing is specified at an executable level — no actual color values, type scale, radius/shadow tokens, or a worked example that could be applied directly.

4 / 5

Workflow Clarity

The "## Workflow" section (line 11) is completely empty, so no sequence of steps is ever articulated — the body reads as a style brief, not a process. It is not a 2 because the surrounding sections (Visual target → Implementation guidance → Recommended patterns) provide a rough implicit progression, and not a 4+ because an explicitly labeled workflow exists but contains nothing.

3 / 5

Progressive Disclosure

At under 50 lines with no bundle files, the skill needs no external references, and it is organized into clearly labeled, scannable sections (Scope, Visual target, Implementation guidance, Recommended patterns, Tuning knobs, Avoid). It is not a 5 because of two organization defects: the empty "Workflow" header and the "Use When" section that restates the description verbatim.

4 / 5

Total

15

/

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 communicates a clear and specific design direction in third person, with good natural keyword coverage and a distinct stylistic niche. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and leaves the triggering conditions implicit.

Suggestions

Append an explicit trigger clause, e.g. "Use when building SaaS onboarding flows, landing pages, or product mockups that call for warm paper tones and an orange accent."

Mention the concrete artifact types users would name (landing page, onboarding flow, product mockup, UI card) to improve trigger term coverage and distinctiveness.

State one or two additional concrete actions beyond "create" (e.g. "apply across page shells, forms, CTAs, and illustration zones") to lift specificity.

DimensionReasoningScore

Specificity

The description names the domain ("paper-toned SaaS design system") with specific stylistic parameters ("warm neutrals, orange accent signals, rounded premium forms"), but describes only one action — creating the system — rather than several concrete actions. It is not a 4 because the anchor for 4 requires a list of several specific actions, which this does not provide.

3 / 5

Completeness

It clearly answers "what" ("Create a clean paper-toned SaaS design system with warm neutrals, orange accent signals...") but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is specific and well-articulated.

3 / 5

Trigger Term Quality

Terms like "SaaS design system", "warm neutrals", "orange accent", "forms", and "product illustration surfaces" are natural phrasings a user would use when requesting this style. It falls short of 5 because common variations users would actually say — "landing page", "onboarding", "UI", or specific artifact types — are missing.

4 / 5

Distinctiveness Conflict Risk

The warm-paper-plus-orange SaaS aesthetic carves out a fairly distinct niche among design-direction skills, with only minor overlap risk against other brand/theme skills. It is not a 5 because without explicit trigger phrases, it could still fire for generic SaaS UI or warm-palette requests outside its intended scope.

4 / 5

Total

14

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MengTo/Skills

Path

agent-skills/web-design/orange-clean-paper-saas/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.