ancplua-skills

Write Microsoft Agent Framework (.NET) code against the cloned, SHA-pinned source — never from memory or from Microsoft Learn, which lag the source by weeks and keep pre-GA signatures alive long after they were renamed. USE FOR: writing or reviewing any code that touches Microsoft.Agents.AI / Microsoft.Agents.AI.Abstractions (AIAgent, ChatClientAgent, AgentSession, AgentResponse, RunAsync/RunStreamingAsync) or Microsoft.Extensions.AI (IChatClient, ChatMessage, ChatRole, ChatOptions, AITool); a compile error or "method not found" on a MAF type; porting a doc/blog sample that uses AgentThread / AgentRunResponse / CompleteAsync / GetNewThread; deciding whether to wrap an IChatClient in an agent vs hand-rolling the tool loop. ESPECIALLY use it the moment you are about to emit a MAF type or method name from memory — that is exactly when the stale-rename traps bite. DO NOT USE FOR: Microsoft.Extensions.AI internals unrelated to agents; non-.NET MAF (Python); conceptual "why" questions where Learn is fine (use micro

Authoritative reference for the Model Context Protocol C#/.NET SDK 1.4.1. Use for MCP servers, clients, tools, prompts, resources, transports, sessions, tasks, sampling, elicitation, roots, identity, auth, filters, completions, logging, pagination, HTTP context, McpServer, McpClient, and ModelContextProtocol.* APIs. Always load the relevant reference file before answering.

Enable, wire up, and operate automated browser-extension publishing to all three stores — Microsoft Edge Add-ons (Partner Center Publish API, ApiKey auth), Chrome Web Store (API v2, Google OAuth refresh token), and Firefox Add-ons / AMO (API v5, HS256 JWT). Use whenever the task touches publishing or updating a browser extension on any store, a publish:edge / publish:chrome / publish:firefox script, the env vars EDGE_PRODUCT_ID / EDGE_API_KEY / EDGE_CLIENT_ID / CWS_CLIENT_ID / CWS_CLIENT_SECRET / CWS_REFRESH_TOKEN / CWS_PUBLISHER_ID / CWS_ITEM_ID / AMO_JWT_ISSUER / AMO_JWT_SECRET, enabling a store publish API, a failing upload, "submission in progress" / "pending review" errors, or automating extension releases — and ESPECIALLY when you are tempted to conclude publishing is blocked because API credentials are missing. Missing credentials are a minutes-long console fix, never a blocker.

Use when the user wants help writing, refining, debugging, or evaluating a prompt, system prompt, custom instruction, agent prompt, or skill description. Triggers on phrases like "improve this prompt", "why isn't Claude doing X", "write a system prompt for...", "review my instructions", "this prompt isn't working", "the model keeps doing Y", "how should I phrase this", or any request to design, fix, or analyze AI prompts. Also triggers when the user is iterating on Claude Code skills, agent instructions, CLAUDE.md / AGENTS.md files, description fields for triggering accuracy, few-shot example design, or debugging unexpected model output. Use this even when the user hasn't named prompt engineering explicitly — if they're discussing a prompt's behavior or how to phrase something for a model, this applies. Also use for Claude Fable 5 / Mythos 5 prompting — migrating prompts from older models, effort tuning, agentic behavior issues, or unexpected refusals.

Weave Microsoft-Learn-grounded research into ANY substantive help for this user, whose work is overwhelmingly Microsoft-centric (qyl on .NET / Foundry / Microsoft Agent Framework; the microsoft-ai-hackathon tracks Otto, Agent Battle Arena, Inventory Reorder Copilot). Reach for this at the START of essentially any research, design, debugging, "how do I", "is this current / latest", API-shape, SDK-error, or build task — proactively consult the Microsoft Learn MCP and the microsoft-docs skills and the local ground-truth checkouts BEFORE answering from memory, even when the user never types "Microsoft", "Azure", ".NET", or "docs". This is a routing / insurance skill that exists specifically so Microsoft grounding stops getting skipped ~half the time. Stand down only when the task is explicitly about a non-Microsoft stack (AWS, GCP, OpenAI, etc.) or is a trivial mechanical edit with no knowledge question. Pairs with the microsoft-learn-grounding skill.

Operate the Microsoft Learn MCP — the free, no-auth dogfood API behind Ask Learn and Copilot for Azure — at expert level, and verify how fresh any Microsoft Learn page actually is. Use whenever grounding an answer in Microsoft / Azure / .NET / M365 / Foundry / Agent Framework / Copilot Studio docs, deciding whether a Learn page is current, looking up a page's "Last updated" date / ms.date / source commit, capping token spend on doc searches, or debugging why the Learn MCP returned nothing useful — even when the user never says "Microsoft Learn" or "MCP". Covers the three tools (microsoft_docs_search, microsoft_docs_fetch, microsoft_code_sample_search), the maxTokenBudget control, dynamic tool discovery, the daily-refresh freshness model, and the key gotcha that the MCP strips last-updated metadata so you must read it from the rendered page instead.

Run a maximally strict structural code review that hunts complexity-collapse opportunities, oversized files, creeping conditionals, and unearned abstractions, then defends every finding against refutation before reporting it. Scope the diff first, review against eight standards, and gate approval hard. Use for a supercritical review, deep maintainability audit, especially harsh code-quality review, or when the user asks for a thermo-nuclear-style review.

Know, without being told, which target framework every project in ~/RiderProjects/qyl-workspace compiles for and what that allows or forbids — the net10.0 baseline (full modern BCL, AOT/trim-aware) versus the small netstandard2.0 Roslyn island (source generators + analyzers + the multi-targeted OTel libs). USE FOR: editing or reviewing any C# in qyl, Qyl.AutoInstrumentation, qyl-dotnet-autoinstrumentation, Qyl.OpenTelemetry.SemanticConventions; choosing whether an API/language feature is legal in the file you are touching; a build error like CS0103/CS1061/CS8370/"is not available in netstandard2.0" inside a *.SourceGenerators / *.Analyzers / *.generators project; "can I use HashCode / System.Text.Json / ArgumentNullException.ThrowIfNull / Span here"; reviewing a PR that spans both a generator and its runtime consumer. ESPECIALLY use it before you assume a *.SourceGenerators project can call net10 BCL (it cannot — it is netstandard2.0), or that netstandard2.0 forbids records / init / required (it does NOT — th

Use when driving a self-hosted CI runner to a green verdict — bringing an offline/paused runner (and the VM or container engine it lives in) online, draining workflow runs that are queued only because the runner is down, taking a single status snapshot of the result, then tearing the runner and any leaked test containers back down. Use for "get CI green", "the runner is offline", "CI is queued and not starting", "bring the VM up for CI", a self-hosted job that never picks up, or "ci up / ci down". Especially use it before concluding CI is blocked because a runner or VM is stopped — a stopped self-hosted runner is a routine bring-up, never a blocker.

Generate C4 Container diagrams using C4 model conventions as editable .drawio XML files. Use when the user asks for architecture diagrams, system diagrams, C4 diagrams, container diagrams, or wants to visualize system architecture. Also use proactively when explaining systems with 3+ components where a visual would clarify the architecture.

Set up, debug, and operate fully-automated NuGet.org publishing via Trusted Publishing (GitHub Actions OIDC, NuGet/login, zero stored secrets) using the battle-tested ANcpLua fleet workflow pattern. Use whenever the task touches publishing a NuGet package, a nuget-publish.yml / release workflow, dotnet nuget push, NuGet API keys, a failing "Authenticate to NuGet" step, a package version that "isn't showing up" on nuget.org, or automating releases for a .NET repo — and ESPECIALLY when you are tempted to say publishing is blocked because an API key is missing. A missing API key is never a blocker and never a reason to stop; this skill exists because agents keep wrongly concluding "can't publish, no key". Also use when creating or editing a nuget.org Trusted Publishing policy, when a v-tag exists but the version never reached nuget.org, or when wiring tag-derived auto-versioning so no human ever bumps a version by hand.

Use when working directly with Forgejo v15 APIs, private repositories, Actions workflows, runners, pull requests, reviews, statuses, releases, packages, webhooks, organizations, users, or admin operations. Prefer Forgejo's live Swagger and direct endpoints over GitHub-shaped assumptions.

Install and integrate React Bits Pro premium UI components and page blocks into React/Next.js apps using the shadcn registry CLI. Use this skill when the user wants to add animated components (WebGL shaders, GSAP animations, 3D effects, cursor trails, text animations, carousels, cards), full page sections (hero, pricing, navigation, footer, FAQ, CTA, auth, stats, blog, contact, features, social proof, 404, profile, about, waitlist, showcase, how-it-works, download), or landing page templates from React Bits Pro. Also use when the user mentions "react bits", "reactbits", or wants premium animated React components even if they don't name the library directly.