CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-presentations

Create, revise, and verify slide presentations in an active iPolloWork Design session while retaining the selected template's visual and editable contracts.

Quality

75%

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 ./examples/plugin-packages/design-agent/skills/ipollowork-presentations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A model of token efficiency and progressive disclosure: a lean routing body over real, well-organized reference files. Its weaknesses are execution-side — abstract phrasing, one garbled sentence, and no explicit validation/feedback loop for the whole-deck batch operations the skill itself mandates.

Suggestions

Add an explicit validation checkpoint and retry loop for whole-deck batch edits (e.g. after a batch change, verify every affected slide and re-run the batch if any slide fails acceptance).

Fix the garbled sentence "Initial/full authoring plans needs before layout" — it is currently unactionable.

Replace vague directives like "apply the shared media workflow, including live capabilities, authorized model selection, actual placement and plan/check outcomes" with pointers to the specific sections of shared-guidelines.md that define each step.

DimensionReasoningScore

Conciseness

The body is ~24 lines with zero padding, no explanations of concepts Claude already knows, and every line carries a rule or routing instruction. It matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place") — nothing can be trimmed without losing content.

5 / 5

Actionability

There is real specificity in places — "stable `data-ipw-slide` roots", "semantic `--ipw-*` values", "separate `data-pptx-text`, `data-pptx-shape` and `data-pptx-image` objects", "`media/artifact_preview_review` is the sole client batch preview" — but much of the guidance is abstract ("apply the shared media workflow, including live capabilities, authorized model selection, actual placement and plan/check outcomes") and one sentence is garbled ("Initial/full authoring plans needs before layout"). That mixed profile fits anchor 3: some concrete guidance but incomplete, with key executable details deferred without precise signposting.

3 / 5

Workflow Clarity

The "Read by task" section gives per-task routing, and partial validation is present ("check font fit", "distinguish checked, unavailable and unverified work"), but there is no explicit validate → fix → retry feedback loop, and the skill mandates whole-deck batch operations ("shared token/style changes require one whole-deck batch") with no stated validation checkpoint — per the scoring notes that caps workflow_clarity at 3. It is above anchor 2 because the sequence and per-task reading order are defined, but below anchor 4 because checkpoints are implicit rather than explicit.

3 / 5

Progressive Disclosure

All three referenced files exist (references/slides-ppt.md, references/shared-guidelines.md, references/layout.md), references are one level deep (only sibling cross-links, no chains), and each is conditionally gated ("Read Layout selection only when selecting or recomposing a layout"), exactly matching anchor 5's clear overview with well-signaled one-level-deep references. slides-ppt.md is well-sectioned, and the body's routing maps cleanly onto those sections.

5 / 5

Total

16

/

20

Passed

Description

66%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 concise, third-person description with a clear what and a distinct niche, but the when-half is missing entirely — no explicit trigger clause tells Claude (or the router) when to invoke it. Adding a "Use when..." clause with natural trigger phrases would lift completeness and trigger quality simultaneously.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to create, edit, re-theme, or check slide presentations/decks inside an iPolloWork Design session."

Add natural synonyms and file extensions users actually say — "deck", "slides", "Powerpoint", ".pptx" — to improve trigger-term coverage.

Optionally enumerate the covered task types (theme edits, layout selection, asset placement, delivery verification) to close the remaining specificity gap.

DimensionReasoningScore

Specificity

Names the domain (slide presentations in an iPolloWork Design session) and three concrete actions — "Create, revise, and verify" — plus the contract-retention obligation. It falls short of anchor 5 because layout selection, theme edits, asset work, and delivery are not surfaced as capabilities, but it clearly exceeds the 1-2-action scope of anchor 3.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance; "in an active iPolloWork Design session" is a scope qualifier, not a trigger phrase, so per the judging guidelines completeness is capped at 3. It is not a 2 because the what-half is fully specified, and not a 4 because the when-half is absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"slide presentations", "create", "revise", "verify", and "template" are natural phrases a user would say, comparable in density to anchor 4's "PDF files, forms, document extraction". A few common variations are missing ("deck", "slides", "PowerPoint", ".pptx"), so it does not reach anchor 5's synonym/extension coverage, and it is well above anchor 3's sparse keyword sets.

4 / 5

Distinctiveness Conflict Risk

The "iPolloWork Design session" scope and "template's visual and editable contracts" carve a distinct niche with minimal conflict risk, matching anchor 4. It stops short of anchor 5 because generic presentation keywords (slides, pptx, decks) could still pull this skill in for tasks better served by generic presentation skills.

4 / 5

Total

15

/

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

Devin-AXIS/iPolloWork

Path

examples/plugin-packages/design-agent/skills/ipollowork-presentations/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.