opencode-agent-file-generator

Generate and update AGENTS.md files from SKILL.md metadata across monorepos.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-agent-file-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-agent-file-generator
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-agent-file-generator
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-agent-file-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates propagation of skill metadata into AGENTS.md to keep agent documentation in sync with newly added or updated skills across a multi-package workspace.

Core Features & Use Cases

  • Automated AGENTS.md propagation: Automatically initialize and refresh AGENTS.md files for all sub-packages based on the latest SKILL.md data.
  • Dependency-aware updates: Builds a skill graph to determine relevant skills per project and updates root and per-package context accordingly.
  • Workspace-scale orchestration: Handles monorepos with nested packages, organizations, or submodules, ensuring consistency across the entire workspace.

Quick Start

Run the Python pipeline to analyze skills and regenerate all AGENTS.md files across the workspace.

Frequently Asked Questions about opencode-agent-file-generator

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

FAQPage Schema
How do I automatically generate AGENTS.md files across a monorepo?

To generate AGENTS.md files across a monorepo, this skill reads SKILL.md frontmatter and runs a Python pipeline to build a dependency graph, automatically initializing and refreshing agent documentation for all sub-packages.

What is the best way to keep agent documentation in sync with newly added skills in a multi-project workspace?

Keeping agent documentation in sync is handled by propagating skill metadata into AGENTS.md files, ensuring each project references relevant capabilities whenever new skills are added or existing ones are reorganized.

How does dependency-aware skill graph update work for nested workspace packages?

Dependency-aware updates work by reading skill metadata to build a dependency graph that determines relevant skills per project, then updating both root and sub-package AGENTS.md files accordingly.

Can I use this AGENTS.md propagation tool for monorepos with nested submodules?

Yes, this workspace-scale orchestration handles monorepos with nested packages, organizations, or submodules, applying dependency-aware updates to ensure consistency across the entire multi-package workspace.

When do I need to regenerate AGENTS.md files in my workspace?

You need to regenerate AGENTS.md files when new skills are added or existing skills are reorganized in a multi-project workspace, ensuring all sub-packages reference the latest capabilities from SKILL.md data.