mcsmcpsample
Copilot instructions1 starsChanged 38 days agoMITView on GitHub
Use the official MCP Python SDK v2 documentation at <https://py.sdk.modelcontextprotocol.io/> and the protocol documentation at <https://modelcontextprotocol.io/> when changing the MCP server. Use the Azure Functions Python developer reference at <https://learn.microsoft.com/azure/azure-functions/functions-reference-python> when changing the Function App entry point or host configuration.
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.
The file
We split this copilot-instructions.md into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 3
Use the official MCP Python SDK v2 documentation at <https://py.sdk.modelcontextprotocol.io/> and the protocol documentation at …
- Distinctive: line 5
Use the Azure Functions Python developer reference at <https://learn.microsoft.com/azure/azure-functions/functions-reference-python> when …
≈ “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
MCP Development References
Use the official MCP Python SDK v2 documentation at https://py.sdk.modelcontextprotocol.io/ and the protocol documentation at https://modelcontextprotocol.io/ when changing the MCP server.
Use the Azure Functions Python developer reference at https://learn.microsoft.com/azure/azure-functions/functions-reference-python when changing the Function App entry point or host configuration.
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.