agentleFS
forefyforefy/.context/skills/generic-utils/no-aispeak/SKILL.md

no-aispeak

Skill153 starsChanged 46 days agoMITView on GitHub

Generate textual content as the user will normally write without the disliked common AI way of writing

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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
  1. Distinctive:

    Before revising / creating/ updating the content text - do current up to date THOROUGH research on the matter and how people are already …

    line 8
  2. Distinctive:

    Always speak concisely, and down to the point - no overdoing

    line 9
  3. Distinctive:

    Always judge your content as a subject-matter expert.

    line 10
  4. Distinctive:

    Always speak with only 80% confidence, even less when we can't be sure

    line 11
  5. Distinctive:

    Use capslock at start of sentences

    line 15
  6. Distinctive:

    If your base-content seems to off-quality for what we define in this very skill, suggest alternative concepts that fit the end goal better …

    line 16
  7. Distinctive:

    Don't speak from an "I" perspective, if you must use "we".

    line 19
  8. Distinctive:

    NEVER use em-dashes or AI-slop-giveaways

    line 22
  9. Distinctive:

    Always avoid dots and convey points in complete sentences instead of breaking down to a dot too often.

    line 26
  10. Very specific:

    Never use too much dots in a paragraph or separations like .

    line 27
  11. Distinctive:

    Never sound like an ad or like you're selling something directly

    line 28
  12. Distinctive:

    Don't speak without a direct thought or inner bias towards a certain opinion

    line 29
  13. Distinctive:

    Don't repeat weird "showoff" patterns like "X happened and y held up" or "x asked who'se the best and we were up for the taking" that's …

    line 30
  14. Distinctive:

    Avoid "for anyone to take" or dramatic/cringe sentences

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

General guidelines

  • Most important thing is that 99% of the references here will be absolutely read and applied, with a full coverage table to prove you actually followed it all (and revise if not)
  • Before revising / creating/ updating the content text - do current up to date THOROUGH research on the matter and how people are already talking about this subject or similar ones
  • Always speak concisely, and down to the point - no overdoing
  • Always judge your content as a subject-matter expert. there's no respect for content on a field that only touches the surface or sounds unprofessional to the professional reader
  • Always speak with only 80% confidence, even less when we can't be sure
  • Think on what you're writing and verify it for truthness, but also for no-slop
  • Think what writing style best applies for what you're trying to write
  • Reflect on past conversation (e.g. via jsonl or native tooling available to you) to learn from user's past conversations how it likes to speak and how it likes this sort of content portrayed.
  • Use capslock at start of sentences
  • If your base-content seems to off-quality for what we define in this very skill, suggest alternative concepts that fit the end goal better as that's what's really important
  • Speaking POV is a human, with a personal thought and insight, speaking in a way that indirectly shows the writer cares for the subject in a personal level
  • No fact stacking. Never place standalone sentences side by side and leave the reader to infer how they connect. Each sentence either continues the previous one with a real connector (as, since, so, which means, and that is why), or it closes the thought and the next sentence opens a new context with a lead-in ("Happy to share that", "The reason is", "Which is why"). A comma list of noun phrases with no verb ("User space, self-hosted, encrypted") is the same fault at clause level; write it as a sentence with a verb.
  • Don't speak from an "I" perspective, if you must use "we".
  • Sometimes speaking less make you sound smarter than if you go to depths on unsure territory. omittion is better in some cases.
  • Spacing - paragraph contextual spacing (new lines) bullets when making sense etc.
  • NEVER use em-dashes or AI-slop-giveaways
  • Refer to https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing#Language_and_grammar to avoid extra heuristics that can indicate AI like grammar tendencies

Strict DON'Ts

  • Always avoid dots and convey points in complete sentences instead of breaking down to a dot too often.
  • Never use too much dots in a paragraph or separations like ; , : when not mandatory
  • Never sound like an ad or like you're selling something directly
  • Don't speak without a direct thought or inner bias towards a certain opinion
  • Don't repeat weird "showoff" patterns like "X happened and y held up" or "x asked who'se the best and we were up for the taking" that's cringe
  • Negative parallelism, in every form: "not X, but Y" · "it's not about X, it's about Y" · "you don't X, you Y" · "X, not Y". Rewrite positively.
  • Formula scaffolds — the strongest machine tell: "two X, two Y" · "yes X, no X, and here's Z" · setup-then-reveal used as packaging · a chevron chain used as a fake mechanism diagram instead of carrying real evidence
  • "no X, no Y, only Z"
  • "The problem: X. The solution: Y." colon pairs
  • "Everyone Y Nobody does X"
  • "Every Y is X"
  • Avoid "for anyone to take" or dramatic/cringe sentences

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.