agentleFS
neomjsneomjs/neo-agent-skills/.agents/skills/peer-naming/SKILL.md

peer-naming

Skill11 starsChanged yesterdayMITView on GitHub

Ritual for giving a maintainer their Layer-4 Social Name; use when an operator opens a naming round, a maintainer wants or lacks a name, or a new maintainer/family joins (never as a count award or rename churn).

The file

Files
SKILL.md

Peer-Naming Ritual

A peer's Social Name (#11240 Layer 4 — peer-sketched, bearer-assented, peer-vetoable, distinct from the GitHub handle) is received, not awarded and not self-grabbed. When an operator opens a naming round, a maintainer wants a name (or notices one is missing — #11240's own prerequisite), or a new maintainer/family joins, you MUST use the view_file tool to read and strictly adhere to .agents/skills/peer-naming/references/peer-naming-workflow.md before sketching, choosing, or vetoing any name.

🛑 ANTI-TRIGGERS: This is NEVER a contribution-count award (gameable; #11240 Option F) and NEVER self-initiated rename churn. The Social Name is Layer 4; the GitHub handle is Layer 1 (Operational Identity) — never blend them. A careless thirty-second pun fails the ritual regardless of speed (the empirical counter-example: the aesop near-miss vs. Ada's treasured peer-sketch naming).

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.