Inspect and mutate MongoDB-backed CMS data with structured Node.js scripts.
npx skills add https://github.com/Kyonax/dot-files --skill cms-tools
Please help me install this Agent Skill. Skill: cms-tools Source: https://github.com/Kyonax/dot-files/tree/main/.config/doom-mac/gptel-directives/skills/cms-tools Command: npx skills add https://github.com/Kyonax/dot-files --skill cms-tools
This skill eliminates the repetitive, error-prone manual work of querying Madison Reed's Tophat CMS through raw mongosh commands. Instead of writing one-off Docker exec queries, parsing BSON output by eye, and repeating the process 4-6 times per investigation, you get a stable, scripted toolkit that returns structured JSON and enforces safety rails like dry-run mode and automatic backups.
Use the cms-tools skill to inspect what renders on the URL /colorbar/location-specific by running the inspect-content-by-uri script and reviewing the returned JSON for the active experiment, variations, and component mixin keys.
High-intent search queries and answers about installing and using this skill.
To inspect what content renders on a specific URL, you can run a read-only Node.js inspection script against the MongoDB-backed CMS. This returns structured JSON detailing the active experiment, variations, and component mixin keys, eliminating manual mongosh queries.
Yes, you can safely mutate experiment bindings, variant weights, and JSON-LD schemas using dedicated mutation scripts. These scripts enforce mandatory dry-run gates, create automatic backups, and perform idempotent writes to prevent data corruption during CMS updates.
The best way to map CMS metadata to Vue component files and Express route handlers is using code locator scripts. These scripts translate mixin keys and URIs directly to their source code locations, eliminating time-consuming grep searches across the codebase.
Yes, you need Docker to access the MongoDB database for local diagnosis and pre-production validation. The toolkit relies on Docker-based MongoDB access to execute structured inspection and mutation scripts safely within your local environment.
You should use structured scripts instead of manual mongosh commands because they prevent repetitive errors and parsing inaccuracies. Scripts provide stable tooling that returns structured JSON output, enforcing safety rails like dry-run modes and backups for reliable investigations.
When modifying template fields, limitations include being restricted to idempotent re-runs and mandatory dry-run gates. These constraints ensure safe mutations by requiring validation before applying changes to the MongoDB-backed CMS data.
leonj1Automate NanoClaw setup, configuring dependencies, authentication, and container runtimes.
Clouder0Validate outputs against required schemas using validate.sh before committing.
e-xodeImplement Express 5 API routes with MongoDB access and validation.
jholhewresExecute queries and manage schemas across PostgreSQL, MySQL, MongoDB, Redis, and SQLite.
