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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

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

The body delivers specific, actionable domain guidance with clear section structure and signaled references, but suffers from redundancy between sections, thin workflow checkpoints for slides/posters, inlined content that duplicates the reference files, and one dead reference path.

Suggestions

Remove `examples/post-acceptance-plan.md` from the Reference Files list or add the missing file so no referenced path is broken.

De-duplicate inline design specifics (font sizes, poster layout, color schemes) against references/design-guidelines.md and references/deliverable-checklists.md, keeping the body as an overview that points into them.

Collapse the overlapping Best Practices section into Core Features, or fold both into the reference checklists, to cut repeated guidance such as "one key message per slide" and anticipated-question prep.

Dimension	Reasoning	Score
Conciseness	Mostly efficient concrete specifics (font pt sizes, poster dimensions, image sizes) earn their place, but Best Practices overlaps Core Features ("one key message per slide", anticipated-question prep appear twice) and could be tightened.	3 / 5
Actionability	For an instruction-only skill the guidance is concrete and actionable — exact slide counts per talk length, content structure, font sizes, poster sizes, and a Hook->Problem->Method->Result->Link thread template — with only minor gaps.	4 / 5
Workflow Clarity	Three arrow-sequenced workflows are present and the promotion/Xquik path includes verification and an approval gate, but the presentation and poster workflows are thin one-liners with implicit rather than explicit checkpoints.	3 / 5
Progressive Disclosure	A Reference Files section signals one-level-deep references, but design detail (font sizes, poster layout, color schemes) is duplicated inline versus references/design-guidelines.md, and the referenced examples/post-acceptance-plan.md does not exist.	3 / 5
	Total	13 / 20 Passed

Description

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

The description clearly answers both what and when using concrete, natural trigger phrases in third person, carving out a distinct post-acceptance niche. It sits just below top marks because the "what" clause is generic and a few natural trigger variants (LinkedIn, blog) are missing.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("create presentation slides", "design poster", "make academic poster", "write promotion content", "create Twitter thread"), though the "what" summary ("comprehensive workflow") stays generic and omits LinkedIn/blog from the action list.	4 / 5
Completeness	Both "what" ("Provides comprehensive workflow for presentation, poster, and promotion content creation") and "when" (explicit "should be used when the user asks to..." with concrete triggers) are present; the "what" could be more specific about deliverables, keeping it just below a 5.	4 / 5
Trigger Term Quality	Strong natural-phrase coverage including synonyms (poster/design poster/make academic poster; prepare presentation/create slides) that users would actually say, but a few natural variants (LinkedIn post, blog post) are absent.	4 / 5
Distinctiveness Conflict Risk	The post-acceptance academic niche with specific triggers (academic poster, Twitter thread, post-acceptance conference preparation) is mostly distinct, with only minor overlap risk against a generic slide-creation skill.	4 / 5
	Total	16 / 20 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: 6ed46da

Reviewed: 8 days 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.