manual-updater

Scan .agent folders and update DOT_AGENTS_MANUAL.md entries for agents, skills, and workflows.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill manual-updater-driveconnect-alpha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manual-updater
Source: https://github.com/DriveConnect-alpha/DriveConnect/tree/main/.agent/skills/manual-updater
Command: npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill manual-updater-driveconnect-alpha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill keeps the DOT_AGENTS_MANUAL.md documentation in sync with the actual repository content by updating, adding, or removing entries as agents, skills, and workflows are added, modified, or deleted.

Core Features & Use Cases

  • Automatically detect changes in .agent/agents, .agent/skills, and .agent/workflows and reflect them in the manual.
  • Support targeted updates when specific components are named for update, or a full resync to reconcile all entries.
  • Enforce governance with a gatekeeper: if no targets are provided, the agent prompts for the names to update.

Quick Start

Run the updater to synchronize DOT_AGENTS_MANUAL.md with the current repository state.

Frequently Asked Questions about manual-updater

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

FAQPage Schema
How do I automatically sync documentation with my repository's agent structure?

To automatically sync documentation with your agent structure, this skill scans .agent folders for additions, changes, and deletions to update DOT_AGENTS_MANUAL.md. It detects modifications in .agent/agents, .agent/skills, and .agent/workflows to reflect current repository content.

How do I update DOT_AGENTS_MANUAL.md when specific agents or workflows change?

You can perform targeted updates to DOT_AGENTS_MANUAL.md by supplying specific component names. If no targets are provided, a gatekeeper logic prompts you for the names to update, ensuring precise synchronization of agents, skills, and workflows.

What is the best way to reconcile all manual entries after deleting multiple agent folders?

The best way to reconcile all manual entries after deletions is running a full resync. The included Python script scans the current .agent structure and automatically removes obsolete entries from DOT_AGENTS_MANUAL.md.

Can I use this updater to add documentation entries for newly created agent folders?

Yes, you can use this updater to add documentation entries for newly created agent folders. It scans the .agent directory structure to detect new agents, skills, and workflows, automatically generating corresponding entries in the manual.

Why does the documentation sync script prompt me for component names instead of updating automatically?

The documentation sync script prompts for component names due to enforced gatekeeper logic. If no targets are supplied for the update, it requires you to specify names, preventing unintended modifications to your DOT_AGENTS_MANUAL.md entries.

Does the manual updater require any external dependencies to run the sync workflow?

No, the manual updater does not require external dependencies to run the sync workflow. It operates using included Python scripts to scan .agent folders and update DOT_AGENTS_MANUAL.md without needing additional packages.