poster-layout-planner

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

Quality

17%

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

35%

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

The content supplies real executable commands and a working script, but is weighed down by large amounts of generic boilerplate and thin reference material, with workflows that lack explicit validation feedback loops.

Suggestions

Remove or move generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) out of SKILL.md so the overview stays lean and poster-specific.

Delete the circular 'See `## X` above for related details' pointer lines that add tokens without adding guidance.

Add an explicit validate->fix->retry feedback loop around the poster-generation step, and either populate references/guidelines.md with real poster-design rules or drop the reference.

Dimension	Reasoning	Score
Conciseness	The body is padded with templated boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) and meta-pointers like 'See `## Features` above for related details' that explain generic process concepts Claude already knows, matching the verbose/padded score-1 anchor.	1 / 3
Actionability	There are concrete executable commands (`python -m py_compile scripts/main.py`, `python scripts/main.py`) and a real script with a defined Input Parameters table, but the higher-level reasoning guidance ('Use the packaged script path or the documented reasoning path') stays abstract and the poster-domain guidance is thin.	2 / 3
Workflow Clarity	A numbered Workflow and Example run plan provide a sequence with a parse-validation checkpoint and a fallback note, but there is no explicit validate->fix->retry feedback loop for the actual poster deliverable, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	References are one level deep and signaled (`scripts/main.py`, `references/`), but the SKILL.md itself is a monolithic wall of inline boilerplate that should be split out, and references/guidelines.md is a near-empty two-bullet stub.	2 / 3
	Total	7 / 12 Passed

Description

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 a templated, circular statement that fails to say what the skill concretely does or when to use it, relying on generic meta-language indistinguishable from many other workflow skills.

Suggestions

Replace the circular phrasing with concrete poster actions, e.g. 'Designs academic poster layouts: section placement, visual hierarchy, size recommendations, and content flow.'

Add an explicit trigger clause using natural user language, e.g. 'Use when creating or rearranging academic conference posters, planning poster section layout, or sizing poster content.'

Drop the generic meta-terms ('structured execution', 'explicit assumptions', 'output boundaries') which apply to nearly any skill and dilute distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names no concrete poster actions (e.g. section placement, layout design, visual hierarchy); instead it uses abstract meta-language like 'structured execution, explicit assumptions, and clear output boundaries', matching the score-1 vague/abstract anchor.	1 / 3
Completeness	The 'what' is circular ('Use poster layout planner for other workflows that need...') and the 'when' is only implied with no explicit 'Use when...' clause or concrete triggers, so both what and when are very weak.	1 / 3
Trigger Term Quality	Apart from the word 'poster' embedded in the skill name, the trigger language is generic jargon ('structured execution', 'explicit assumptions', 'output boundaries') rather than natural phrases a user would say like 'design an academic poster' or 'plan my poster layout'.	1 / 3
Distinctiveness Conflict Risk	'Structured execution, explicit assumptions, and clear output boundaries' is generic enough to apply to almost any workflow skill, so it would conflict with many skills rather than carving a clear poster-layout niche.	1 / 3
	Total	4 / 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: aipoch/medical-research-skills
Path: scientific-skills/Academic Writing/poster-layout-planner/SKILL.md
Commit: f5ef65b

Reviewed: 1 day 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.