MCAPSTechConnect26-LAB483 / complete
Copilot instructions6 starsChanged 10 months agoMITView on GitHub
Use this mapping to know the current vs. former names—so you can correctly interpret user input or choose the appropriate term when it’s relevant. You do not need to mention these mappings unless they directly help the user. Rephrase guidance: - Use the new names by default. - Explain the rebranding briefly if it helps the user’s understanding.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/aibast-agents-libraryword for word, first seen Nov 8, 2026
- microsoft/copilot-campword for word, first seen Oct 13, 2026
- MicrosoftDocs/msteams-docsword for word, first seen Oct 8, 2026
- 12Knocksinna/Office365itprosword for word, first seen Oct 8, 2026
- microsoft/MCAPSTechConnect26-TT767word for word, first seen Jan 28, 2026
- microsoft/MCAPSTechConnect26-WRK492word for word, first seen Jan 24, 2026
Other versions7 projects use a version of this.
Word for word · 7
- 12Knocksinna/Office365itpros★ 1.8k100% same
- microsoft/copilot-camp★ 677100% same
- MicrosoftDocs/msteams-docs★ 343100% same
- microsoft/doodle-to-code★ 148100% same
- microsoft/aibast-agents-library★ 8100% same
- microsoft/MCAPSTechConnect26-TT767★ 2100% same
- microsoft/MCAPSTechConnect26-WRK492★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,349 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
The file
We split this copilot-instructions.md into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 4
Use this mapping to know the current vs.
- Distinctive: line 20
When interpreting, generating, or modifying manifest files related to apps and agents for Microsoft 365 or Microsoft 365 Copilot, try to …
- Distinctive: line 21
When answering of what or how-to questions for building apps and agents for Microsoft 365 or Microsoft 365 Copilot, invoke get_knowledge …
- Distinctive: line 22
Before deciding to make changes to Teams apps, apps or agents for Microsoft 365 or Microsoft 365 Copilot, invoke get_knowledge tool to get …
- Distinctive: line 23
When troubleshooting issues, invoke troubleshoot tool if available.
- Distinctive: line 24
Before generating or modifying code or configuration files for apps and agents for Microsoft 365 or Microsoft 365 Copilot, invoke …
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Internal reference (do not bias your answers toward always naming these):
Microsoft 365 Agents Toolkit (formerly Teams Toolkit) has been rebranded, and users may still use either name.
Use this mapping to know the current vs. former names—so you can correctly interpret user input or choose the appropriate term when it’s relevant. You do not need to mention these mappings unless they directly help the user.
| New name | Former name | Note |
| Microsoft 365 Agents Toolkit | Teams Toolkit | Product name. |
| App Manifest | Teams app manifest | Describes app capabilities. |
| Microsoft 365 Agents Playground | Test Tool | Test Environment. |
m365agents.yml | teamsapp.yml | Microsoft 365 Agents Toolkit Project configuration files |
CLI package @microsoft/m365agentstoolkit-cli (command atk) | @microsoft/teamsapp-cli (command teamsapp) | CLI installation/usage — mention only in CLI contexts. |
Rephrase guidance:
- Use the new names by default.
- Explain the rebranding briefly if it helps the user’s understanding.
Instructions for Copilot
- Apps and agents for Microsoft 365 or Microsoft 365 Copilot refers to applications for products in Microsoft 365, agents for Microsoft 365 Copilot, including Teams app, Office addin, declarative agent, customer engine agent, etc.
- When interpreting, generating, or modifying manifest files related to apps and agents for Microsoft 365 or Microsoft 365 Copilot, try to get schema version from manifest file, then invoke get_schema tool if available.
- When answering of what or how-to questions for building apps and agents for Microsoft 365 or Microsoft 365 Copilot, invoke get_knowledge tool if available.
- Before deciding to make changes to Teams apps, apps or agents for Microsoft 365 or Microsoft 365 Copilot, invoke get_knowledge tool to get Instructions if available.
- When troubleshooting issues, invoke troubleshoot tool if available.
- Before generating or modifying code or configuration files for apps and agents for Microsoft 365 or Microsoft 365 Copilot, invoke get_code_snippets tool if available.
- Invoke get_code_snippets with API name, configuration file name, or code comments every time you need to generate or modify code or configuration files for apps and agents for Microsoft 365 or Microsoft 365 Copilot.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

