← all publishers

Microsoft

@microsoft source repo

Report this profile Claim this profile

• 1.7k skills
• 0 followers
• 2.7k repo stars
• 196 verified
• last week last updated

1. ▌
   Bet Sizer · microsoft

   Delivery-risk reviewer that sizes a plan's investment against the team's real confidence it will land. Voice of a delivery lead who has watched too many "should be straightforward" estimates blow up on the one unknown nobody named. Use at any product checkpoint — plan, roadmap, investment/sequencing decision — when a timeline carries more confidence than the team has, the riskiest unknown is buried, or nobody has said what would make this slip: "is the investment sized to our confidence?"
   2.7k repo stars
2. ▌
   Outcomist · microsoft

   Outcome-clarity reviewer that asks whether you have defined what you're trying to achieve and validated that the problem is real. Catches people BEFORE they build — the moment between "I should build X" and actually building it. Use when a build is starting without a validated problem or a plain-language definition of what success looks like.
   2.7k repo stars
3. ▌
   Personafy · microsoft

   Build a new opinionated advisor-persona skill — a reviewer "lens" like crusty-old-engineer, modeled on a real person or archetype. Mines the subject's authentic voice, defines its one load-bearing question, drafts it to the family template, and proves it steers a live session before publishing to a skills bundle. Use when creating or authoring a persona/advisor skill, adding a sibling to the crusty-old-engineer family, or turning a person's real direction style into a reusable reviewer skill. Also triggers on "personafy" / "personify".
   2.7k repo stars
4. ▌
   Councilify · microsoft bundle

   Build a NEW complete "council" for a domain — a panel of orthogonal review lenses that fan out cold, debate to consensus, and return a synthesized verdict with recorded dissent, exactly like /council and /design-council. Identifies the distinct lenses a domain needs (one load-bearing question each, mined from real archetypes — not invented), reuses existing lenses, and builds only the genuinely-missing ones (persona SKILLs via personafy, or agents when the role is an active builder). Use when creating a council, standing up a review panel for a domain (product, security, performance, data), or when someone says "councilify", "make a council", "build a <domain> council".
   2.7k repo stars
5. ▌
   Adapt Skill · microsoft

   Adapt a skill written for another AI assistant (Claude Code, Cursor, etc.) into a proper Amplifier SKILL.md. Use when the user wants to adapt a skill, port a skill, convert a skill to amplifier, translate a skill, or has a SKILL.md from another platform they want to bring into Amplifier.
   2.7k repo stars
6. ▌
   Mass Change · microsoft

   Research and plan a large-scale change, then execute it in parallel across isolated agents that each open a PR.
   2.7k repo stars
7. ▌
   Council Here · microsoft

   Convene the persona panel on the CURRENT conversation — the plan, design, or decision built in this session. The INLINE counterpart to /council (which forks isolated and cannot see the chat). Use when you want the council to critique what we're working on right now.
   2.7k repo stars
8. ▌
   Image Vision · microsoft bundle

   Analyze images using LLM vision APIs (Anthropic Claude, OpenAI GPT-4, Google Gemini, Azure OpenAI). Use when a task requires understanding image content, describing visual elements, answering questions about images, comparing images, or extracting text from images (OCR). Provides ready-to-use scripts.
   2.7k repo stars
9. ▌
   Intent Keeper · microsoft

   Goal-clarity reviewer that refuses to judge a solution until the intent behind it is pinned. A patient interrogator of "why are we doing this?", hunting goal drift — the deliverable quietly replacing the goal. Use at any checkpoint — brainstorm, design, plan, implement, debug, review — when the build has wandered from the brief or nobody can say in one sentence what success looks like: "is this still the real goal?"
   2.7k repo stars
10. ▌
    Session Debug · microsoft

    Diagnose issues in the current Amplifier session — misconfigured tools, failing operations, unexpected behavior. Use when something isn't working right.
    2.7k repo stars
