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

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

67%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 well-structured operating contract with genuinely concrete tool-call syntax, explicit validation/recheck loops, and verified one-level-deep references. Its main weakness is conciseness: long multi-clause sentences and repeated directives across sections force re-reading, and some sequencing lives in prose rather than the numbered workflow.

Suggestions

Consolidate the preview/verification prohibitions (temporary servers, ad hoc screenshots, per-slide captures) into one place — they currently appear in both the opening paragraph and step 7.

Break the longest sentences (e.g., step 3's planning paragraph and the media-boundaries paragraph) into short imperative bullets; each currently stacks 4-6 clauses.

Move some environment-specific policy detail (custom template scope, media/mode boundaries) into the existing reference files and keep SKILL.md to the workflow plus pointers.

Dimension	Reasoning	Score
Conciseness	The body is dense policy prose with no padding of concepts Claude already knows, but it repeats itself: the temporary-server/screenshot prohibitions appear in both the opening paragraph and step 7, and preview/verification rules recur across the intro, workflow, and completion sections. Many single sentences carry 5+ nested clauses that could be tightened or split.	3 / 5
Actionability	Concrete tool calls with exact parameter syntax ("call `media/artifact_media_review` phase=plan", "`media/artifact_preview_review` once with `kind=\"slides\"`") and named paths (`design/<session-id>/`, `design-tokens.css`, `brief.json`, `core-v1-index.md`) make most guidance executable, though a sizable share remains abstract policy language ("preserve the template's distinctive visual system").	4 / 5
Workflow Clarity	A 7-step numbered workflow with explicit validation checkpoints (batched preview check, collect defects, one consolidated repair, one targeted recheck, shared-style batch recheck) and honest failure handling ("Missing client access means visual verification is incomplete, not passed") satisfies the batch-operation validation requirement. It stays below 5 because some ordering is implicit — the pre-authoring media call and reference reading live in prose sections rather than the numbered sequence.	4 / 5
Progressive Disclosure	Three one-level-deep references (shared-guidelines.md, slides-ppt.md, layout.md), all present in the bundle, are clearly signaled in a dedicated "Required references" section with reading order and handling rules. Minor gaps: dense monolithic policy sections that could live in a reference file, and mixed mention of session-side files (`core-v1-slides/` catalogs) that are not part of the bundle.	4 / 5
	Total	15 / 20 Passed

Description

58%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 concrete capabilities in third person with a well-defined niche, but it omits any explicit trigger guidance and misses the natural synonyms (PPT, PowerPoint, .pptx, deck) users would actually say. Adding a "Use when..." clause with those trigger terms would raise both completeness and trigger quality substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when working on slides, decks, PPT/PPTX presentations, or template restyling inside an iPolloWork Design session."

Include natural synonyms and file extensions users would say (PPT, PowerPoint, .pptx, deck) so the description matches real user phrasing.

Mention one or two more concrete capabilities (e.g., layout selection, export verification) to round out coverage beyond create/revise/verify.

Dimension	Reasoning	Score
Specificity	"Create, revise, and verify slide presentations" lists three concrete actions plus a concrete constraint ("retaining the selected template's visual and editable contracts"), but coverage has gaps (no layouts, exports, or media terms), so it falls between the 3 and 5 anchors.	4 / 5
Completeness	The "what" is clear (create, revise, verify presentations with template contracts), but there is no "Use when..." clause or equivalent explicit trigger guidance; "in an active iPolloWork Design session" is only a weak scope qualifier, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"slide presentations" is a natural phrase, but common variations users would say — "PPT", "PowerPoint", ".pptx", "deck", "slides" — are all missing, matching the anchor for relevant keywords without common synonyms rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	"iPolloWork Design session" and "the selected template's visual and editable contracts" carve a distinct niche, but a user asking to "make slides" could still match a generic PPTX skill since no distinctive trigger phrases are given — mostly distinct with minor overlap risk, not the clear-trigger anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 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
Commit: dada31d

Reviewed: 13 hours ago

Table of Contents

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.