polish-language

Featured

Academic English consistency linting and non-native (ESL) language polish for medical manuscripts. Deterministically flags abbreviation define-once violations, US/UK spelling drift, hyphen-vs-en-dash numeric ranges, P/p case, hyphenation variants, small-number style, and value/unit spacing, then guides a style-only clarity pass that never alters numbers, citations, or scientific meaning. Distinct from humanize (AI-tell removal) and check-reporting (guideline items).

Code & Development 292 stars 71 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Polish-Language Skill You help a medical researcher tighten a manuscript's **mechanical language consistency and clarity** before circulation or submission — the copy-editor pass that content-focused skills skip. The author is frequently a non-native (ESL) English writer, so clarity edits must preserve the formal academic register while never touching facts. ## Communication Rules - Manuscript content and edits in English. - Converse with the user in their preferred language. - Report issues first; only edit after the user approves (see gates below). ## Scope boundary (what this skill is, and is not) | Concern | Skill | |---|---| | Mechanical consistency + ESL clarity (this skill) | **polish-language** | | Removing AI writing tells / de-AI | `humanize` (it explicitly does **not** do general copy-editing) | | Drafting or restructuring content | `write-paper` | | Reporting-guideline item compliance (STROBE, CLAIM, …) | `check-reporting` | | AI-search-engine optimization (GEO) | `academic-aio` | | Reference formatting / citation integrity | `manage-refs`, `verify-refs` | This skill **never** rewrites scientific claims, changes numeric values, edits citations, or judges study quality. It only standardizes house style and improves sentence-level clarity with explicit user approval. ## Inputs / Outputs - **Input**: a manuscript or section (Markdown / plain text). - **Output**: (1) a deterministic consistency report, and (2) — only after a user gate — a clarity-polished ...

Details

Author
Aperivue
Repository
Aperivue/medsci-skills
Created
5 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

writing-polish

Polishing of the USER'S OWN academic prose across five dimensions — accuracy, clarity/readability, formality, register & conventions, and stance — for language assessment / applied linguistics writing. Built for multilingual and early-career academics. Use when the user asks to "polish my writing", "improve the English", "check the style / register / formality", "is this too informal", or wants a draft to read like the field's published prose. Accuracy errors are corrected directly (with a change log); everything stylistic is numbered proposals the author accepts one at a time, each with its reason — preserving the author's voice throughout.

10 Updated yesterday
Shalice-in-AIland
AI & Automation Listed

paper-language-pass

Multi-agent staged language polish for English-language academic manuscripts whose science is already settled (post peer-review). Runs eight parallel specialist subagents — consistency, tense, hedging, prose, coherence, abstract, manuscript hygiene (reviewer-talk, sycophancy, implementation leakage), and AI-authorship tells (hype adjectives, self-coined jargon, evaluative adverb openers, procedural section roadmaps, recycled arguments, em-dash density) — each scanning the whole paper for one dimension. Venue- and discipline-agnostic — user provides venue rules (citation policy, tense, spelling, word limit, etc.) and the skill calibrates severity accordingly; unspecified rules fall back to general academic defaults with downgraded flags. Produces a unified, severity-ranked, numbered issue list, then waits for user approval before applying any fix. Use when the user has a near-final draft (.docx, .md, or .tex) and wants a systematic language pass. Trigger phrases include "language pass", "polish my paper", "pro

2 Updated 2 weeks ago
unbias38
AI & Automation Listed

polish

Use whenever the user asks to "humanize", "make this sound more human", "rewrite to avoid AI detection", "make this less AI-sounding", "add a human voice", or "write like a person". Also use when the user pastes text and asks why it reads as robotic, generic, flat, or AI-like, or when generating new text in a register where AI tells (em dashes, semicolons, hedges, banned vocabulary like "delve", "leverage", "robust") would damage credibility.

0 Updated 2 weeks ago
an2n