← all publishers

mondoohq

@mondoohq source repo

11 published skills

  1. Mql · mondoohq bundle
    Use when writing MQL (Mondoo Query Language) queries, working with Mondoo MCP tools, or developing security policies
    0
    installs
  2. Policy Graph · mondoohq bundle
    Navigates cnspec policy/framework bundles using graph commands. Use when exploring policies, finding checks, tracing compliance mappings, or understanding policy structure.
    0
    installs
  3. New Provider · mondoohq
    Scaffold a new mql provider. Use when the user wants to create a new provider, bootstrap a provider, or add a new integration target (e.g., "create a provider for Datadog", "scaffold a new provider", "add a new provider").
    0
    installs
  4. New Resource · mondoohq bundle
    Add or change a resource in an existing mql provider — schema, codegen, implementation, tests, and verification against a real target. Use when the user wants to add a resource or fields to a provider (e.g. "add a bind9 resource", "expose the tomcat connectors", "add a resource for named.conf", "model the postfix config"), or when a resource returns null, empty, or wrong values and the cause is the schema rather than the API call.
    0
    installs
  5. Provider Release · mondoohq
    Release mql providers by bumping their versions. Use when the user wants to release providers, bump provider versions, check which providers have changes, or prepare a provider release PR. Triggers on requests like "release providers", "bump provider versions", "check provider changes", "release aws provider", or "prepare provider release".
    0
    installs
  6. Staged Discovery · mondoohq
    Add staged discovery support to a provider. Use when the user wants to implement staged/phased discovery, break down discovery into stages, add OptionStagedDiscovery support, or optimize a provider's memory usage during discovery. Triggers on requests like "add staged discovery to gcp", "implement staged discovery for aws", "break down discovery for <provider>", or "optimize <provider> discovery".
    0
    installs
  7. Provider Bug Review · mondoohq bundle
    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 issues", "any pagination problems in the azure provider?", "deep dive the new resources for logic errors", or a general "check this provider for issues". This is the STATIC/logic counterpart to provider-verification (which proves resources against live cloud infra) — reach for this when the goal is finding bugs by reading code, not spinning up infrastructure.
    0
    installs
  8. Update Provider Deps · mondoohq bundle
    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 whether .lr enum comments drifted, and propose a numbered list of new resources and fields the upgrade unlocks for the user to choose from. Use this whenever the user mentions updating, bumping, upgrading, or refreshing SDK or provider dependencies for any provider (azure, aws, gcp, github, cloudflare, okta, alicloud, mongodbatlas, databricks, and the rest), asks what a newer SDK would give us, asks whether a dep bump is safe or breaking, or asks what new fields or resources an SDK version makes available. Also use it for "check for new SDK majors", "are our SDKs current", and "what did we miss in the new SDK". Runs one provider at a time by default; a sweep across several providers is an explicit opt-in.
    0
    installs
  9. Provider Verification · mondoohq bundle
    Verify mql provider resource/field changes against real cloud infrastructure. Given a pull request or a commit range, this provisions Terraform infra in the affected cloud(s), runs mql queries against every new or changed resource and field, reports the hourly cost (pausing for approval above $2/hr), opens a fix PR for any provider bugs it uncovers, and tears the infrastructure back down. Use this whenever someone wants to test, verify, smoke-test, or "prove out" a provider PR or a range of commits against live cloud APIs — e.g. "verify PR #7701 works", "spin up infra to test the new GCP resources", "check the azure changes against real infrastructure", "test resources changed between these commits". Trigger it even when the user only says "test this PR" in the context of an mql provider change.
    0
    installs
  10. Provider API Call Dedup · mondoohq bundle
    Use when a provider scan is slow, times out, or trips rate limits (429, throttling, Retry-After), when the same request URL appears many times in a debug log, when an asset's fields look like they cost one API call per scanned asset, or when auditing any provider under providers/ for redundant per-asset API traffic. Applies to aws, azure, gcp, k8s, okta and any other provider, since the resource cache and init dispatch are shared machinery.
    0
    installs
  11. Check Querypack Deprecations · mondoohq
    Check content/ mql.yaml query packs for usage of deprecated resources or fields from .lr definitions
    0
    installs