CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-design-studio

Route iPolloWork Design sessions by category and author other designs.

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 ./.agents/skills/ipollowork-design-studio/SKILL.md

The canonical home for this skill is ipollowork-design-studio in Devin-AXIS/iPolloWork

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 an exceptionally lean routing overview with excellent progressive disclosure to real, one-level-deep reference files and a clear precedence-ordered workflow. Its main weakness is actionability: the 'Other designs' instructions lean on delegated jargon ('apply acceptance checks', 'resolve installed links once') without concrete steps.

Suggestions

Spell out what the 'Other acceptance, affected editing/interaction and requested supported export checks' concretely involve — at minimum name the specific checks or give a one-line example — rather than delegating entirely to references.

Make 'Resolve installed links once; report missing references without other-checkout searches' operationally concrete: state what resolving a link means and what a report should contain.

Add an explicit pre-completion validation step (e.g., what to verify before declaring an edit complete) so the edit workflow has a visible checkpoint instead of an implied one.

DimensionReasoningScore

Conciseness

The 25-line body is pure telegraphic instruction — "Hand off by manifest category before source reads/edits or shared/type guidance; retain the category." — with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the lean anchor 5.

5 / 5

Actionability

The routing table links, exact paths ("design/<session-id>/", "design-tokens.css"), and "--ipw-*" token names are concrete, but directives like "Apply Other acceptance, affected editing/interaction and requested supported export checks; disclose unverified results" provide no concrete steps or examples of what those checks entail. Some concrete guidance exists but key execution details are missing, matching anchor 3 rather than 4.

3 / 5

Workflow Clarity

The sequence is explicit (hand off before reads/edits, then read source, read affected rules, apply checks, resolve links once) and checkpoints are stated ("Stale selection requires a new locator before edits", acceptance/export checks, "report missing references"). This matches anchor 4 with most checkpoints present; it is not 5 because the validation details are delegated to references with no explicit validate-fix-retry loop.

4 / 5

Progressive Disclosure

The body is a lean overview router that clearly signals one-level-deep references — [Other rules](references/design-other.md), [Design authoring](references/design.md), [Shared guidance](references/shared-guidelines.md) — all of which exist in the bundle. Content is appropriately split and navigation is easy, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Description

53%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 states a clear, domain-specific 'what' with acceptable distinctiveness, but it omits any 'when to use' trigger guidance and lacks natural trigger terms and action synonyms. It reads as a functional summary rather than an invocation description.

Suggestions

Add an explicit 'Use when...' clause naming the invocation scenarios (e.g., 'Use when a manifest routes an iPolloWork Design session or when authoring non-categorized designs').

Include natural trigger terms and synonyms users would say, such as 'design session', 'site', 'app', 'poster', 'cards', 'article', 'report', and 'slides', to improve trigger-term coverage.

Enumerate the concrete actions more fully (route by manifest category, hand off to sibling design skills, edit existing other-design sources, author new designs) to raise specificity.

DimensionReasoningScore

Specificity

"Route iPolloWork Design sessions by category" and "author other designs" name the domain plus 1-2 concrete actions, but coverage is thin (no mention of editing, exporting, or which categories). This matches the anchor for naming a domain with 1-2 concrete actions; it falls short of 4 because it does not list several specific actions with only minor gaps.

3 / 5

Completeness

The 'what' is clear (route sessions by category, author other designs), but the 'when' is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

"iPolloWork Design", "category", and "designs" are relevant keywords, but the description contains no natural trigger phrases ("Use when..."), synonyms, or session-type terms (poster, slides, site, app). Some relevant keywords are present while common variations are missing, matching anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

"iPolloWork Design" is a distinct niche with category-based routing to named sibling skills, so overlap risk is limited to those closely related design skills. Mostly distinct with minor overlap risk matches anchor 4; it is not 5 because no distinct triggers separate it from its own siblings.

4 / 5

Total

13

/

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

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

Devin-AXIS/iPolloWork

Path

.agents/skills/ipollowork-design-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.