← ClaudeAtlas

snifftestlisted

Check a draft against the writer's house rules with the Sniff Test linter. Use when the user says /snifftest, hands you a Markdown or text file and asks whether it passes, asks which house rules a draft trips, or asks for a style or prose check on something they wrote. Reports the rule, the line and how sure the checker is, so the prose can be fixed rather than argued about.
Spirounkempt95/snifftest · ★ 0 · Data & Documents · score 70
Install: claude install-skill Spirounkempt95/snifftest
# Sniff Test A prose linter. It reads Markdown and plain text files, checks them against a YAML ruleset, and prints one line per flag. There are two kinds of rule and they behave differently. **Countable rules** are regular expressions. Dash counts, banned words, sentence rhythm, anything a computer can decide exactly. They run on the machine, cost nothing, and send nothing anywhere. Run them whenever you like. **Judgment rules** need something read rather than counted: a line that undercuts its own claim, a cost stated without a price, a closing sentence that only restates. Deciding those means sending the text to a model, so they only run when the user has already agreed to it on this machine, or agrees now. ## Running it Both passes go through the script in this skill's folder. It pins the version of the tool it fetches and never answers the sending question on your behalf. The free pass, which is the default and the one to reach for first: ```sh sh "<skill-dir>/scripts/run.sh" path/to/draft.md ``` The judgment pass, only when the user has asked for it: ```sh sh "<skill-dir>/scripts/run.sh" --judge path/to/draft.md ``` Directories work in place of files. Several paths work too. Check the file the user asked about and nothing else. A file they did not name is not yours to send. ## Rules about the judgment pass Run the free pass as often as it is useful. It is local and free. The judgment pass sends the draft off the machine, so it is the user's call and not y