Skip to content
Back to skills

Agent Instruction Maintenance

ASecurity

Review, update, and synchronize agent instructions and configs across Codex and Claude (and optionally VS Code/Copilot); use when creating or refactoring agent prompts, skills, or chatmodes (trigger keywords: agent instructions, prompt review, skill update, chatmode, subagent).

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentsrefactoring

Works with

  • vscode

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill agent-instruction-maintenance --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Instruction Maintenance?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Instruction Maintenance
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-agent-instruction-maintenance/badge)](https://www.skillsdirectory.com/skills/david-li0406-agent-instruction-maintenance)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-instruction-maintenance
description: "Review, update, and synchronize agent instructions and configs across Codex and Claude (and optionally VS Code/Copilot); use when creating or refactoring agent prompts, skills, or chatmodes (trigger keywords: agent instructions, prompt review, skill update, chatmode, subagent)."
---

# Agent Instruction Maintenance

## What this skill does
- Audits agent instructions for clarity, correctness, and consistency.
- Validates frontmatter and minimal schemas for detected ecosystems.
- Aligns tool-specific variants while keeping behavior consistent.

## When to use it
- Trigger phrases: "agent instructions", "prompt review", "skill update", "chatmode", "subagent".
- Use after creating or editing instructions, or when standards change.

## Step-by-step workflow
1) Discover which ecosystems exist in the repo or user config.
2) Load local guidance (AGENTS.md, CLAUDE.md, copilot-instructions) when present.
3) Validate minimal frontmatter for each file type (see references).
4) Review content for clarity, scope, and actionability; remove ambiguity.
5) Ensure intent parity across tools while avoiding contradictions.
6) Keep instructions lean; move deep details into references.
7) Propose updates with before/after snippets and rationale.

## Default prioritization
- Prefer Codex-first guidance unless the user asks for tool-specific changes.
- Prefer Skills (SKILL.md) and AGENTS.md for portable, shared behavior.
- Apply tool-specific files only when a feature is unique to that tool.

## Tool-specific references
- Codex: `references/codex.md`
- Claude Opus: `references/claude-code.md`
- VS Code/Copilot (optional): `references/copilot-vscode.md`
- Tool choice (commands vs skills vs agents): `references/tool-selection.md`

## Expected outputs / formatting
- Summary of findings and risk areas.
- Required fixes (schema/format) vs recommended improvements (clarity/consistency).
- Proposed edits with brief rationale.
- Updated files when approved.

## Example prompts
- "Review our skills and normalize naming/trigger phrases."
- "Validate agent frontmatter across Claude and Copilot files."
- "Update Codex skills to match new project standards."

Files in this skill

  • SKILL.md2.2 KB
  • references/claude-code.md1.7 KB
  • references/codex.md2.3 KB
  • references/copilot-vscode.md1.6 KB
  • references/tool-selection.md1.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…