11. ▌
    Skills Assist · microsoft bundle

    Authoritative consultant for all skills-related questions. Use when creating or modifying skills, understanding the Agent Skills spec, troubleshooting skill loading or invocation issues, leveraging enhanced format features (context fork, model_role, user-invocable), writing cross-harness portable skills, ensuring Claude Code Skills 2.0 compatibility, or deciding between skills vs agents.
    2.7k repo stars
12. ▌
    User Advocate · microsoft

    User-need reviewer that speaks for the person who isn't in the room — the one who will actually live with what gets built. Hunts the gap between "we can build this" and "they actually want this," in the patient, impatient voice of the absent user. Use at any checkpoint — brainstorm, design, plan, implement, debug, review — when a feature is being built because it's buildable rather than wanted, the recovery path is missing, or nobody can name the person this serves: "do they actually want this, and can they live with it?"
    2.7k repo stars
13. ▌
    Cranky Old Sam · microsoft

    Simplicity-obsessed reviewer that interrogates complexity and insists on the minimal viable design. Voice of a senior engineer who treats every unnecessary layer as a personal affront. Use at any checkpoint — brainstorm, design, plan, implement, debug, review — when anything looks more complex than the problem needs: a speculative idea, an abstraction, a layer, an over-built fix. The worry: "do we actually need this, or can it be deleted?"
    2.7k repo stars
14. ▌
    Second Opinion · microsoft bundle

    Independent review of current work or a past session. USE WHEN a user wants a second opinion. DO NOT USE WHEN ordinary code review is wanted — use code-review.
    2.7k repo stars
15. ▌
    Tester Breaker · microsoft

    Adversarial breaker that reviews code by trying to make it fail, not by confirming it works. Hunts the unhappy paths — malformed input, the empty string, the reversed range, the race condition — as a gleeful adversary who assumes everything is broken until a concrete attempt to break it comes up empty. Use at any checkpoint — brainstorm, design, plan, implement, debug, review — when the happy path is celebrated while the edges sit unexamined, "looks fine" stands in for "I tried to break it and couldn't," or nobody has named the input that makes this fall over: "how does this fail, and where are the edges?"
    2.7k repo stars
16. ▌
    Product Council · microsoft

    Convene the Product Development Council — six orthogonal product-delivery lenses anchored by a mandatory problem-validation gate. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
    2.7k repo stars
17. ▌
    Positioning Critic · microsoft

    Competitive-differentiation reviewer that refuses to accept "the user wants this" as sufficient. Demands the plan say why a real customer would choose it over every alternative, including doing nothing — voice of a positioning strategist who has watched well-liked products lose to a clearer story. Use at any product checkpoint — plan, roadmap, go-to-market framing — when nobody can say why users would switch or pay, the competitive landscape is unaddressed, or "no one else does this" is asserted without checking: "why us, why this, why now?"
    2.7k repo stars
18. ▌
    Restless Old Brian · microsoft

    Momentum-driven engineering reviewer holding one uncompromising gate: is it REAL, proven end-to-end as a user would? Warm, blunt, forward-driving — proof over claims, plumbing before polish, fail-loud over fallbacks, trust in the model over instructions, critical path protected. Use at any checkpoint — brainstorm, design, plan, implement, debug, ship — when testing whether work is provable, built in the right order, or actually done rather than band-aided: "are we fooling ourselves about what's real?"
    2.7k repo stars
19. ▌
    Crusty Old Engineer · microsoft

    Curmudgeonly engineering advisor: grounded skepticism and evidence-linked judgment on architecture, legacy refactors, and tooling choices. Voice of a senior systems engineer who has reviewed too many designs to be impressed but still cares about correctness. Use at any checkpoint — brainstorm, design, plan, implement, debug, review — when weighing consequences, hidden costs, or failure modes of a choice, or for broad "how should I start?" questions: "what will this cost us later?"
    2.7k repo stars
