Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides specialized utilities for FinOps practitioners and developers managing Azure environments. It enables a structured approach to investigating cost spikes, analyzing resource breakdowns for AKS and AI services, and implementing OpenAI functionality within the .NET ecosystem.
By isolating actual spend analysis from forecasting, the tools help users identify why bills increase and pinpoint expensive resources across namespaces and clusters.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
Install selected skills with the skills.sh wizard
Installs: Selected skills from the complete microsoft/skills catalog; not limited to the paths listed here. · GitHub Copilot
In a terminal, start the installation wizard. Select the skills you need and choose the target agent. For GitHub Copilot, the documented example destination is `.github/skills/`; the wizard can also symlink skills when multiple agents are selected.
Replace [RESOURCE_NAME] with the resource's PascalCase name, such as Project.
Replace [FIELD_DEFINITIONS] with each field's name, type, validation constraints, and whether it is required.
Replace [ALIAS_REQUIREMENTS] with the snake_case-to-camelCase mappings needed by the API, or state that none are needed.
Replace [TARGET_PATH] with the desired project path; the documented example location is `src/backend/app/models/`.
Use the pydantic-models-py skill to create a small Pydantic v2 model set for [RESOURCE_NAME] from [FIELD_DEFINITIONS]. Include the documented Base, Create, Update, Response, and InDB variants, make update fields optional, and use camelCase aliases where [ALIAS_REQUIREMENTS] calls for them. Place the models in [TARGET_PATH] and summarize the generated variants.
Replace [STORE_NAME] with a PascalCase store name, such as Project.
Replace [STATE_FIELDS] with the required state field names and TypeScript types.
Replace [ACTIONS] with the small set of state-changing operations the store needs.
Replace [TARGET_PATH] with the desired project path; the documented example directory is `src/frontend/src/store/`.
Use the zustand-store-ts skill to create a small TypeScript Zustand store named [STORE_NAME] in [TARGET_PATH]. Implement [STATE_FIELDS] and [ACTIONS], separate the state and action interfaces, wrap the store with subscribeWithSelector, and show one individual selector suitable for a React component.
Replace [EVENT_HUBS_OR_SERVICE_BUS] with Azure Event Hubs or Azure Service Bus.
Replace [ERROR_AND_SYMPTOMS] with the exact error text and observed behavior.
Replace [SDK_LANGUAGE_AND_VERSION] with the client language, package name, and version when known.
Replace [RELEVANT_CONFIGURATION] with non-secret details such as entity name, consumer group, retry settings, prefetch, batch size, and authentication method; do not include credentials.
Use the azure-messaging skill to produce a read-only first-pass diagnosis of this [EVENT_HUBS_OR_SERVICE_BUS] SDK problem: [ERROR_AND_SYMPTOMS]. Account for [SDK_LANGUAGE_AND_VERSION] and [RELEVANT_CONFIGURATION]. Identify the most likely causes, the checks that would distinguish them, and a recommended fix supported by the applicable Microsoft documentation. Do not change resources or configuration.
Claude
Copilot
OpenCode