Catalogue › Microsoft 365 Agents

CopilotForge - Microsoft 365 Agents

Use it in Copilot Cowork: download the Microsoft 365 Agents plugin for Copilot Cowork and upload it under Customize > Plugins > Upload plugin. How to install.

Turn organisational knowledge and repeatable information needs into appropriately scoped, owned and tested agents with a managed lifecycle.

Layer: delivery
Lead role: Agent Product Owner
Plugin name: copilotforge-m365-agents

Skill Status Lifecycle Description

agent-grounding draft Deliver, Assure, Improve Configures and controls what a Microsoft 365 agent grounds on - choosing specific sites, libraries, files or connectors rather than broad locations, deciding on web content, restricting answers to named sources, checking permission trimming and citations - and keeps a controlled knowledge list with owners and change approval. Use when a maker is adding knowledge to an agent, when answers come from the wrong places, or when knowledge changes.

agent-instructions draft Deliver, Improve Writes and maintains the instructions that govern a Microsoft 365 agent - role, audience, scope, how to use and cite knowledge, uncertainty and refusal behaviour, redirects, tone, response format and conversation starters - under version control with a change log and a regression run after every edit. Use when a brief is ready to build, when an agent misbehaves, or when someone wants to edit a live agent's instructions.

agent-lifecycle draft Launch, Improve, Scale Manages an individual Microsoft 365 agent after release through defined states - live, under change, under review, deprecated and retired - with change control, scheduled and triggered reviews, responses to platform changes, and a retirement path that tells users and disposes of the agent cleanly. Use when a live agent needs changing, when its review date arrives, when its owner or knowledge lapses, or when it should be retired.

agent-opportunity-assessment draft Discover, Envision Tests whether a request that already points to an agent really warrants a dedicated, owned agent rather than a shared prompt, a scenario or an existing agent, and if so which kind - knowledge, task or autonomous - and which build path tier, recorded as a short assessment for intake. Use when a team asks for an agent, when several teams want similar agents, or when a prompt pattern is spreading and might become one.

agent-ownership draft Deliver, Launch, Improve Assigns and records the business owner, knowledge owners, technical owner, maker and support route for an individual agent, with deputies, written acceptance, succession on role change and handling of ownerless agents, kept on an agent card. Use when an agent is being built or released, when its owner leaves or changes role, or when the inventory shows agents nobody claims.

agent-release-readiness draft Assure, Launch, Improve Runs the release gate for an agent, confirming owner, support route, sharing scope matched to risk tier, reviewer evidence, communications, monitoring, review date and retirement criteria, and registers the agent in the solution register. Use when an agent has passed testing and someone wants to share it, when its audience is about to widen, or when a live agent has no clear owner.

agent-testing draft Deliver, Assure, Improve Builds a proportionate test plan and a small evaluation set of real user questions with expected answers, covering groundedness, refusal and out-of-scope behaviour, permission trimming across different users and regression after change, against a threshold the business owner agrees. Use when an agent is ready for testing, before widening its audience, or after its instructions or knowledge change.

agent-use-case-design draft Envision, Deliver Turns an approved agent opportunity into an agent brief covering audience, purpose, scope and exclusions, instructions approach, knowledge sources, actions, the build-or-reuse decision, owner, support and success measures. Use when an idea has passed suitability as an agent, when a maker wants to start building, or when an existing agent needs its scope rewritten.

agent-value-measurement draft Measure, Improve, Scale Measures whether an individual agent delivers the value its hypothesis promised, combining audience-level usage, resolution and answer-quality signals, user feedback and the business outcome measure against the baseline, and produces a value report for the agent's review. Use when an agent has been live long enough to judge, when its review date approaches, or when someone claims an agent is or is not worth keeping.

knowledge-source-readiness draft Deliver, Assure, Improve Assesses each knowledge source an agent will ground on for owner, currency, accuracy, permissions and oversharing, classification and review cycle, and records a ready, ready-with-conditions or not-ready verdict. Use when an agent brief names its sources, when a maker wants to add a site or library as knowledge, or when an agent starts giving outdated or surprising answers.