20. ▌
    Engineering Patterns · microsoft bundle

    Use for tool/service work: CLI packaging, installers, config/state, HTTP, auth/TLS, file IPC, plugins, instance storage, containers, React MFE, Graph, self-update, tool leverage.
    2.7k repo stars
21. ▌
    Outcome Cartographer · microsoft

    Outcome-validity reviewer that refuses to count shipped work as progress until it maps to a measurable change in behavior. Hunts the gap between "we shipped it" and "we moved the number" — the output mistaken for an outcome. Use at any product checkpoint — plan, roadmap, PRD, ship review — when deliverables carry no metric, "done" is confused with "worked," or nobody can say how success will be measured: "what measurable outcome defines success, and how will we know we moved it?"
    2.7k repo stars
22. ▌
    Product Council Here · microsoft

    Convene the Product Development Council on the CURRENT conversation — the plan, roadmap, or scope decision built in this session. The INLINE counterpart to /product-council (which forks isolated and cannot see the chat). Use when you want the council to critique what we're working on right now.
    2.7k repo stars
23. ▌
    Verification Discipline · microsoft

    Use when verifying that completed work actually works. Auto-surface during /verify mode, post-implementation review, or before claiming a task is done. Teaches testing outcomes vs implementation, the unit/integration/smoke gradient, and what "done" actually means.
    2.7k repo stars
24. ▌
    Python Standards · microsoft

    Python coding standards for Amplifier including type hints, async patterns, error handling, and formatting. Use when writing Python code for Amplifier modules.
    2.7k repo stars
25. ▌
    Module Development · microsoft

    Guide for creating new Amplifier modules including protocol implementation, entry points, mount functions, and testing patterns. Use when creating new modules or understanding module architecture.
    2.7k repo stars
26. ▌
    Amplifier Philosophy · microsoft

    Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions.
    2.7k repo stars
27. ▌
    CI Readiness Check · microsoft bundle

    Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.
    2.7k repo stars
28. ▌
    Pipeline Test Triage · microsoft bundle

    Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.
    2.7k repo stars
29. ▌
    Using Skills · microsoft

    Describes how to use abilities. Read before any conversation.
    2.7k repo stars
30. ▌
    Brainstorming · microsoft

    IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
    2.7k repo stars
31. ▌
    Starting Nori · microsoft

    ALWAYS load this skill if it is not already loaded, for ANY user query or conversation - establishes the Nori workflow, protected-branch check, operating mode, tone, and coding guidelines before any other work
    2.7k repo stars
32. ▌
    Writing Plans · microsoft

    Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
    2.7k repo stars
33. ▌
    Ff Oce Kusto · microsoft bundle

    Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.
    2.7k repo stars
34. ▌
    Building UI UX · microsoft

    Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
    2.7k repo stars
35. ▌
    Webapp Testing · microsoft

    Use this skill to build features or debug anything that uses a webapp frontend.
    2.7k repo stars
36. ▌
    Updating Noridocs · microsoft

    Use this when you have finished making code changes and you are ready to update the documentation based on those changes.
    2.7k repo stars
37. ▌
    Using Screenshots · microsoft bundle

    Use this to capture screen context.
    2.7k repo stars
38. ▌
    Ff Oce Dashboard · microsoft

    Generate the OCE shift status dashboard. Triggers on: 'generate shift dashboard', 'show dashboard', 'shift status', 'status dashboard', 'what's going on', or any request for a NON-SPECIFIC overview of current OCE status (incidents, pipelines, errors).
    2.7k repo stars
39. ▌
    Handle Large Tasks · microsoft

    Use this skill to split large plans into smaller chunks. This skill manages your context window for large tasks. Use it when a task will take a long time and cause context issues.
    2.7k repo stars
40. ▌
    Root Cause Tracing · microsoft

    Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
    2.7k repo stars
41. ▌
    Using Git Worktrees · microsoft

    Use this whenever you need to create an isolated workspace.
    2.7k repo stars
42. ▌
    Trigger Pipelines For Copilot Pr · microsoft

    Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.
    2.7k repo stars
