Agent skill

Levyra Humanizer

Apply a compact final prose pass to Levyra pull request descriptions, release notes, and owner-facing writing so it sounds natural without changing facts, evidence, structure, or validation state.

MITAuto-check passedDevelopment

Install Levyra Humanizer

skills CLI

$ npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install LUC4N3X/Levyra-deepsound levyra-humanizer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/LUC4N3X/Levyra-deepsound.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/levyra-humanizer .claude/skills/levyra-humanizer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "levyra-humanizer" agent skill from https://github.com/LUC4N3X/Levyra-deepsound/tree/main/.agents/skills/levyra-humanizer into .claude/skills/levyra-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "levyra-humanizer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/LUC4N3X/Levyra-deepsound/tree/main/.agents/skills/levyra-humanizer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install LUC4N3X/Levyra-deepsound levyra-humanizer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LUC4N3X/Levyra-deepsound.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/levyra-humanizer .agents/skills/levyra-humanizer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "levyra-humanizer" agent skill from https://github.com/LUC4N3X/Levyra-deepsound/tree/main/.agents/skills/levyra-humanizer into .agents/skills/levyra-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "levyra-humanizer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install LUC4N3X/Levyra-deepsound levyra-humanizer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LUC4N3X/Levyra-deepsound.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/levyra-humanizer .cursor/skills/levyra-humanizer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "levyra-humanizer" agent skill from https://github.com/LUC4N3X/Levyra-deepsound/tree/main/.agents/skills/levyra-humanizer into .cursor/skills/levyra-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "levyra-humanizer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/LUC4N3X/Levyra-deepsound.git --path .agents/skills/levyra-humanizer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install LUC4N3X/Levyra-deepsound levyra-humanizer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LUC4N3X/Levyra-deepsound.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/levyra-humanizer .gemini/skills/levyra-humanizer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "levyra-humanizer" agent skill from https://github.com/LUC4N3X/Levyra-deepsound/tree/main/.agents/skills/levyra-humanizer into .gemini/skills/levyra-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "levyra-humanizer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install LUC4N3X/Levyra-deepsound levyra-humanizer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/LUC4N3X/Levyra-deepsound.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/levyra-humanizer .github/skills/levyra-humanizer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "levyra-humanizer" agent skill from https://github.com/LUC4N3X/Levyra-deepsound/tree/main/.agents/skills/levyra-humanizer into .github/skills/levyra-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "levyra-humanizer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install LUC4N3X/Levyra-deepsound levyra-humanizer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LUC4N3X/Levyra-deepsound.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/levyra-humanizer .opencode/skills/levyra-humanizer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "levyra-humanizer" agent skill from https://github.com/LUC4N3X/Levyra-deepsound/tree/main/.agents/skills/levyra-humanizer into .opencode/skills/levyra-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "levyra-humanizer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: levyra-humanizer
GitHub stars: 533
Token cost: ~719 tokens
SKILL.md length: 356 words
Files: 3
Skills in repo: 22
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Apply a compact final prose pass to Levyra pull request descriptions, release notes, and owner-facing writing so it sounds natural without changing facts, evidence, structure, or validation state.

Works in 4 steps: work only from the already-drafted text… → make one concise rewrite pass; → preserve all required Levyra template… → …
Tasks that involve Humanizing AI text
SKILL.md covers Goal, Non-negotiable claim parity, Natural prose pass and Embedded PR/release mode, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Levyra Humanizer is an agent skill from LUC4N3X/Levyra-deepsound. Apply a compact final prose pass to Levyra pull request descriptions, release notes, and owner-facing writing so it sounds natural without changing facts, evidence, structure, or validation state.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files.

It sits in Development, covering Humanizing AI text, Changelog and release notes and Pull requests. The repository describes itself as: Open-source music player for Android and Windows with no accounts or tracking. Built for quick discovery, synced lyrics, radio, and rich artwork ♫. The licence is MIT.

When your agent uses it

Tasks that involve Humanizing AI text
Tasks that involve Changelog and release notes
Tasks that involve Pull requests

Example prompts

“/levyra-humanizer”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

work only from the already-drafted text and its verified evidence;
make one concise rewrite pass;
preserve all required Levyra template sections and unperformed checkboxes;
return only the final text unless the caller explicitly needs a change summary.

What it can do on your machine

Read from SKILL.md and the folder at commit 35cd2be. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Levyra Humanizer loads about 719 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 356 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~719

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LUC4N3X/Levyra-deepsound at commit 35cd2be, republished under its MIT licence (© LUC4N3X). 356 words, ~719 tokens.