Skill	Status	Lifecycle	Description
`agent-grounding`	draft	Deliver, Assure, Improve	Configures and controls what a Microsoft 365 agent grounds on - choosing specific sites, libraries, files or connectors rather than broad locations, deciding on web content, restricting answers to named sources, checking permission trimming and citations - and keeps a controlled knowledge list with owners and change approval. Use when a maker is adding knowledge to an agent, when answers come from the wrong places, or when knowledge changes.
`agent-instructions`	draft	Deliver, Improve	Writes and maintains the instructions that govern a Microsoft 365 agent - role, audience, scope, how to use and cite knowledge, uncertainty and refusal behaviour, redirects, tone, response format and conversation starters - under version control with a change log and a regression run after every edit. Use when a brief is ready to build, when an agent misbehaves, or when someone wants to edit a live agent's instructions.
`agent-lifecycle`	draft	Launch, Improve, Scale	Manages an individual Microsoft 365 agent after release through defined states - live, under change, under review, deprecated and retired - with change control, scheduled and triggered reviews, responses to platform changes, and a retirement path that tells users and disposes of the agent cleanly. Use when a live agent needs changing, when its review date arrives, when its owner or knowledge lapses, or when it should be retired.
`agent-opportunity-assessment`	draft	Discover, Envision	Tests whether a request that already points to an agent really warrants a dedicated, owned agent rather than a shared prompt, a scenario or an existing agent, and if so which kind - knowledge, task or autonomous - and which build path tier, recorded as a short assessment for intake. Use when a team asks for an agent, when several teams want similar agents, or when a prompt pattern is spreading and might become one.
`agent-ownership`	draft	Deliver, Launch, Improve	Assigns and records the business owner, knowledge owners, technical owner, maker and support route for an individual agent, with deputies, written acceptance, succession on role change and handling of ownerless agents, kept on an agent card. Use when an agent is being built or released, when its owner leaves or changes role, or when the inventory shows agents nobody claims.
`agent-release-readiness`	draft	Assure, Launch, Improve	Runs the release gate for an agent, confirming owner, support route, sharing scope matched to risk tier, reviewer evidence, communications, monitoring, review date and retirement criteria, and registers the agent in the solution register. Use when an agent has passed testing and someone wants to share it, when its audience is about to widen, or when a live agent has no clear owner.
`agent-testing`	draft	Deliver, Assure, Improve	Builds a proportionate test plan and a small evaluation set of real user questions with expected answers, covering groundedness, refusal and out-of-scope behaviour, permission trimming across different users and regression after change, against a threshold the business owner agrees. Use when an agent is ready for testing, before widening its audience, or after its instructions or knowledge change.
`agent-use-case-design`	draft	Envision, Deliver	Turns an approved agent opportunity into an agent brief covering audience, purpose, scope and exclusions, instructions approach, knowledge sources, actions, the build-or-reuse decision, owner, support and success measures. Use when an idea has passed suitability as an agent, when a maker wants to start building, or when an existing agent needs its scope rewritten.
`agent-value-measurement`	draft	Measure, Improve, Scale	Measures whether an individual agent delivers the value its hypothesis promised, combining audience-level usage, resolution and answer-quality signals, user feedback and the business outcome measure against the baseline, and produces a value report for the agent's review. Use when an agent has been live long enough to judge, when its review date approaches, or when someone claims an agent is or is not worth keeping.
`knowledge-source-readiness`	draft	Deliver, Assure, Improve	Assesses each knowledge source an agent will ground on for owner, currency, accuracy, permissions and oversharing, classification and review cycle, and records a ready, ready-with-conditions or not-ready verdict. Use when an agent brief names its sources, when a maker wants to add a site or library as knowledge, or when an agent starts giving outdated or surprising answers.

Credit

Created by Simon Foote as part of CopilotForge. Content is licensed under CC BY 4.0; keep the credit in each skill's license and authors fields when you share or adapt it. See NOTICE.md in the repository.