CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-talk

End-to-end conference talk pipeline: paper → slide outline → Beamer + PPTX → per-page polish → assurance checks (claim / citation / anonymity) → final export and report. Default-good for academic conference talks (NeurIPS / ICML / ICLR / VALSE / 投稿 talks). Trigger phrases: "做 talk", "做 PPT 全流程", "talk pipeline", "end-to-end slides", "做演讲", "conference talk full workflow". Use when the user wants the complete talk artifact, not just a slide deck.

Quality

90%

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

81%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 strong orchestration skill: the workflow is unambiguously sequenced with validation and fail-closed feedback loops at every phase, and nearly all steps carry exact commands and file contracts. The main costs are a duplicated staging spec, an anecdotal Empirical Origin section, and a couple of mechanism-free steps (anonymity scan, verdict de-staging).

Suggestions

Remove the duplicate audit-input/ staging tree from Output Layout (keep only the Phase-4.0 copy) and drop or compress the Empirical Origin section — this trims roughly 25 lines of redundancy without losing operational content.

Specify the Phase-4.3 anonymity scan concretely (e.g., a grep pattern list for author/title/URL leak classes and the exact placeholder tokens to whitelist) so it is executable like the other audits.

Define the de-staging step mechanically (e.g., rewrite 'audit-input/sections/slide_text.tex#S-K' verdict paths to 'Slide K' with a one-line sed/python command) to close the last actionability gap.

DimensionReasoningScore

Conciseness

The body is dense skill-specific operational content with no explanations of concepts Claude already knows, but the audit-input staging tree is duplicated in full in both Output Layout and Phase 4.0, and the Empirical Origin section is time-stamped backstory rather than instruction. Efficient with some over-length that could be trimmed — above level 3, below level 5.

4 / 5

Actionability

Most phases give copy-paste-ready commands ("latexmk -pdf -xelatex main.tex", "soffice --headless --convert-to pdf", exact sub-skill invocation strings, exact staged \input{} contents), but the Phase-4.3 anonymity scan has no tool or procedure, and "de-stage the path prefix so the verdicts cite slide K" states an outcome without the mechanism — mostly executable with minor gaps.

4 / 5

Workflow Clarity

Phases 0–6 are clearly sequenced with the assurance-ladder table mapping which phases run per level, explicit checkpoints (Phase-1 pause for approval), per-phase validation (artifact existence, page-count equality, sha256 notes match), and feedback loops (verdict downgrades, fail-closed halts surfaced for human review). This matches the top anchor including its error-recovery loop requirement.

5 / 5

Progressive Disclosure

No references/scripts/assets bundle exists; external pointers are one level deep and clearly signaled ("See ../shared-references/effort-contract.md"), but the ~390-line body inlines material that could be externalized (the full Phase-4 staging adapter spec, the reviewer-backend blockquote) and the shared-reference files live outside this skill directory so their availability cannot be verified from the bundle. Good structure with minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: concrete multi-stage capability list, explicit bilingual trigger phrases, a clear use-when clause, and explicit disambiguation from narrower sibling skills. It uses third-person/declarative voice throughout with no fluff.

DimensionReasoningScore

Specificity

The description enumerates the full pipeline concretely — "paper → slide outline → Beamer + PPTX → per-page polish → assurance checks (claim / citation / anonymity) → final export and report" — covering every phase of the skill with no coverage gaps, matching the comprehensive multiple-concrete-actions anchor rather than the minor-gaps anchor below.

5 / 5

Completeness

Both what (the full stage chain) and when ("Use when the user wants the complete talk artifact, not just a slide deck" plus explicit trigger phrases) are stated explicitly and concretely, matching the level-5 anchor rather than the level-4 anchor where 'when' could be more explicit.

5 / 5

Trigger Term Quality

It lists explicit trigger phrases in both English and Chinese ("做 talk", "做 PPT 全流程", "talk pipeline", "end-to-end slides", "做演讲", "conference talk full workflow") plus venue names (NeurIPS / ICML / ICLR / VALSE / 投稿), giving comprehensive natural-term coverage with synonyms; "not just a slide deck" also covers deck/slides phrasing.

5 / 5

Distinctiveness Conflict Risk

The end-to-end pipeline niche is explicitly disambiguated from single-purpose skills ("not just a slide deck") and scoped by venue names, giving a clear niche with distinct triggers and minimal conflict risk with slide-generation or polish-only skills.

5 / 5

Total

20

/

20

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.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository

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

Path

skills/skills-codex/paper-talk/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.