agentleFS
namddpnamddp/social-media-agent-skills/AGENTS.md

social-media-agent-skills

AGENTS.md0 starsChanged 3 months agoMITView on GitHub

The file

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

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

  • ≈2

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Read C:/Users/Admin/AGENTS.md and this repository's README.md before changes.

    line 3
  2. Distinctive:

    Keep every workflow draft-only and approval-first.

    line 4
  3. Common:

    Never add social credentials, browser cookies, or unattended publishing.

    line 5
  4. Distinctive:

    Keep Python modules below 200 lines.

    line 7
  5. Distinctive:

    Run syntax checks, tests, coverage, and package build before commits.

    line 8
  6. Common:

    Never commit credentials, private drafts, customer data, caches, or build outputs.

    line 9

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

Agent Instructions

  • Read C:/Users/Admin/AGENTS.md and this repository's README.md before changes.
  • Keep every workflow draft-only and approval-first.
  • Never add social credentials, browser cookies, or unattended publishing.
  • Preserve explicit destinations, dry-run behavior, and overwrite protection.
  • Keep Python modules below 200 lines.
  • Run syntax checks, tests, coverage, and package build before commits.
  • Never commit credentials, private drafts, customer data, caches, or build outputs.

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.