agentsclimarketplace
Sign in

Cloudx audit

Skill cloudx-io/cloudx-sdk-agents/.agents/skills/cloudx-audit

Audit an existing CloudX SDK integration in a publisher app for correctness, staleness, lifecycle, coexistence, and privacy issues. Use when asked to check, audit, review, or validate a CloudX integration that already exists, or after upgrading the CloudX SDK version.From its SKILL.md

Install
npx -y skills add cloudx-io/cloudx-sdk-agents --skill cloudx-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, as published. Nobody here has run it

CloudX Integration Audit

Audit the CloudX integration already present in this app. Do not add new integration work — for that, use cloudx-integrate.

Iron rule: never judge the integration against APIs from memory. Fetch the current docs first (https://docs.cloudx.io/llms.txt, then the platform pages — see ../cloudx-integrate/references/doc-map.md) and diff the code against what the docs say today. An integration written against an older SDK may compile and still be wrong or incomplete; the platform changelog page shows what changed.

Steps

  1. Detect — platform, CloudX SDK dependency and adapters present, ad formats used, existing mediation SDKs, CMP tooling. Match playbook signals in ../cloudx-integrate/references/playbook-index.md and read the playbooks that apply.
  2. Fetch — the platform integration overview, the ad-format page for each format the app uses, the platform changelog, and adapter pages for adapters present.
  3. Diff code against current docs:
    • Dependency coordinates and adapter set vs the current documented ones. For each installed adapter, verify its overview page's requirements are fully met (extra Maven repositories, manifest/Info.plist entries, native view requirements). If the publisher's enabled-network set is knowable (ask, or CloudX MCP/CLI config/show), flag mismatches both ways: compiled-in adapters for networks not enabled (dead weight) and enabled networks with no adapter in the binary (silent zero contribution).
    • Initialization: documented location, once, before ad loads, correct config.
    • Each ad format: creation, listeners, readiness checks, show requirements, lifecycle/destroy handling per the current docs page.
    • Removed/renamed APIs still referenced (changelog is the evidence).
  4. Coexistence — if another mediation stack is present: both init paths intact, fallback or first-look wiring per the platform's first-look docs page, no circular loading, per coexist-mediation.md.
  5. Privacy — CMP writes IAB consent strings before ads load; no usage of privacy APIs the changelog marks removed; consent forwarded to any coexisting mediation SDK (per consent-and-cmp.md).
  6. Report — findings ranked by severity: breaks now / breaks on upgrade / revenue risk / hygiene. Each finding cites the file:line and the docs page that contradicts it. End with the SDK-version gap (dependency present vs current documented version) and the changelog entries in between.

Keep looking

Skills are one crate of 627,559. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.