CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-slides

Generate conference presentation slides (beamer LaTeX → PDF + editable PPTX) from a compiled paper, with speaker notes and full talk script. Use when user says "做PPT", "做幻灯片", "make slides", "conference talk", "presentation slides", "生成slides", "写演讲稿", or wants beamer slides for a conference talk.

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, well-validated phased workflow and executable code/templates. It is slightly verbose in places and, lacking any bundle files, keeps content monolithic rather than splitting large templates into referenced files.

Suggestions

Move the full beamer LaTeX template, talk-script manuscript, and Q&A templates into reference files under references/ and link to them one level deep to improve progressive disclosure.

Trim inferable narrative ('Unlike posters... slides tell a temporal story') and placeholder prose to tighten conciseness and respect the token budget.

Bundle the referenced tools/extract_paper_style.py helper and shared-references/integration-contract.md, or remove the references if they are not part of this skill, so referenced paths are real and verifiable.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and templates, but includes exposition Claude could infer (the 'Unlike posters... slides tell a temporal story' narrative, long rationale tables, and full placeholder-prose templates for the talk script and Q&A) that could be tightened. Not a 3 because of this padded narrative and template prose; not a 1 because the bulk is concrete, executable guidance rather than concept explanation.

2 / 3

Actionability

Provides fully executable guidance: concrete bash checks ('which pdflatex', 'ls $PAPER_DIR/sections/*.tex'), a complete beamer LaTeX template, a python-pptx generation script outline, and an explicit state JSON schema. Not a 2 because the code is complete and copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

An explicit 8-phase sequence (0-8) with state persistence after each phase, a STOP checkpoint in Phase 1, and a Phase 4 validation loop (parse error → fix → recompile, max 3 attempts, pdfinfo page-count verification) plus AUTO_PROCEED=false enforcing confirmation. Not a 2 because validation checkpoints and feedback loops are explicit, not merely implied.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent), yet the ~600-line body keeps large inline templates (full LaTeX template, talk script, Q&A) that could be split into reference files, and references an external helper (tools/extract_paper_style.py) and shared-references/integration-contract.md not present in the bundle. Not a 3 because content that should be separate is inline and referenced paths are unverifiable; not a 1 because sections are well-organized and references are at most one level deep.

2 / 3

Total

10

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete, clearly stating both what the skill produces and when to invoke it with natural multilingual trigger terms. It is distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Generate conference presentation slides', 'beamer LaTeX → PDF + editable PPTX', 'with speaker notes and full talk script', matching the anchor for listing multiple specific concrete actions. It is not a 2 because it goes beyond naming a domain and partial actions to enumerating several distinct deliverables.

3 / 3

Completeness

Explicitly answers both 'what' (generate slides/PPTX/notes/script from a compiled paper) and 'when' via an explicit 'Use when user says...' trigger clause. Not a 2 because the trigger guidance is explicit rather than only implied.

3 / 3

Trigger Term Quality

Provides broad natural-term coverage in two languages ('make slides', 'conference talk', 'presentation slides', '做PPT', '做幻灯片', '生成slides', '写演讲稿', 'beamer slides for a conference talk') a user would actually say. Not a 2 because it covers many common variations rather than just a few.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (conference talk slides from a paper) with distinct triggers unlikely to fire for unrelated skills. Not a 2 because the scope is specific enough to avoid overlapping with general document or poster skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (632 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

Total

13

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.