Tessl • The management layer for AI agent skills

SkillPublic

design-pull

Pull a Claude Design project into a local, git-ignored design folder and keep a catalogue of what was pulled and implemented. Use for "/design-pull", "pull the design", "sync designs", or to mark a design file as implemented after committing UI code built from it.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An unusually tight operational skill: concrete commands, strict quoting and untrusted-data rules, and a pull workflow with genuine error-recovery loops at every exit code. The only structural observation is that all detail lives in one ~100-line file with no bundle split.

Dimension	Reasoning	Score
Conciseness	Every line is operational — commands, exit codes, quoting rules — with no explanation of concepts Claude already knows; even the "Side effect: results from other MCP servers... over about 8 KB are also saved to files" note is decision-relevant context, not padding. Lean throughout; matches the 5 anchor.	5 / 5
Actionability	Fully executable, copy-paste-ready guidance: exact MCP setup command, JSON env config, "yarn tsx .claude/skills/design-pull/design.ts <command> ..." invocation, quoting rules with the '\'\'' escape, and concrete per-flag commands like "plan '<folder>' '<listing>' --out '<run>/plan.json'". Matches the 5 anchor.	5 / 5
Workflow Clarity	The 8-step Pull workflow is clearly sequenced with a pre-flight check (step 1, output limit), explicit stop conditions ("stop and show the error", --force "only when the user confirms"), and feedback loops for exit codes 2 (re-read, re-write, --retry) and 3 (parent listing, --listing). Removed files are moved to .removed/ rather than deleted. Exemplary validation; matches the 5 anchor.	5 / 5
Progressive Disclosure	Well-sectioned single file (Prerequisites, Rules, Arguments, Pull, Mark and unmark, Agent rule) with clear navigation, and its two external pointers (the spec doc and the design.ts helper) are one level deep and clearly signaled. Not 5 because ~100 lines of dense operational detail (the full exit-code matrix and import procedures) sit inline in one file, which could be split, and the skill ships no bundle files to verify against.	4 / 5
	Total	19 / 20 Passed

Description

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

A strong description: concrete verb-led actions, explicit third-person voice, and a well-formed "Use for" clause with quoted trigger phrases. The only weaknesses are a few missing natural synonyms and a slight pull-vs-sync trigger ambiguity.

Suggestions

Add one or two natural synonyms such as "download the design" or "import designs" to broaden trigger coverage without adding length.

Clarify direction in the trigger terms (e.g. "pull/download designs from Claude Design") so "sync designs" cannot match a push/sync counterpart skill.

Dimension	Reasoning	Score
Specificity	Three verb-led concrete actions — "Pull a Claude Design project into a local, git-ignored design folder", "keep a catalogue of what was pulled and implemented", "mark a design file as implemented after committing UI code" — cover the skill's main capabilities (pull, catalogue, mark). Not 4 because coverage is comprehensive rather than having minor gaps; unmark's absence is trivial.	5 / 5
Completeness	Explicitly answers both: what ("Pull a Claude Design project into a local, git-ignored design folder and keep a catalogue...") and when ("Use for '/design-pull', 'pull the design', 'sync designs', or to mark a design file as implemented...") with concrete quoted trigger phrases. Matches the 5 anchor exactly.	5 / 5
Trigger Term Quality	"pull the design", "sync designs", "/design-pull", and "mark a design file as implemented" are natural phrases users would say. Not 5 because common synonyms like "download the design", "import designs", or "Claude Design" are missing.	4 / 5
Distinctiveness Conflict Risk	"Claude Design project", "catalogue", and pull-specific framing create a clear niche, but the "sync designs" trigger invites overlap with a plausible design-sync/push counterpart skill. Mostly distinct with minor overlap risk — fits the 4 anchor; not 5 because of that sync ambiguity.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: .claude/skills/design-pull/SKILL.md
Revision: a85ef55

Reviewed: 1 day ago

Discovery Implementation Validation

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.

design-pull

Table of Contents

Is this your skill?