agentleFS
ZimoLiaoZimoLiao/scholaraio/.claude/skills/publish/SKILL.md

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

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.
  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • suxrobGMSkill

    render

    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-dharSkill

    optimize

    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

  • AnthropicSkill

    analyze

    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

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 3 projects that use this

  • AnthropicSkill

    start

    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

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
  1. Very specific:

    Use this skill only after the user clearly says the deliverable is final, audited, or ready to publish.

    line 8
  2. Very specific:

    Do not put user deliverables in the repository root except under published/, and do not commit published/ to the ScholarAIO repo.

    line 18
  3. Distinctive:

    Before creating or changing a published archive:

    line 22
  4. Very specific:

    Never delete source files from workspace/.

    line 26
  5. Distinctive:

    Use one folder per final deliverable:

    line 30
  6. Very specific:

    Default mode copies PDFs and source ZIPs into assets/papers/, producing a self-contained site suitable for a separate GitHub Pages …

    line 81
  7. Distinctive:

    Keep metadata accurate: title, date, PDF filename, authors, subject, keywords, and note should match the actual deliverable.

    line 92
  8. Very specific:

    After archiving, run scholaraio publish-site so the static site reflects the new item.

    line 93
  9. Very specific:

    If the configured output directory is missing, either pass --out-dir or help the user set publish.site_output_dir.

    line 94
  10. Distinctive:

    Treat the generated site as deployable output.

    line 95

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 the scholaraio publish-site generator
  • published/: 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:

  1. Confirm with the user that the deliverable is final enough to archive.
  2. Recommend a backup for important outputs, especially before replacing an existing archive directory.
  3. 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-report

Configured output directory:

publish:
  site_output_dir: ~/generated-report

Then:

scholaraio publish-site

Default 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 --symlink

Agent 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-site so the static site reflects the new item.
  • If the configured output directory is missing, either pass --out-dir or help the user set publish.site_output_dir.
  • Treat the generated site as deployable output; if it lives in another Git repo, ask before committing or pushing there.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.