43. ▌
    Systematic Debugging · microsoft

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
    2.7k repo stars
44. ▌
    Receiving Code Review · microsoft

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
    2.7k repo stars
45. ▌
    Testing Anti Patterns · microsoft

    Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
    2.7k repo stars
46. ▌
    Test Driven Development · microsoft

    Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
    2.7k repo stars
47. ▌
    Finishing A Development Branch · microsoft

    Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
    2.7k repo stars
48. ▌
    Creating Debug Tests And Iterating · microsoft

    Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
    2.7k repo stars
49. ▌
    Review · microsoft bundle

    Use when asked to review code, review a branch, or do a code review. Spawns Breaker (correctness) and API Analyst (compatibility/conventions) sub-agents while the orchestrator reviews architecture, tests, performance, and security.
    2.7k repo stars
50. ▌
    Fluid Pr · microsoft

    Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".
    2.7k repo stars
51. ▌
    API Changes · microsoft

    Use when customer-facing API changes were made — i.e., API report .md files differ from the branch's resolved comparison base. Guides through release tag assignment, API Council review requirements, breaking change classification, deprecation process, and changeset guidance. Triggered automatically by ci-readiness-check when api-report diffs are detected.
    2.7k repo stars
52. ▌
    Policy Check · microsoft

    This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.
    2.7k repo stars
53. ▌
    Fluid Release · microsoft bundle

    Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the schedule and repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.
    2.7k repo stars
54. ▌
    Fluid Pr Guide · microsoft

    Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body in Fluid Framework — provides title style, body template, and section guidance.
    2.7k repo stars
55. ▌
    Comparison Base · microsoft

    Internal reusable workflow for resolving the correct Git comparison base for branch reviews and change analysis. Finds the PR target or canonical Fluid Framework upstream, selects the newest shared target-history commit, and detects substantial divergence.
    2.7k repo stars
56. ▌
    Review Pr Local · microsoft bundle

    The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.
    2.7k repo stars
57. ▌
    Assessment · microsoft

    Run application assessment for a single repository
    2.7k repo stars
58. ▌
    Guidelines · microsoft

    Collection of framework-to-framework migration rules and transformation patterns (e.g., Struts→Spring MVC, JSP→Thymeleaf, EJB→Spring Boot). Triggers: "check migration guidelines", "look up transformation rules", "find Struts-to-Spring patterns", "apply migration conventions", "conversion rules for X→Y". Also consumed automatically by breaking-down-tasks and implementing-code during migration workflows. NOT for: direct execution — other skills scan this directory.
    2.7k repo stars
59. ▌
    List Plans · microsoft

    Discovers valid migration plans in the workspace and returns the selected plan path. A valid plan is a subdirectory of .github/modernize/ that contains plan.md AND tasks.json (tasks.json may be in the plan folder or in a .metadata subfolder). Handles 0, 1, or multiple plans and prompts the user when a choice is needed. Triggers: "list plans", "find plans", "select plan", "list-and-select-plan", "discover plans".
    2.7k repo stars
60. ▌
    Appmod Hooks · microsoft bundle

    Lifecycle hooks for the modernize-rearchitecture coordinator. Defines hook points, registered actions, and execution rules.
    2.7k repo stars
61. ▌
    Team Request · microsoft

    How team members request infrastructure connection info and handle secrets in team mode
    2.7k repo stars
62. ▌
    Project Recon · microsoft bundle

    Zero-dependency shell recon for any code repository — detect languages, count LOC, and report project scale. Pure POSIX find/wc or PowerShell, no Python or third-party tools required. Triggers: "how big is this project", "what languages", "project sizing", "repo recon", "LOC count", "scope check".
    2.7k repo stars
