poster-layout-planner
Use poster layout planner for other workflows that need structured execution, explicit assumptions, and clear output boundaries.
24
6%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Academic Writing/poster-layout-planner/SKILL.mdQuality
Discovery
0%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 description is critically weak across all dimensions. It fails to explain what the skill actually does, uses abstract jargon instead of natural trigger terms, and is so generic that it could conflict with nearly any structured planning skill. The phrase 'for other workflows' is particularly problematic as it implies this is a secondary use case without ever establishing the primary one.
Suggestions
Replace vague language with concrete actions the skill performs, e.g., 'Creates structured poster layouts with defined sections, dimensions, and content placement' instead of 'structured execution'.
Add an explicit 'Use when...' clause with natural trigger terms users would say, such as 'poster', 'layout', 'design poster', 'conference poster', 'poster template'.
Remove the phrase 'for other workflows' and instead clearly define the primary purpose and scope of the skill to establish a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses extremely vague language like 'other workflows', 'structured execution', 'explicit assumptions', and 'clear output boundaries' without naming any concrete actions or specific capabilities. | 1 / 3 |
Completeness | The 'what' is essentially missing — it says to use the poster layout planner for 'other workflows' but never explains what the skill actually does. The 'when' is vaguely implied ('workflows that need structured execution') but is too abstract to serve as an explicit trigger. | 1 / 3 |
Trigger Term Quality | The only potentially useful trigger term is 'poster layout planner', but the rest of the description uses abstract jargon ('structured execution', 'output boundaries') that users would never naturally say. There are no natural keywords a user would use to find this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'workflows that need structured execution' could apply to virtually any planning or project management skill. It provides no clear niche or distinct triggers to differentiate it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is overwhelmingly generic boilerplate with almost no poster-layout-specific content. The actual domain knowledge (section placement, visual hierarchy, size recommendations, content flow optimization) is listed as bullet points in a Features section but never elaborated with concrete examples, algorithms, or executable guidance. The document is roughly 5x longer than it needs to be while simultaneously lacking the actionable content that would make it useful.
Suggestions
Remove all generic boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria) and focus on poster-layout-specific guidance with concrete examples of input sections and resulting layout plans.
Add at least one complete worked example showing a real poster size, real section list, and the expected JSON output with actual layout coordinates or placement descriptions.
Replace the generic workflow steps with poster-layout-specific steps (e.g., 'Calculate grid based on poster dimensions', 'Assign sections to grid cells based on reading flow', 'Validate that all sections fit within bounds').
Eliminate circular section references ('See ## Features above') and consolidate the content into a lean structure: Quick Start, Input/Output spec with examples, and domain-specific layout rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. Multiple sections reference each other circularly ('See ## Features above', 'See ## Prerequisites above', 'See ## Workflow above'). Contains extensive boilerplate (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria) that adds no actionable value. The actual poster-layout-planning content is buried under generic skill scaffolding that Claude doesn't need. | 1 / 3 |
Actionability | Despite the length, there is almost no concrete guidance on how to actually design a poster layout. The 'Example Usage' just shows running a script with --help. No actual poster layout examples, no sample inputs/outputs with real data, no executable code showing layout logic. The workflow steps are entirely generic and not specific to poster layout planning. | 1 / 3 |
Workflow Clarity | There is a numbered workflow with steps and some error handling guidance, but the steps are generic ('Confirm the user objective', 'Validate that the request matches the documented scope') rather than specific to poster layout planning. No validation checkpoints specific to layout quality or correctness. The workflow could apply to literally any skill. | 2 / 3 |
Progressive Disclosure | The document is a monolithic wall of text with 15+ sections, many of which are boilerplate. Circular references ('See ## Features above') add confusion rather than navigation. The references/ directory is mentioned but never described. Content that should be in separate files (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) is all inline. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- aipoch/medical-research-skills
- Commit
0b96148
- Reviewed
Table of Contents
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.