agentleFS
Sign inStart free
pipefypipefy/mcp-builders/AGENTS.md

mcp-builders

AGENTS.md4 starsChanged 3 months agoApache-2.0View on GitHub

This repository holds the MCP Builders program rules and skill submissions. It does not contain the Pipefy MCP server, CLI, or install docs. For setup, product context, and toolkit skills, use the Pipefy AI Toolkit. Every pull request that touches submissions/ runs the validator in CI (.github/workflows/validate-submission.yml). Run the same check locally: When turning a skill submission issue into a PR:

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    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:

    Every pull request that touches submissions/ runs the validator in CI (.github/workflows/validate-submission.yml).

    line 26
  2. Distinctive:

    Run the same check locally:

    line 28
  3. Common:

    Never commit tokens, API keys, real organization or pipe IDs, customer names, or personal data.

    line 36
  4. Distinctive:

    Keep contact email in the issue or PR description only — do not add it to submission files.

    line 37
  5. Distinctive:

    Do not duplicate install or MCP setup docs here.

    line 38
  6. Distinctive:

    When turning a skill submission issue into a PR:

    line 42
  7. Very specific:

    Create the folder at submissions/<issue-author>/<skill-name>/.

    line 44
  8. Very specific:

    Commit SKILL.md and EVIDENCE.md with the issue author as the commit author.

    line 45
  9. Distinctive:

    Use the contact email from the issue for follow-up.

    line 46

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

Agent guide

This repository holds the MCP Builders program rules and skill submissions. It does not contain the Pipefy MCP server, CLI, or install docs. For setup, product context, and toolkit skills, use the Pipefy AI Toolkit.

Read first

  • CONTRIBUTING.md — how people submit skills, contact info, folder rules, and review outcomes
  • docs/writing-a-skill.md — skill content requirements
  • docs/judging.md — rubric and acceptance criteria
  • template/ — SKILL.md and EVIDENCE.md starters

Submission layout

submissions/<github-handle>/<skill-name>/
├── SKILL.md
├── EVIDENCE.md
└── assets/          # optional screenshots referenced from EVIDENCE.md
  • <github-handle> is the submitter's GitHub username, lowercase.
  • <skill-name> is kebab-case and must match the name field in the SKILL.md frontmatter.

Validation

Every pull request that touches submissions/ runs the validator in CI (.github/workflows/validate-submission.yml).

Run the same check locally:

python3 scripts/validate_submission.py submissions/<github-handle>/<skill-name>

Hard rules

  • Never commit tokens, API keys, real organization or pipe IDs, customer names, or personal data.
  • Keep contact email in the issue or PR description only — do not add it to submission files.
  • Do not duplicate install or MCP setup docs here; link to pipefy/ai-toolkit instead.

Converting issues to pull requests

When turning a skill submission issue into a PR:

  1. Create the folder at submissions/<issue-author>/<skill-name>/.
  2. Commit SKILL.md and EVIDENCE.md with the issue author as the commit author.
  3. Use the contact email from the issue for follow-up; do not write it into the repo.

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