agentleFS
SoFarSoGoodyaSoFarSoGoodya/mathmodel-weave/skills/publication/SKILL.md

publication

Skill2 starsChanged 41 days agoMITView on GitHub

Build and review a Chinese XeLaTeX mathematical-modeling paper from a fixed selected result, evidence freeze, and formal execution manifest. Use for final paper narrative, result-backed figures, submission PDFs, or publication checks; do not use to change algorithms, samples, metrics, units, or human approval.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the selected-result record, evidence freeze, formal run manifest, current rule config, and available human adoption facts before …

    line 8
  2. Very specific:

    Create a short paper_plan.md that states what each section answers, the frozen evidence it uses, the mathematical or visual role, and the …

    line 14
  3. Distinctive:

    Use execution-owned data and scripts for data figures.

    line 19
  4. Very specific:

    Use mathmodel_agent.publication.build_publication(case_root, request) for the deterministic pipeline.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Publication

Read the selected-result record, evidence freeze, formal run manifest, current rule config, and available human adoption facts before drafting. Stop with a science revision when the run identity, metric value/definition/unit, sample set, aggregation, adopted claim, or rule binding conflicts. Display-only changes such as final size, typography, color, marker, linestyle, hatch, legend, and caption may proceed without recomputing a Metric.

Create a short paper_plan.md that states what each section answers, the frozen evidence it uses, the mathematical or visual role, and the conclusion boundary. Write one coherent TeX source rather than concatenating agent fragments. Repeated result values must come from generated/results.tex, not manual transcription.

Use execution-owned data and scripts for data figures. Match final insertion width, provide a non-color encoding, and draw intervals only when the run defines them. When only an original real image exists without data or a script, disclose that it cannot be redrawn. Never present a conceptual illustration as measured data.

Build the electronic target with XeLaTeX, then check citations, placeholders, anonymity, critical numbers, page/size rules, metadata, embedded fonts, and the text layer. Rasterize every page and inspect all of them. Compilation alone leaves visual_review_pending; review_ready requires explicit page-complete visual notes and is not human approval.

Use mathmodel_agent.publication.build_publication(case_root, request) for the deterministic pipeline. See docs/modules/publication.md for the request fields, rule configuration, CLI hook, and exact commands.

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.