agent-customization

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? VS Code agent customizations often fail silently due to YAML frontmatter errors, wrong file locations, or vague descriptions, leaving developers unsure why their instructions, skills, or agents 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 missing trigger keywords in descriptions. - Use Case: A developer wants coding standards applied only to Python files; the skill guides creating a .instructions.md file in .github/instructions/ with a specific applyTo glob and keyword-rich description. ## Quick Start Ask the agent to create a workspace-level instructions 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 .instructions.md file in .github/instructions/ with a YAML frontmatter containing a keyword-rich description and an optional applyTo glob pattern. The body holds concise, actionable guidelines loaded when relevant files or tasks match.

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

Both appear as slash commands in chat. A prompt is a single focused task with parameterized inputs, while a skill is a multi-step workflow bundled with scripts, references, and assets in its own folder with a SKILL.md entry point.

Why are my Copilot instructions not being applied?▼

Silent failures usually come from YAML frontmatter errors like unescaped colons, tabs instead of spaces, or a name that mismatches the folder. Also check that the description contains trigger keywords, since discovery depends on it.

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.

Should I use copilot-instructions.md or AGENTS.md?▼

Use only one, not both. copilot-instructions.md in .github/ is recommended for project-wide standards, while AGENTS.md is an open standard supporting monorepo hierarchies with files in root or subfolders.