PoshMcp

{what this skill teaches agents}

Add boolean configuration flags to the update-config CLI command using TryParseRequiredBoolean() for argument parsing and GetOrCreateObject() for JSON section navigation, following the three-step flow and nesting conventions established across PRs #85, #86, and #92. WHEN: adding a new --flag to update-config, nesting a config value under a JSON section, or writing unit tests for CLI config flag parsing.

Resolve configuration file paths in CLI commands using the same shared pipeline as the doctor/diagnostics so all commands target the same effective config file. WHEN: adding a new CLI command that reads or writes config, debugging a command that mutates a different config file than doctor reports, or implementing config-aware CLI behavior in a multi-location config environment.

Implement discovery-source attribution tracking for MCP tool enumeration by creating a dedicated tracker interface with first-writer-wins semantics, recording at discovery call sites (not in the doctor/reporter), and wiring both in-process and OOP paths to agree on provenance. WHEN: the doctor or a reporting surface infers tool source heuristically, adding source attribution to a new discovery path, or aligning in-process and OOP discovery provenance.

Implement OAuth 2.1 + Entra ID authentication for an MCP server using a lightweight AS metadata proxy — handling RFC 9728 protected resource metadata, RFC 8414 AS metadata, and a /register endpoint that eliminates client_id prompts for all MCP clients. WHEN: adding OAuth to an MCP server, MCP clients ask users to paste a client_id, authorization redirects go to the wrong endpoint, or debugging Entra DCR limitations.

Publish .NET NuGet packages to GitHub Packages using GitHub PAT authentication — covering gh auth token retrieval, write:packages scope verification, dotnet pack/push workflow, and owner resolution from git remote. WHEN: publishing a NuGet package to GitHub Packages, debugging 401 on dotnet nuget push, adding a GitHub Packages NuGet source, or resolving write:packages scope errors.

Extend the PoshMcp OOP discover wire format (RemoteToolSchema + parallel payload) safely without breaking backward compatibility with older OOP hosts or C# servers. WHEN: adding new fields to OOP discover responses, threading per-command metadata across the JSON-RPC boundary, or adding new top-level optional payload objects to the discover response.

Avoid redundant expensive computations — especially IsolatedPowerShellRunspace setup — by passing pre-computed results as optional nullable parameters to private delegation methods, with null-coalescing fallback for callers that don't pre-compute. WHEN: a public method computes expensive data then calls a private helper that recomputes the same data, or when runspace/session initialization is executing twice.

Execute the full release workflow: bump version, update changelog, run dotnet format and dotnet test quality gates, prepare release notes, commit and push to main, wait for CI green, then create and push the annotated tag. WHEN: shipping a new release, bumping version in the repo, creating a git tag, or running pre-release quality gates.

Recover coordinator working context at startup using the session-recall CLI — reconstructing in-flight files, last checkpoint, and session summary before spawning agents. Falls back to direct SQL when CLI is unavailable. WHEN: coordinator startup after a crash or compaction, now.md shows active work, suspected session interruption, or searching for prior work on a topic.

Handle PowerShell commands whose parameter types cannot be JSON-serialized by applying three-tier graceful fallback: skip optional parameters, skip unviable parameter sets, or skip entire commands — preserving server startup. WHEN: adding MCP tool schema generation, encountering PSObject/ScriptBlock/Stream parameters, debugging server startup failures due to unserializable types, or extending IsUnserializableType checks.

Manage sequential PR merges from git worktrees — covering rebase timing, dotnet restore on cold checkouts, gh pr merge exit code interpretation, and force-push configuration. WHEN: merging PRs from git worktrees, debugging NETSDK1004 on worktree test runs, interpreting non-zero exit from gh pr merge, or resolving worktree branch push failures.

{what this skill teaches agents}

Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. Use this skill when the user asks for a diagram of their Azure resources or help in understanding how the resources relate to each other.

Generate a complete MCP server project in C# with tools, prompts, and proper configuration

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Generate a custom checklist for the current feature based on user requirements.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Create or update the feature specification from a natural language feature description.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Design Azure infrastructure using natural language, or analyze existing Azure resources to auto-generate architecture diagrams, refine them through conversation, and deploy with Bicep. When to use this skill: - "Create X on Azure", "Set up a RAG architecture" (new design) - "Analyze my current Azure infrastructure", "Draw a diagram for rg-xxx" (existing analysis) - "Foundry is slow", "I want to reduce costs", "Strengthen security" (natural language modification) - Azure resource deployment, Bicep template generation, IaC code generation - Microsoft Foundry, AI Search, OpenAI, Fabric, ADLS Gen2, Databricks, and all Azure services