agentleFS
Sign inStart free
docxologydocxology/template/.github/actions/setup-meta-provider/AGENTS.md

template / setup-meta-provider

AGENTS.md20 starsChanged 13 days agoApache-2.0View on GitHub

This composite action owns only genuine Meta wheel preparation for an explicitly prepared environment. Source is the canonical public projects/templates/templateliteraturemeta_analysis tree. Keep checkout, interpreter setup and uv sync --locked --group installed-build explicit in each caller. Use the existing project-only exemplar exporter without a rename to create an independent runner-temporary packaging copy. Build there with the absolute locked root .venv/bin/python; build and egg-info metadata belong to that owned copy, never the canonical checkout. Do not clean canonical Source or relax its…

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep checkout, interpreter setup and uv sync --locked --group installed-build explicit in each caller.

    line 7
  2. Distinctive:

    Verify with actionlint and the real Advanced/hydration tests.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

Meta provider setup

This composite action owns only genuine Meta wheel preparation for an explicitly prepared environment. Source is the canonical public projects/templates/template_literature_meta_analysis tree.

Keep checkout, interpreter setup and uv sync --locked --group installed-build explicit in each caller. Use the existing project-only exemplar exporter without a rename to create an independent runner-temporary packaging copy. Build there with the absolute locked root .venv/bin/python; build and egg-info metadata belong to that owned copy, never the canonical checkout. Do not clean canonical Source or relax its Git-body inventory. Install into python-executable, defaulting to the same interpreter. Pass that input through the quoted PROVIDER_PYTHON environment variable; retain noneditable installation and --no-deps so provider preparation cannot change the locked dependency selection.

Verify with actionlint and the real Advanced/hydration tests. See README.md for the caller contract.

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