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

74%

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

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

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.

The body is an exemplary token-efficient router: no padding, real one-level-deep references, and strong conditional-loading discipline. Its weaknesses are compressed, sometimes grammatically broken instruction bullets that hurt actionability, and the absence of an explicit workflow sequence with validation checkpoints for edit and delivery operations.

Suggestions

Repair and clarify the compressed bullets — e.g. rewrite "Initial/full authoring plans needs before layout" and the asset-work bullet so each is an unambiguous instruction a reader can execute without interpretation.

Add a short ordered workflow (read source/tokens → plan → edit → validate/preview → deliver) with explicit checkpoints, since edits and whole-deck batch previews are destructive/batch operations that currently lack a validation loop.

In the asset-work bullet, link the specific shared-guidelines.md media workflow section so the guidance is actionable rather than a jargon summary.

DimensionReasoningScore

Conciseness

The 19-line body is lean and dense with rules and routing instructions only — no padding, no explanations of concepts Claude already knows, and every line carries a constraint or a pointer.

5 / 5

Actionability

The task-mapped reading list with real markdown links to references/slides-ppt.md, references/shared-guidelines.md, and references/layout.md is concrete, but bullets like "apply the shared media workflow, including live capabilities, authorized model selection, actual placement and plan/check outcomes" and the garbled "Initial/full authoring plans needs before layout" are too compressed or ambiguous to act on without guessing.

3 / 5

Workflow Clarity

Content is organized by task type rather than as a sequence, and verification is only implicit ("plan/check outcomes", "the PPT acceptance section", "check editor/export behavior when affected") — there is no explicit edit→validate→deliver order with checkpoints, and batch preview/acceptance steps lack a feedback loop.

3 / 5

Progressive Disclosure

All three referenced files exist, are relevant, and are one level deep with clear markdown links; loading is task-conditioned ("Read Layout selection only when selecting or recomposing a layout", "Do not load layout catalogs or media guidance for unchanged assets") making navigation and conditional loading exemplary.

5 / 5

Total

16

/

20

Passed

Description

62%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 is distinct and reasonably specific, naming three concrete actions within a well-bounded niche. Its main weaknesses are the missing explicit "Use when..." trigger clause and the absence of common presentation synonyms (PPT, PowerPoint, .pptx) that users naturally say.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating, editing, or verifying presentations in an iPolloWork Design session, or when the user mentions slides, decks, PPT, or .pptx files."

Include common synonyms and file extensions (PPT, PowerPoint, .pptx, deck) so the description matches the natural phrases users say and the PPT-focused body content.

Broaden the action list to cover the skill's other capabilities (theme-only edits, asset generation, layout selection, delivery/preview verification) to close the coverage gaps.

DimensionReasoningScore

Specificity

"Create, revise, and verify slide presentations" names three concrete actions plus a specific constraint ("retaining the selected template's visual and editable contracts"), but coverage has minor gaps — theme edits, asset work, and delivery are handled by the skill yet unmentioned.

4 / 5

Completeness

The "what" is clear (create, revise, verify presentations under template contracts), but there is no "Use when..." clause or equivalent explicit trigger guidance; "in an active iPolloWork Design session" only weakly implies the when, so completeness is capped at 3.

3 / 5

Trigger Term Quality

"slide presentations", "template", and "Design session" are natural terms, but common synonyms users would say — PPT, PowerPoint, .pptx, deck — are absent even though the body is heavily PPT-focused, matching the anchor for relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"iPolloWork Design session" plus template visual/editable contracts define a clear niche with distinct triggers; virtually no other skill would fire on these terms.

5 / 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

.agents/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.