makinari-agents-md

Create and maintain a canonical AGENTS.md with a Legacy section.

1|Updated May 8, 2025
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-agents-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makinari-agents-md
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-agents-md
Command: npx skills add https://github.com/Uncodier/API --skill makinari-agents-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes a single AGENTS.md in the repository root to operationalise the harness principles for the active flow, ensuring a stable, read-mostly operating manual that is not overwritten by sibling skills and preserving previous content under a Legacy section.

Core Features & Use Cases

  • Creates a canonical AGENTS.md per flow type at the repository root and appends new sections rather than rewriting existing content.
  • Preserves historical decisions by moving older content into a collapsed Legacy section while writing the new canonical body.
  • Defines governance rules and anchors for future changes, ensuring consistency across branches and teams.

Quick Start

Run this skill at bootstrap or when the orchestrator switches the flow type to generate or update the AGENTS.md at the repository root.

Frequently Asked Questions about makinari-agents-md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a canonical AGENTS.md operating manual for my repository?

To generate a canonical AGENTS.md operating manual, run this skill during bootstrap or when the orchestrator switches flow types. It creates an authoritative operating manual at the repository root, enforcing template guidelines, section order, and append-only revisions.

How does AGENTS.md versioning work when preserving legacy documentation?

AGENTS.md versioning works by moving older content into a collapsed Legacy section while writing the new canonical body. This append-only approach ensures historical decisions are preserved and previous content is not overwritten by sibling skills.

When do I need to update the AGENTS.md governance file in my workflow?

You need to update the AGENTS.md governance file at bootstrap or when the orchestrator switches the active flow type. This ensures the repository root maintains a single authoritative operating manual with correct governance rules and anchors for future changes.

Can I maintain consistent project documentation across branches using AGENTS.md?

Yes, you can maintain consistent project documentation across branches. The skill defines governance rules and anchors for future changes, ensuring a stable, read-mostly operating manual that serves as the primary project contract across teams.

What is the best way to prevent sibling skills from overwriting repository documentation?

The best way to prevent sibling skills from overwriting repository documentation is using this skill to enforce append-only revisions in AGENTS.md. It moves older content into a Legacy section rather than rewriting, ensuring a stable operating manual.

Does AGENTS.md generation require any specific dependencies or components?

AGENTS.md generation requires no specific dependencies or components. The skill operates independently to automate the creation and maintenance of the canonical operating manual, applying template guidelines and legacy handling without external module requirements.