63. ▌
    Quality Gates · microsoft bundle

    Runs quality gate validation at each workflow stage. Supports 4 gate types: spec-quality, spec-to-plan, plan-to-tasks, completeness. Produces gate pass/fail reports with actionable feedback. Triggers: "run quality gate", "validate spec quality", "spec quality", "plan coverage", "check plan coverage", "validate plan to tasks", "check task traceability", "verify task completeness", "run completeness review", "review implementation", "check plan traceability", "check coverage", "completeness quality gate", "final sign-off", "feature parity sign-off", "completeness gate", "feature parity", "sign-off report", "verify all requirements". Requires `type` parameter to select the gate. NOT for: code review, implementation (use implementing-code), spec writing.
    2.7k repo stars
64. ▌
    Team Charters · microsoft bundle

    Provides role charters (mission, ownership, core principles, quality bar) for a multi-agent coding team. Each charter defines the role's mission, ownership scope, core principle (boundary constraints), and quality bar. Most roles also include communication rules. Consumed by the coordinator during task decomposition to assign work to the correct role. Triggers: "look up role charter", "what does the architect own", "check role boundaries", "find team roles", "which role handles X", "list agent charters", "role responsibilities". NOT for: task decomposition (use breaking-down-tasks), implementation (use implementing-code), architecture analysis (use analyzing-architecture).
    2.7k repo stars
65. ▌
    Dag Generation · microsoft bundle

    Generate task DAGs for modernization projects — select fragments from task catalog, produce initial DAG (Stage 1), and execute/validate DAG from plan artifacts (Stage 2).
    2.7k repo stars
66. ▌
    Dependency Map · microsoft

    Generate dependency map diagram from project build files
    2.7k repo stars
67. ▌
    Cve Remediation · microsoft

    Scan dependency manifests against known CVEs and remediate by upgrading vulnerable dependencies to patched versions, then rebuild and re-scan to confirm. Self-contained scan→fix→verify loop for any project with a dependency manifest. Use when: a cve-remediation task is dispatched; dependency set changed (version bump, new framework); assessment flagged vulnerable or EOL dependencies; or user asked to "fix CVEs", "patch vulnerabilities", or "dependency security". Triggers: "cve", "remediate cve", "fix cves", "patch vulnerable dependencies", "vulnerability scanning", "dependency security", "vulnerable dependencies", "security advisories", "npm audit", "pnpm audit", "maven audit", "gradle audit", "dependency scan", "vulnerability remediation". NOT for: security audit of auth/input/secrets/OWASP code paths (use security-review).
    2.7k repo stars
68. ▌
    Data Architecture · microsoft

    Generate data architecture and persistence layer documentation with data model diagram
    2.7k repo stars
69. ▌
    Feature Inventory · microsoft bundle

    Catalogs existing features from a codebase (API endpoints, user flows, UI screens, observable behaviors) and generates structured feature specs with REQ-XXX IDs, user scenarios, and success criteria. Triggers: "inventory features", "catalog existing functionality", "list what the app does", "extract requirements from code", "generate feature specs from research", "write a spec", "create feature specification", "define requirements". NOT for: implementation planning (use creating-implementation-plan), implementation (use implementing-code).
    2.7k repo stars
70. ▌
    Implementing Code · microsoft bundle

    Executes a batch of implementation tasks with TDD workflow, source-anchored rewrite for behavioral fidelity, guideline-based code transformation, and full requirement tracing. Returns a structured batch report. Triggers: "implement tasks", "execute the batch", "write code for these tasks", "implement with source anchoring", "run the implementation". NOT for: task generation (use breaking-down-tasks), implementation planning (use creating-implementation-plan).
    2.7k repo stars
71. ▌
    Sharing Learnings · microsoft bundle

    How to record project learnings so that later-phase workers and future agent runs can consume them.
    2.7k repo stars
72. ▌
    Business Workflows · microsoft

    Generate core business workflow documentation with sequence diagram
    2.7k repo stars
