How do I install the Update AI Config skill?

Run npx skillmds@latest add tomevault-io/update-ai-config 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 Update AI Config 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 Update AI Config?

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 Update AI Config free to use?

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

Who published Update AI Config?

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

Update AI Config by tomevault-io — Agent Skill

Name: Update AI Config
Author: tomevault-io

File contents

Manage AI Config Templates

IMPORTANT: This project uses universal-ai-config (uac). All AI configuration lives in the <%= config.templatesDir %>/ directory as universal templates. NEVER edit generated target-specific files (e.g. .claude/, .github/copilot-instructions.md, .cursor/) directly — those are overwritten on every uac generate run. Always modify the source templates in <%= config.templatesDir %>/.

When the user wants to add or change AI configuration for this project, follow these steps:

1. Understand the Request

Read the template guide at <%= instructionPath('uac-template-guide') %> to understand the available template types and when to use each.

2. Determine the Template Type

Based on the user's request, decide which type of template to work with:

Persistent context, rules, or guidelines → Use /update-instruction
Repeatable task, workflow, or slash command → Use /update-skill
Specialized AI persona with restricted tools → Use /update-agent
Automatic lifecycle automation (on events) → Use /update-hook
MCP server configuration → Use /update-mcp

3. Delegate

Invoke the appropriate skill with the user's requirements. If the intent is ambiguous, ask the user to clarify before proceeding. For example:

"Add a rule about error handling" → /update-instruction
"Create a deploy workflow" → /update-skill
"Set up a code reviewer" → /update-agent
"Run linting after file edits" → /update-hook
"Add an MCP server for GitHub" → /update-mcp

Important

The delegated skills (/update-instruction, /update-skill, /update-agent, /update-hook, /update-mcp) primarily create or modify files inside <%= config.templatesDir %>/. They may also modify files in directories listed under additionalTemplateDirs in the config — but only with explicit user confirmation, since those are shared templates that may affect other projects. Never edit generated output files in .claude/, .cursor/, .github/, or similar target-specific directories — those are regenerated from templates and any direct changes will be lost.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: update-ai-configdescription: Create, update, or manage AI configuration templates. Analyzes what the user needs and delegates to the appropriate template-specific skill. Use when this capability is needed.---# Manage AI Config Templates**IMPORTANT:** This project uses universal-ai-config (`uac`). All AI configuration lives in the `<%= config.templatesDir %>/` directory as universal templates. NEVER edit generated target-specific files (e.g. `.claude/`, `.github/copilot-instructions.md`, `.cursor/`) directly — those are overwritten on every `uac generate` run. Always modify the source templates in `<%= config.templatesDir %>/`.When the user wants to add or change AI configuration for this project, follow these steps:## 1. Understand the RequestRead the template guide at `<%= instructionPath('uac-template-guide') %>` to understand the available template types and when to use each.## 2. Determine the Template TypeBased on the user's request, decide which type of template to work with:- **Persistent context, rules, or guidelines** → Use `/update-instruction`- **Repeatable task, workflow, or slash command** → Use `/update-skill`- **Specialized AI persona with restricted tools** → Use `/update-agent`- **Automatic lifecycle automation (on events)** → Use `/update-hook`- **MCP server configuration** → Use `/update-mcp`## 3. DelegateInvoke the appropriate skill with the user's requirements. If the intent is ambiguous, ask the user to clarify before proceeding. For example:- "Add a rule about error handling" → `/update-instruction`- "Create a deploy workflow" → `/update-skill`- "Set up a code reviewer" → `/update-agent`- "Run linting after file edits" → `/update-hook`- "Add an MCP server for GitHub" → `/update-mcp`## ImportantThe delegated skills (`/update-instruction`, `/update-skill`, `/update-agent`, `/update-hook`, `/update-mcp`) primarily create or modify files inside `<%= config.templatesDir %>/`. They may also modify files in directories listed under `additionalTemplateDirs` in the config — but only with explicit user confirmation, since those are shared templates that may affect other projects. Never edit generated output files in `.claude/`, `.cursor/`, `.github/`, or similar target-specific directories — those are regenerated from templates and any direct changes will be lost.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/fabis94) — claim your Tome and manage your conversions.

Frequently asked questions

Update AI Config