nuko-nova-unslop
AGENTS.md1 starsChanged 7 days agoApache-2.0View on GitHub
This repository contains one shared writing skill packaged for Codex and Claude Code. Run these before committing:
- Installs packages
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository4 other files it gives its agents.
- nuko-nova-unslopSkill
- super-tightenSkill
- tightenSkill
- unslopSkill
The file
We split this AGENTS.md into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Keep the zero-em-dash house preference subordinate to quotations and fixed strings, but not to an author sample unless the user explicitly …
- Distinctive: line 24
Keep personality inside an owned voice.
- Distinctive: line 25
Treat human writing as purposeful, audience-aware, emotionally proportionate language, not as automatic slang, casualness, quirks, …
- Distinctive: line 27
Treat delegated prose as source material and apply the skill in the parent before delivery because client output styles may not propagate …
- Distinctive: line 28
Do not ship lifecycle hooks or any final-output interceptor.
- Distinctive: line 29
Add a regression fixture for every non-obvious behavioral fix.
- Distinctive: line 30
Never ingest a third-party phrase corpus wholesale.
- Distinctive: line 31
Keep the skill body concise and route detailed material into one-level references.
- Distinctive: line 32
Treat unslopped human-facing prose as the default acceptance criterion, not an optional user-requested pass.
- Distinctive: line 37
Run these before committing:
- Distinctive: line 49
After changing skill or output-style prose, run the behavior evals and compare the score with the previous run and with the no-plugin arm:
- Very specific: line 57
Run claude plugin validate .
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repository guidance
This repository contains one shared writing skill packaged for Codex and Claude Code.
Source of truth
skills/nuko-nova-unslop/SKILL.mddefines runtime behavior.skills/unslop/SKILL.mdis the short explicit alias and must only route to the canonical skill.skills/tighten/SKILL.mdis the focused compression command. It must route through the complete canonical skill before the second-stage rules inskills/nuko-nova-unslop/references/tighten.md.skills/super-tighten/SKILL.mdis a standalone combined Unslop, compression, and ASD-STE100 workflow. Its runtime instructions must not route to another writing skill or reference. Preserve the distinction between applying STE rules and verifying full vocabulary conformance against the official standard.output-styles/nuko-nova-unslop.mdmakes the standard apply to every Claude Code response while the plugin is enabled.skills/nuko-nova-unslop/agents/openai.yamlkeeps implicit Codex invocation enabled.- The files under
skills/nuko-nova-unslop/references/hold detailed runtime rules. Maintainer material lives indocs/: followdocs/evolution.mdfor upstream review, and record sources indocs/source-map.md. That folder is not shipped in the skill or served by the MCP host. evals/holdsclaude plugin evalcases that measure behavior with and without the plugin. Change skill prose against eval results, not against exact-wording checks.skills/nuko-nova-unslop/scripts/markdown_source.pyowns shared Markdown recognition and offset-preserving masking. The linter and preservation guard apply their own editorial policies to its results..codex-plugin/plugin.jsonand.claude-plugin/plugin.jsonmust keep name, version, description, author, repository, and license aligned.upstreams.lock.jsonrecords reviewed upstream state; a new SHA is not accepted until its relevant diff has been reviewed and the package gates pass.- A recurring owner-created automation may publish only when its prompt explicitly grants the exact Nuko Nova Unslop push, release, marketplace, and client-update actions and every target is reverified during that run.
Editing contract
- Preserve the skill's fact and voice safeguards when changing pattern rules.
- Keep the zero-em-dash house preference subordinate to quotations and fixed strings, but not to an author sample unless the user explicitly requests em dashes for the current piece. Never satisfy it with spaced double hyphens or staccato fragments.
- Keep personality inside an owned voice; never let an edit donate opinions or experiences to a represented author.
- Treat human writing as purposeful, audience-aware, emotionally proportionate language, not as automatic slang, casualness, quirks, fragments, or deliberate mistakes.
- Apply the no-cringe standard through ownership, proportion, audience fit, and substance. Keep subjective cringe signals contextual and advisory.
- Treat delegated prose as source material and apply the skill in the parent before delivery because client output styles may not propagate to subagents.
- Do not ship lifecycle hooks or any final-output interceptor. The writing skill may advise and lint, but it must never block, rewrite, or delay an answer at a client lifecycle boundary.
- Add a regression fixture for every non-obvious behavioral fix.
- Never ingest a third-party phrase corpus wholesale. Curate small, explainable rules with false-positive boundaries.
- Keep the skill body concise and route detailed material into one-level references.
- Treat unslopped human-facing prose as the default acceptance criterion, not an optional user-requested pass.
- On authorized automated evolution runs, publish accepted behavioral changes through the full repository, release, marketplace, and client-update sequence. Report a no-op when no justified change exists.
Required checks
Run these before committing:
pnpm check
python3 /Users/judiazm/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/nuko-nova-unslop
python3 /Users/judiazm/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/unslop
python3 /Users/judiazm/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/tighten
python3 /Users/judiazm/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/super-tightenpnpm check runs the portable bundle, Python, and MCP checks and is also the CI entry point. tests/validate_bundle.py is the required repository-owned plugin validator; it checks both client manifests, shipped resources, invocation metadata, and hook-free packaging. Install workspace dependencies with pnpm install --frozen-lockfile first. The skill creator checks above depend on the local Codex installation and remain separate.
After changing skill or output-style prose, run the behavior evals and compare the score with the previous run and with the no-plugin arm:
claude plugin eval . --runs 3 --judge-model sonnet --no-publish --threshold 0 --output-dir /tmp/unslop-evalEvals call models and cost money, so they are not part of pnpm check or CI.
Run claude plugin validate . when Claude Code is available. Treat package validation, marketplace registration, installation, and client reload as separate states.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

