agentleFS
Sign inStart free
rumoiirumoii/rumo-engineering-skills/AGENTS.md

rumo-engineering-skills

AGENTS.md7 starsChanged 14 days agoMITView on GitHub

This repository distributes reusable agent skills for Codex, Claude Code, and other clients that load SKILL.md directories. It contains no product source code; its scripts are helpers bundled with the skills, plus the installers and repository checks. Commits and pushes follow skills/rumo-git-commit/SKILL.md and repository-local instructions.

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Keep every skill independent of a specific company, product, repository name, internal host, deployment path, or agent client.

    line 5
  2. Very specific:

    Put private project facts in a local profile or optional private profiles checkout and access them through rumo-project-profile.

    line 6
  3. Common:

    Never commit or print passwords, tokens, private keys, or private certificate material.

    line 10
  4. Distinctive:

    Write every skill in your own words.

    line 12
  5. Very specific:

    Follow the skill structure in CONTRIBUTING.md and skills/rumo-prose/references/agent-docs.md.

    line 19

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

Repository Guidance

This repository distributes reusable agent skills for Codex, Claude Code, and other clients that load SKILL.md directories. It contains no product source code; its scripts are helpers bundled with the skills, plus the installers and repository checks.

  • Keep every skill independent of a specific company, product, repository name, internal host, deployment path, or agent client. When a step depends on one client, label it as client-specific and give a client-neutral alternative or an explicit stop condition.
  • Put private project facts in a local profile or optional private profiles checkout and access them through rumo-project-profile.
  • Resolve bundled scripts relative to the installed skill directory.
  • Preserve unrelated working-tree changes and installed skills from other sources.
  • Validate frontmatter, metadata, relative links, helper scripts, installers, and the catalog before push. Before pushing a change that adds, removes, merges, or renames a skill, or alters a description, run the acceptance in CONTRIBUTING.md.
  • Never commit or print passwords, tokens, private keys, or private certificate material.
  • State explicit stop conditions for ambiguous or state-changing workflows.
  • Write every skill in your own words. Do not copy text from other projects, and do not add attribution notes or separate license files inside skill directories.

Commits and pushes follow skills/rumo-git-commit/SKILL.md and repository-local instructions.

Layout

  • skills/ holds the default skills that the installers always link; extras/ holds optional skills installed with -Extras or --extras. A default skill must not link to an extra.
  • Follow the skill structure in CONTRIBUTING.md and skills/rumo-prose/references/agent-docs.md.

Skill Language Policy

  • In skills/*/SKILL.md and extras/*/SKILL.md, write frontmatter description and the Markdown body in English. Clients select skills from frontmatter name and description only, so keep both self-sufficient.
  • agents/openai.yaml in each skill is optional Codex UI metadata; other clients ignore it. Keep interface.display_name in English only. Keep interface.short_description in Chinese so the skill list can show an English name with a Chinese explanation. Prefer English for interface.default_prompt.
  • Preserve Chinese only when it is required as literal product data, such as UI text, branch/product labels, user trigger phrases, commit-message requirements, or examples that must intentionally produce Simplified Chinese output.
  • Reference files under each skill's references/ may keep Chinese source material, scanned product text, and UI/business examples when translating them would reduce their value as product evidence.

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