agent-customization

Create and troubleshoot VS Code agent customization files including instructions, prompts, hooks, agents, and skills.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill agent-customization-az0512124155azz-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-customization
Source: https://github.com/az0512124155azz-sys/CodeForge/tree/main/extensions/copilot/assets/prompts/skills/agent-customization
Command: npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill agent-customization-az0512124155azz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? VS Code agent customization files (instructions, prompts, hooks, custom agents, skills) often fail silently due to YAML frontmatter errors, wrong file locations, or missing descriptions, leaving users unsure why their customizations are ignored. ## Core Features & Use Cases - Primitive Selection Guidance: Decision flow for choosing between agent instructions, file instructions, prompts, hooks, custom agents, and skills based on the task. - Creation Workflow: Step-by-step process covering scope selection (workspace vs user profile), file placement, frontmatter requirements, and validation. - Troubleshooting Reference: Documents common pitfalls like unescaped colons in YAML, overly broad applyTo patterns, and weak descriptions that break discovery. - Use Case: A developer wants coding standards applied only to Python files; the skill guides creating a .instructions.md file in .github/instructions/ with applyTo: "**/*.py" and a keyword-rich description. ## Quick Start Ask the agent to create a workspace instruction file that applies your team's testing conventions to all TypeScript files.

Frequently Asked Questions about agent-customization

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

FAQPage Schema
How do I create custom instructions for VS Code Copilot?▼

Create a copilot-instructions.md file in the .github folder for project-wide rules, or a .instructions.md file in .github/instructions/ with an applyTo glob for file-specific guidance. Include a keyword-rich description so the agent can discover it on demand.

What is the difference between a prompt file and a skill in VS Code?▼

Both appear as slash commands in chat. A prompt file (.prompt.md) handles a single focused task with parameterized inputs, while a skill (SKILL.md) provides a multi-step workflow with bundled scripts, references, and assets.

Why is my VS Code instruction file being ignored?▼

Silent failures usually come from YAML frontmatter errors like unescaped colons, tabs instead of spaces, or a name that does not match the folder. Quote descriptions containing colons and verify the file sits in the correct .github location.

When should I use hooks instead of instructions?▼

Use hooks when behavior must be enforced deterministically, such as blocking dangerous commands or auto-formatting after edits. Instructions only guide agent behavior non-deterministically, while hooks run shell commands at lifecycle events like PreToolUse and PostToolUse.

Can I restrict which tools a custom agent can use?▼

Yes, the tools field in .agent.md frontmatter accepts built-in aliases like read, search, edit, and execute, plus MCP server tools. Setting tools to an empty array removes all tool access for conversational-only agents.