microsoft/fluidframework · Archived
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.
npx skills add microsoft/fluidframework --skill policy-check
This repository is archived — consider an actively maintained alternative.
Use when asked to review code, review a branch, or do a code review. Spawns Breaker (correctnes…
6 installsUse when creating a pull request in the Fluid Framework repo.
6 installsUse when customer-facing API changes were made — i.e., API report .md files differ from the bra…
6 installsUse when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness",…
5 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deploymen…
568.2K installsPre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installsGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE…
566.9K installsGuidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns…
566.6K installsOther skills from microsoft/fluidframework · top by installs.
npx skills add microsoft/fluidframework
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Files included with this skill beyond the listing page.
SKILL.md
610 B
SUMMARY.md
251 B
Run pnpm policy-check --path <relative-path> from the repo root to check a specific package. Do NOT cd into the package directory.
Even when changes are applied to a single package, repository-wide checks (pnpm policy-check without --path) are still appropriate since changes in one package can cause policy failures in others.