Install the "polish-language" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/polish-language into .claude/skills/polish-language/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "polish-language", 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.
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 Aperivue/medsci-skills --skill polish-language -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "polish-language" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/polish-language into .agents/skills/polish-language/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "polish-language", 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 Aperivue/medsci-skills --skill polish-language -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "polish-language" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/polish-language into .cursor/skills/polish-language/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "polish-language", 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.
--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 Aperivue/medsci-skills --skill polish-language -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "polish-language" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/polish-language into .gemini/skills/polish-language/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "polish-language", 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.
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 Aperivue/medsci-skills --skill polish-language -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "polish-language" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/polish-language into .github/skills/polish-language/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "polish-language", 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 Aperivue/medsci-skills --skill polish-language -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "polish-language" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/polish-language into .opencode/skills/polish-language/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "polish-language", 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
polish-language
GitHub stars
331
Token cost
~1.5k tokens
SKILL.md length
706 words
Files
14 (incl. scripts)
Skills in repo
54
Repo updated
First seen
Licence
MIT
At a glance
A skill your agent uses when a manuscript needs a copy-edit for consistency and non-native English clarity.
Works in 4 steps: Deterministic consistency lint (no LLM… → Triage with the user (gate) → Apply mechanical fixes (style-only) → …
A manuscript needs a copy-edit for consistency and non-native English clarity
SKILL.md covers Workflow and Reproducible challenge card
Runs Shell and Python scripts from its folder; calls python3 and bash
What it does
Polish Language is an agent skill from Aperivue/medsci-skills. Use when a manuscript needs a copy-edit for consistency and non-native English clarity. Flags abbreviation, US/UK spelling, en-dash range, P/p, hyphenation, number-style and unit-spacing issues, then polishes style only. AI-tell removal is /humanize.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including scripts (for example `scripts/lint_challenge/fixture/consistent_uk.md`, `scripts/lint_challenge/fixture/consistent_us.md` and `scripts/lint_challenge/fixture/manuscript.md`).
It sits in Research & Science, covering Humanizing AI text. The repository describes itself as: Agent Skills for medical research — literature search, reporting-guideline & citation checks, statistics, publication figures, submission. Works with Claude Code, Codex, Cursor &… The licence is MIT.
When your agent uses it
A manuscript needs a copy-edit for consistency and non-native English clarity
Tasks that involve Humanizing AI text
Example prompts
“/polish-language”
Requirements
Python 3
A Bash shell
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 3b14ae2. 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
Ships 10 files in scripts/ (Shell and Python), which the agent can run.
Shell commands in SKILL.md call:
python3
bash
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
Polish Language loads about 1.5k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 706 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~67
When it runs· the whole SKILL.md, loaded when a task matches
~1.5k
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); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/polish-language/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.
name
polish-language
description
Use when a manuscript needs a copy-edit for consistency and non-native English clarity. Flags abbreviation, US/UK spelling, en-dash range, P/p, hyphenation, number-style and unit-spacing issues, then polishes style only. AI-tell removal is /humanize.
metadata.triggers
polish language, copy-edit, consistency check, ESL, non-native English, house style, abbreviation consistency, en-dash, US UK spelling, proofread manuscript…
Polish-Language Skill
Tighten a manuscript's mechanical language consistency and clarity before circulation or
submission — the copy-editor pass content-focused skills skip. The author is often a non-native
(ESL) English writer, so clarity edits keep the formal academic register and never touch facts.
Manuscript edits are in English.
This skill never rewrites scientific claims, changes numeric values, edits citations, or
judges study quality; it standardizes house style and improves sentence-level clarity, with
explicit user approval for every edit. Out of scope: AI-tell removal (humanize, which does not
do general copy-editing), drafting or restructuring (write-paper), reporting-guideline items
(check-reporting), AI-search optimization (academic-aio), reference formatting and citation
integrity (manage-refs, verify-refs), and translation.
Input: a manuscript or section (Markdown / plain text). Output: (1) the deterministic
consistency report, and (2) — only after a user gate — a clarity-polished revision with a change
log limited to style.
Workflow
Phase 1: Deterministic consistency lint (no LLM judgement)
Run the bundled linter — it reports, never edits:
bash
python3 "${CLAUDE_SKILL_DIR}/scripts/lint_consistency.py" path/to/manuscript.md
# add --strict to exit non-zero when any issue is found (CI / pre-submission gate)
It flags eight families, each with line numbers and a per-category + total count:
Spelling — mixed US/UK variants (analyze/analyse, tumor/tumour, …); reports the minority
side against the document's dominant variant.
Numeric ranges — hyphen between numbers where an en-dash belongs (5-10 → 5–10).
p-values — mixed P/p case; impossible P = 0.000.
Hyphenation / terminology — variant forms of one term (follow-up / followup / "follow up").
Small numbers — single digits 1–9 written as digits in prose.
Units — missing space between value and unit (5mg → 5 mg).
Thousands separator (title vs body) — a float title writes a number with a period
separator (3.681) that the body writes with a comma (3,681).
Present the report to the user. The linter output is the source of truth for what is
mechanically wrong: do not invent further "issues" from memory, and label anything else you
notice as an editorial suggestion, not a linter finding. The fixed rules do not settle every
grammar or journal preference, so triage flags in context.
Phase 1b: Figure-SOURCE locale drift
Text baked into a figure never reaches Phase 1, so a UK word typed into a PowerPoint panel or
plotting script ships in a US manuscript unseen. Scan the figure sources (no OCR):
bash
python3 "${CLAUDE_SKILL_DIR}/scripts/lint_figure_locale.py" --manuscript path/to/manuscript.md --figures-dir figures/
# --spelling us|uk forces the target; otherwise it reads a `spelling:` front-matter field,
# then falls back to the body's own US/UK majority. --strict exits non-zero on any drift.
It reads <a:t> runs inside *.pptx slide XML and the text of *.py / *.R plotting scripts,
with the same US↔UK families as Phase 1. FIGURE_LOCALE_DRIFT is Minor — copy-edit the
source before the raster is re-exported. A missing figures directory is not an error; it exits 0
with nothing judged.
Show full SKILL.md (292 more words)Show less
Phase 2: Triage with the user (gate)
Walk the user through the report. Some flags are author choices (a journal may mandate UK
spelling, or digits for all numbers). User approval is required before any edit — confirm
per category which to apply and which to keep. Record the decisions; do not auto-apply.
Phase 3: Apply mechanical fixes (style-only)
For each approved category, apply the deterministic fix with Edit:
standardize spelling to the chosen variant,
replace numeric-range hyphens with en-dashes,
normalize P/p and fix P = 0.000 to the reported inequality,
unify hyphenation, spell out small numbers, add value/unit spaces,
define each abbreviation once at first use; remove redundant redefinitions.
Re-run lint_consistency.py after editing — the count should drop to the issues the user chose
to keep. This re-run is the verification gate; never claim a fix without it.
If the user requests a clarity pass, improve readability sentence by sentence while preserving
meaning, register, numbers, and citations:
split run-on sentences; fix article (a/an/the) and preposition usage;
correct subject–verb agreement and awkward non-native phrasings;
prefer active voice only where it does not change emphasis or claims.
Show each proposed change as a before/after diff and get user review before writing. Numbers,
p-values, effect sizes, units, citations, and claims are copied verbatim; an edit that would
change any of them is out of scope — skip it. Never merge, add, or drop a scientific claim,
number, or reference. If a sentence's meaning is even slightly uncertain, leave it and ask; do
not invent domain facts to smooth a sentence. Every applied change must trace to a linter flag
or a user-approved clarity suggestion in the change log.
Reproducible challenge card
Deterministic and network-free (synthetic manuscript with seeded defects +
expected/report.txt):
Polish Language 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.
Improve the clarity and voice of AI-assisted academic writing (papers, theses, rebuttals) and funding proposals (NSF Project Summary/Description, NIH Specific Aims): preserve scholarly conventions…
Polishes academic prose without changing its meaning: grammar and flow fixes, tone matched to the evidence, AI-tone removal and Chinese-to-English rewriting for submission.
A skill your agent uses when researchers ask to remove generic, templated, or AI-like patterns from Chinese or English academic prose, make an AI-assisted draft sound more like the author's own…
Draft, audit, or minimally revise English- or Chinese-language academic prose to reduce formulaic, vacuous, mechanically repetitive, or process-leaking language while preserving claims, evidence…
A skill your agent uses when a clinical CSV/Excel dataset needs profiling and cleaning before analysis (missing values, outliers, duplicates, type mismatches).
A skill your agent uses when an institutional Word form (.doc/.docx IRB protocol, ethics application, grant template) must be filled without breaking its styles, tables, fonts or page layout.
A skill your agent uses when looking for research topics a longitudinal cohort database can answer (NHIS, UK Biobank, an institutional EMR or registry).
A skill your agent uses when a manuscript needs a copy-edit for consistency and non-native English clarity. Polish Language is an agent skill from Aperivue/medsci-skills. Use when a manuscript needs a copy-edit for consistency and non-native English clarity.
When should I use Polish Language?
Polish Language fits situations like: A manuscript needs a copy-edit for consistency and non-native English clarity; tasks that involve Humanizing AI text.
How do I install Polish Language in Claude Code?
Run `npx skills add Aperivue/medsci-skills --skill polish-language -a claude-code`. Or copy the skill folder (skills/polish-language in Aperivue/medsci-skills) into .claude/skills/polish-language in your project. Claude Code loads it when a task matches its description.
How do I install Polish Language in Codex?
Run `npx skills add Aperivue/medsci-skills --skill polish-language -a codex`. Or copy the skill folder (skills/polish-language in Aperivue/medsci-skills) into .agents/skills/polish-language in your project. Codex loads it when a task matches its description.
Can I use Polish Language 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 Aperivue/medsci-skills --skill polish-language -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/polish-language, .gemini/skills/polish-language, .github/skills/polish-language and .opencode/skills/polish-language in your project.
What does Polish Language need to run?
Going by SKILL.md and its folder, Polish Language needs a shell and Python for the scripts in its folder and the command-line tools its instructions call (python3 and bash). Our summary lists: Python 3; A Bash shell.
Does Polish Language 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 Polish Language 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Polish Language use?
Polish Language is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Polish Language use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Polish Language?
Skills that share tags, products or a category with Polish Language: Academic Humanizer (AIScientists-Dev/academic-humanizer, 1.9k stars), Academic Paper Polish (HKUSTDial/Supervisor-Skills, 8.7k stars), Research (EliasOulkadi/shokunin, 114 stars) and Scholar Anti AI Writing (catlog22/maestro-flow, 564 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Polish Language?
Aperivue (a GitHub organization) maintains it in Aperivue/medsci-skills, which has 331 GitHub stars. The repository holds 54 skills in this directory. The repository was last updated on October 5, 2026.
Source: Aperivue/medsci-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.