npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kensio/technical-prose-style

v1.18.1

Published

A measured prose style for documentation, with a checker calibrated on human technical writing.

Downloads

2,726

Readme

@kensio/technical-prose-style

A technical writing style for documentation, packaged as an agent skill. It targets the constructions that make unedited LLM prose tiring to read, and it ships the measurement that picked them.

The goal is prose that costs the reader less. Concealment is a different aim and out of scope. Text that follows every rule here is still identified as machine-written by a commercial detector. Six rewritten documents were put through one to check.

Most writing guidance for LLMs is a list of banned words. Word lists can be obeyed completely while the prose still reads as machine-written, because the tells are syntactic. This skill was built by measuring 192,000 words of Claude-written documentation against 66,000 words of Django, Go, Rust and Python documentation, and keeping only the patterns where the two differed by a factor of two or more. Thresholds are set so that no human document in the corpus fails and every LLM document does.

Install

Into any agent that reads SKILL.md:

npx @kensio/skills add technical-prose-style

That copies the skill directory into .agents/skills/, where Codex, Cursor, Copilot, Gemini CLI and the other implementations of the specification look for one. Pass --agent claude for .claude/skills/, --agent copilot for .github/skills/, and --user to install it for every project at once.

Claude Code also takes it as a plugin:

claude plugin marketplace add KensioSoftware/kensio.ai
claude plugin install technical-prose-style@kensio

Or pin it in a repository as a dependency:

npm install @kensio/technical-prose-style

Every skill is also published as a zip on each release, for a machine with no npm reach. Unzip it into .agents/skills/ and it is installed.

The patterns

Significance tail. A fact, then a comma, then a clause explaining why the fact matters. Measured at 8.1 times the human rate. State the fact and leave the working out.

Contrastive definition. Defining a thing by the alternative it displaces, with rather than or instead of. 6.2 times.

Contrastive coda. The same move wearing a comma, as in assert behaviour, not call counts. 8.3 times, and the sharpest separation in the study. It went undetected for four releases, because the regex above only ever matched the two-word forms.

Negation framing. Sentences built on nothing, is not, does not. 5.2 times. "Nothing here replaces the process clock" is "time belongs to this instance", written backwards.

Appositive tail. A trailing , which is or , which means that comments on its own sentence. 5.3 times.

Colon explainer. A colon joining a claim to a restatement of itself. 2.3 times, and it rose as em dashes were banned. The construction moved and never went away.

One name for one thing. Distinct words per 100 is the cleanest separator found. 15 human documents average 0.628 and none exceeds 0.664, while 55 LLM documents average 0.685 and none falls below 0.658. Human technical writing names a thing and goes on naming it that. It ships as advisory, because padding with repeated words would move the number the right way and make the prose worse.

Short listing strings

The rules above are calibrated on documents of 200 words and more. A package description or a card subtitle is a different genre, and the skill carries a separate section for it. Forty descriptions from long-established npm packages have a median length of seven words, and not one of them uses the Thing for X: doing A, doing B, and doing C shape that an LLM reaches for every time.

What it tells you to leave alone

The measurement also found what fails to separate good prose from bad. That turns out to be most of a normal style guide.

  • Sentence length. 20.9 words against 19.8. Long sentences were slightly more common in the human corpus.
  • AI vocabulary. Django and Effective Go use powerful, robust, crucial and friends ten times more often than the Claude corpus did. A word list measures compliance with a word list.
  • Em dashes. Punctuation is where the habit lands. Closing one mark moves it to the next.
  • The rule of three and parataxis. A spaCy dependency parse found the exemplars using prose triples twice as often and parataxis seven times as often. Both are marks of the human corpus.

The checker

The skill includes a checker that scores markdown against every pattern and prints the worst sentence for each one over threshold.

node skills/technical-prose-style/scripts/prose-check.mjs docs/

Rates are per 1000 words, compared against the human baseline. --json gives machine-readable output and --examples N prints more samples. A non-zero exit means something is over a fail threshold. The checker drops into CI as it stands.

Full method, corpora and dropped candidates are in reference/measurements.md.

Part of kensio.ai. Licensed under the Apache License 2.0. See the LICENSE in the repository root.