Agent skill

Provider Bug Review

by mondoohq in mondoohq/mql

Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

Custom licenceAuto-check passedDevOps & Cloud

Install Provider Bug Review

skills CLI
$ npx skills add mondoohq/mql --skill provider-bug-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mondoohq/mql provider-bug-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mondoohq/mql.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/provider-bug-review .claude/skills/provider-bug-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
provider-bug-review
GitHub stars
412
Token cost
~2.9k tokens
SKILL.md length
1,488 words
Files
3 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

  • Works in 5 steps: Scope and prioritize → Learn the house patterns FIRST (do not… → Fan out analysis agents by file-group → …
  • It for review the okta provider for bugs
  • SKILL.md covers When this is the right tool, The core loop and The bug taxonomy
  • Calls git and make

What it does

Provider Bug Review is an agent skill from mondoohq/mql. Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data. Use this whenever someone wants to audit, review, deep-dive, bug-hunt, or "find problems in" a provider (aws, gcp, azure, okta, k8s, or any provider under providers/) — whether the ask is a whole provider, a recently-shipped set of resources, or a PR/commit range. Trigger it for "review the okta provider for bugs", "audit gcp for nil…

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/agent-prompt-template.md` and `references/bug-taxonomy.md`).

It sits in DevOps & Cloud, covering Container orchestration, Caching and Code review. It works with Google Cloud, Microsoft Azure, Amazon Web Services and Kubernetes. The repository describes itself as: open source, cloud-native, graph-based query language.

When your agent uses it

  • It for review the okta provider for bugs
  • Audit gcp for nil issues
  • Any pagination problems in the azure provider?
  • Deep dive the new resources for logic errors

Example prompts

  • “find problems in”
  • “review the okta provider for bugs”
  • “audit gcp for nil issues”
  • “/provider-bug-review”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Scope and prioritize
  2. Learn the house patterns FIRST (do not skip)
  3. Fan out analysis agents by file-group
  4. Verify every candidate against source
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit d9f1bd2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Provider Bug Review loads about 2.9k tokens when it runs, and up to ~9k if it reads all its reference files. Until then it costs about 225 tokens; SKILL.md has 1,488 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~225
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,488 words (~2,944 tokens).

“Find the bugs in an mql provider that a compiler and a passing test suite will not catch: pagination loops that silently return one page, pointer derefs that panic on a real-world null, a field that resolves differently through the…”

— opening of SKILL.md by mondoohq, Custom licence
name
provider-bug-review

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (references) in .agents/skills/provider-bug-review of mondoohq/mql.

  • SKILL.md
  • references/agent-prompt-template.md
  • references/bug-taxonomy.md

Open the folder on GitHubat commit d9f1bd2

Compare with similar skills

Provider Bug Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Provider Bug Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Provider Bug Review this skillmondoohq/mql412—~2.9kAutomated safety check: PassCustom licence
Kcli Cluster Deploymentkarmab/kcli653—~1.5kAutomated safety check: PassApache-2.0
Extend Discovery Typerunwhen-contrib/runwhen-local163—~1.7kAutomated safety check: PassApache-2.0
Kclikarmab/kcli653—~2.6kAutomated safety check: WarnApache-2.0
Azure Arcvinayaklatthe/microsoft-security-skills175—~1.9kAutomated safety check: PassMIT
Cloud Devopsdavila7/claude-code-templates33k4 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Guides deployment and management of Kubernetes clusters with kcli.

    653 GitHub stars~1.5k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Extend Discovery Type

    runwhen-contrib/runwhen-local

    Add or enrich a resource type in an existing RunWhen Local discovery indexer (Azure azureapi, GCP gcpapi, AWS, or Kubernetes).

    163 GitHub stars~1.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Kcli

    karmab/kcli

    Comprehensive guide for kcli usage. An agent skill from karmab/kcli.

    653 GitHub stars~2.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: warnings
  • Azure Arc

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure Arc — projecting on-premises, multicloud (AWS/GCP), and edge servers, Kubernetes, and data services into Azure Resource Manager for unified governance, security, and management.

    175 GitHub stars~1.9k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed
  • Cloud Devops

    davila7/claude-code-templates

    Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.

    33k GitHub starsUsed in 4 repos~1.4k tokens
    DevOps & CloudAuto-check passed
  • Resource Tagging

    ancoleman/ai-design-components

    Apply and enforce cloud resource tagging strategies across AWS, Azure, GCP, and Kubernetes for cost allocation, ownership tracking, compliance, and automation.

    525 GitHub stars~4k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check passed

More from mondoohq/mql

All 9 skills in this repo
  • Verify mql provider resource/field changes against real cloud infrastructure.

    412 GitHub stars~3.7k tokensUpdated today
    Auto-check passed
  • Upgrade an mql provider's vendored SDKs (all providers or a named subset), audit the new versions for breaking changes and fix call sites while keeping shipped MQL fields backwards-compatible, check…

    412 GitHub stars~4.5k tokensUpdated today
    Auto-check passed
  • New Provider

    mondoohq/mql

    Scaffold a new mql provider. An agent skill from mondoohq/mql.

    412 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • New Resource

    mondoohq/mql

    Add or change a resource in an existing mql provider — schema, codegen, implementation, tests, and verification against a real target.

    412 GitHub stars~5.6k tokensUpdated today
    Auto-check passed
  • Provider Release

    mondoohq/mql

    Release mql providers and cut mql/cnspec releases, stable or pre-release.

    412 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Staged Discovery

    mondoohq/mql

    Add staged discovery support to a provider. An agent skill from mondoohq/mql.

    412 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Questions about Provider Bug Review

What does Provider Bug Review do?

Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data. Provider Bug Review is an agent skill from mondoohq/mql. Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

When should I use Provider Bug Review?

Provider Bug Review fits situations like: it for review the okta provider for bugs; audit gcp for nil issues; any pagination problems in the azure provider?; deep dive the new resources for logic errors.

How do I install Provider Bug Review in Claude Code?

Run `npx skills add mondoohq/mql --skill provider-bug-review -a claude-code`. Or copy the skill folder (.agents/skills/provider-bug-review in mondoohq/mql) into .claude/skills/provider-bug-review in your project. Claude Code loads it when a task matches its description.

How do I install Provider Bug Review in Codex?

Run `npx skills add mondoohq/mql --skill provider-bug-review -a codex`. Or copy the skill folder (.agents/skills/provider-bug-review in mondoohq/mql) into .agents/skills/provider-bug-review in your project. Codex loads it when a task matches its description.

Can I use Provider Bug Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mondoohq/mql --skill provider-bug-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/provider-bug-review, .gemini/skills/provider-bug-review, .github/skills/provider-bug-review and .opencode/skills/provider-bug-review in your project.

What does Provider Bug Review need to run?

Going by SKILL.md and its folder, Provider Bug Review needs the command-line tools its instructions call (git and make).

Does Provider Bug Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Provider Bug Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Provider Bug Review use?

Provider Bug Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Provider Bug Review use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.1k tokens, read only when the agent opens those files.

What are the alternatives to Provider Bug Review?

Skills that share tags, products or a category with Provider Bug Review: Kcli Cluster Deployment (karmab/kcli, 653 stars), Extend Discovery Type (runwhen-contrib/runwhen-local, 163 stars), Kcli (karmab/kcli, 653 stars) and Azure Arc (vinayaklatthe/microsoft-security-skills, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Provider Bug Review?

mondoohq (a GitHub organization) maintains it in mondoohq/mql, which has 412 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 11, 2026.

Source: mondoohq/mql on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.