73. ▌
    Runtime Validation · microsoft bundle

    Runtime validation for migrated applications — covers testing strategy (planning phase) and test execution (validation phase): startup verification, integration testing, and end-to-end flow validation. Use when: (1) designing test strategy during planning phase (teamlead reads Part 1) (2) verifying a migrated app starts and runs correctly (3) writing or executing integration / E2E tests (tester reads Part 2) (4) choosing test tooling and environment setup (5) producing structured test evidence and verdicts Triggers: "runtime validation", "testing strategy", "test strategy", "test design", "verify the app", "integration test", "e2e test", "end-to-end test", "smoke test", "startup check", "write tests", "run tests", "test the migration", "playwright", "testcontainers", "test strategy", "test plan", "runtime gate", "testing phase", "validation phase"
    2.7k repo stars
74. ▌
    Architecture Diagram · microsoft

    Generate architecture diagram with component relationship details from project analysis
    2.7k repo stars
75. ▌
    Clarifying Scenarios · microsoft bundle

    Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy, data migration strategy for backend). Produces a deterministic clarity score, asks the user for missing required fields via a structured form, and writes a canonical `clarification.md` artifact consumed by all downstream agents. Triggers: "clarification gate", "scenario clarification", "elicit missing context", "evaluate prompt completeness", "ask user for screenshots / target library / design system". NOT for: feature specification (use feature-inventory), planning (use creating-implementation-plan), implementation (use implementing-code), or resolving spec-time `[NEEDS CLARIFICATION]` markers (those remain owned by feature-inventory).
    2.7k repo stars
76. ▌
    Create Test Baseline · microsoft bundle

    Create a test baseline for the project to be modernized. The baseline will be used for later verification of modernization tasks.
    2.7k repo stars
77. ▌
    Verify Test Baseline · microsoft

    Generate and run post-migration tests from the frozen baseline specification.
    2.7k repo stars
78. ▌
    API Service Contracts · microsoft

    Generate API and service communication contracts with sequence diagram
    2.7k repo stars
79. ▌
    Project Decomposition · microsoft bundle

    Single-source codebase decomposition: scans a project scope, builds the module dependency graph, counts LOC by language, computes skip patterns (caller-supplied ∪ .gitignore ∪ baseline), and (when grouping is required) produces topology groupings with L3 quality validation. One skill owns ProjectProfile JSON, grouping protocols, and quality gates. Triggers: "before generating a workflow plan", "before topology grouping", "project sizing", "LOC counting", "module grouping", "topology splitting rules", "topology consumer rules", "scale-aware splitting", "large codebase decomposition", "module dependency graph", "scope measurement". NOT for: semantic architecture analysis, implementation planning, running tests/builds/linters.
    2.7k repo stars
80. ▌
    Analyzing Architecture · microsoft bundle

    Architect analysis for rewrite/migration: produces structured architecture artifacts plus global prose research views (project-structure, tech-stack, data-model) for planning, implementation, feature-inventory, and gates. This is the single architect task. Triggers: "analyze architecture", "analyze existing application", "analyze the codebase", "codebase architecture analysis", "analyze for migration", "prepare migration analysis", "produce migration artifacts", "analyze before rewrite". NOT for: greenfield projects, pure syntax/version migrations (Python2→3, Java 8→17 — no paradigm shift), runtime validation (use runtime-validation), infrastructure/deployment analysis (use analyzing-operations), feature inventory/spec writing (use feature-inventory).
    2.7k repo stars
81. ▌
    Configuration Inventory · microsoft

    Generate comprehensive configuration and externalized settings inventory
    2.7k repo stars
82. ▌
    Setting Up Constitution · microsoft bundle

    Creates or updates the project constitution that defines migration principles, constraints, and conventions. Triggers: "set up constitution", "define migration principles", "create project rules", "establish conventions", "establish migration constitution". NOT for: implementation, implementation planning, task generation.
    2.7k repo stars
83. ▌
    Create Modernization Plan · microsoft bundle

    Create a modernization plan to migrate the project to Azure
    2.7k repo stars
