publish
Skill589 starsChanged todayMITView on GitHub
Use when the user says a paper, review, report, or LaTeX deliverable is final and wants it archived under published/ or exposed through the static published-paper site.
67 other projects use a version of this.
Adopted by
Most recently taken up by
- filecoin-project/filecoin-skillstheir own version, first seen Nov 16, 2026
- noelceta/content-enginetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
- foster-systems/shelftheir own version, first seen Nov 15, 2026
- carlos2219/web-kittheir own version, first seen Nov 15, 2026
Used with
Projects with it also use create, render and 5 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.
MicrosoftSkillcreate
Also in 4 projects that use this
suxrobGMSkillrender
Generate raster images (PNG, JPEG, WebP) from natural language prompts using Python rendering engines. Covers graphics, charts, layouts, and procedural art. Not for SVG output.
Also in 3 projects that use this
aakash-dharSkilloptimize
Analyzes code for performance issues including slow algorithms, memory leaks, unnecessary re-renders, database query problems, and resource bottlenecks. Use when the user says "this is slow", "optimize this", "performance issue", "why is this taking so long?", or "make this faster".
Also in 3 projects that use this
AnthropicSkillanalyze
Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
Also in 3 projects that use this
kt057Skillcheck
lint, typecheck, test を一括実行して結果をサマリーする
Also in 3 projects that use this
AnthropicSkillstart
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
Also in 3 projects that use this
- +1 more from anthropics
Other versions67 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 67
- code-yeongyu/oh-my-openagent★ 71ksame name
- code-yeongyu/oh-my-opencode★ 71ksame name
- garrytan/gbrain★ 33ksame name
- TencentCloud/Octop★ 12ksame name
- harbor-framework/harbor★ 7.1ksame name
- laude-institute/harbor★ 7.1ksame name
- Q00/ouroboros★ 6.4ksame name
- paean-ai/deeptide★ 1.1ksame name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- agent-tower/core★ 402same name
57 more not listed
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
- posterSkill
- 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
10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill only after the user clearly says the deliverable is final, audited, or ready to publish.
- Very specific: line 18
Do not put user deliverables in the repository root except under published/, and do not commit published/ to the ScholarAIO repo.
- Distinctive: line 22
Before creating or changing a published archive:
- Very specific: line 26
Never delete source files from workspace/.
- Distinctive: line 30
Use one folder per final deliverable:
- Very specific: line 81
Default mode copies PDFs and source ZIPs into assets/papers/, producing a self-contained site suitable for a separate GitHub Pages …
- Distinctive: line 92
Keep metadata accurate: title, date, PDF filename, authors, subject, keywords, and note should match the actual deliverable.
- Very specific: line 93
After archiving, run scholaraio publish-site so the static site reflects the new item.
- Very specific: line 94
If the configured output directory is missing, either pass --out-dir or help the user set publish.site_output_dir.
- Distinctive: line 95
Treat the generated site as deployable output.
“Common” is measured: kept by at least 6 in 10 of the 56 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
Published Paper Archive And Site Generation
Use this skill only after the user clearly says the deliverable is final, audited, or ready to publish. Drafts should stay under workspace/.
Architecture
The publishing workflow has three separate layers:
scholaraio/: upstream code and thescholaraio publish-sitegeneratorpublished/: local audited deliverable archive, git-ignored by this repository- an optional separate GitHub Pages repository: generated static site files
Do not put user deliverables in the repository root except under published/, and do not commit published/ to the ScholarAIO repo.
Safety Gate
Before creating or changing a published archive:
- Confirm with the user that the deliverable is final enough to archive.
- Recommend a backup for important outputs, especially before replacing an existing archive directory.
- Never delete source files from
workspace/; publishing is a copy/archive step.
Archive Layout
Use one folder per final deliverable:
published/<YYYY-MM-DD>-<short-title>/
├── metadata.json
├── main.pdf
├── main.tex
├── images/
└── misc/Recommended metadata.json:
{
"title": "Full title",
"date": "YYYY-MM-DD",
"keywords": ["keyword"],
"subject": "field or topic",
"pdf_filename": "main.pdf",
"tex_files": ["main.tex"],
"images_dir": "images",
"misc_dir": "misc",
"authors": ["Author", "Claude (AI Assistant)"],
"note": "Final audited deliverable."
}The site generator reads published/*/metadata.json, builds a source ZIP beside each archive, and writes a static site.
Generate The Site
Explicit output directory:
scholaraio publish-site --out-dir ~/generated-reportConfigured output directory:
publish:
site_output_dir: ~/generated-reportThen:
scholaraio publish-siteDefault mode copies PDFs and source ZIPs into assets/papers/, producing a self-contained site suitable for a separate GitHub Pages repository.
Local preview mode uses symlinks instead of copying assets:
scholaraio publish-site --out-dir ~/generated-report --symlinkAgent Behavior
- Confirm the archive folder name and metadata before writing final archive files.
- Keep metadata accurate: title, date, PDF filename, authors, subject, keywords, and note should match the actual deliverable.
- After archiving, run
scholaraio publish-siteso the static site reflects the new item. - If the configured output directory is missing, either pass
--out-diror help the user setpublish.site_output_dir. - Treat the generated site as deployable output; if it lives in another Git repo, ask before committing or pushing there.
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.

