foundry-research
Skill677 starsChanged 4 months agoMITView on GitHub
Researches and compiles comprehensive information about Microsoft Foundry, including documentation, architecture, models, and deployment options. Use when user asks to "research Microsoft Foundry", "learn about Foundry", "Foundry documentation", "Foundry architecture", "Foundry models", "how to deploy with Foundry", "Foundry features", or "Foundry capabilities".
In this repository8 other files it gives its agents.
- src/extend-m365-copilot/path-e-lab01-declarative-copilot/RepairServiceAgent/AGENTS.mdAGENTS.md
- archive/src/agent-framework/complete/.github/copilot-instructions.mdCopilot instructions
- .github/copilot-instructions.mdCopilot instructions
- copilot-dev-camp-lab-authorSkill
- dev-camp-deckSkill
- dev-camp-documentSkill
- weekly-status-mailSkill
- zava-claims-exportSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 36
Ask the user to clarify their specific Foundry interest:
- Distinctive: line 45
Search: "Microsoft Foundry platform overview architecture"
- Distinctive: line 46
Search: "Microsoft Foundry models and capabilities"
- Distinctive: line 47
Search: "Microsoft Foundry deployment options"
- Distinctive: line 48
Search: "Microsoft Foundry best practices"
- Distinctive: line 49
Search: Specific topic based on user interest (e.g., "Foundry agents", "Foundry fine-tuning")
- Distinctive: line 107
All research comes from two primary sources:
- Distinctive: line 125
All searches are performed against official Microsoft documentation and Copilot Dev Camp resources
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Microsoft Foundry Research Skill
What This Skill Does
This skill helps you deep-dive into Microsoft Foundry documentation and capabilities by:
- Searching multiple topics across Microsoft Foundry documentation
- Collecting architecture guides, model documentation, and deployment patterns
- Organizing findings into clear sections (Overview, Architecture, Models, Deployment, Best Practices)
- Generating a comprehensive research summary with links and code samples
When to Use This Skill
Activate this skill when you need:
- Overview of Microsoft Foundry platform and components
- Understanding of available models and their capabilities
- Deployment and configuration guidance
- Best practices for building with Foundry
- Integration patterns with Azure services
- Code samples and quickstart guides
Workflow
Step 1: Topic Definition
Ask the user to clarify their specific Foundry interest:
- Foundry platform overview? (architecture, components)
- Specific model? (which model and its capabilities)
- Deployment scenario? (local, cloud, hybrid)
- Integration use case? (agents, workflows, content generation)
Step 2: Multi-Topic Research
Conduct multiple searches across the Microsoft Learn MCP Server:
- Search: "Microsoft Foundry platform overview architecture"
- Search: "Microsoft Foundry models and capabilities"
- Search: "Microsoft Foundry deployment options"
- Search: "Microsoft Foundry best practices"
- Search: Specific topic based on user interest (e.g., "Foundry agents", "Foundry fine-tuning")
Step 3: Information Organization
Compile findings into these sections:
## Microsoft Foundry Research Summary
### Overview
[Platform description, key components, use cases]
### Architecture
[System design, core components, integration points]
### Available Models
[Model list with capabilities, performance characteristics]
### Deployment Options
[Local development, cloud deployment, hybrid approaches]
### Best Practices
[Recommended patterns, performance optimization, security]
### Getting Started
[Quickstart guides, code examples, resources]
### Related Services
[Azure integration, complementary services]
### Additional Resources
[Links to official documentation and samples]Step 4: Deliverable Format
Structure findings as a detailed markdown document with:
- Clear section headers
- Bullet points for key information
- Direct links to Learn documentation
- Code snippets where relevant
- Architecture diagrams described in text
- Comparison tables for models or options
Output Format
The skill produces a comprehensive research report with:
| Component | Content |
| Executive Summary | 2-3 sentence overview of Foundry |
| Core Findings | 5-7 key points about the user's interest area |
| Technical Details | Architecture, models, APIs, configuration |
| Code Examples | Relevant quickstart code or integration patterns |
| Best Practices | Performance, security, and scalability guidance |
| Resource Links | Direct links to Learn documentation |
Information Sources
All research comes from two primary sources:
1. Microsoft Learn MCP Server (https://learn.microsoft.com/api/mcp)
- Microsoft official documentation
- Quickstart guides and tutorials
- Architecture patterns and design guides
- Code samples and reference implementations
- Best practice recommendations
2. Copilot Developer Camp (https://microsoft.github.io/copilot-camp/)
- Official Dev Camp labs and learning modules
- Hands-on tutorials and walkthroughs
- Code samples and working examples
- Best practices from the training curriculum
- Real-world scenarios and use cases
Notes
- All searches are performed against official Microsoft documentation and Copilot Dev Camp resources
- Response times depend on the complexity of the topic and number of searches needed
- Findings are cited directly from Microsoft Learn and Copilot Developer Camp resources
- Code examples are from official Microsoft quickstarts and Copilot Dev Camp samples
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.

