agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/aibast-agents-library/community_rapp/project/.github/copilot-instructions.md

aibast-agents-library / project

Copilot instructions8 starsChanged 3 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

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
  1. Distinctive:

    Use this mapping to know the current vs.

    line 4
  2. Distinctive:

    When interpreting, generating, or modifying manifest files related to apps and agents for Microsoft 365 or Microsoft 365 Copilot, try to …

    line 20
  3. Distinctive:

    When answering of what or how-to questions for building apps and agents for Microsoft 365 or Microsoft 365 Copilot, invoke get_knowledge …

    line 21
  4. Distinctive:

    Before deciding to make changes to Teams apps, apps or agents for Microsoft 365 or Microsoft 365 Copilot, invoke get_knowledge tool to get …

    line 22
  5. Distinctive:

    When troubleshooting issues, invoke troubleshoot tool if available.

    line 23
  6. Distinctive:

    Before generating or modifying code or configuration files for apps and agents for Microsoft 365 or Microsoft 365 Copilot, invoke …

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

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 nameFormer nameNote
Microsoft 365 Agents ToolkitTeams ToolkitProduct name.
App ManifestTeams app manifestDescribes app capabilities.
Microsoft 365 Agents PlaygroundTest ToolTest Environment.
m365agents.ymlteamsapp.ymlMicrosoft 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free