agentleFS
Miyamura80Miyamura80/MCP-Template/.agents/skills/manage-agent-config/SKILL.md

manage-agent-config

Skill1 starsChanged 5 months agoMITView on GitHub

Manage files under .claude/{skills,agents,rules}/, .agents/{skills,rules}/, or .codex/agents/. Covers dual-tool Claude/Codex layout and reminds to run make sync-agent-config.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always edit .claude/agents/<name>.md (markdown + YAML frontmatter).

    line 20
  2. Very specific:

    Run make sync-agent-config - the TOML appears.

    line 22
  3. Very specific:

    Read the new-agent-rule skill before writing your first rule.

    line 28
  4. Very specific:

    Run make sync-agent-config - stale symlinks and orphaned TOMLs are pruned automatically.

    line 33
  5. Distinctive:

    Do not use any of these in a shared skill:

    line 43
  6. Distinctive:

    All of those are Claude-only.

    line 49
  7. Very specific:

    Always run make sync-agent-config.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

Managing Claude <-> Codex skills and subagents in this repo

This repo is dual-tool. Before you create or edit anything under .claude/, .agents/, or .codex/, read this and the detailed rule at .claude/rules/codex-claude-sync.md.

Decision tree

Creating a new skill?

  1. Does it need Claude-only features (allowed-tools, argument substitutions, shell preprocessing, or Claude-specific interpolations)?
    • Yes -> .claude/skills/<name>/SKILL.md (real directory, no symlink). Claude-only.
    • No -> .agents/skills/<name>/SKILL.md. Shared; make sync-agent-config creates the .claude/skills/<name> symlink.

Creating a new subagent?

  • Always edit .claude/agents/<name>.md (markdown + YAML frontmatter). That is the source of truth.
  • .codex/agents/<name>.toml is generated - never hand-edit.
  • Run make sync-agent-config - the TOML appears.

Creating a new path-scoped rule?

  • .claude/rules/<name>.md is the source of truth. Use globs: frontmatter (not paths:).
  • .agents/rules/<name>.md is a symlink mirror, created by make sync-agent-config.
  • Read the new-agent-rule skill before writing your first rule.

Renaming or deleting?

  • Rename or delete the source file (under .agents/skills/, .claude/agents/, or .claude/rules/).
  • Run make sync-agent-config - stale symlinks and orphaned TOMLs are pruned automatically.

Frontmatter rules for shared skills

.agents/skills/<name>/SKILL.md must only use:

  • name (required, lowercase-hyphens, <=64 chars)
  • description (required, <=250 chars - Codex and Claude use this for implicit matching)
  • Plain markdown body

Do not use any of these in a shared skill:

  • allowed-tools, disable-model-invocation, user-invocable, context, agent, model, effort, hooks, paths, shell, argument-hint
  • $ARGUMENTS, $1...$N, ${CLAUDE_SKILL_DIR}, ${CLAUDE_SESSION_ID} substitutions
  • Backtick-bang shell preprocessing or fenced shell-preprocessing blocks

All of those are Claude-only. In Codex they pass through literally and confuse the model. If you need them, make the skill Claude-only (see decision tree above).

Subagent format notes

Claude .md frontmatter keys that don't exist in Codex (tools, model, color) are preserved as TOML comments in the generated .codex/agents/<name>.toml for human reference. They do not affect Codex behavior. If tool restrictions matter to the agent's job, describe them in the prose body so both tools read them.

After any change

Always run make sync-agent-config. The prek pre-commit hook will block the commit otherwise. The script is idempotent and silent when there's nothing to do.

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.