setup-agent-machine

Generates a YAML manifest, per-directory indexes, and AGENTS.md for agent machine context.

11|1|Updated Jul 25, 2025

Search Tags:#agents.md #search optimization #yaml manifest #agent context #directory indexing #machine setup

Ready to run

npx skills add https://github.com/tomzx/agents --skill setup-agent-machine-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-agent-machine
Source: https://github.com/tomzx/agents/tree/main/skills/setup-agent-machine
Command: npx skills add https://github.com/tomzx/agents --skill setup-agent-machine-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents waste time guessing where to search on a machine. This Skill interviews the user, records searchable directories in a manifest, builds per-directory index files, and writes an AGENTS.md so any future agent knows exactly where to look. ## Core Features & Use Cases - Interactive directory interview: Collects confirmed paths from the user in rounds, supporting single paths and `/` glob expansion, with existence verification. - Index generation: Delegates to the index-directory skill to build one index file per directory under `indexes/`, refreshing only missing or stale entries on re-run. - AGENTS.md authoring: Writes a marked generated section telling agents how to pick at most three candidate directories and keep indexes current. - Use Case: Run `/setup-agent-machine ~/src ~/notes/` on a new workstation so every future agent session reads the indexes first and searches only the two or three relevant directories instead of scanning the whole disk. ## Quick Start Run /setup-agent-machine in the directory where you want the agent context, then answer the interview questions with the directories agents should search.

Frequently Asked Questions about setup-agent-machine

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

FAQPage Schema

How do I set up a directory so agents know where to search?▼

Run /setup-agent-machine in the target directory. It interviews you for searchable paths, writes agent-machine.yaml, builds one index file per directory under indexes/, and generates an AGENTS.md explaining how agents should use them.

What is the difference between a plain path and a /* path in the manifest?▼

A plain path like /home/user/src indexes that single directory as one unit. A path ending in /* indexes each directory directly under it separately, and any directory added there later gets indexed too.

Does setup-agent-machine overwrite an existing AGENTS.md file?▼

It asks before modifying an existing AGENTS.md. If the file lacks the generated Agent machine context marker, you choose whether to append a generated section, overwrite the file, or abort.

How do I add new directories after the initial setup?▼

Re-run /setup-agent-machine with the new paths as arguments, for example /setup-agent-machine ~/src/new-project. It appends them to the manifest and builds only the new indexes, leaving existing ones untouched.

When are directory indexes refreshed on a re-run?▼

An index is rebuilt only if it is missing or stale. Stale means its Last indexed date is older than 30 days or you confirm the directory changed significantly; all other indexes are left as-is.