agentleFS
Sign inStart free
vosslabvosslab/vosslab-skills/AGENTS.md

vosslab-skills

AGENTS.md5 starsChanged 21 days agoMITView on GitHub

Canonical rules live in docs/. Read them; this file only points and flags repo quirks.

The file

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

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Run repo Python tools via source source_me.sh && python3 <path-to-script>.py (Python 3.12 only).

    line 15
  2. Very specific:

    When changing code, run focused tests on the changed file (tests use the -k flag, e.g.

    line 18
  3. Distinctive:

    When in doubt, implement the changes the user asked for rather than waiting for a response.

    line 21

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

AGENTS.md

Canonical rules live in docs/. Read them; this file only points and flags repo quirks.

Style and rules

  • Repo style: docs/REPO_STYLE.md
  • Python style: docs/PYTHON_STYLE.md
  • Markdown style: docs/MARKDOWN_STYLE.md
  • Pytest style: docs/PYTEST_STYLE.md
  • E2E tests: docs/E2E_TESTS.md
  • Human guidance: docs/HUMAN_GUIDANCE.md
  • Skills index: docs/SKILLS_INDEX.md

Repo quirks

  • Run repo Python tools via source source_me.sh && python3 <path-to-script>.py (Python 3.12 only). This is an AI-agent runtime rule, not a requirement for repo scripts.
  • Generated files: edit the source, then regenerate; do not hand-edit output. index_lib/build_all.py validates sidecars and builds the skill index, agent index, and plugin manifests from canonical sources; index_lib/list_loaded_skills.py lists loaded skills.
  • Preserve existing file content outside the intended edit boundary. Modify files in place, avoid repository-history or staging operations, and record requested changes in docs/CHANGELOG.md.
  • When changing code, run focused tests on the changed file (tests use the -k flag, e.g. pytest test_feature.py -k changed_file.py); documentation changes need no tests.

User directive (overrides defaults)

When in doubt, implement the changes the user asked for rather than waiting for a response; the user is not the best reader and will likely miss your request and then be confused why it was not implemented or fixed.

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