CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-slide-specification

Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.

Quality

77%

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 ./plugins/pptx-deck-creation/skills/pptx-slide-specification/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 exceptionally lean, well-organized contract that appropriately pushes schema detail to a verified one-level-deep reference. Its main weakness is workflow clarity: the author-to-build-to-verify sequence and the repair feedback loop are implicit in the body and only materialize in the reference, leaving validation checkpoints to be inferred rather than followed.

Suggestions

Add a short numbered authoring sequence to the body (draft summary/layout_policy, build each slide's layout_tree, run the task-local builder, verify against the contract) so the end-to-end workflow does not have to be reconstructed from the reference.

Surface the verification loop inline in the Build contract: state that after building, actual object bounds are compared with the contract and out-of-bounds or overlapping objects are repaired per the reference's repair order.

Inline a minimal one-slide JSON snippet (or enumerate the allowed `classification` values) so the required contract is executable without first opening the reference.

DimensionReasoningScore

Conciseness

The ~26-line body is dense with contract specifics and contains no filler, no explanations of concepts Claude already knows, and no padding; every sentence adds constraints (e.g. 'No renderer may decide placement, shrink text, or infer layout after the audit.'). Nothing could be trimmed, so anchor 4's 'minor instances of over-explanation' does not apply.

5 / 5

Actionability

Guidance is highly concrete — required per-object fields, named native kinds, a 9 pt minimum, `Inches(...)` bbox mapping, and rejecting zero or negative geometry before adding an object — but there is no inline example of the JSON shape, and terms like `classification` values and `layout_design` objects are only illustrated in the reference. Mostly executable with minor gaps matches anchor 4; anchor 5 would require inline common-case examples covering the schema.

4 / 5

Workflow Clarity

Sections are logically ordered (contract, authoring rules, build contract) and one inline checkpoint exists ('Reject zero or negative geometry before adding an object'), but the end-to-end author, build, verify, repair sequence is implicit in the body — the rebuild-and-compare feedback loop lives only in references/layout-contract.md. Steps listed with checkpoints missing or implicit matches anchor 3; anchor 4 would require the sequence with most checkpoints present in the body itself.

3 / 5

Progressive Disclosure

The under-50-line body is cleanly sectioned and schema detail is appropriately split into a single, real, one-level-deep reference, clearly signaled ('See `references/layout-contract.md` for the compact schema and repair guidance') and verified to exist with exactly the promised compact schema and repair guidance. This matches the clear-overview, well-signaled-reference anchor.

5 / 5

Total

17

/

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 carves a distinct, specific niche and includes an explicit, well-targeted 'Use when' clause, but it embeds the capability inside the trigger sentence, omits natural synonyms (PowerPoint, presentation, slides, .pptx), and leans on the jargon phrase 'coordinate-explicit'. It is functional and above average overall, with clear room to broaden trigger coverage and separate the what from the when.

Suggestions

Lead with a third-person capability statement before the trigger, e.g. 'Authors and repairs coordinate-explicit JSON specifications for editable PPTX decks. Use when...' so the what is explicit rather than embedded in the when-clause.

Add natural trigger synonyms users would actually say: PowerPoint, presentation, slides, slide layout, and the .pptx file extension.

Replace or gloss the internal jargon 'coordinate-explicit' with natural phrasing such as 'explicit final coordinates / inch bounding boxes' so the trigger reads the way a user would phrase the request.

DimensionReasoningScore

Specificity

The description names the domain ('coordinate-explicit JSON specification for an editable PPTX deck') and exactly two concrete actions ('authoring or repairing'), matching the anchor for 1-2 concrete actions without comprehensive coverage. Score 4 requires several listed specific actions, which a two-verb trigger clause does not reach.

3 / 5

Completeness

An explicit 'Use when...' clause states when to trigger the skill, and the 'what' is conveyed only through the gerund phrase ('authoring or repairing a coordinate-explicit JSON specification') rather than a standalone capability statement. It clears anchor 3 because the 'when' is explicit and specific, but does not reach anchor 5's fully separated what-and-when with multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords are present (PPTX, deck, JSON, specification, authoring, repairing), but common variations a user would naturally say — PowerPoint, presentation, slides, layout, .pptx — are missing, and 'coordinate-explicit' is internal jargon rather than a user phrase. This matches 'some relevant keywords but missing common variations or synonyms' better than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

The niche (coordinate-explicit JSON specifications for editable PPTX decks) is distinct with narrow triggers, but 'authoring... a PPTX deck' could still overlap with a general presentation-creation skill. Minor overlap risk with a closely related skill matches anchor 4; anchor 5 would require triggers with essentially no conflict potential.

4 / 5

Total

14

/

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-slide-specification/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.