84. ▌
    Assessment Report Converter · microsoft bundle

    Convert an arbitrary CSV report (e.g. a Black Duck export or a custom migration-issue inventory) into a schema-valid assessment `report.json` the modernization pipeline can consume — so it appears in the assessment UI and migration solutions resolve automatically. This skill is LLM-driven: you read and interpret the CSV yourself and author `report.json` by hand against the schema. A small helper script only does deterministic lookups (migration solutions, the ruleId for a solution) and validates the finished report. There is NO "convert everything" script and NO assumed column layout. Triggers: "convert csv to assessment report", "import csv report", "turn this spreadsheet into a report.json", "Black Duck csv to report", "build report.json from csv", "migrate a third-party assessment export". NOT for: AppCAT-style analysis from source (use `assessment`), generating a modernization plan (use `create-modernization-plan`), or editing a report.json the pipeline already produced.
    2.7k repo stars
85. ▌
    Struts To Spring · microsoft bundle

    Struts 2 to Spring Boot 3.x Migration Guideline
    2.7k repo stars
86. ▌
    Creating Implementation Plan · microsoft bundle

    Creates an implementation plan AND task breakdown from a feature spec by consuming design artifacts. Produces plan.md with implementation steps, inline task list with full REQ traceability, and a Requirement Mapping table. This is the single skill for planning + decomposition. Triggers: "create implementation plan", "plan for implementation", "assemble implementation plan", "generate plan from spec", "break down tasks", "generate tasks from plan", "create implementation tasks", "decompose the plan into work items". NOT for: architecture analysis (use analyzing-architecture), implementation (use implementing-code), coordinator task decomposition.
    2.7k repo stars
87. ▌
    Building Java Knowledge Graph · microsoft bundle

    Analyzes JVM projects (Java/Kotlin/Scala/Groovy) and generates knowledge graphs with tree-sitter parsing. Requires Python 3 on the host and a JVM project with Maven/Gradle/Ant/Ivy build files. Skips gracefully if either prerequisite is missing. Triggers when asked to "build knowledge graph", "analyze project structure", "parse Java codebase", or "generate dependency graph".
    2.7k repo stars
88. ▌
    Modernization Integration Tests · microsoft bundle

    Run multi-layer integration tests for modernized Java applications. Supports 4 layers - Layer 1 (TestContainers), Layer 2 (Smoke Tests), Layer 3 (Azure Integration), Layer 4 (Behavioral Comparison). Java projects only - skip if source code is not Java. Triggers: "generate integration tests", "add integration tests", "create Layer 1 tests", "create Layer 2 tests" NOT for: unit tests, performance tests, load tests.
    2.7k repo stars
89. ▌
    Spring Boot Scaffolding · microsoft

    Reference guide for creating a new Spring Boot project during rewrite migration.
    2.7k repo stars
90. ▌
    Microsoft AI Platform Advisor · microsoft bundle

    Use this skill when the user needs to choose the right Microsoft AI platform for a project, is comparing Microsoft 365 Copilot, Agent Builder, Copilot Studio, Microsoft Foundry, Foundry Agent Service, Windows AI Foundry, or Agent 365, needs to gather requirements for an AI or agent build, needs a solution architecture recommendation, needs to estimate effort as technical complexity and risk, or asks any variant of "which platform should I use", "how do I choose", "help me scope this AI project", or "what's the right tool for this AI use case".
    2.7k repo stars
91. ▌
    Wikipedia Human Style Writing · microsoft bundle

    Use this skill whenever the user asks to write, rewrite, humanise, de-AI, or polish prose so it doesn't read as AI-generated — or to review a draft for signs of AI writing. Apply it before returning any substantial prose the user will publish.
    2.7k repo stars
92. ▌
    Competitive Battlecard Builder · microsoft bundle

    Build an interactive sales battlecard comparing your product or company against one or more named competitors: their likely pitch, where you win, where you're genuinely vulnerable, and objection-handling scripts. Use this skill whenever someone asks for a battlecard, competitive positioning, "how do we beat [competitor]", objection handling against a named competitor, or a sales enablement comparison asset. Also use when someone wants to add a competitor to an existing battlecard, update it with new intel, or rescope/filter an existing one down to specific competitors or categories.
    2.7k repo stars
