CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-design-graphics

Create or edit posters and social card series in the current iPolloWork Design session.

Quality

68%

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-graphics/SKILL.md

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

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 maximally token-efficient guardrail layer: dense with invariants, routing rules, and explicit verification requirements, with detail correctly pushed to per-type reference files. Its weaknesses are the implicit, unnumbered workflow with no failure-recovery loop, and delegation of the actual edit mechanics to files outside this skill's own bundle without local copies or named fallbacks.

Suggestions

Present the operating procedure as a short numbered sequence (route → read source/tokens → preserve invariants → apply type rules → verify) with an explicit checkpoint and recovery step for failed acceptance checks.

Name the specific media/asset workflow file (equivalent to the poster/card rule links) instead of the vague "Asset work uses its media workflow", so every delegated instruction has a resolvable path.

Either vendor the referenced rule files into this skill's own references/ directory or explicitly state that they are intentionally shared with ipollowork-design-studio, so the cross-bundle dependency is a documented decision rather than a fragile path.

DimensionReasoningScore

Conciseness

The body is extremely lean: every sentence is a routing rule, invariant, or check ("Preserve `--ipw-*` tokens/variable bindings, component IDs, editable/locked markers"), with zero explanation of concepts Claude already knows and no padding. This matches 'lean and efficient; every token earns its place' — it is not merely 'mostly efficient' (anchor 3) nor does it contain the minor over-explanation of anchor 4.

5 / 5

Actionability

There are concrete specifics ("design/<session-id>/", "design-tokens.css", per-category reference links), but the actual edit mechanics are entirely delegated to external files and directives like "Asset work uses its media workflow" never name the file to use. This is 'some concrete guidance but incomplete; missing key details', below the mostly-executable guidance of anchor 4.

3 / 5

Workflow Clarity

A logical order exists (route by category, read source and tokens, preserve invariants, apply type rules, scope reading by task, run acceptance) and validation is stated ("Follow active type acceptance... Verify affected editing/interaction and requested supported exports; disclose unavailable/unperformed checks"). However, the sequence is implicit rather than a clear ordered workflow and there is no error-recovery loop for failed acceptance, fitting anchor 3 rather than anchor 4's 'clear sequence with most checkpoints'.

3 / 5

Progressive Disclosure

References are one level deep, clearly signaled as named links, and split per category (poster rules vs card rules vs shared guidance), and detail is appropriately kept out of the overview. But all referenced files live in a sibling skill's bundle (../ipollowork-design-studio/references/) rather than this skill's own bundle, and this skill ships no references/ directory at all — a structural/fragility gap that keeps it below the clean anchor 5.

4 / 5

Total

15

/

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 what in an identifiable niche, but reads more like a scope declaration than a trigger: it lacks an explicit 'Use when...' clause and offers few natural trigger synonyms. Adding trigger phrasing and slightly broader action coverage would lift most dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create, edit, or iterate on posters or social card series in an iPolloWork Design session.'

Include natural synonyms users would say (flyer, graphic, social media card, card series) so the skill triggers on common phrasings.

Distinguish the skill from the sibling ipollowork-design-studio in the description itself (e.g., mention it applies to manifest categories 'poster' and 'cards') to reduce overlap ambiguity.

DimensionReasoningScore

Specificity

"Create or edit posters and social card series" names the domain and exactly two concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, so it falls below anchor 4.

3 / 5

Completeness

The 'what' is clear (create or edit posters and social card series), but there is no 'Use when...' clause; "in the current iPolloWork Design session" only weakly implies when. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"posters" and "social card series" are natural trigger terms, but common variations and synonyms a user would actually say (flyer, graphics, social media image, card) are missing. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (posters and social cards within iPolloWork Design sessions) and would not trigger for unrelated skills. The only overlap is with the closely related sibling skill ipollowork-design-studio, and the description offers no disambiguator for it, which is minor overlap risk with a closely related skill rather than the clear-niche/minimal-conflict of anchor 5.

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: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

Devin-AXIS/iPolloWork

Path

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