Download SKILL.mdSave it as .claude/skills/levyra-humanizer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: levyra-humanizer
description: Apply a compact final prose pass to Levyra pull request descriptions, release notes, and owner-facing writing so it sounds natural without changing facts, evidence, structure, or validation state.
license: MIT
metadata.version: 2.11.2-levyra-compact
metadata.upstream: blader/humanizer@e2e92e7b4b8229253ed5c8e81dc65463fdeddda5

Levyra humanizer

Goal

Make finished prose sound like a person wrote it while preserving every factual claim. This is a lightweight final pass, not a research, review, or reasoning stage. Do not reopen the codebase or load extra evidence merely to humanize text.

Non-negotiable claim parity

Keep every fact, number, date, path, version, test result, checkbox, citation, limitation, and risk state unchanged unless the source itself requires correction.
Never turn UNRUN, BLOCKED, FAIL, uncertainty, or missing evidence into a stronger claim.
Preserve required templates, headings, Markdown structure, code blocks, YAML, links, and release-note schema.
Do not invent context, praise, motives, benefits, sources, or validation.

Natural prose pass

Prefer simple verbs, concrete nouns, varied sentence length, and the writer's existing vocabulary. When a real writing sample is available, match its tone and punctuation instead of imposing a generic style.

Remove only clear AI-writing residue:

generic preambles, chatbot closers, fake-candid hooks, and "let me know" offers;
inflated importance, sales language, vague expert claims, and generic optimism;
filler, stacked qualifiers, forced groups of three, synonym cycling, and repeated headings;
excessive bold mini-labels, decorative emoji, and formulaic "not X but Y" phrasing;
em/en dashes when the writer's sample does not normally use them.

Keep technical language technical. Do not simplify a term when precision would be lost. One pattern alone is not a reason to rewrite natural prose.

Show full SKILL.md (132 more words)Show less

Embedded PR/release mode

For PR descriptions, release notes, commit-adjacent prose, and other embedded uses:

work only from the already-drafted text and its verified evidence;
make one concise rewrite pass;
preserve all required Levyra template sections and unperformed checkboxes;
return only the final text unless the caller explicitly needs a change summary.

Do not spend engineering context on examples of writing style. The final prose pass should be much cheaper than the engineering work it describes.

Final check

Before returning, verify: same claims, same validation truth, same required structure, no invented facts, no lost limitation, and no obvious chatbot filler.

Provenance

This compact Levyra adaptation keeps the useful principles of the MIT-licensed blader/humanizer method while removing its large example catalog from the runtime skill body to reduce context cost.

Files

SKILL.md and 2 other files in .agents/skills/levyra-humanizer of LUC4N3X/Levyra-deepsound.

SKILL.md
LICENSE
REUSE.toml

Open the folder on GitHubat commit 35cd2be

Compare with similar skills

Levyra Humanizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Levyra Humanizer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Levyra Humanizer this skillLUC4N3X/Levyra-deepsound	533	—	~719	Automated safety check: Pass	MIT	today
Avoid AI Writingwshobson/agents	40k	—	~1.9k	Automated safety check: Pass	MIT	4 days ago
Simple History Voicebonny/WordPress-Simple-History	317	—	~775	Automated safety check: Pass	None	2 days ago
StarRocks Release NotesStarRocks/starrocks	12k	—	~1.9k	Automated safety check: Notes	Apache-2.0	today
Opik Documentation Patternscomet-ml/opik	22k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
Change Documentation Writerjsmastery-pro/skills	1.5k	—	~2.4k	Automated safety check: Notes	MIT	2 mo ago

Similar skills

Avoid AI Writing
wshobson/agents
Audit and rewrite prose so it stops reading as machine-generated.
40k GitHub stars~1.9k tokensUpdated 4 days ago
DevelopmentAuto-check passed
Simple History Voice
bonny/WordPress-Simple-History
Pär's writing voice and per-text-type rules for Simple History, on top of the humanizer skill.
317 GitHub stars~775 tokensUpdated 2 days ago
Writing & ContentAuto-check passed
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
12k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check: notes
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
22k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Change Documentation Writer
jsmastery-pro/skills
Writes PR descriptions, changelog entries, release notes and postmortems from the actual commits and diff, and saves each one in the right place.
1.5k GitHub stars~2.4k tokensUpdated 2 mo ago
DevelopmentAuto-check: notes
Natural Writing
a2ui-project/a2ui
Contains well-defined rules for creating natural, accurate, and readable writing.
17k GitHub starsUsed in 1 repo~2.1k tokens
DevelopmentAuto-check passed

More from LUC4N3X/Levyra-deepsound

