Individual skill
no-aispeak
Generate textual content as the user will normally write without the disliked common AI way of writing
skills/generic-utils/no-aispeak/SKILL.md
Source commit 0c1bc93fd5124e7a862d61c1b434f32ba8790e3a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 153
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-security Repository topic
- ai-skills Repository topic
- security-skills Repository topic
- dynamic-workflow Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,615 bytes
Read excerpt
## 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".