CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slides-polish

Per-page Codex review + targeted python-pptx / Beamer fixes for academic talk slides. Use AFTER /paper-slides (or any externally generated PPTX/Beamer) when the deck looks 'mostly OK' but the user wants a final pass that aligns visual weight with a reference, bumps PPTX fonts to projector-readable size, kills italic style leaks, fixes text-frame overflow, and catches per-slide layout drift. Trigger phrases: "polish slides", "slides 排版不对", "PPTX 字体太小", "和 Beamer 比一下", "per-page review", "和 codex 一页一页过".

Quality

85%

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

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

Highly actionable and exceptionally well-sequenced, with real validation feedback loops and domain-specific gotchas Claude would not know. The costs are token weight from repeated invariants and a monolithic structure that inlines reference material while simultaneously depending on external shared files, contradicting its own "zero external dependencies" rationale.

Suggestions

Move the style-preset tables (Phase 2 Beamer fix patterns, Phase 3c PPTX pitfalls, inspector JSON schema) into references/ files (e.g., references/fix-catalogs.md, references/style-presets.md), keeping SKILL.md as a phase-by-phase overview with clearly signaled one-level-deep links.

State each hard invariant once (in Hard Invariants) and reference it from Constants and the phases instead of repeating the reference-required, xhigh-reasoning, anonymity, and page-number rules verbatim in multiple sections.

Trim the "Empirical Origin" and "Prior Skill Relationship" sections to one or two lines each; the empirical narrative duplicates points already made in the Phase 1 rationale.

DimensionReasoningScore

Conciseness

The operational core (commands, font tables, fix catalogs) is dense and non-padding, but the ~570-line body restates load-bearing rules multiple times (reference-required, xhigh reasoning, anonymity placeholders, page-number cap each appear 2-3 times across Constants, phases, and Hard Invariants) and includes narrative sections ("Empirical Origin", "Prior Skill Relationship") that could be cut or tightened.

3 / 5

Actionability

Copy-paste-ready throughout: exact render commands ("pdftoppm -r 150 -png <pdf> <out-stem>", "soffice --headless --convert-to pdf"), full per-page Codex prompt templates, an executable find_shape Python helper with abort semantics, concrete LaTeX macros, and specific hex/pt values. The inspector and apply_fix are specified as contracts rather than code, with the flexibility explicitly justified ("Implementations may evolve; the contract is what downstream phases depend on").

5 / 5

Workflow Clarity

Phases 0-5 are clearly sequenced with explicit validation checkpoints: re-triage with a loop-back rule ("If > 2 NEEDS-WORK remain, loop back to Phase 1"), speaker-notes byte-level integrity check, anonymity fail-closed scan, assert-unique shape matching, checkpoint snapshots every 3 slides, and resumable state via POLISH_STATE.json — matching the feedback-loop-heavy top anchor.

5 / 5

Progressive Disclosure

No references/, scripts/, or assets/ directories exist; everything (style-preset tables, Beamer/PPTX fix catalogs, inspector JSON schema) is inlined in one ~570-line SKILL.md, while six ../shared-references/*.md files are referenced from outside the bundle. Headers make it navigable, but the catalog and preset material clearly belongs in separate one-level-deep reference files.

3 / 5

Total

16

/

20

Passed

Description

92%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 strong description: concrete action inventory, explicit use-timing relative to /paper-slides, and a bilingual trigger-phrase list. The only weakness is that English synonym/extension coverage (e.g., ".pptx", "slide formatting") is thinner than its Chinese counterpart.

DimensionReasoningScore

Specificity

Lists multiple concrete, comprehensive actions: "per-page Codex review + targeted python-pptx / Beamer fixes", "aligns visual weight with a reference, bumps PPTX fonts to projector-readable size, kills italic style leaks, fixes text-frame overflow, and catches per-slide layout drift" — no vague filler and no coverage gaps within its niche.

5 / 5

Completeness

Clearly answers both questions: the "what" is the enumerated polish actions, and the "when" is explicit ("Use AFTER /paper-slides … when the deck looks 'mostly OK'") and reinforced with concrete trigger phrases — matching the top anchor exactly.

5 / 5

Trigger Term Quality

Explicit trigger phrases in two languages ("polish slides", "slides 排版不对", "PPTX 字体太小", "和 Beamer 比一下", "per-page review", "和 codex 一页一页过") give good natural-keyword coverage, but common English variants like "fix slide formatting", "slide layout", or the ".pptx" extension are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (post-generation visual polish) with distinct triggers; the "Use AFTER /paper-slides" clause explicitly separates it from the closest related skill, minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (579 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

12

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/slides-polish/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.