poster-layout-planner

Use poster layout planner for other workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

42%

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 ./scientific-skills/Academic Writing/poster-layout-planner/SKILL.md

Quality

Content

48%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 is well-structured with a real executable script and a sequenced workflow including a validation checkpoint, but it is weighed down by large amounts of generic templated boilerplate and a script that does not actually expose the documented CLI interface. The poster-specific substance is a small fraction of the file.

Suggestions

Remove the generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template) that do not add poster-specific guidance, or move them into references/guidelines.md.

Make scripts/main.py accept the documented inputs (size, sections) via argparse so the advertised "python scripts/main.py --help" and parameter table are actually functional.

Replace the generic "Reference material available in references/" line with a specific link such as "See references/guidelines.md for academic poster design guidelines and visual design principles."

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose with several padded generic sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) that teach concepts Claude already knows and add no poster-specific value, matching the anchor for noticeable verbosity with several padded sections.	2 / 5
Actionability	Concrete commands and a real script are present ("python -m py_compile scripts/main.py", "python scripts/main.py", the Input Parameters table, the Output Format JSON), but "python scripts/main.py --help" is non-functional because main.py has no argparse and the script runs a hardcoded demo rather than accepting the documented inputs, leaving key execution gaps.	3 / 5
Workflow Clarity	The Workflow section gives a clear five-step sequence with an explicit validation checkpoint (Quick Check: "python -m py_compile scripts/main.py") and error-handling fallback guidance, fitting the anchor for a clear sequence with most checkpoints present and only minor gaps.	4 / 5
Progressive Disclosure	The bundle exists (references/guidelines.md, scripts/main.py) and scripts/main.py is specifically referenced, but references/ is only mentioned generically ("Reference material available in references/") without signaling guidelines.md by name, so references are present but not clearly signaled.	3 / 5
	Total	12 / 20 Passed

Description

36%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 is largely uncustomized boilerplate: it names the poster-layout domain but never states the concrete capability (designing academic poster layouts) and offers only generic trigger conditions. It would poorly signal when to invoke this skill over a generic structured-workflow skill.

Suggestions

Rewrite the description to state the concrete capability, e.g. "Designs academic poster layouts: section placement, visual hierarchy, size recommendations, and content flow."

Add an explicit "Use when..." trigger clause with natural phrases a user would say, such as "Use when creating academic or conference posters, planning poster section layout, or sizing poster content."

Replace the generic "structured execution, explicit assumptions, clear output boundaries" language with poster-specific trigger terms (academic poster, conference poster, poster dimensions) to reduce overlap with other structured-workflow skills.

Dimension	Reasoning	Score
Specificity	The phrase "poster layout planner" names the domain, but the only actions offered ("structured execution, explicit assumptions, and clear output boundaries") are generic boilerplate with no poster-specific concrete actions, matching the anchor that names a domain but gives only generic actions.	2 / 5
Completeness	The "what" is essentially just the skill name restated rather than a statement of what it does (it never says it designs/layouts posters), and the "when" clause ("for other workflows that need structured execution...") is generic and not a concrete trigger, so it falls at the vague-what-plus-weak-when anchor.	2 / 5
Trigger Term Quality	"poster" and "poster layout" are relevant natural keywords, but common variations a user would actually say ("academic poster", "conference poster", file extensions) are absent, so it sits at the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The "poster layout planner" niche is somewhat specific, but the trigger conditions (structured execution, explicit assumptions, output boundaries) are generic and would overlap with any structured-workflow skill, matching the somewhat-specific-but-still-overlapping anchor.	3 / 5
	Total	10 / 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: aipoch/medical-research-skills
Path: scientific-skills/Academic Writing/poster-layout-planner/SKILL.md
Commit: 63c61d3

Reviewed: 10 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.