poster-layout-planner
Use poster layout planner for other workflows that need structured execution, explicit assumptions, and clear output boundaries.
19
6%
Does it follow best practices?
Impact
—
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 specify what the skill actually does, uses abstract jargon instead of natural trigger terms, and is so generic that it would conflict with many other skills. The description reads more like a vague meta-comment about reusing a tool than an actionable skill description.
Suggestions
Replace abstract language with concrete actions the skill performs (e.g., 'Creates structured poster layouts with defined sections, dimensions, and content placement').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to design a poster, create a layout, or arrange content on a visual canvas').
Remove the self-referential framing ('Use poster layout planner for other workflows') and instead describe the skill's specific domain and capabilities to distinguish it from other planning or layout tools.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'structured execution,' 'explicit assumptions,' and 'clear output boundaries' without naming any concrete actions or specific capabilities. There is no indication of what the skill actually does. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' — it only vaguely references 'other workflows.' The 'when' is equally vague ('workflows that need structured execution'). There is no explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | The terms used ('structured execution,' 'explicit assumptions,' 'clear output boundaries') are abstract jargon that users would not naturally say. 'Poster layout planner' is mentioned but only as a reference, not as a trigger for what this skill does. No natural user keywords are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'workflows that need structured execution' could apply to virtually any planning, project management, or organizational skill. It would conflict with many other skills and provides no clear niche. | 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 a heavily templated, boilerplate-heavy document that provides almost no domain-specific guidance for poster layout planning. The vast majority of content is generic project management scaffolding (risk assessment, security checklists, lifecycle status, evaluation criteria) that wastes tokens without teaching Claude how to actually design poster layouts. The few domain-relevant elements (Features list, Input Parameters, Output Format) are skeletal and lack concrete examples or executable logic.
Suggestions
Remove all boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria) and replace with concrete poster layout guidance: grid systems, section sizing rules, visual hierarchy principles with specific examples.
Add at least one complete input/output example showing realistic poster dimensions, sections, and the resulting layout_plan with section_placement coordinates.
Eliminate circular self-references ('See ## Features above') and consolidate the workflow into a single clear sequence specific to poster layout generation.
Replace the generic 'Example Usage' (py_compile + --help) with an actual end-to-end example showing how to produce a poster layout from specific inputs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. Multiple sections reference each other circularly ('See ## Features above', 'See ## Prerequisites above', 'See ## Workflow above'). The skill explains generic concepts Claude already knows (what risk assessment is, what security checklists are, lifecycle status). The 'When to Use' section repeats the description verbatim. Much of the content (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) is boilerplate that adds no actionable value for poster layout planning. | 1 / 3 |
Actionability | Despite its length, the skill provides almost no concrete, executable guidance for actually designing a poster layout. The 'Example Usage' just shows how to compile and run a script with --help. The workflow steps are entirely abstract ('Confirm the user objective', 'Validate that the request matches'). There are no actual examples of poster layout input/output, no concrete layout algorithms, and no real executable code for the stated purpose. | 1 / 3 |
Workflow Clarity | There is a numbered workflow with steps and some error handling/fallback guidance. However, the steps are generic and abstract rather than specific to poster layout planning. There are no validation checkpoints tied to the actual domain task (e.g., validating that sections fit within poster dimensions). The workflow reads like a generic template applicable to any skill, not a poster-specific process. | 2 / 3 |
Progressive Disclosure | The document is a monolithic wall of text with 15+ sections, many of which are boilerplate. It references 'references/' directory and 'scripts/main.py' but no bundle files are provided. Circular self-references ('See ## Features above') add confusion rather than navigation. Content that could be separate (security checklist, risk assessment, lifecycle status) is inlined, while the actual domain-specific content (poster layout rules, examples) is absent. | 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
73f6514
- 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.