agentleFS
frankxaifrankxai/starlight-automation-agent-skills/AGENTS.md

starlight-automation-agent-skills

AGENTS.md0 starsChanged 3 months agoMITView on GitHub

This repo is public-safe automation doctrine and skill packaging. Before release, classify changes as:

The file

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

6 rules. About 1 is common, 4 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Keep live workflow exports, private URLs, secrets, customer data, and personal memory out of this repo.

    line 7
  2. Distinctive:

    Prefer concise skills over long manuals.

    line 8
  3. Very specific:

    Run scripts/scan_public_safety.py before publishing.

    line 10
  4. Distinctive:

    Do not include local machine paths in public docs.

    line 11
  5. Distinctive:

    Use mock payloads and placeholders for examples.

    line 12
  6. Distinctive:

    Before release, classify changes as:

    line 16

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

This repo is public-safe automation doctrine and skill packaging.

Rules

  • Keep live workflow exports, private URLs, secrets, customer data, and personal memory out of this repo.
  • Prefer concise skills over long manuals. Put detailed platform notes in references.
  • Validate every skill with scripts/validate_skill_bundle.py.
  • Run scripts/scan_public_safety.py before publishing.
  • Do not include local machine paths in public docs.
  • Use mock payloads and placeholders for examples.

Publishing

Before release, classify changes as:

  • public-safe: generic doctrine, skills, mock examples, validation scripts.
  • private-only: live automations, credentials, private memory, business-sensitive data.
  • rewrite: useful pattern that needs sanitization before publication.

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.