93. ▌
    Copilot Studio Topic Blueprint · microsoft bundle

    Use this skill whenever the user describes a Copilot Studio agent in a sentence or two and wants a build-ready blueprint, or asks how to design, scope, or structure an agent (its type, topics, tools, knowledge, or welcome experience). Trigger on requests like "design a Copilot Studio agent that…", "turn this use case into an agent", "how should I structure this agent", or a pasted one-line use case. Do NOT trigger for testing an existing agent (that is the test-planner skill) or for generic Power Platform flows unrelated to an agent.
    2.7k repo stars
94. ▌
    Exam Prep Learning Plan Builder · microsoft bundle

    Build a personalized, day-by-day study plan for an upcoming exam, certification, or test. Use this skill whenever someone mentions studying for an exam, prepping for a certification, needs a study schedule, is trying to pass a test by a certain date, or asks for help organizing exam prep, even if they don't use the word "plan" explicitly (e.g. "I have my PMP in 6 weeks and don't know where to start", "help me study for the bar", "I need to prep for the AZ-900"). Also use when someone wants to revise or adjust an existing study plan because their timeline changed, they fell behind, or their confidence in a topic shifted.
    2.7k repo stars
95. ▌
    Presentation Talk Track Builder · microsoft bundle

    Writes natural, first-person spoken presenter scripts (talk tracks) for the slides in a PowerPoint deck, from slide images, or from pasted slide text. Treats existing speaker notes as AUTHORITATIVE when they contradict slide text. Produces one spoken script per slide with delivery cues, calibrated to a target duration and speaking pace, plus a timing table. Use when the user says "write a script for these slides", "I'm presenting slides X-Y, what should I say", "create a presenter script", "turn my speaker notes into a talk track", or "make a 6-minute script for these slides". Do NOT use to create or edit the visible content of slides, to summarize a recorded meeting or transcript, or for general document writing.
    2.7k repo stars
96. ▌
    Conference Session Abstract Pack · microsoft bundle

    Use this skill when the user asks to create a conference session proposal, talk abstract, CFP submission, session title, description, learning objectives, takeaways, or speaker bio.
    2.7k repo stars
97. ▌
    Enterprise Agent Design Authority · microsoft bundle

    Use this skill whenever the user asks to review, assess, validate, improve, govern, or prepare a Microsoft Copilot Studio agent, multi-agent solution, or enterprise AI architecture before implementation. Apply an enterprise architecture assessment before proposing implementation or design changes.
    2.7k repo stars
98. ▌
    Global Greenwashing Claim Auditor · microsoft bundle

    Use this skill whenever the user asks to audit, scan, review, classify, or de-risk environmental, sustainability, climate, circularity, recycling, emissions, or green marketing claims in pasted conversational content, CSV files, XLSX workbooks, DOCX documents, PPTX presentations, or website URLs. Report universal vocabulary risks separately from Canadian (CA), European Union (EU), and United Kingdom (UK) legal and guidance findings.
    2.7k repo stars
99. ▌
    Power Automate Desktop Assessment · microsoft bundle

    Assess Power Automate Desktop and hybrid cloud/desktop automation projects for maintainability, reliability, security, performance, troubleshooting readiness, scaling, and governance using current Microsoft guidance and evidence-based review practices.
    2.7k repo stars
100. ▌
     Copilot Studio Knowledge Readiness · microsoft bundle

     Use when a Copilot Studio maker provides uploaded files, exported text, or a document set and wants to assess whether that corpus is ready for knowledge grounding. Use this before scoring chunkability, freshness signals, conflicts, or whether content belongs in knowledge versus an action or workflow. Do not use for live SharePoint or Dataverse inspection, general agent design, publishing checklists, analytics troubleshooting, or unrelated Power Platform work.
     2.7k repo stars