poster
Skill585 starsChanged 3 months agoMITView on GitHub
Use when the user needs an academic poster, conference poster, poster-style visual summary, section planning, figure-text balance, or poster packaging workflow.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- PKU-DAIR/AutoScitheir own version, first seen Oct 25, 2026
- DAIR-AutoResearch/AutoScitheir own version, first seen Oct 15, 2026
- skyllwt/OmegaWikitheir own version, first seen Oct 8, 2026
- skyllwt/AutoScitheir own version, first seen Sep 28, 2026
- phanghonghao/THU-Awesome-Skillstheir own version, first seen Aug 10, 2026
Used with
Projects with it also use exp-pilot-eval, exp-pilot-run and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skyllwtSkillexp-pilot-eval
Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.
Also in 4 projects that use this
skyllwtSkillexp-pilot-run
Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.
Also in 4 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 4 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 4 projects that use this
Yusong-EnceladusSkillpaper-compile
Compile LaTeX paper to PDF, fix errors, and verify output. Use when user says \"编译论文\", \"compile paper\", \"build PDF\", \"生成PDF\", or wants to compile LaTeX into a submission-ready PDF.
Also in 4 projects that use this
- +1 more from skyllwt
- +6 more from Lambenthan
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- DAIR-AutoResearch/AutoSci★ 1.7ksame name
- PKU-DAIR/AutoSci★ 1.7ksame name
- skyllwt/AutoSci★ 1.7ksame name
- skyllwt/OmegaWiki★ 1.7ksame name
- phanghonghao/THU-Awesome-Skills★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/scholaraio.mdcCursor rule
- academic-writingSkill
- arxivSkill
- auditSkill
- backupSkill
- bioinformaticsSkill
- citation-checkSkill
- citationsSkill
- documentSkill
- drawSkill
- enrichSkill
- exploreSkill
- exportSkill
- graphSkill
- gromacsSkill
- importSkill
- indexSkill
- ingestSkill
- insightsSkill
- lammpsSkill
- literature-reviewSkill
- metricsSkill
- nature-workflowSkill
- openfoamSkill
- paper-guided-readingSkill
- paper-writingSkill
- patent-fetchSkill
- patent-searchSkill
- publishSkill
- quantum-espressoSkill
- renameSkill
- research-gapSkill
- review-responseSkill
- scientific-runtimeSkill
- scientific-tool-onboardingSkill
- scrubSkill
- searchSkill
- setupSkill
- showSkill
- technical-reportSkill
- topicsSkill
- translateSkill
- workspaceSkill
- writing-polishSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Create a poster-ready content package without duplicating the full workflows of the other writing skills.
- Distinctive: line 17
Do not treat a poster like a shortened paper.
- Distinctive: line 21
Use this skill when the user wants:
- Distinctive: line 27
If the user mainly wants:
- Distinctive: line 44
Use one main upstream workflow:
- Distinctive: line 64
prefer figures, tables, and short bullets over dense prose
- Distinctive: line 66
remove any paragraph that needs sustained close reading
- Very specific: line 70
Use /draw when the poster needs diagrams, cleaned figures, timelines, or concept maps.
- Very specific: line 71
Use /document when the result should be packaged into a practical file such as PPTX or another layout-friendly deliverable.
- Very specific: line 72
If the user explicitly needs a print-ready poster size, keep the poster structure here, then use /document to implement the layout.
- Distinctive: line 86
Claim discipline: every block must support the poster's main message.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Academic Poster Workflow
Create a poster-ready content package without duplicating the full workflows of the other writing skills.
Purpose
This skill is for poster-specific organization:
- define the poster's audience and message
- decide what belongs on the poster and what must be omitted
- convert literature or manuscript content into poster sections
- route figure/layout work to
/drawand/document
Do not treat a poster like a shortened paper. A poster is a visual argument with a small number of high-priority claims.
When To Use
Use this skill when the user wants:
- a conference poster
- a poster-style literature summary
- a visual one-page research overview
- help deciding poster sections, text density, and figure priorities
If the user mainly wants:
- a slide deck: route to
/document - a long written report: route to
/technical-report - a paper section: route to
/paper-writing
Workflow
1. Clarify Poster Context
Identify:
- target venue or audience
- poster goal: present a study, summarize a topic, or pitch a direction
- expected size or format if the user knows it
- available materials: workspace papers, manuscript draft, figures, data
2. Choose The Content Source
Use one main upstream workflow:
| Situation | Route |
| Poster summarizes a research field | /literature-review |
| Poster presents a user's own paper or method | /paper-writing |
| Poster motivates a new topic or open problem | /research-gap |
3. Build A Poster Skeleton
Default sections:
- Title + one-sentence claim
- Background / problem
- Method or comparison frame
- Key evidence or findings
- Main takeaway
- References / contact / QR block if needed
Keep these rules:
- one central claim, not many equal claims
- prefer figures, tables, and short bullets over dense prose
- each section should answer one question only
- remove any paragraph that needs sustained close reading
4. Route Assets And Packaging
- Use
/drawwhen the poster needs diagrams, cleaned figures, timelines, or concept maps. - Use
/documentwhen the result should be packaged into a practical file such asPPTXor another layout-friendly deliverable. - If the user explicitly needs a print-ready poster size, keep the poster structure here, then use
/documentto implement the layout.
Output Pattern
Recommended outputs inside workspace/<name>/:
poster-outline.mdposter-copy.mdposter-assets/- packaged deliverable from
/document
Principles
- Poster first: optimize for scanability, not completeness.
- Visual priority: text exists to support figures and claims.
- Claim discipline: every block must support the poster's main message.
- Honest scope: current first-class packaging is via
/document; do not imply a dedicated poster renderer if none exists.
Example
用户说:"帮我把这个工作区做成一个 conference poster"
→ 用本 skill确定 poster 骨架和主张,再转 /paper-writing 或 /literature-review 生成文案,必要时接 /draw 和 /document
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

