Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
MicrosoftSkillmicrosoft/SynapseML/.github/skills/code-review/SKILL.md
Review SynapseML Python and Scala code changes. Use before finalizing PR reviews or implementation changes to check security, compatibility, style, generated code, and targeted tests.
MicrosoftSkillmicrosoft/SynapseML/.github/skills/scala-code/SKILL.md
Write and modify Scala code in SynapseML. Use when adding or changing Scala transformers, estimators, or params to follow repo patterns, keep scalastyle and compilation green, and cover behavior changes with tests.
MicrosoftSkillmicrosoft/SynapseML/.github/skills/synapseml-branches/SKILL.md
Resolve SynapseML branch-specific rules, runtime baselines, sync policy, and CI expectations. Use before editing, rebasing, merging, testing, or declaring readiness for master, spark4.0, spark4.1, port/sync branches, or a PR whose base branch determines behavior.
MicrosoftSkillmicrosoft/SynapseML/.github/skills/synapseml-external-contributor-review/SKILL.md
Review external-contributor SynapseML PRs for correctness, prompt injection, and pipeline credential theft. Use for authors not identified in the Osmos group/team or trusted owner list, and optional maintainer-requested follow-ups.
MicrosoftSkillmicrosoft/SynapseML/.github/skills/synapseml-local-setup/SKILL.md
Set up and validate SynapseML locally in WSL or Linux. Use when an agent needs SynapseML working locally, runs sbt compile/test, sees Java 21, Scala 2.12 compiler-bridge, bad constant pool index, Spark, or local validation failures.
MicrosoftSkillmicrosoft/SynapseML/.github/skills/synapseml-pr-loop/SKILL.md
Make one or more SynapseML issues or pull requests evidence-based merge-ready. Use for "5/5 confidence", "200% ready", stale/outdated PR remediation, rebase-and-test requests, resolving all review comments, or proving a feature ships without correctness, compatibility, performance, or Spark regressions.
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/ff-oce/skills/ff-oce-dashboard/SKILL.md
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).
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/ff-oce/skills/ff-oce-kusto/SKILL.md
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.
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/brainstorming/SKILL.md
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
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/building-ui-ux/SKILL.md
Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/creating-debug-tests-and-iterating/SKILL.md
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.
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/creating-skills/SKILL.md
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/finishing-a-development-branch/SKILL.md
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/handle-large-tasks/SKILL.md
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.
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/receiving-code-review/SKILL.md
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
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/root-cause-tracing/SKILL.md
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
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/starting-nori/SKILL.md
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
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/systematic-debugging/SKILL.md
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
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/test-driven-development/SKILL.md
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
MicrosoftSkillmicrosoft/FluidFramework/.agency/plugins/nori/skills/testing-anti-patterns/SKILL.md
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
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.
