technical-documentation

Audit and align repository governance files and documentation across agent workflows.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill technical-documentation-borealbytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-documentation
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/.agents/skills/technical-documentation
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill technical-documentation-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical documentation and agent-governance files are often inconsistent across large repos, leading to misaligned contributor practices, unclear instructions for agents, and fragile OpenClaw overlays.

Core Features & Use Cases

  • Governance surface alignment for AGENTS.md/CONTRIBUTING.md and canonical vs alias policies.
  • OpenClaw overlay guidance and page-type preservation for documentation projects.
  • Multi-agent orchestration guidance using sub-agents to map scope, validate references, and maintain docs quality over time.
  • Evergreen and brownfield doc audits, plus contributor onboarding and governance automation.
  • Use Case: Maintain a single, consistent policy core that feeds both Cursor/Claude and Codex workflows while keeping AGENTS/CONTRIBUTING aligned.

Quick Start

Begin by auditing repository governance files (AGENTS.md and CONTRIBUTING.md), then perform a scoped documentation audit across docs and READMEs to surface growth opportunities.

Frequently Asked Questions about technical-documentation

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

FAQPage Schema
How do I audit technical documentation and agent-instruction files for consistency in a large repository?

To audit technical documentation and agent-instruction files, you identify and remedy gaps in governance surfaces like AGENTS.md and CONTRIBUTING.md, performing scoped audits across docs and READMEs to surface growth opportunities.

What is OpenClaw overlay guidance and how does it preserve page types in documentation projects?

OpenClaw overlay guidance ensures page-type preservation for documentation projects by validating canonical entry points and frontmatter definitions, maintaining a unified policy core across Cursor/Claude and Codex workflows.

How do I maintain a single policy core that feeds both Cursor/Claude and Codex workflows?

You maintain a single policy core by validating canonical entry points and frontmatter definitions, ensuring cross-agent consistency using sub-agents to map scope and validate references across Cursor/Claude and Codex workflows.

Can I use sub-agents to map scope and validate references for repository governance automation?

Yes, you can use sub-agents for multi-agent orchestration to map scope, validate references, and maintain technical documentation quality over time, covering both evergreen and brownfield doc audits.

What is the best way to align AGENTS.md and CONTRIBUTING.md files for contributor onboarding in brownfield repositories?

The best way to align AGENTS.md and CONTRIBUTING.md files is to apply governance surface alignment for canonical versus alias policies, performing brownfield doc audits to ensure contributor onboarding consistency.

Does this approach work for evergreen documentation audits or only brownfield scenarios?

This approach works for both evergreen and brownfield documentation audits, identifying and remedying gaps in repository technical documentation and agent-instruction governance across all scenarios.