No AI Slop: evidence-led editing, packaging and evaluation
Deploy No AI Slop as a reviewed skill package, not a new writing service
Distinguish a host integration from a source package build, avoid blind global installation and account for a Windows validator limitation.
What you will learn
- Choose the host and installation scope explicitly
- Package building has a narrower platform claim
- Keep rollback separate from deleting personal configuration
Before you start
- A draft whose facts can be checked
- Basic understanding of assistant instructions and plugin scope
Inspect pattern evidence, preserve meaning and distinguish package checks from unmeasured editing outcomes.
Key takeaways
- Review global installer scope instead of copying acceptance flags blindly.
- --check performs a build and cleanup.
- The observed Windows issue concerns package validation, not all host usage.
Choose the host and installation scope explicitly
The pinned README documents a skills installer command with global and automatic-acceptance flags. That is an upstream example, not a requirement to change every local assistant profile. Review the installer and the target host’s supported import route first. A trial should have a known scope and a record of the files or plugin entries it adds.
The manifest points to ./skills/ and includes interface metadata, starter prompts and artwork paths. Host discovery, rule loading and useful editing are three distinct acceptance checks. A package appearing in a plugin list proves only discovery; it does not show that the current conversation received the intended rules or respected them.
Package building has a narrower platform claim
scripts/build_plugin.py validates source metadata, copies a seven-file package and creates a versioned ZIP. The workflow runs this on Ubuntu with Python 3.12. Its --check option still builds output and then removes it, so it is not a read-only inspection command. Run it only in a disposable reviewed checkout, not over a distribution directory you need to preserve.
Our isolated Windows case calls validate_build on a synthetic package and observes rejection because relative Path strings use backslashes while the expected set uses forward slashes. That is a packaging-validator limitation, not proof that a host cannot consume the skill on Windows. The upstream workflow’s Linux environment also does not certify every platform.
Keep rollback separate from deleting personal configuration
Pin the rules, checklist and manifest together so a rollback restores a coherent package. Record the exact installation entry and previous version. Disable or remove that entry through the selected host’s documented mechanism, then start a fresh conversation; old context can still contain instructions after a package setting changes.
No global installation, account setup or live host activation was performed for this series. We ran only the reviewed source validation functions against temporary synthetic files. Teams should complete discovery, rule-loading and output checks before making the package a default for everyone.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Select the host and a limited trial scope.
- 2
Record revision and the exact installation entry.
- 3
Verify discovery, loaded rules and editing separately.
- 4
Test rollback in a fresh conversation.
Copy-ready example
{
"rolloutScope": "disposable-profile",
"revision": "000650b156983f5159695b441477f4e63b25dc85",
"discoveryVerified": false,
"rulesLoaded": false,
"editingVerified": false,
"globalInstallExecuted": false
}Frequently asked questions
Is there a server to deploy?
The repository supplies a skills-only package; no separate writing server is established by this code.
Does the Windows test mean the skill is unusable there?
No. It identifies a path comparison issue in the Python package validator, not a host compatibility result.
Sources
- No AI Slop / README.mdSource checked 2026-09-14
- No AI Slop / .codex-plugin/plugin.jsonSource checked 2026-09-14
- No AI Slop / scripts/build_plugin.pySource checked 2026-09-14
- No AI Slop / .github/workflows/plugin.ymlSource checked 2026-09-14