declauding
/declauding
Uruchamia przegląd stylu na szkicu tekstu, który ma przeczytać inny człowiek, zanim trafi do publikacji, np. opisu PR albo raportu.
- Autor
- oaustegard ↗
- Repozytorium
- claude-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 27
- Skrypty
- 6
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 6 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/declaude_diff.py, scripts/declaude_lint.py, scripts/declaude_rank.py, scripts/declaude_review.py, scripts/fresh_eyes.py, tests/test_fresh_eyes.py
Co robi i kiedy
Uruchamia przegląd stylu na szkicu tekstu, który ma przeczytać inny człowiek, zanim trafi do publikacji, np. opisu PR albo raportu.
Wyzwalacze z opisu
Oryginalny opis (EN)
Load it without being asked at the start of any task whose deliverable is prose that another person will read, such as a PR description, commit message, README, doc, postmortem, blog post, issue or review comment, report, release note or essay, and run it on the draft before the text is pushed, posted, published or saved. Draft first without this skill in context, from a positive writing brief if one exists. Also use it when someone says "de-claude", "de-slop", "humanize this", "this reads like AI" or "make it sound human", or asks for a voice, tone or register edit. It rewrites the constructi
Jak działa
- Do not invent specifics
- The generative test
- Model profiles
- Author's writing sample
- Workflow
- Overcorrection
- Signs of a person writing
- Earned exceptions
- Annotated mode
- Calibration
Podgląd SKILL.md
---
name: declauding
description: Load it without being asked at the start of any task whose deliverable is prose that another person will read, such as a PR description, commit message, README, doc, postmortem, blog post, issue or review comment, report, release note or essay, and run it on the draft before the text is pushed, posted, published or saved. Draft first without this skill in context, from a positive writing brief if one exists. Also use it when someone says "de-claude", "de-slop", "humanize this", "this reads like AI" or "make it sound human", or asks for a voice, tone or register edit. It rewrites the constructions that mark prose as model-written into plain technical prose, and checks that the rewrite kept the draft's claims. The constructions include staged reveals, verdict headers, aphoristic closers, "it's not X, it's Y", em-dash drama, forced triads, flat-certainty adverbs, noun stacks and dropped 'that'. Do not use it on fiction, poetry, code or quoted text. For a full adversarial review of a deliverable, use challenging.
metadata:
version: 0.14.0
---
# Declauding
Turn LLM-shaped prose into prose that a human technical writer would have written.
It has two output modes. **Clean** (the default) returns only the rewritten
text. **Annotated** returns a single-file HTML artifact: the rewritten text with
every changed passage marked, and for each mark the original, the tic's name and
the reason it goes. A toggle hides the marks so the result can be read straight
through.
What you deliver depends on how the skill was called:
- **Pasted text** (default) — the user gives text in the conversation. Return
the rewrite, plus a short list of what changed if the edit was substantial.
- **File** — the user points at a path. Rewrite the file in place and report a
summary in the conversation rather than pasting the whole result back. Edit
prose only: leave code blocks, frontmatter, data, link targets and quoted
specimens alone.
- **Embedded** — another skill or agent is calling this as one step of a larger
job (a PR description, a commit message, a doc). Return the final text and
nothing else. No preamble, no summary, no tic list.
## Do not invent specifics
The rewrite must not contain a fact, name, number, date, quote or citation that
is not in the source. A register pass is prone to this, because the fix for a
vague sentence is a specific one, and that specific has to come from the source
or from the author.
*Experts believe it plays a crucial role* becomes *the sources here do not say
who studies it*, or gets cut. It does not become *researchers at Lanzhou
University* unless the source says so. When a sentence needs real-world detail
to work, ask for it or write the plain version without it.
Opinions and stance count as voice rather than fact. Keeping the author's
judgment is required (see Overcorrection); adding a factual claim they did not
make is a defect even when the result reads more human.
## The generative test
Most entries in `references/register.md` (the staging, flat-certainty and
confiding families) describe one habit: building a sentence so the reader feels
a finding arrive, instead of stating the finding.
Apply one test to each sentence: is it saying the thing, or performing having
had the thought? Rewrite the second kind so that it says the thing.
The register has five families. Read the one the draft needs first.
| Entries | Family | Mechanism |
|---|---|---|
| 1–23, 37–42 | Staging | The sentence performs a finding arriving: reveals, verdict headers, aphoristic closers, welded epigrams |
| 24–36 | Encyclopedic and chatbot | Nothing is staged; the writing runs on defaults: copula avoidance, participle tails, forced triads, chatbot residue |
| 43–47 | Flat certainty | This skill's own output. An adverb, compound or absolute negative stands in for evidence: `plainly`, `quietly`, `refusal`, `re-derived`, `byte-identical`, `nothing` |
| 48–52 | Confiding essayist | Staging aimed at the reader's trust: announced honesty, stranded auxiliaries, obituary headlines. From Simon Willison's [llm-cliche-highlighter](https://github.com/simonw/tools/blob/main/llm-cliche-highlighter.html), updated 2026-08-27 |
| 53–56 | Compressed syntax | Nothing is staged; a claim is packed into fewer words than a reader can parse: noun stacks, verbed nouns, dropped *that*, a subject waiting behind a list for its verb. The fix makes the sentence longer. From [arXiv 2610.29162](https://arxiv.org/abs/2610.29162) |
A clean pass tends to land in the flat-certainty register, which is also the
fastest-growing cluster of GitHub pull request descriptions: 0.70% of early
2025 and 39.5% of August 2026 (`references/corpus.md`). Its version of the test
asks whether a sentence states the finding or performs having settled it. Fix
it by checking that each adverb, compound or negative has evidence behind it.
Do not put the staging back.
## Model profiles
When you know which model wrote the draft, read its file in
`references/models/` before step 2. When you know which model you are, read your
own file too. Each file has two sections: what to look for in that model's
drafts, and what to check in your own rewrite when you are that model.
| Model | File | Where its tics sit |
|---|---|---|
| Opus 5, Opus 5.5 | `models/opus-5.md` | Headers and paragraph closers; the linter misses most of them |
| Opus 4.6, 4.8 | `models/opus-4.md` | Closers, em dashes, one metaphor reused across paragraphs |
| Sonnet 4.6, 5 | `models/sonnet.md` | Em dashes and negation-first reversals |
| Haiku 4.5 | `models/haiku.md` | The encyclopedic family; the linter catches most of it |
| Sonnet 5.5, Haiku 5.5 | not yet profiled | Use the same tier's file as a prior and expect drift |
| Fable 5.1 | `models/fable.md` | Bolded list leads and takeaways |
When Claude is cleaning its own draft, one file covers both sections; run step
2b in a subagent or separate context. When the author is unknown or human, skip
the profiles.
On any model's draft, check the opening for a contents-list standfirst (entry
42): *here's what happened, and what we should have measured*.
## Author's writing sample
If the user supplies a sample of their writing, read it before editing and match
its habits: sentence lengths, paragraph openings, punctuation, recurring
phrases, vocabulary level. Do not upgrade casual words, regularize deliberate
quirks, or apply a register rule the sample contradicts.
The sample wins over every rule here, including the em-dash density guard in
entry 16. If the author uses em dashes at three per hundred words, that is their
voice, and scrubbing the tell would make the text less like them and no more
human. The same holds for their existing published work when it is available and
the current draft is not.
## Workflow
Script paths below are relative to this skill's directory. From any other
working directory, prefix them with `/mnt/skills/user/declauding/`.
**1. Read the whole piece before editing anything.** Tics carry factual errors.
A sentence written to sound important is disproportionately likely to be wrong,
because it was built for shape rather than for accuracy. Designations of the form
*the X that answers the real question* frequently designate the wrong X, and the
draft itself often contradicts them a paragraph later. Note contradictions now;
they are the most valuable thing this pass produces.
**1a. Find the point before fixing sentences.** Write, in one sentence of your
own, the thing the draft wants the reader to come away knowing. If you cannot,
or the draft spends most of its length on material that does not bear on that
sentence, the problem is above the sentence level and the sentence pass will not
fix it: every sentence can be locally fine while the piece says little, which is
why readers of model drafts report reaching the end of a page and not knowing
what it said. In that case, say so, get the point from the author when it is
theirs to supply, write that sentence first, and rebuild from it, keeping only
the material that supports it. Rewriting from the point is cheaper than
sentence-by-sentence repair on a draft like this, and is what editors of model
prose report doing anyway. On a draft whose point is clear, this step takes one
sentence and moves on. Hand the stated point to step 4a's reader as well: the
newcomer read checks that a reader who does not share your context can find it.
**2. Run the mechanical scan.**
```
python3 scripts/declaude_lint.py DRAFT.md
python3 scripts/declaude_lint.py DRAFT.html # HTML is flattened automatically
python3 scripts/declaude_lint.py DRAFT.md --skip-quoted # if the draft quotes bad prose
python3 scripts/declaude_lint.py POST.md --statement-headers # house style writes headers as findings (entry 7)
```
It flags greppable tells with line numbers and categories, plus four shapes that
are not lexical: forced triads in both their comma-list and anaphora forms,
one-line-paragraph beats, fragment runs, and constructions the document uses more
than once. The `reuse` block is the cheapest signal it produces, because a
construction used twice is a habit and counting is free.
The scan makes no judgments, so everything it flags still needs the
sentence-level test. It finds roughly two thirds of what a careful pass finds.
The third it misses takes the most effort to find by hand: staged paragraph
shape, staged closers, dressed metaphor and every earned exception. Step 2b
covers part of that third, and the rest is yours. A clean report is not evidence
that the draft is clean. Expect a clean report on Opus 5 drafts, which stage heavily in
shapes the scan cannot see.
Use `--skip-quoted` on any draft that quotes bad prose as a specimen. Without it
the scan reports the draft's own examples, and real passes have lost time to
that.
HTML input is flattened before scanning: `<h1>`–`<h6>` become headings so the
header rules see them, and a `.subtitle`, `.eyebrow` or `.post-meta` element is
treated as a heading too, because a reader takes a subtitle as a header. Force with `--html`, disable with `--no-html`. Reported line numbers
refer to the flattened view.
The `corpus-register` density line locates a register and does not identify an
author. Above roughly 1.0 per 100 words the draft sits in the cluster's register,
and a person who chooses that register scores there too, so the line is a cue to
read entries 43 to 47 and never a licence to cut `nothing` or `measured` on
sight. `references/corpus.md` has the figures.
Lint every string that reaches the reader, not only the body file. Page titles,
subtitles and deck headers are prose, and a builder that takes them as CLI
arguments rather than from the file will hide them from this scan.
**2a. Optionally, rank the sentences.**
```
python3 scripts/declaude_rank.py DRAFT.md --top 15
```
Sorts sentences by how staged they look, using a fitted direction in embedding
space (the mean of `embed(was) - embed(now)` over the register's before/after
pairs). It shortlists and decides nothing. On the one pass it was measured
against it ranked all nine edited sentences at a median of 13 of 53, where the
regex scan had found one of the nine. It cannot score documents. Needs torch and
transformers; every other stage is standard library. `references/preservation.md`
has the numbers.
**2b. Run the structural review.**
```
python3 scripts/declaude_review.py DRAFT.md
```
This stage covers part of what the scan misses. It extracts the slots that regex
cannot judge and sends only those to a model, along with the structural entries
from `references/register.md`. The slots are every header, the opening sentence,
each closing sentence and each isolated one-sentence paragraph. Sending slots
instead of the whole document keeps the payload small enough to run on every
draft. Use `--emit-prompt` where no API key is available, and `--slots` to see
the extraction alone.
The scan and the review catch different things. The scan finds a verdict header
(entry 7) deterministically and over-flags commas, including the ones that belong
to a citation. The review reads a comma in context and finds the aphoristic closer, which
no regex reaches. Run both.
Run stage 2 in a context that did not write the draft. A model reviewing its own
prose is the actor that chose the words. With `--emit-prompt`: if you did not
write the draft, answer the prompt yourself; if you did, hand it to a subagent.
If you wrote it and cannot spawn one, answer it anyway and say in your report
that the review was not independent.
For a full-document register review against a named voice signature, use the
`challenging` skill's `prose-register` profile instead. It checks for positive
markers of the voice, drift across the piece and an imposter test, and costs
more to run than this script.
**3. Sentence pass.** For every sentence, in order: stating or staging? Load
`references/register.md` for the catalogue of tells and their fixes, and
`references/exceptions.md` before deleting any flagged shape — it lists when
each shape carries a claim. Start with the family the draft needs: the author
model's profile in `references/models/` names it; on a draft this skill or another model already
cleaned, read 43 to 47 first; on a personal essay, a launch post, or anything
addressed to the reader as a confidant, read 48 to 52 first; on a chat reply or a
coding-session report, read 53 to 56 first.
**4. Structure pass.** Headers (are they labels or verdicts?), paragraph breaks
(is an isolated line a real pivot or a drum roll?), fragment runs, rhetorical
questions, and the closer (does the last paragraph paraphrase the subtext of
what preceded it? delete it). On a README or other doc, check that it describes
the thing as it is now. How a section or feature came to be, what an earlier
version did and what was measured before a change belong in the changelog, or in
the commit message when there is no changelog. Readers come to a README for the
current snapshot and rarely open the history (entry 34).
**4a. Newcomer read, when the draft describes something that just changed.**
Run this step on a README, doc, page or results section written or revised right
after a change to the thing it describes. The failure it catches: text that
leans on a version the reader never saw, because it was written with the
change in mind. No sentence-level pass sees it. A bad example: a game's
start-screen step reading *pick your options here, upright*, written after the
options moved off a sideways screen. *Here* and *upright* only mean something
to a reader who saw that screen; the step a newcomer needs is *lock rotation in
portrait, then choose your options below*. The same failure shows as a README
that explains how a bug was fixed where the reader needs to know how the
feature behaves, or as one section updated while another still describes the
old behaviour. Words like *now* and *no longer* are rarely present, and
automatic judges missed it (`references/fresh-eyes.md`). A reader who never
saw the old version catches it. You cannot be that reader for your own text, so
hand the text to one:
```
python3 scripts/fresh_eyes.py packet README.md docs/setup.md
```
Pass every reader-facing file the work touched. The script writes the packet, a
single Markdown file holding those files' text as it stands (Markdown whole,
visible text only for HTML), and prints its path and a prompt. Send the prompt
verbatim to a subagent that has not seen this conversation; the subagent reads
the packet from disk and lists what a newcomer would stumble on, section by
section. Fix each point or say why it stands; the step is done when a read of
the final text comes back with nothing you have not answered. Where no
subagent tool exists, read the packet yourself top to bottom, with nothing else
open, list every phrase that leans on something the packet never says, and
report that the read was not independent.
When this skill is installed as a plugin, a Stop hook enforces the step: a turn
that changed visible prose in a `.md` or `.html` file cannot end until a
subagent has been sent that prompt after the last edit to those files. It skips
changelogs, Log sections, generated pages and edits under 20 characters of
prose, and logs each run to `~/.claude/fresh-eyes-log.jsonl`, which shows
whether the hook runs in a given environment.
**5. Check what the edit did.**
```
python3 scripts/declaude_diff.py SOURCE.md REWRITE.md
python3 scripts/declaude_diff.py --git path/to/draft.html --ref HEAD
```
Run this before reporting the pass done. It compares source against rewrite for
numbers, names, quotations, code and link targets by presence, and for
superlative, scope, negation and hedge constructions by count, and reports what
the edit lost and what it invented. It counts constructions rather than tokens
because rewriting "the format that most invites staged reveals" as "more than
most formats do" keeps the word and drops the ranking.
An embedding similarity does not substitute for it: on the three real cases in
`references/preservation.md` the lossy rewrite scores *higher* cosine to the
source than the faithful one. Paraphrase invariance is what an encoder is trained
for, and dropping a ranking word is a paraphrase by that measure.
The script guards claims and ignores voice, so treat each finding as a question
to answer, and pass `--waive` for a rephrasing it cannot see through. Then check
the rewrite for four failure modes, all of them common:
- Content lost. Ask it as a question and answer it claim by claim, not paragraph
by paragraph: *does the rewrite drop a claim the source made?* A dropped
superlative leaves the paragraph looking intact, which is why the
read-through misses it. Every fact, number, caveat and hedge-with-content must
survive. Keep a real qualification even when a tic wraps it.
See Earned exceptions for what hides inside a watched phrase. You may change
the structure: merge or split paragraphs, compress the dull parts, and dwell
where the author would. When keeping the information and mirroring the
original's shape pull against each other, keep the information.
- Claims changed. Rewriting "the drop is largest where chains are longest" into
"long chains cause the drop" is an edit that invents a finding. Register only.
- Facts invented. Ask it directly: does the rewrite state any name, number, date
or citation that is not in the source? See "Do not invent specifics" above.
- Mush. See Overcorrection below.
**6. Report factual problems separately.** Never silently fix a contradiction
found while editing. The author needs to know their draft disagreed with
itself, and only they can say which version is true.
## Overcorrection
The failure mode of this skill is prose stripped of confidence, rhythm and
personality until every sentence is the same length and the writer has no
opinions. That is worse than the tics.
- Do not compress what is left. A rewrite that cuts staging tends to stack three
nouns where a phrase stood, drop *that* from a long clause, or press a noun
into service as a verb. If the rewrite is shorter and takes longer to parse,
it is worse (entries 53 to 56).
- Keep the certainty. "Class imbalance breaks the metric before overfitting
does" is flat *and* certain. Aim for prose that is plain and still sure of
itself.
- Do not delete first-person judgment. "I did not expect the overlap to survive
a 3x range in bits per weight" is exactly right — specific, falsifiable,
personal. Human technical writers state preferences and surprise directly.
- Do not enforce uniform sentence length. Short for facts, compound for
dependencies and caveats. Variation carries information; monotony is its own
tell.
- Do not delete metaphor. Delete metaphor that is *doing significance work*
where a plain noun fits. A metaphor that is the clearest available description
stays.
- Keep digression, asides and mild informality. Cut symmetry, antithesis and
balanced parallel clauses.
## Signs of a person writing
These are evidence of a person writing. Editing them out is how a register pass
makes a draft worse, and each one is easier to destroy than to put back.
- **Specific, hard-to-fabricate detail.** A street name, an odd quote, "the guy
who used to run the build before he left". Models tend to round specifics off,
and people tend to keep them.
- **Mixed feelings and unresolved tension.** *I think this is mostly right and it
still bothers me and I cannot say why.* Clean takes are the model default.
- **Genuine self-interruption.** A parenthesis that corrects the sentence it sits
in, an aside that goes nowhere. Models rarely interrupt themselves.
- **Repetition of a word** where a synonym would be worse. That is entry 27 read
in the right direction.
- **Uneven depth.** Three paragraphs on the part the author cares about and one
line on the part they do not is how people write.
- **Dated and subcultural references.** Slang or in-jokes pinned to a year.
Things that are not tells on their own, and should not be edited on their own:
polished grammar, formal vocabulary, a mixed casual-and-formal register, curly
quotes, a single em dash, one short emphatic sentence, an unsourced claim, a
salutation or sign-off. Look for clusters. A single em dash is punctuation. Em
dashes together with a forced triad, *vibrant tapestry* and a Conclusion section
are strong evidence of model text.
Do not edit a watched phrase inside a quotation, a title, a proper name, or an
example where the phrase is being discussed rather than used. The linter's
`--skip-quoted` does this mechanically; do it by eye too.
## Earned exceptions
Every entry fires on a shape, and a shape sometimes carries a claim. Cutting it
then removes content while looking like it removed only style, and the result
reads fluently, so a read-through does not catch it. `references/exceptions.md`
has a banned-when and earned-when row for each shape; check the row before
deleting. Two common cases: "X rather than Y" is earned when the reader was
already holding Y, and a short closer is earned when it states a fact
("Default retries are back to 3.") rather than a moral.
Modifiers inside a watched phrase carry content. "The single most important
new build" ranks that item against every other item; "the important new build"
ranks nothing. "Simultaneously X, Y and Z" claims the three hold at once; "X, Y
and Z" does not. Superlatives, rankings, simultaneity, scope words, and the
condition attached to a hedge all live inside phrasings this skill cuts.
## Annotated mode
Read `references/annotating.md`. It specifies the artifact: markup for changed
spans and edit notes, the toggle, the tic-tally table, and how to handle
passages deliberately left alone.
Rules that make the annotation useful rather than decorative:
- Quote the original verbatim in every note, so the reader can check the edit.
- Name the tic using the register's vocabulary so the reader accumulates a
vocabulary rather than 40 unrelated opinions.
- Say why *this instance* is a tic. Explaining the category teaches nothing
about the text in front of the reader.
- Mark what was kept and why, so the reader learns what works as well as what
fails.
- Bundle stacked tics into one note per passage. Do not split a sentence into
four notes to inflate the count.
## Calibration
When a draft's register is unclear, read real prose in the target
genre before editing — the author's own earlier writing, or a well-known human
writer in that domain. Human technical prose runs on, digresses, states
preferences without justifying them, and repeats a word rather than reaching for
elegant variation. Its sentence length follows what each sentence has to say.
## Scope
Applies to: blog posts, READMEs, PR and commit descriptions, reports,
documentation, essays, release notes, technical explainers.
Do not apply to: fiction and poetry (different register entirely), direct
quotations, other people's text being quoted, marketing copy where the client
wants the staging, or anything where the "tic" is the author's established
voice. Ask before running this on someone else's writing rather than a draft.
## Extending
The register is a working document, not a standard. Adding to it:
1. Add the specimen to `tests/sample-tics.md`, verbatim from real prose.
2. Add a register entry: tell, why, fix, and the real before/after. Entries
without a before/after get argued about instead of applied.
3. If the tell is lexical, add a rule to `scripts/declaude_lint.py` and confirm
`tests/sample-clean.md` still reports zero. That file is human-written prose,
so a rule that fires on it is a bad rule. Holding the false-positive budget
keeps the linter worth running.
4. Bump `metadata.version`.
To add a model profile, sample that model with no voice instruction and score
it as `oaustegard/experiments` `model-register-drift/` did. Write the file as
instructions: where to look, what to cut, with one specimen per rule. Leave the
scores in the experiment; the file gets one evidence line. Add a row to the
Model profiles table.
Promote a phrase to its own register entry only after it appears in two real
drafts. An entry written from one sighting matches that phrase and misses its
paraphrases.
Pliki w paczce (27)
- CHANGELOG.md 41 KB
- README.md 7 KB
- SKILL.md 25 KB
- assets/annotated.template.html 5 KB
- assets/staging-axis.json 5 KB
- hooks/hooks.json 1 KB
- references/annotating.md 3 KB
- references/corpus.md 5 KB
- references/exceptions.md 6 KB
- references/fresh-eyes.md 2 KB
- references/preservation.md 5 KB
- references/register.md 55 KB
- references/models/fable.md 1 KB
- references/models/haiku.md 1 KB
- references/models/opus-4.md 1 KB
- references/models/opus-5.md 3 KB
- references/models/sonnet.md 1 KB
- scripts/declaude_diff.py 12 KB
- scripts/declaude_lint.py 52 KB
- scripts/declaude_rank.py 7 KB
- scripts/declaude_review.py 12 KB
- scripts/fresh_eyes.py 22 KB
- tests/sample-clean.md 2 KB
- tests/sample-structure.html 1 KB
- tests/sample-structure.md 1 KB
- tests/sample-tics.md 10 KB
- tests/test_fresh_eyes.py 14 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · oaustegard/claude-skills | 100 | MIT |
| Calvin-LLC/skills | 100 | MIT |
| oaustegard/claude-skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 1c9254e73b50 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 80writing:no-diary
Usuwa z tekstu, na przykład opisu PR albo dokumentacji, zbędny żargon i opis procesu pracy, zostawiając sam wynik. - 100declaudify
Sprawia, że tekst napisany przez AI jest prosty i najważniejsze zdanie stoi na początku, bez zmiany treści. - 100anti-slop
Oczyszcza tekst ze sztucznych zwrotów AI, nie zmieniając jego treści, po polsku i po angielsku, np. przed wysłaniem opisu PR. - 100unslop
Usuwa ślady AI z tekstów czytanych przez ludzi, jak opis PR, commit, README czy odpowiedź w recenzji, przed przekazaniem. - 90writing-axes
Prowadzi szkicowanie, recenzję i przepisywanie tekstów dla ludzi od odbiorcy i celu: wpisy, README, artykuły, maile, dokumentacja, runbooki, komunikaty błędów, notatki wydań i tytuły. - 90storyscope-writing
Pisze i poprawia tekst tak, by nie nosił strukturalnych śladów AI mierzonych w StoryScope: e-maile, dokumentacje, raporty, eseje.