agentleFS
Sign inStart free
cjh-solvercjh-solver/MathModeling-Skills-Arsenal/skills/01-core/contest-orchestrator/AGENTS.md

MathModeling-Skills-Arsenal / contest-orchestrator

AGENTS.md14 starsChanged 11 days agoApache-2.0View on GitHub

Maintain a deterministic mathematical-modeling contest orchestrator. The v4.18 stable release provides evidence-bound COLLAB decision gates, claim-driven visual planning, capability-driven appendix coverage, and dedicated provenance for problem-analysis flowcharts, technical-roadmap diagrams and scientific schematics, while preserving scope selection, typed model-blueprint composition, structured per-subproblem modeling evidence, modeling-solution input/derivation contracts, cross-question symbol/interface checks, abstract evidence/numeric provenance, source-level layout/reference checks, formal-delivery drift detection, literature landing, strict LaTeX appendix input/material/minted checks, Windows-safe UTF-8 LaTeX fallback, and reproducible replay. Run these checks before a release: The current…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 1 is common, 4 are distinctive, and 0 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never run destructive Git cleanup or reset commands.

    line 10
  2. Distinctive:

    Do not write live contest artifacts into this skill directory.

    line 11
  3. Distinctive:

    Use isolated temporary directories for generated test papers and reports.

    line 12
  4. Common:

    Keep secrets and personal identifiers out of source, fixtures, and reports.

    line 13
  5. Distinctive:

    Run these checks before a release:

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

contest-orchestrator development rules

Goal

Maintain a deterministic mathematical-modeling contest orchestrator. The v4.18 stable release provides evidence-bound COLLAB decision gates, claim-driven visual planning, capability-driven appendix coverage, and dedicated provenance for problem-analysis flowcharts, technical-roadmap diagrams and scientific schematics, while preserving scope selection, typed model-blueprint composition, structured per-subproblem modeling evidence, modeling-solution input/derivation contracts, cross-question symbol/interface checks, abstract evidence/numeric provenance, source-level layout/reference checks, formal-delivery drift detection, literature landing, strict LaTeX appendix input/material/minted checks, Windows-safe UTF-8 LaTeX fallback, and reproducible replay.

Protected state

  • Preserve all existing user changes and untracked competition replay data.
  • Never run destructive Git cleanup or reset commands.
  • Do not write live contest artifacts into this skill directory.
  • Use isolated temporary directories for generated test papers and reports.
  • Keep secrets and personal identifiers out of source, fixtures, and reports.

Architecture

  • SKILL.md is the concise entrypoint and router; VERSION is the single version source.
  • Detailed operational policy belongs in references/.
  • Deterministic checks belong in scripts/ and must return meaningful exit codes.
  • Data result figures route through ModelViz → scipilot-figure-skill; problem-analysis flowcharts and technical-roadmap diagrams route to tech-route-maker; mechanism, force and geometry schematics route to tikz-scientific-figures; Draw.io is explicit-request only.
  • scope_router.py is the read-only scope/evidence planner; delivery_all.py is the canonical end-to-end delivery command for FULL_CONTEST.
  • Academic prose is routed through the local academic-writing adapter; claim-centered editing is opt-in and its mathmodel_patch_guard.py must pass before a prose patch is merged into a contest paper.

Validation

Run these checks before a release:

python -m compileall -q scripts tests planner memory
python -m unittest discover -s tests -p "test_*.py"
python scripts/skill_health_check.py . --strict --smoke
python -X utf8 <skill-creator-root>/scripts/quick_validate.py .
python scripts/replay_profiles.py --strict

The current stable release is 4.18. Preserve full-contest-legacy as the v4.16 compatibility baseline.

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.

Check your setup, free