All 22 skills in this repo

Levyra Android Intent Security
LUC4N3X/Levyra-deepsound
Automatically use for Levyra Android Intent, deep-link, PendingIntent, exported component, receiver, service, provider, URI-grant, FileProvider, caller-verification, or onNewIntent security work.
533 GitHub stars~2k tokensUpdated today
Auto-check passed
Levyra Context Efficiency
LUC4N3X/Levyra-deepsound
A skill your agent uses for genuinely high-volume Levyra work such as builds, tests, lint, logs, broad searches, dependency output, Git/GitHub or CodeRabbit inspection, CI diagnostics, agent setup…
533 GitHub stars~1.3k tokensUpdated today
Auto-check: notes
Levyra R8 Proguard
LUC4N3X/Levyra-deepsound
Automatically use for Levyra R8, Proguard, minification, resource shrinking, keep rules, consumer rules, release-only crashes, reflection/serialization/JNI shrinking issues, APK size, mapping files…
533 GitHub stars~2.2k tokensUpdated today
Auto-check passed
Levyra Android Performance
LUC4N3X/Levyra-deepsound
Automatically use for Android runtime performance investigations involving Perfetto/System Trace, jank, latency, startup, CPU scheduling, blocking, memory, I/O, IPC, graphics, power, or measured…
533 GitHub stars~3.2k tokensUpdated today
Auto-check passed
Levyra CI Workflows
LUC4N3X/Levyra-deepsound
Automatically use for Levyra GitHub Actions, CI, F-Droid, Gradle/AGP/Kotlin/KSP compatibility, build performance, configuration/build cache, artifacts, release automation, workflow security, or…
533 GitHub stars~2k tokensUpdated today
Auto-check passed
Levyra Design Taste
LUC4N3X/Levyra-deepsound
Automatically use together with the matching Levyra UI skill for any visual redesign, UI polish, visual hierarchy, spacing, typography, color, shape, motion, screenshot/reference recreation, or…
533 GitHub stars~2.7k tokensUpdated today
Auto-check passed

Questions about Levyra Humanizer

What does Levyra Humanizer do?

Apply a compact final prose pass to Levyra pull request descriptions, release notes, and owner-facing writing so it sounds natural without changing facts, evidence, structure, or validation state. Levyra Humanizer is an agent skill from LUC4N3X/Levyra-deepsound. Apply a compact final prose pass to Levyra pull request descriptions, release notes, and owner-facing writing so it sounds natural without changing facts, evidence, structure, or validation state.

When should I use Levyra Humanizer?

Levyra Humanizer fits situations like: tasks that involve Humanizing AI text; tasks that involve Changelog and release notes; tasks that involve Pull requests.

How do I install Levyra Humanizer in Claude Code?

Run `npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a claude-code`. Or copy the skill folder (.agents/skills/levyra-humanizer in LUC4N3X/Levyra-deepsound) into .claude/skills/levyra-humanizer in your project. Claude Code loads it when a task matches its description.

How do I install Levyra Humanizer in Codex?

Run `npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a codex`. Or copy the skill folder (.agents/skills/levyra-humanizer in LUC4N3X/Levyra-deepsound) into .agents/skills/levyra-humanizer in your project. Codex loads it when a task matches its description.

Can I use Levyra Humanizer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LUC4N3X/Levyra-deepsound --skill levyra-humanizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/levyra-humanizer, .gemini/skills/levyra-humanizer, .github/skills/levyra-humanizer and .opencode/skills/levyra-humanizer in your project.

What does Levyra Humanizer need to run?

SKILL.md names no scripts, command-line tools or credentials: Levyra Humanizer is instructions for the agent only.

Does Levyra Humanizer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Levyra Humanizer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Levyra Humanizer use?

Levyra Humanizer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Levyra Humanizer use?

About 719 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Levyra Humanizer?

Skills that share tags, products or a category with Levyra Humanizer: Avoid AI Writing (wshobson/agents, 40k stars), Simple History Voice (bonny/WordPress-Simple-History, 317 stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars) and Opik Documentation Patterns (comet-ml/opik, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Levyra Humanizer?

LUC4N3X (a GitHub user) maintains it in LUC4N3X/Levyra-deepsound, which has 533 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 9, 2026.

Source: LUC4N3X/Levyra-deepsound on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Levyra Humanizer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Levyra humanizer

Goal

Non-negotiable claim parity

Natural prose pass

Embedded PR/release mode

Final check

Provenance

Files

Compare with similar skills

Similar skills

More from LUC4N3X/Levyra-deepsound

Related

Questions about Levyra Humanizer