How do I install the 00 Repo Init skill?

Run npx skillmds@latest add ai-driven-dev/00-repo-init 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 00 Repo Init safe to use?

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

Which AI agents work with 00 Repo Init?

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 00 Repo Init free to use?

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

Who published 00 Repo Init?

ai-driven-dev (@ai-driven-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

00 Repo Init by ai-driven-dev — Agent Skill

Name: 00 Repo Init
Author: ai-driven-dev

00 Repo Init

Initialize a project repository with git init, a default branch, a bootstrap commit, CONTRIBUTING.md, and optionally the remote. Use when the user wants to init or set up a new repo, or publish to a remote. Not for committing, opening a PR, or tagging.

ai-driven-dev 8c15d41 4 files · 4.9 KB Updated Sep 17, 2026

File contents

Repo Init

Status: experimental.

Initializes a project's repository locally and, on request, on the remote host, then returns the remote URL.

Actions

#	Action	Role	Input
01	`init`	Resolve VCS config, `git init`, set the default branch, write `CONTRIBUTING.md`, bootstrap commit	cwd, default_branch, remote_url
02	`publish`	Create the remote repo on the resolved host and push, return its URL	cwd, non_interactive

Run 01 → 02. init alone for local-only; publish after it to create the remote. Before running an action, read its file in actions/, not only the table or assets.

Transversal rules

The local step is idempotent. If the target is already a git work tree, init does nothing and reports.
init makes one bootstrap commit (--allow-empty) so HEAD exists and is pushable. The project's real first commit stays the commit skill's job.
publish is outward-facing. It confirms before creating the remote unless non_interactive is set.
The provider is open. Resolve the host and how to reach it (CLI, MCP, or API) from the VCS memory when present, else from the VCS tooling available in the environment. Never restrict to a fixed list or a fixed mechanism. main is the default-branch fallback.

Prerequisites

git on the PATH. For publish, the resolved host's tooling (CLI, MCP, or API) available and authenticated.

Assets

assets/CONTRIBUTING.md: the project-root CONTRIBUTING.md template.

---name: 00-repo-initdescription: Initialize a project repository with git init, a default branch, a bootstrap commit, CONTRIBUTING.md, and optionally the remote. Use when the user wants to init or set up a new repo, or publish to a remote. Not for committing, opening a PR, or tagging.---# Repo Init> Status: experimental.Initializes a project's repository locally and, on request, on the remote host, then returns the remote URL.## Actions| # | Action | Role | Input || --- | --------- | ------------------------------------------------------------------------------------------------- | ------------------------------- || 01 | `init` | Resolve VCS config, `git init`, set the default branch, write `CONTRIBUTING.md`, bootstrap commit | cwd, default_branch, remote_url || 02 | `publish` | Create the remote repo on the resolved host and push, return its URL | cwd, non_interactive |Run `01 → 02`. `init` alone for local-only; `publish` after it to create the remote.Before running an action, read its file in `actions/`, not only the table or assets.## Transversal rules- The local step is idempotent. If the target is already a git work tree, `init` does nothing and reports.- `init` makes one bootstrap commit (`--allow-empty`) so `HEAD` exists and is pushable. The project's real first commit stays the commit skill's job.- `publish` is outward-facing. It confirms before creating the remote unless `non_interactive` is set.- The provider is open. Resolve the host and how to reach it (CLI, MCP, or API) from the VCS memory when present, else from the VCS tooling available in the environment. Never restrict to a fixed list or a fixed mechanism. `main` is the default-branch fallback.## Prerequisites- `git` on the PATH. For `publish`, the resolved host's tooling (CLI, MCP, or API) available and authenticated.## Assets- `assets/CONTRIBUTING.md`: the project-root `CONTRIBUTING.md` template.

Frequently asked questions