ado-project-discovery
Skill5 starsChanged 5 months agoMITView on GitHub
Use when the user asks about Azure DevOps projects, teams, organisation structure, or wants to list what projects or teams exist. "list my ADO projects", "what projects are in my organisation", "show teams in the Platform project", "which team owns the backend workload", "find the project for the mobile app", "how many teams does the Finance project have", "who is in the Cloud Infra team"
In this repository10 other files it gives its agents.
- ado-contextSkill
- ado-pipelinesSkill
- ado-pm-reportingSkill
- ado-pull-requestsSkill
- ado-repositoriesSkill
- ado-searchSkill
- ado-sprints-capacitySkill
- ado-test-plansSkill
- ado-wikiSkill
- ado-work-itemsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
List projects: Call core_list_projects to get the full project list with IDs, names, state (active/deleted), and visibility.
- Distinctive: line 37
Filter if needed: If the user named a specific project, match by name (case-insensitive).
- Distinctive: line 38
If ambiguous, present the full list and ask the user to confirm.
- Very specific: line 40
List teams (if asked): Call core_list_project_teams(projectId) to get team names, team IDs, and descriptions.
- Distinctive: line 43
Surface next steps: After listing, suggest follow-up actions the user can take: browse repos, create work items, check pipelines in the …
- Very specific: line 66
Use the project name and ID returned here as inputs to other skills (ado-work-items, ado-pipelines, ado-repositories, etc.).
- Distinctive: line 68
If the organisation has a large number of projects (>20), ask the user for a keyword to filter before presenting results.
- Very specific: line 75
After listing and selecting a project here, the result can be passed to ado-context to store it as the session-wide active project.
≈ “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
ADO Project Discovery
List and explore Azure DevOps projects and team structure across an organisation.
When to use
- User wants to know which projects exist in their ADO organisation
- User needs to find the right project before creating work items or browsing repos
- User wants to see the teams inside a project
- User is onboarding and needs an overview of the organisation structure
MCP tools used
| Tool | Purpose |
core_list_projects | List all projects in the organisation |
core_list_project_teams | List all teams within a specific project |
Workflow
- List projects. Call
core_list_projectsto get the full project list with IDs, names, state (active/deleted), and visibility. - Filter if needed. If the user named a specific project, match by name (case-insensitive). If ambiguous, present the full list and ask the user to confirm.
- List teams (if asked). Call
core_list_project_teams(projectId)to get team names, team IDs, and descriptions. Present as a flat table. - Surface next steps. After listing, suggest follow-up actions the user can take: browse repos, create work items, check pipelines in the project.
Output Format
Projects
| Project | State | Visibility | ID |
| Platform | Active | Private | abc-123 |
| Mobile App | Active | Private | def-456 |
| Finance Modules | Active | Private | ghi-789 |
Teams in a project
| Team | Description |
| Platform Core | Owns backend services and infra |
| Platform QA | Quality assurance and test automation |
| Platform DevOps | Pipeline and environment management |
Notes
- Use the project name and ID returned here as inputs to other skills
(
ado-work-items,ado-pipelines,ado-repositories, etc.). - If the organisation has a large number of projects (>20), ask the user for a keyword to filter before presenting results.
core_list_projectsreturns projects across all process templates (Agile, Scrum, CMMI).
Active context
This skill also powers the implicit context resolution used by all other skills.
- After listing and selecting a project here, the result can be passed to
ado-contextto store it as the session-wide active project. - Suggest: "To avoid specifying the project every time, say: 'set active project Platform'."
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.