Catalog QA Auditor
Audit a product catalog for silent data corruption: empty prompts, duplicates, template residue, leaked secrets.
- What
- Audit a product catalog for silent data corruption: empty prompts, duplicates, template residue, leaked secrets.
- Cost
- Free
- Needs
- Run a catalog audit in four steps. You need: read access to your product database and Python.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
The Catalog QA Auditor catches the errors nobody finds by opening listings one by one. It runs automated read-only scans over a product database, surfaces only the anomalies, and fixes them with a re-read after every write. It was built for a 1,900-listing directory where a full audit costs a few thousand tokens instead of a full catalog read, and it has caught real incidents: installation prompts containing literally nothing but a code fence, the same prompt pasted onto the wrong listing, and prices contradicting their own labels. The check list covers installation prompts (empty, corrupted, or duplicated across listings), template residue ({{ }}, TODO, lorem, [insert markers in user-facing text), missing translations (EN present but FR empty), invalid or empty creation dates (which break "New" sections and date sorting), duplicate repo URLs (normalized before comparison, so /blob/... suffixes and root URLs are both caught), price inconsistencies (paid flag vs price vs label), secrets and PII swept from texts (API keys and emails pasted by accident are invisible to the naked eye), orphaned sellers and suspicious slugs, and sitemap vs database counts (a gap means an incomplete build). Link health runs quarterly in the background because thousands of HTTP requests are slow. The workflow is monthly, plus after any data incident, with a dated corrections log for every run. The operating rules are strict: scans are SELECT-only, dedupe happens on slugs and ids never on display names, one fix at a time with a re-read between writes, and every pipeline bug found becomes a new guardrail instead of just a data fix. It also includes the post-insert validation ritual born from a real incident: after every bulk insert and before every build, validate against the database that critical fields are actually present and non-empty, because truthiness checks lie.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Run a catalog audit in four steps. You need: read access to your product database and Python. 1. Schedule: full audit once a month, plus after any data incident. Link health (every URL in the catalog) once a quarter, in the background. 2. Scan: run every check as SELECT-only queries. Filter in Python and surface only the anomalies: empty or duplicated install prompts, template residue ({{, TODO, lorem), missing translations, invalid dates, duplicate normalized repo URLs, price inconsistencies (is_free vs price vs label), secrets swept from texts (sk-, ghp_, AKIA patterns), orphaned sellers, suspicious slugs, and sitemap vs database count gaps. 3. Triage: data corruption (empty prompt, duplicate, invalid date) gets fixed directly in the database with a re-read after EVERY update before the next one. Non-critical gaps (missing translation, short description) get fixed where there is traffic; leave the long tail alone. If an anomaly reveals a pipeline bug, harden the pipeline with a new guardrail instead of just fixing the data. 4. Report: write a dated section in your corrections log with the date, checks run, anomalies found, decisions, and fixes applied. After every bulk insert and before every build, validate that critical fields are actually present and non-empty in the database. Rules: read-only scans, dedupe on ids never display names, one fix at a time, never a destructive correction without re-reading.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.