How do I install the Configure AI skill?

Run npx skillmds@latest add tomevault-io/configure-ai in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Configure AI safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Configure AI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Configure AI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Configure AI?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Configure AI by tomevault-io — Agent Skill

Name: Configure AI
Author: tomevault-io

Configure AI

Authors AGENTS.md and defines the skills-vs-docs boundary for a repo. Configures AI coding tools (Claude Code, Codex, Antigravity CLI, Copilot) and the skills-as-docs philosophy. Use when creating or auditing AGENTS.md, setting up AI tooling for a project, or deciding what belongs in a skill versus docs/. Do NOT use for README structure -> use write-readme; for llms.txt generation -> use create-llms-txt; for Claude-specific skill features (invocation control, subagents, model overrides) -> use extend-oss-skills-to-claude. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

AI Workflows

Specifications

Convention	Spec
SKILL.md	Agent Skills Specification
AGENTS.md	agents.md Standard
llms.txt	llms.txt Specification

Skills vs Docs

Skills (skills/<name>/SKILL.md) = executable agent instructions. How to do things (conventions, workflows, tool usage)
Docs (docs/) = project documentation. What was decided and why (rfcs/, guides/, plans/, runbooks/, architecture/)
Both exist in every project; neither replaces the other
Every repo should also have: README.md (humans) + AGENTS.md (AI) + llms.txt (LLM discovery)
Root-level standard files (README, AGENTS.md, CONTRIBUTING, LICENSE, CODEOWNERS, llms.txt) stay at root; everything else goes in docs/

AI Tools

Tool	Usage
Claude Code (opus)	Primary AI coding assistant. Architecture, refactoring, multi-file edits
OpenAI Codex	`workspace-write` "Auto" base config with a guardian auto-reviewer; ships writer, reviewer, plan, and guardian profiles/agents
Google Antigravity CLI (agy)	Replaces legacy Gemini CLI; per-command allow/deny lists managed in-app via `/permissions`, `--sandbox` for terminal restrictions
GitHub Copilot	Inline completion plus `settings.json` (model, reasoning effort, theme)

Claude Code Configuration

Claude Code is configured per-project via CLAUDE.md files at the repository root. These files define:

Project context tech stack, directory structure, key patterns
Coding conventions naming, formatting, commit style
Behavioral rules what to avoid, how to handle edge cases
Memory persistent notes stored in .claude/ directories

Best Practices

Keep CLAUDE.md concise; it's loaded into every conversation
Use separate memory files for detailed topic notes
Reference project-specific tools and commands
Define verification steps (build, test, lint)

AGENTS.md Standard

Every repo MUST have AGENTS.md at root.

Template Structure

Identity project name, one-line description
Architecture high-level component overview
Commands build, test, lint, run
Code Style language-specific conventions
Extension Guide how to add features

Do NOT include static directory trees or file tables; structure goes stale. Instead, instruct agents to use tree and ripgrep/ag to discover project layout on the fly.

Skills Standard

Every repo with a CLI or library should have skills/<name>/SKILL.md:

Frontmatter: name, description, argument-hint (for CLI tools)
Content: step-by-step guidance for using or extending the project
Skills live in skills/<name>/SKILL.md within each repo

Git Workflows

AI-assisted commit, review, and PR authoring live in dedicated agent skills (ship, pr, review), not in the release tool. The release tool (sr) is release-engineering only as of v7: release, status, config, init, migrate, completions, update. See sync-release for release conventions and sr migrate for the upgrade guide from older versions.

Source: urmzd/dotfiles — distributed by TomeVault.

---name: configure-aidescription: Authors AGENTS.md and defines the skills-vs-docs boundary for a repo. Configures AI coding tools (Claude Code, Codex, Antigravity CLI, Copilot) and the skills-as-docs philosophy. Use when creating or auditing AGENTS.md, setting up AI tooling for a project, or deciding what belongs in a skill versus docs/. Do NOT use for README structure -> use write-readme; for llms.txt generation -> use create-llms-txt; for Claude-specific skill features (invocation control, subagents, model overrides) -> use extend-oss-skills-to-claude. Use when this capability is needed.---# AI Workflows## Specifications| Convention | Spec ||------------|------|| SKILL.md | [Agent Skills Specification](https://agentskills.io/specification) || AGENTS.md | [agents.md Standard](https://agents.md/) || llms.txt | [llms.txt Specification](https://llmstxt.org/) |## Skills vs Docs- **Skills** (`skills/<name>/SKILL.md`) = executable agent instructions. *How to do things* (conventions, workflows, tool usage)- **Docs** (`docs/`) = project documentation. *What was decided and why* (rfcs/, guides/, plans/, runbooks/, architecture/)- Both exist in every project; neither replaces the other- Every repo should also have: README.md (humans) + AGENTS.md (AI) + llms.txt (LLM discovery)- Root-level standard files (README, AGENTS.md, CONTRIBUTING, LICENSE, CODEOWNERS, llms.txt) stay at root; everything else goes in `docs/`## AI Tools| Tool | Usage ||------|-------|| Claude Code (opus) | Primary AI coding assistant. Architecture, refactoring, multi-file edits || OpenAI Codex | `workspace-write` "Auto" base config with a guardian auto-reviewer; ships writer, reviewer, plan, and guardian profiles/agents || Google Antigravity CLI (agy) | Replaces legacy Gemini CLI; per-command allow/deny lists managed in-app via `/permissions`, `--sandbox` for terminal restrictions || GitHub Copilot | Inline completion plus `settings.json` (model, reasoning effort, theme) |## Claude Code ConfigurationClaude Code is configured per-project via `CLAUDE.md` files at the repository root. These files define:- **Project context** tech stack, directory structure, key patterns- **Coding conventions** naming, formatting, commit style- **Behavioral rules** what to avoid, how to handle edge cases- **Memory** persistent notes stored in `.claude/` directories### Best Practices- Keep `CLAUDE.md` concise; it's loaded into every conversation- Use separate memory files for detailed topic notes- Reference project-specific tools and commands- Define verification steps (build, test, lint)## AGENTS.md StandardEvery repo MUST have `AGENTS.md` at root.### Template Structure1. **Identity** project name, one-line description2. **Architecture** high-level component overview3. **Commands** build, test, lint, run4. **Code Style** language-specific conventions5. **Extension Guide** how to add featuresDo NOT include static directory trees or file tables; structure goes stale. Instead, instruct agents to use `tree` and `ripgrep`/`ag` to discover project layout on the fly.## Skills StandardEvery repo with a CLI or library should have `skills/<name>/SKILL.md`:- **Frontmatter:** `name`, `description`, `argument-hint` (for CLI tools)- **Content:** step-by-step guidance for using or extending the project- Skills live in `skills/<name>/SKILL.md` within each repo## Git WorkflowsAI-assisted commit, review, and PR authoring live in dedicated agent skills (`ship`, `pr`, `review`), not in the release tool. The release tool (`sr`) is release-engineering only as of v7: `release`, `status`, `config`, `init`, `migrate`, `completions`, `update`. See `sync-release` for release conventions and `sr migrate` for the upgrade guide from older versions.---> Source: [urmzd/dotfiles](https://github.com/urmzd/dotfiles) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions