A technical project manager is standardizing Copilot guidance for a 50-person program: reusable steps for API reviews, one-off questions about a bug, and persistent tone rules for all answers. Which distinction correctly identifies the characteristics of skills, prompts, and instructions?
Select an answer to reveal the explanation.
Short Explanation
You are sorting tools into the right drawers. Reusable playbooks, single asks, and always-on rules each have a home and role clarity keeps your 50 teammates getting consistent help.
Full Explanation
Skills encapsulate reusable procedural knowledge that an agent can invoke across tasks, prompts express single task-specific requests with context, and instructions define persistent constraints such as tone or policy applied across interactions, which maps directly to API reviews, a one-off bug inquiry, and tone rules. Swapping instructions and prompts fails because one-off questions need ephemeral context rather than persistent rules, while reusable reviews need packaged procedure rather than a single request. Using prompts for tone fails because tone must persist across turns rather than being retyped each time, and misassigning skills to single bugs wastes reusable packaging on ephemeral needs. Using skills for tone fails because tone is a constraint not a procedure, while instructions for a single bug over-persists narrow context. For the exam, remember skills equal reusable how-to, prompts equal now, instructions equal always, and in practice store skills and instructions in versioned files so the whole program inherits updates.