voice
Skill2 starsChanged 17 days agoMITView on GitHub
Bring a page in this repository to the atlas voice, or check a page before opening a PR. Use when the user says "bring this page to the atlas voice", "check a page before opening a PR", "прогони страницу через голос", "почини стиль страницы", or when the voice linter fails in CI.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- Deupaxx/EveryDay-Writertheir own version, first seen Nov 16, 2026
- ShiroTsuma/Voice-MCPtheir own version, first seen Nov 15, 2026
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
- codeboehm/maximtheir own version, first seen Nov 15, 2026
- guaardvark/guaardvarktheir own version, first seen Nov 13, 2026
- BermanRoman/promt-seo-geotheir own version, first seen Nov 8, 2026
Used with
Projects with it also use emotion, claude-buddy and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
igoroliveirgSkillemotion
Identifies and applies the right emotional drivers for each audience and product in copy. Activate when the user asks how to make copy more emotional, how to connect with the reader, which triggers to use, how to awaken desire, or any emotional appeal technique in persuasive text.
Also in 4 projects that use this
autonomous-aiSkillclaude-buddy
Coordinate with the Claude Buddy companion (Claude Desktop + Claude Code on the user's Mac) — voice-approve tool permission prompts and stay aware of Claude activity.
Also in 3 projects that use this
autonomous-aiSkillface-enroll
Manage the device's face recognition roster — enroll new faces (3 paths: user-supplied photo, agent-captured snapshot on user request, or HAL's familiar-stranger prompt) and maintain the enrolled set (status / remove / reset). All enrolled persons are friends; strangers stay unnamed until promoted via one of the enroll flows.
Also in 3 projects that use this
- +9 more from autonomous-ai
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- autonomous-ai/autonomous-os★ 569same name
- autonomous-ai/lampOS★ 569same name
- autonomous-ai/Physical-AI-Operating-System★ 569same name
- guaardvark/guaardvark★ 320same name
- jvm-skills/jvm-skills★ 140same name
- simota/agent-skills★ 99same name
- crisandrews/ClawCode★ 64same name
- Deupaxx/EveryDay-Writer★ 39same name
- ggombee/code-forge★ 18same name
- shreyaskarnik/voice-mcp★ 17same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Run the repository's own linter against a page, then fix what it reports against STYLE.md.
- Very specific: line 25
Read the target page's frontmatter.
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/voice
Run the repository's own linter against a page, then fix what it reports against STYLE.md.
The rules live in STYLE.md at the repository root. Read it. Do not restate its rules here or in your
answer — quote the section the linter names and fix against that section.
Before you touch anything
- Confirm you are inside the
pet-project-atlasrepository.scripts/lint-voice.mjsandSTYLE.mdboth have to exist. If they do not, stop and say so — this skill only works here. - Read the target page's frontmatter.
voice: guestmeans stop. A guest case keeps its author's voice: the ban list, the page shape and the length rules do not apply to it. Report that the page is a guest case and change nothing in its prose. The number rule still applies to guest pages, so an unsourced-number error on a guest page is a real error — fix that one by adding a source or deleting the number, and nothing else.
Run the linter
The script takes either a directory or a single file. Point it straight at the page you are fixing:
node scripts/lint-voice.mjs src/content/docs/<section>/<page>.mdFor the whole repository, use the package script:
npm run lint:voiceOutput shape, one finding per line:
<file>:<line>: <what broke>. <what to do>. (STYLE.md §N Section)Errors exit non-zero and fail the build. Warnings keep the build green.
Fix each finding
Work one finding at a time, in the order the linter printed them. For each one open the section of
STYLE.md named in the parentheses and fix against it.
- §3 Ban list — a banned word is a symptom of a sentence with no claim in it. Replace the sentence with a concrete claim from the author's own log. A synonym from the thesaurus is not a fix.
- §2 Page shape — the four required H2 headings are matched literally, at level two, before any other H2. A heading with nothing under it counts as missing.
- §4 Numbers — either add the date to
updated:and the source tosources:, or delete the number. A URL goes in asTitle — https://…, and the title says why that link is there. Never soften a number into words. If you cannot find the source, the number goes. - §5 Length — a warning, not an error. Split the sentence. If a page throws many of these, say so: it usually needs cutting, not exceptions.
You may not invent a fact to satisfy a rule. If a fix needs a number, a source or a failure the author has not given you, ask for it. An unanswered question is a better outcome than a fabricated sentence.
Finish
- Re-run the linter on the same path. The page's rows must be gone.
Show the diff:
git diff -- <path>- Do not commit. Show the diff, name each change and the rule behind it, and wait for the author to confirm. Commit only after they say so.
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
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.

