post-acceptance

This skill should be used when the user asks to "prepare conference presentation", "create presentation slides", "design poster", "make academic poster", "write promotion content", "create Twitter thread", or mentions post-acceptance conference preparation. Provides comprehensive workflow for presentation, poster, and promotion content creation.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/post-acceptance/SKILL.md

Quality

Content

35%

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

The skill body is verbose and restates widely-known presentation and design knowledge, offers generic advice instead of concrete instructions, and presents shallow single-line workflows. Progressive disclosure is weakened by a broken reference and unlisted existing bundle files.

Suggestions

Trim generic guidance Claude already knows (basic slide/poster design principles, common-sense tips) and keep only post-acceptance-specific, non-obvious content to improve token efficiency.

Fix the broken 'examples/post-acceptance-plan.md' reference and add clearly signaled links to the existing poster-templates, presentation-templates, and promotion-examples directories so the real bundle is discoverable.

Replace the arrow-chain pseudo-workflows with concrete, sequenced steps that include checkpoints (e.g., validate slide count against talk length, review poster at print scale) rather than vague narrative lines.

Dimension	Reasoning	Score
Conciseness	The body restates common knowledge Claude already has — 'one key message per slide', 'use figures and diagrams over text', 'high-contrast colors for readability', 'design for scanning, not reading' — and is padded with generic advice, violating the 'add only what Claude doesn't know' principle.	1 / 3
Actionability	It is instruction-only (no code expected), but the guidance is largely generic advice — 'Practice timing with a stopwatch', 'Arrive early to test equipment', 'Engage with comments' — rather than concrete, skill-specific instructions, though specifics like font sizes and image dimensions add some concrete value.	2 / 3
Workflow Clarity	Workflows are single-line arrow chains ('Paper accepted -> Identify key messages -> Create slide outline -> ...') that list steps but lack validation checkpoints or feedback loops, fitting the 'steps listed but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	The body is a ~145-line monolithic guide with most content inline, lists only three reference paths, and references a non-existent file ('examples/post-acceptance-plan.md') while leaving the existing template/example subdirectories (poster-templates, presentation-templates, promotion-examples) entirely unsurfaced.	2 / 3
	Total	7 / 12 Passed

Description

92%

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, well-structured description with explicit use-when triggers and concrete deliverable enumeration. Its main weakness is that several trigger phrases are broad enough to overlap with general design or social-media skills.

Suggestions

Tighten the trigger phrases with the qualifying 'post-acceptance' or 'conference' context to reduce overlap with general presentation or social-media skills (e.g., 'create conference presentation slides').

Drop the vague filler 'Provides comprehensive workflow' in favor of concrete action verbs that state what the skill produces.

Dimension	Reasoning	Score
Specificity	Enumerates concrete deliverable areas — 'prepare conference presentation', 'design poster', 'create Twitter thread' — naming multiple specific actions across presentation, poster, and promotion; the only soft spot is the vague filler 'Provides comprehensive workflow'.	3 / 3
Completeness	Explicitly answers both what ('Provides comprehensive workflow for presentation, poster, and promotion content creation') and when ('This skill should be used when the user asks to...'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Quotes many natural phrases a user would say — 'create presentation slides', 'make academic poster', 'write promotion content', 'create Twitter thread' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The post-acceptance niche is reasonably specific, but generic triggers like 'create presentation slides', 'design poster', and 'create Twitter thread' could overlap with general presentation or social-media skills.	2 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/post-acceptance/SKILL.md
Commit: 2f7766f

Reviewed: about 13 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.