Init

Skill honerlaw/agent-marketplace/plugins/minerva/skills/init

A personal plugin marketplace for AI coding agents. Each plugin provides skills and automation scripts.

Install

npx -y skills add honerlaw/agent-marketplace --skill init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scaffolds the `.minerva/` directory layout and agent-file Routing section — durable records, knowledge tracking, and project memory for agent work in a project. Idempotent — re-runs report per-piece status without rewriting anything in place, and it warns about legacy `.minerva/decisions/` layouts. Use when adopting minerva or setting up durable record/knowledge discipline for the first time in a project, or when the user invokes `minerva:init`.

SKILL.md

3.6 KB, 784 tokens by cl100k_base, as published. Nobody here has run it

One-time scaffolding for a project. Creates the .minerva/ directory layout, verifies it's not being gitignored, adds a Routing section to the project's agent file, and offers to commit the scaffold.

Usage

minerva:init — scaffold the current project root. No arguments.

Pre-flight detection

Before changing anything, inspect the project:

Project root is the current working directory.
Already initialized? Look for .minerva/. If it exists, you're in idempotent mode — report what's already there (folder ✓, gitignore ✓, agent file(s) ✓, knowledge dir ✓) and apply only the missing pieces.
Pre-existing flat layout? If work/ or decisions/ exist at the project root (i.e. someone used a pre-.minerva/ version of minerva, or set up the directories manually), do not touch them. Report:
```
Detected a pre-existing flat layout at <paths>. minerva:init won't migrate it automatically.
To move to the .minerva/ layout, run:
  mv work .minerva/work && mv decisions .minerva/knowledge
```
Continue with the rest of minerva:init (folder creation, gitignore check, agent file). The flat-layout warning is informational.

Legacy nested decisions/ directory? If .minerva/decisions/ exists (the directory was renamed to .minerva/knowledge/ in an earlier minerva version), do not touch it. Report:

Detected legacy .minerva/decisions/ — minerva renamed this to .minerva/knowledge/ but the old directory is still here.
No skill reads .minerva/decisions/ anymore. To migrate:
  mv .minerva/decisions/* .minerva/knowledge/  # then renumber if needed
  rmdir .minerva/decisions
Review for NNN collisions across the two directories before merging.

Continue with the rest of minerva:init. This warning is informational.

Git repo? If .git/ is absent, skip the gitignore check entirely and silently. Still scaffold the folder and update the agent file.

Steps

Execute steps 1–5 in order; their full protocols live verbatim in references/steps.md — read it now, before step 1: 1 scaffold .minerva/ (directory layout, idempotent per-piece status), 2 gitignore check (.minerva/worktrees/ entry), 3 agent-file detection + Routing section (template-of-record, stale-marker refresh), 4 commit offer, 5 report.

Out of scope

Migrating a pre-existing flat work/ + decisions/ layout. minerva:init only reports it; the user runs the mv themselves.
Migrating .minerva/decisions/ to .minerva/knowledge/. Same — report only, user runs the move.
Authoring or rewriting CLAUDE.md / AGENTS.md content beyond the Routing section.
Editing .gitignore to remove offending user-authored patterns. (Init does install .minerva/worktrees/ if missing — that entry is part of the scaffold, not user territory.)
Auto-refreshing a stale Routing section without the gate. Agent files are user territory — the refresh is always offered, diffed, and confirmable, never silent.
Splice-preserving refresh (updating canonical bullets while keeping unrecognized custom lines). Future hardening; v1 is a gated whole-section replace.

Gives 0 of the 12 instructions most project setup skills give in 784 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-06

ask one question at a timein 29 of 999, across 28 files
detect the package manager from lockfilesin 28 of 999, across 9 files
present findings to the userin 25 of 999, across 4 files
explore current repo statein 24 of 999, across 3 files
update the agent skills block in place if it existsin 24 of 999, across 3 files
install husky lint-staged and prettierin 23 of 999, across 4 files
create the lintstagedrc filein 22 of 999, across 3 files
commit all changed filesin 22 of 999, across 3 files
run lint-staged to verify it worksin 22 of 999, across 3 files
initialize huskyin 21 of 999, across 2 files
create the husky pre-commit filein 21 of 999, across 2 files
create a prettierrc file if missingin 21 of 999, across 2 files

Said here and by no other author read

Use the current working directory as the project root
Report existing pieces and apply only missing ones
Do not touch pre-existing flat layouts
Do not touch legacy nested decisions directories
Skip the gitignore check silently if git is absent
Read the full steps protocol before executing step one

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.