Agents
Copilot instructions1.1k starsChanged 12 days agoMITView on GitHub
Synchronization owns maintenance of generated Teams samples in every language. The language profiles in automation/teams-sample-sync/config/targets.yml define the managed destination roots, currently samples/dotnet/teams/** and samples/nodejs/teams/**. This rule also applies to future language profiles. Outside that process, do not change any files in those roots, including implementations, project/package versions, lockfiles, shared helpers such as AspNetExtensions.cs, tests, manifests, configuration, assets, documentation, formatting, cleanup, or dependency updates. The authorized maintenance path includes the synchronization runtime and Copilot tasks assigned through workflow-generated handoff issues with…
Trending
Quiet this year.thin dataabout the whole repository
Who's talking about microsoft/Agents
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
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,336 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 repository18 other files it gives its agents.
- agents-sdk-to-prodSkill
- agents-sdk-typescript-debuggingSkill
- agents-sdk-typescript-otelSkill
- agents-sdk-typescriptSkill
- bf-to-agents-sdk-typescript-migrationSkill
- teams-sdk-to-agents-sdk-typescript-migrationSkill
- agents-sdk-dotnet-activityhandler-migrationSkill
- agents-sdk-dotnet-debuggingSkill
- agents-sdk-dotnet-otelSkill
- agents-sdk-dotnetSkill
- agents-sdk-to-prodSkill
- bf-to-agents-sdk-dotnet-migrationSkill
- teams-sdk-to-agents-sdk-dotnet-migrationSkill
- agents-sdk-python-otelSkill
- agents-sdk-to-prodSkill
- agents-sdk-provisionSkill
- teams-app-manifestSkill
- sync-teams-samples-to-agents-sdkSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 16
If an ordinary task needs a change or encounters a build failure in these roots, report the problem and identify the synchronization work …
≈ “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
Generated Teams samples
Synchronization owns maintenance of generated Teams samples in every language.
The language profiles in automation/teams-sample-sync/config/targets.yml define
the managed destination roots, currently samples/dotnet/teams/** and
samples/nodejs/teams/**. This rule also applies to future language profiles.
Outside that process, do not change any files in those roots, including implementations,
project/package versions, lockfiles, shared helpers such as AspNetExtensions.cs, tests,
manifests, configuration, assets, documentation, formatting, cleanup, or dependency updates.
The authorized maintenance path includes the synchronization runtime and Copilot tasks assigned through workflow-generated handoff issues with prepared patches and migration evidence. Assignment to an arbitrary issue does not grant this exception. Follow the synchronization instructions and validation requirements for the selected samples.
If an ordinary task needs a change or encounters a build failure in these roots, report the problem and identify the synchronization work needed. Reference an existing issue when appropriate; do not automatically open an issue or trigger a workflow.
Review generated samples normally: flag real defects, unauthorized changes, and missing or failing validation. Recommend fixing them through synchronization, including required SDK compatibility migrations, rather than manual generated-output patches.
Automation source and the shared contract harness outside these roots remain maintainable through ordinary tasks. This ownership guidance does not replace CI enforcement.
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.