1,370 published Skills
1370 Skills · 102 repositories
Containers
engineering-patterns
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.
Microsoft
@microsoftOpen source projects and samples from Microsoft
Open source projects and samples from Microsoft
Redmond, WA
microsoft.com
microsoft.com1,370 published Skills
Curated from public sources. This profile has not been claimed.
GitHub sources1370 Skills · 102 repositories
102 sources1370 standalone skills1370 published skills
UI Design
crusty-old-engineer
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?"
UI Design
cranky-old-sam
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?"
Application Security
councilify
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
UX Research
council
Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
UX Research
council-here
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.
Testing
code-review
Review changed code for reuse, quality, and efficiency, then fix any issues found.
Strategy
bet-sizer
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?"
AI Agents
adapt-skill
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.
Developer Tools
ten-lane-highway
Become the Highway Manager: drive many parallel /goal lanes continuously toward a defined outcome, refilling lanes on every wake so none sit idle. Use when the user wants continuous parallel throughput toward an outcome: "run the highway", "/highway", "10-lane highway", "keep N lanes full", "keep re-feeding lanes as they drain", "drive this for me in parallel", "do them all and monitor", "keep the lanes full", "work the whole list in parallel until done". NOT for a one-shot batch that launches once and drains together — use goal-batch. NOT for bounded edits that each end in their own PR — use
Developer Tools
goalify
Compose and lint a /goal stop-condition from the current conversation, catching known termination-failure patterns before showing it to the user. Use when the user wants to turn the current task into a /goal loop, asks to "goalify this", wants a stop condition for autonomous work, says "write a goal condition", "make this a /goal", "turn this into a goal", or asks for help wording a condition for /goal.
Testing
goal-batch
Batch independent work into isolated /goal lanes — one worktree, branch, and tmux session each — get your approval, then verify and merge every lane yourself. Use when work decomposes into pieces that can run at the same time: "run these in parallel", "goal-batch", "launch lanes for these", "work these N tasks simultaneously", "batch these as goals". Nothing launches until you've seen the lane split and said go, and this is NOT fire-and-forget: the orchestrating session re-runs the full suite after every merge and never accepts a lane's own claim that it finished. NOT for bounded edits that ea
Testing
amplifier-config
Explain, inspect, troubleshoot, and safely modify Amplifier CLI configuration — providers, settings scopes, bundles, routing, skills, and source overrides. Use when someone describes desired Amplifier CLI behavior and needs effective-value provenance, a safe change plan, implementation, or outcome-based verification.
Testing
pre-push-review
Pre-PR self-review using the same criteria as the automated review-pr-opened GitHub Action. Catches stale mock patch targets, dead imports with noqa suppressors, fixture env-var leaks, and silent ineffective patches BEFORE they are flagged by CI. Run before pushing any branch to a PR on microsoft/amplifier-resolve. Triggers on: "review before push", "pre-PR check", "self-review before pushing", "catch issues before CI", "is this ready to push".
Testing
pr-review
Local PR review in your session — exhaustive (5 independent review lenses with quality synthesis) or prompt-shot (single-pass five-check framework). No GitHub comment posted. Use when the user wants a local code review of a branch diff, staged changes, or PR before pushing/merging.
AI Agents
agentic-workflows
Route gh-aw workflow create/debug/upgrade requests to the right prompts.
Cloud Platforms
microsoft-docs
查詢官方 Microsoft 文件以尋找跨 Azure、.NET、Agent Framework、Aspire、VS Code、GitHub 等的概念、教學和程式碼範例。預設使用 Microsoft Learn MCP，對於存在於 learn.microsoft.com 以外的內容則使用 Context7 和 Aspire MCP。
Developer Tools
jupyter-notebook
當使用者要求建立、搭建或編輯 Jupyter 筆記本（`.ipynb`）用於實驗、探索或教學時使用；優先使用隨附範本並執行輔助腳本 `new_notebook.py` 來產生一個乾淨的起始筆記本。
Cloud Platforms
microsoft-docs
查詢官方 Microsoft 文件以尋找跨 Azure、.NET、Agent Framework、Aspire、VS Code、GitHub 等的概念、教學與程式範例。預設使用 Microsoft Learn MCP，對於存在於 learn.microsoft.com 以外的內容，則使用 Context7 與 Aspire MCP。
Developer Tools
jupyter-notebook
當使用者要求建立、搭建或編輯用於實驗、探索或教學的 Jupyter 筆記本 (`.ipynb`) 時使用；優先採用內建範本並執行輔助腳本 `new_notebook.py` 以產生一個乾淨的起始筆記本。
Cloud Platforms
microsoft-docs
查詢官方 Microsoft 文件，以尋找有關 Azure、.NET、Agent Framework、Aspire、VS Code、GitHub 等的概念、教學及程式碼範例。預設使用 Microsoft Learn MCP，對於存放在 learn.microsoft.com 以外的內容，則使用 Context7 與 Aspire MCP。
Developer Tools
jupyter-notebook
當使用者要求建立、搭建或編輯 Jupyter 筆記本（`.ipynb`）以進行實驗、探索或教學範例時使用；優先使用隨附的範本，並執行輔助腳本 `new_notebook.py` 來產生一個乾淨的起始筆記本。
Cloud Platforms
microsoft-docs
查询官方 Microsoft 文档，以查找有关 Azure、.NET、Agent Framework、Aspire、VS Code、GitHub 等的概念、教程和代码示例。默认使用 Microsoft Learn MCP，对于存在于 learn.microsoft.com 之外的内容，则使用 Context7 和 Aspire MCP。
Developer Tools
jupyter-notebook
在用户请求为实验、探索或教程创建、搭建或编辑 Jupyter 笔记本（`.ipynb`）时使用；优先使用捆绑的模板并运行辅助脚本 `new_notebook.py` 来生成一个干净的起始笔记本。