paper-poster

Generate a conference poster (article + tcbposter LaTeX → A0/A1 PDF + editable PPTX + SVG) from a compiled paper. Use when user says "做海报", "制作海报", "conference poster", "make poster", "生成poster", "poster session", or wants to create a poster for a conference presentation.

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/paper-poster/SKILL.md

Quality

Discovery

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.

This is an excellent skill description that clearly specifies the concrete actions (generating conference posters), the technical approach (LaTeX tcbposter), input/output formats, and provides comprehensive bilingual trigger terms. The explicit 'Use when' clause with both Chinese and English trigger phrases ensures reliable skill selection. It serves as a strong example of a well-crafted description.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and outputs: generate a conference poster from a compiled paper, specifying the technology stack (article + tcbposter LaTeX), output formats (A0/A1 PDF + editable PPTX + SVG), and the input (compiled paper).	3 / 3
Completeness	Clearly answers both 'what' (generate a conference poster with specific formats from a compiled paper) and 'when' (explicit 'Use when' clause with multiple trigger phrases and a contextual condition).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms in both English and Chinese: '做海报', '制作海报', 'conference poster', 'make poster', '生成poster', 'poster session', plus the contextual trigger 'create a poster for a conference presentation'. These are terms users would naturally say.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche: conference poster generation using LaTeX tcbposter with specific output formats. The bilingual trigger terms and specific domain (conference posters from papers) make it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

55%

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

This skill is exceptionally thorough and actionable — it provides everything needed to generate a conference poster with concrete, executable code and clear multi-step workflows with validation checkpoints. However, it is severely undermined by extreme verbosity (likely 2000+ lines) with massive repetition of warnings and rules, and a complete lack of progressive disclosure — all reference material is inlined rather than split into separate files. The content would be far more effective at ~30% of its current length with detailed tables and templates moved to referenced files.

Suggestions

Extract venue color schemes, font size tables, content budget tables, and layout diagrams into a separate POSTER_REFERENCE.md file, keeping only the default venue inline

Extract the complete LaTeX template and card style definitions into a POSTER_TEMPLATE.tex file referenced from the skill

Consolidate the repeated warnings (beamer, adjustbox, symlinks, etc.) — each should appear exactly once in the Key Rules section, not scattered throughout the workflow phases

Remove explanatory context Claude already knows (e.g., 'Unlike papers (dense prose, 8-15 pages), posters are visual-first', 'A poster is NOT a paper summary') and trust Claude's understanding of poster design principles

Dimension	Reasoning	Score
Conciseness	This skill is extremely verbose — easily 2000+ lines with massive amounts of repeated information. The same warnings appear multiple times (e.g., 'NEVER use beamer' is stated in at least 3 places, 'NEVER use adjustbox' repeated, portrait column guidance repeated). Color scheme tables, font size tables, content budget tables, and layout diagrams are all inlined when they could be in reference files. Many explanatory asides ('A poster is NOT a paper summary', 'Unlike papers (dense prose, 8-15 pages)') explain concepts Claude already understands.	1 / 3
Actionability	The skill provides highly concrete, executable guidance throughout: complete LaTeX templates with copy-paste-ready code, specific bash commands for installation and compilation, Python scripts for PPTX generation and SVG conversion, exact font sizes, hex color codes, and grid coordinates. The code examples are complete and executable, not pseudocode.	3 / 3
Workflow Clarity	The multi-phase workflow (Phase 0-8) is clearly sequenced with explicit checkpoints ('⛔ STOP HERE and wait for user response'), validation steps (compilation error handling loop with max 3 attempts, visual review loop with score threshold), state persistence via JSON, and feedback loops for error recovery. The visual review iteration loop with scoring rubric is particularly well-designed.	3 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files for detailed content. The entire color scheme table, all layout diagrams, complete LaTeX templates, full Python scripts, card style definitions, font size tables, and content budget tables are all inlined in a single massive file. The venue color schemes, card style definitions, and PPTX generation scripts should clearly be in separate reference files.	1 / 3
	Total	8 / 12 Passed

Validation

72%

Warnings & errors only

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

Validation — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1098 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	8 / 11 Passed

Repository: wanshuiyin/Auto-claude-code-research-in-sleep
Commit: dc00dfb

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.