CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-quality-gates

Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 lean, well-sequenced validation workflow with genuine feedback loops, explicit pass criteria, and a properly disclosed one-level reference to a real, detailed checklist. The weaknesses are localized: the step-4 validator script path is unresolvable within this bundle and no command invocation is shown for it.

Suggestions

Resolve the step-4 dependency: either bundle the validator (e.g. as scripts/validate_package.py with an invocation example like 'python scripts/validate_package.py deck.pptx -o report.json') or state where it lives and how to locate it.

Note in step 4 or the artifacts section what to do when the validator is unavailable for non-production decks, so the workflow degrades explicitly rather than silently.

DimensionReasoningScore

Conciseness

The 24-line body is lean and dense: 'Treat deterministic failures as repair work, not exceptions' and the one-line pass criteria earn their tokens, with zero explanation of concepts Claude already knows (no 'what is OOXML' padding). This matches anchor 5 ('lean and efficient; assumes Claude's competence; every token earns its place') and exceeds anchor 4, which requires trimming some over-explanation — there is none to trim.

5 / 5

Actionability

Most guidance is concrete and executable: apply the real 'references/audit-checklist.md' (verified to exist and to contain concrete checks like the overlap predicate and OOXML validation), compare slide count/bounds/hidden slides, and check named accessibility items. It sits between anchors 3 and 4: below 5 because step 4's 'pptx-reference-deck-analysis/scripts/validate_package.py' path does not exist in this bundle and no invocation syntax is given, but noticeably above 3 since six of seven steps are fully actionable with a resolvable reference.

4 / 5

Workflow Clarity

The 7-step workflow has an explicit sequence, validation checkpoints (steps 2–6 audit geometry, actual bounds, accessibility, and package integrity), an explicit feedback loop ('Repair the spec or task-local builder, rebuild, and rerun the same checks'), a checklist for the complex process, and a separate pass-criteria section. This matches anchor 5 exactly, including the required validate→fix→retry loop for XML/document manipulation.

5 / 5

Progressive Disclosure

The body is a short overview with a well-signaled, one-level-deep reference ('See references/audit-checklist.md for the complete checklist') that resolves to a real file — close to anchor 5. It drops to 4 because 'pptx-reference-deck-analysis/scripts/validate_package.py' points outside the bundle and does not resolve, leaving a navigation gap; anchor 5 requires all referenced content appropriately split and easy to navigate.

4 / 5

Total

18

/

20

Passed

Description

71%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 tight, third-person, appropriately concise description with a clear niche and explicit trigger clause. Its main weakness is trigger-term coverage: it omits the natural synonyms (PowerPoint, presentation, .pptx) users would most likely say, and the what/when are fused into a single clause rather than independently stated.

Suggestions

Add common synonyms and the file extension to the trigger clause, e.g. 'Use when validating, repairing, or QA-checking a PowerPoint (.pptx) presentation or deck'.

State the what separately from the when, e.g. 'Validates and repairs editable PPTX decks for geometry, accessibility, native editability, source lineage, and OOXML package integrity. Use when ...'.

Include a natural trigger for the repair path users would phrase as fixing a broken or flagged deck (e.g. 'when a generated deck fails validation or needs fixing before delivery').

DimensionReasoningScore

Specificity

The description names concrete actions ("validating or repairing") and enumerates five specific quality dimensions ("geometry, accessibility, native editability, source lineage, and OOXML package integrity"), which matches the 'several specific actions; minor gaps' anchor. It falls short of a 5 because the actions stay at the dimension-list level rather than comprehensively covering what validation/repair concretely involves.

4 / 5

Completeness

Both what and when are present — the when is explicit ("Use when validating or repairing an editable PPTX deck") and the what (validate/repair for five named dimensions) is stated — matching anchor 4. It does not reach anchor 5 because the what is fused inside the single 'Use when' clause rather than stated independently with separate concrete trigger phrases, as the anchor-5 exemplar does.

4 / 5

Trigger Term Quality

Relevant keywords like "validating", "repairing", "PPTX", and "editable" are present, but common user phrasings are missing: no "PowerPoint", "presentation", "slides", "deck" variants beyond one use, or the ".pptx" extension. This matches anchor 3 ('relevant keywords but missing common variations or synonyms') and is below anchor 4, which expects good coverage with only a few natural terms missing.

3 / 5

Distinctiveness Conflict Risk

"editable PPTX deck" plus the niche concerns (native editability, source lineage, OOXML package integrity) carve out a distinct validation/repair niche with minimal overlap against general PPTX-creation skills. This clearly matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk') and does not fit anchor 4, which requires residual overlap risk with closely related skills.

5 / 5

Total

16

/

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

wshobson/agents

Path

plugins/pptx-deck-creation/skills/pptx-quality-gates/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.