# Owent Atframe Utils AI Agent Maintenance > AI Agent Maintenance - Skill: `tomevault-io/owent-atframe-utils-ai-agent-maintenance` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/owent-atframe-utils-ai-agent-maintenance` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/owent-atframe-utils-ai-agent-maintenance/raw - Safety review: pending (external: skill-scanner PASS, skillspector CAUTION) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/owent-atframe-utils-ai-agent-maintenance --- # AI Agent Maintenance Use this skill when updating AI-agent guidance for this repository or subproject. ## Required Outcomes - Deeply research the current prompt/skill layout and current AI-agent customization practices before editing. - Keep always-on guidance compact, actionable, and non-redundant. - Keep temporary-artifact guidance consistent: AI-created scratch files and script/log output should go in ignored build subdirectories, not repository roots. - Preserve compatibility across AGENTS-aware tools, VS Code Copilot, Codex, Claude Code, Kilo Code/CLI, Roo Code, Windsurf, Antigravity, OpenClaw/Hermes-style skills, and OpenCode where the repository intentionally supports them. - Keep this repository's AI surfaces independently maintainable; do not require parent, sibling, or vendored-submodule prompt files for `atframe_utils` guidance to make sense. - Re-check and record official source URLs whenever compatibility behavior, skill locations, or frontmatter semantics are changed. - Merge improvements into existing prompt and skill content; do not leave old versions, migration notes, changelog notes, or historical comparison sections. ## Compatibility Model - Prefer `AGENTS.md` as the canonical repository guide; nested `AGENTS.md` files should be specific to the subtree they govern. - Keep `.agents/skills//SKILL.md` as the portable skill source for VS Code, Roo/Kilo/Windsurf/Antigravity-style skill discovery, and OpenClaw/Hermes external skill directories. - Do not maintain `.github/copilot-instructions.md` copies when `AGENTS.md` and `.agents/skills/` cover the same rules. - Keep `CLAUDE.md` as a thin Claude Code bridge that imports `AGENTS.md` and the skills index with `@...` references; prefer imports over symlinks for Windows compatibility. - Keep repeatable workflows in `.agents/skills//SKILL.md`; bridge files should not duplicate full skill bodies. - Do not mirror `.agents/skills` workflows into `.claude/skills`; keep `CLAUDE.md` as the Claude-compatible bridge. - For Roo/Kilo/Windsurf/OpenCode/Antigravity/OpenClaw compatibility, preserve `AGENTS.md` and `.agents/skills/` first. Add tool-specific folders or config (`.roo`, `.kilo`, `.windsurf`, `.opencode`, etc.) only when the repository already uses them or the task explicitly asks for that surface. - Do not commit MCP server secrets, OAuth tokens, or local runtime configuration. If MCP guidance is needed, document least-privilege tool exposure, explicit user consent, timeouts, and secret handling instead of checked-in credentials. ## Procedure 1. **Research first** - Read the nearest `AGENTS.md`, `CLAUDE.md`, `.agents/skills/README.md`, and any relevant `SKILL.md` files before editing. Read legacy `.github` AI customization files only when migrating or deleting them. - Check the nearest `.gitignore` and existing build-directory names before changing temp-file guidance so examples point to ignored build subdirectories that already exist or are safe to create. - If compatibility behavior may change, check current official docs or maintained references for the affected tools. - Capture the URLs or local docs consulted in the final summary, and add a compact source note only when it helps future maintainers avoid repeating the same research. - Respect dirty workspaces: preserve unrelated user or formatter edits and avoid broad reformatting. 2. **Choose the right surface** - Put facts that apply to nearly every task in `AGENTS.md`. - Repository-wide temporary-artifact placement rules belong in `AGENTS.md`; skills should explain how to preserve the rule, not replace it. - Put path-specific or tool-specific rules in their native file only when that scope is needed. - Put multi-step, task-specific, or rarely used guidance in skills. - Prefer links to existing docs or skills over copying long reference material into always-on prompts. 3. **Write compact, discoverable skills** - Keep skill folder names and frontmatter `name` values identical; use lowercase hyphenated names. - Quote descriptions that contain colons and start them with `Use when:` plus concrete trigger words. - Front-load the most important trigger phrases; some tools truncate skill descriptions in listings. - Keep each `SKILL.md` focused. Move bulky examples, scripts, or reference material into sibling files when needed. ### Example policy pattern - Prefer examples like `build/_agent_tmp//notes.txt`, `build/_agent_tmp//script.log`, or an existing ignored build tree such as `build_*/_agent_tmp/`. - If no build tree exists yet, tell the agent to create `build/_agent_tmp/` (or the nearest repo's ignored `build/` subdirectory) instead of root-level `tmp/`, `log/`, or ad-hoc debug files. ### Validate before finishing - Check markdown/frontmatter diagnostics for changed prompt and skill files. - Run a scoped whitespace check for changed prompt and skill files. - Re-read representative files to ensure bridge files stay thin and skill routing points to the current skill. - For nested Git repositories, run status and whitespace checks from each affected repository root. ### Summarize clearly - Report the files changed, compatibility surfaces preserved, and validations run. - Call out skipped build/test work when the change is documentation-only. ## Source Links to Re-check - AGENTS.md guidance: - Agent Skills specification and best practices: - VS Code Copilot custom instructions and skills: - Claude Code memory and skills: - MCP security and tool design: - Roo/Kilo/Windsurf/OpenCode/OpenClaw/Hermes/Antigravity docs when touching those compatibility surfaces. --- > Source: [owent/atframe_utils](https://github.com/owent/atframe_utils) — distributed by [TomeVault](https://tomevault.io).