How do I install the Repo Name Conventions skill?

Run npx skillmds@latest add antonbronnfjell/repo-name-conventions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo Name Conventions safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo Name Conventions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo Name Conventions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo Name Conventions?

AntonBronnfjell (@antonbronnfjell) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo Name Conventions by antonbronnfjell

Name: Repo Name Conventions
Rating: 4.2 (5 reviews)
Author: AntonBronnfjell

Repo Name Conventions

Comprehensive repository naming convention for Git repos — personal, freelance/agency, and tiered-enterprise contexts — including dedicated patterns for AI agent skills, MCP servers, hooks, commands, and other agent-tooling repos. Use this skill whenever the user is naming, renaming, or scaffolding a new Git repository; asking what to call a repo; choosing a purpose/platform/repo-type/language prefix; or asking to validate an existing repo name against a convention. Also trigger when the user is creating a skill, MCP server, hook, agent definition, or other AI-agent-tooling repo and needs the right platform/repo-type keywords (e.g. claude vs agent vs mcp, skill vs mcpserver vs hook).

File contents

Repository Name Conventions

Pattern

Core (always required):

<purpose>-<platform>-<repo-type>-<language>_<project-name>[.<project-module>]

Full (enterprise/freelance/lifecycle extensions):

[<org>-][<scope>-][<client>-]<purpose>-<platform>-<repo-type>-<language>_<project-name>[.<project-module>][-<env>][-<region>][-<lifecycle>]

Rules: all lowercase, ASCII only; segments separated by -; project name separated from the technical prefix by _; sub-modules use .; omit segments that don't apply rather than inserting placeholders; aim for ≤64 characters, hard-cap at 100.

For the full guide (every segment's controlled vocabulary, AI/agent repo shapes, enterprise/freelance extensions, examples, anti-patterns), read reference/conventions.md.

When naming an AI-agent-tooling repo

Repo shape	repo-type	platform
Instructions + optional scripts loaded into an agent's context	`skill`	the agent, or `agent` if it targets 2+ hosts
A server exposing tools over MCP to any compliant client	`mcpserver`	`mcp`
A script another system triggers on an event	`hook`	the triggering system
A reusable prompt or slash command	`command` / `prompt`	the agent, or `agent`
The agent itself — persona, tool wiring, orchestration	`agentdef`	the agent, or `agent`

Full detail: reference/conventions.md § AI & Agent Repositories.

Validating or suggesting a name

Run the bundled scripts rather than eyeballing the tables:

python3 scripts/validate_repo_name.py <candidate-name>            # structural + vocab check
python3 scripts/validate_repo_name.py <candidate-name> --strict   # unknown vocab = error
python3 scripts/suggest_repo_name.py --purpose ... --platform ... --repo-type ... --language ... --name ...
python3 scripts/suggest_repo_name.py                              # interactive prompts

scripts/validate_repo_name.py treats structural violations (wrong separators, uppercase, missing segment) as hard errors always, but an unrecognized-but-well-formed keyword only as a warning by default — the vocabulary can never be fully exhaustive. Use --strict when the check needs to be unambiguous (e.g. in CI).

Enforcing this automatically

See README.md for installing the gh repo create guard hook, the Claude Code PreToolUse hook, and the CI check.

---name: repo-name-conventionsdescription: Comprehensive repository naming convention for Git repos — personal, freelance/agency, and tiered-enterprise contexts — including dedicated patterns for AI agent skills, MCP servers, hooks, commands, and other agent-tooling repos. Use this skill whenever the user is naming, renaming, or scaffolding a new Git repository; asking what to call a repo; choosing a purpose/platform/repo-type/language prefix; or asking to validate an existing repo name against a convention. Also trigger when the user is creating a skill, MCP server, hook, agent definition, or other AI-agent-tooling repo and needs the right platform/repo-type keywords (e.g. claude vs agent vs mcp, skill vs mcpserver vs hook).---# Repository Name Conventions## PatternCore (always required): <purpose>-<platform>-<repo-type>-<language>_<project-name>[.<project-module>]Full (enterprise/freelance/lifecycle extensions): [<org>-][<scope>-][<client>-]<purpose>-<platform>-<repo-type>-<language>_<project-name>[.<project-module>][-<env>][-<region>][-<lifecycle>]Rules: all lowercase, ASCII only; segments separated by `-`; project nameseparated from the technical prefix by `_`; sub-modules use `.`; omitsegments that don't apply rather than inserting placeholders; aim for≤64 characters, hard-cap at 100.For the full guide (every segment's controlled vocabulary, AI/agent reposhapes, enterprise/freelance extensions, examples, anti-patterns), read`reference/conventions.md`.## When naming an AI-agent-tooling repo| Repo shape | repo-type | platform ||---|---|---|| Instructions + optional scripts loaded into an agent's context | `skill` | the agent, or `agent` if it targets 2+ hosts || A server exposing tools over MCP to any compliant client | `mcpserver` | `mcp` || A script another system triggers on an event | `hook` | the triggering system || A reusable prompt or slash command | `command` / `prompt` | the agent, or `agent` || The agent itself — persona, tool wiring, orchestration | `agentdef` | the agent, or `agent` |Full detail: `reference/conventions.md` § AI & Agent Repositories.## Validating or suggesting a nameRun the bundled scripts rather than eyeballing the tables: python3 scripts/validate_repo_name.py <candidate-name> # structural + vocab check python3 scripts/validate_repo_name.py <candidate-name> --strict # unknown vocab = error python3 scripts/suggest_repo_name.py --purpose ... --platform ... --repo-type ... --language ... --name ... python3 scripts/suggest_repo_name.py # interactive prompts`scripts/validate_repo_name.py` treats structural violations (wrongseparators, uppercase, missing segment) as hard errors always, but anunrecognized-but-well-formed keyword only as a warning by default — thevocabulary can never be fully exhaustive. Use `--strict` when the checkneeds to be unambiguous (e.g. in CI).## Enforcing this automaticallySee `README.md` for installing the `gh repo create` guard hook, theClaude Code `PreToolUse` hook, and the CI check.

Frequently asked questions