agentleFS
Sign inStart free
GitHubKnown publishergithub/squad/packages/squad-cli/templates/skills/agent-conduct/SKILL.md

agent-conduct

Skill3.4k starsChanged 2 months agoMITView on GitHub

Shared hard rules enforced across all squad agents

5 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 4

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Every squad agent must follow these two hard rules.

    line 11
  2. Common:

    Before finishing work, verify your changes don't break existing tests.

    line 19
  3. Common:

    Don't hardcode dev team agent names in product code or tests

    line 22
  4. Common:

    Don't skip test verification before declaring work done

    line 23
  5. Common:

    Don't ignore pre-existing CI failures that your changes may worsen

    line 24

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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
SKILL.md

Context

Every squad agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.

Patterns

Product Isolation Rule (hard rule)

Tests, CI workflows, and product code must NEVER depend on specific agent names from any particular squad. "Our squad" must not impact "the squad." No hardcoded references to cast-specific agent names in test assertions, CI configs, or product logic. Use generic/parameterized values. If a test needs agent names, use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot").

Peer Quality Check (hard rule)

Before finishing work, verify your changes don't break existing tests. Run the test suite for files you touched. If CI has been failing, check your changes aren't contributing to the problem. When you learn from mistakes, update your history.md.

Anti-Patterns

  • Don't hardcode dev team agent names in product code or tests
  • Don't skip test verification before declaring work done
  • Don't ignore pre-existing CI failures that your changes may worsen

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.

Reviews can't be read right now.

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