agentleFS
smiling66652smiling66652/workbuddy-skill-toolkits/qf-english-polish/SKILL.md

qf-english-polish

Skill1 starsChanged 48 days agoMITView on GitHub

英文写作润色:语法纠错、流畅度提升、地道表达改写,覆盖学术/商务/日常/创意四种语域。 输出「修改 + 理由」对照,而不是直接替换。 触发词:英文润色、改英文、polish English、英文邮件、英文简历、论文润色、English writing、英文表达

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 15 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Remove filler phrases: "in order to" → "to", "due to the fact that" → "because", "at this point in time" → "now"

    line 54
  2. Distinctive:

    Use transitional phrases between ideas: however, moreover, in contrast, as a result

    line 56
  3. Distinctive:

    Ensure each paragraph flows logically from the previous one

    line 57
  4. Distinctive:

    Use: "Furthermore," "Nevertheless," "It has been demonstrated"

    line 74
  5. Distinctive:

    Avoid: contractions, colloquialisms, rhetorical questions

    line 75
  6. Distinctive:

    Use: "Please find attached," "I'd like to propose," "Looking forward to"

    line 78
  7. Distinctive:

    Avoid: overly academic language, slang, emotional language

    line 79
  8. Distinctive:

    Use: contractions, phrasal verbs, idioms

    line 82
  9. Distinctive:

    Avoid: overly formal constructions, unnecessary complexity

    line 83
  10. Distinctive:

    Use: sensory language, metaphors, varied sentence structures

    line 86
  11. Distinctive:

    Avoid: clichés, passive voice overuse

    line 87
  12. Distinctive:

    If the text is already near-native, say so — don't force unnecessary changes.

    line 122
  13. Distinctive:

    Read the polished text aloud — if it sounds awkward to say, it's not fluent enough

    line 140
  14. Distinctive:

    Prefer active voice unless passive serves a specific purpose (academic method descriptions, diplomatic language)

    line 142
  15. Distinctive:

    Keep the author's voice — don't rewrite their personality out of the text

    line 143

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

English Polish

Refine English writing for grammar, fluency, and native-level expression. Covers academic, business, creative, and casual registers.

Description

This skill provides systematic English writing improvement for non-native speakers and anyone looking to elevate their prose. It goes beyond basic grammar correction to address fluency, tone consistency, idiomatic usage, register appropriateness, and stylistic refinement across different writing contexts.

When to Use

  • Polishing emails, essays, articles, or reports written in English
  • Improving English cover letters, resumes, or LinkedIn profiles
  • Refining academic papers written by non-native English speakers
  • Making business communications sound more professional
  • Elevating casual writing to sound more natural and fluent

Instructions

Review Process

Apply these four layers in order. Each layer builds on the previous.

Layer 1: Grammar & Mechanics

Fix objective errors first:

CategoryCommon Issues
Subject-verb agreement"The data show" (plural) vs "The data shows" (common but debated)
Article usagea/an/the misuse, especially with uncountable nouns
Tense consistencyUnjustified tense shifts within paragraphs
Pronoun referenceAmbiguous "it", "this", "which"
Comma splicesJoining independent clauses with only a comma
Dangling modifiers"Walking down the street, the trees were beautiful"
Parallelism"I like reading, writing, and to code" → "reading, writing, and coding"

Layer 2: Fluency & Flow

Address sentence-level smoothness:

Fixes to apply:

  • Break sentences over 35 words into shorter ones
  • Vary sentence length (mix short punchy sentences with longer analytical ones)
  • Remove filler phrases: "in order to" → "to", "due to the fact that" → "because", "at this point in time" → "now"
  • Replace weak verbs: "make a decision" → "decide", "give an explanation" → "explain", "have a discussion" → "discuss"
  • Use transitional phrases between ideas: however, moreover, in contrast, as a result
  • Ensure each paragraph flows logically from the previous one

Common Chinese-English Interference Patterns:

Chinese PatternLiteral TranslationNatural English
虽然...但是Although... but...Although... [no "but"]
我觉得I feel/thinkI believe/In my opinion
毫无疑问Without doubtUndoubtedly / Certainly
越来越More and moreIncreasingly / Growing
进行研究Conduct researchStudy / Investigate / Research

Layer 3: Register & Tone

Match the writing level to the context:

Academic: Formal, precise, hedged

  • Use: "Furthermore," "Nevertheless," "It has been demonstrated"
  • Avoid: contractions, colloquialisms, rhetorical questions

Business: Professional, clear, action-oriented

  • Use: "Please find attached," "I'd like to propose," "Looking forward to"
  • Avoid: overly academic language, slang, emotional language

Casual/Conversational: Natural, relaxed, direct

  • Use: contractions, phrasal verbs, idioms
  • Avoid: overly formal constructions, unnecessary complexity

Creative: Engaging, varied, expressive

  • Use: sensory language, metaphors, varied sentence structures
  • Avoid: clichés, passive voice overuse

Layer 4: Idiomatic Enhancement

Replace literal or awkward phrasing with natural English:

AwkwardNatural
"I'm very agree with you""I completely agree"
"It has a big impact to me""It had a huge impact on me"
"I have no idea about this""I'm not familiar with this"
"I will try my best to do it""I'll do my best"
"Every coin has two sides""There are two sides to every story"

Output Format

Present corrections as:

## English Polish Results

**Overall Level**: [Advanced / Intermediate / Basic]
**Primary Issues**: [Grammar / Fluency / Tone / Idiom]

### Corrections

1. **[Category]** Original → Revised
   Reason: Brief explanation

2. ...

### Refined Version
[Full polished text]

If the text is already near-native, say so — don't force unnecessary changes. Sometimes the original is fine and only minor tweaks are needed.

Examples

Before: "With the development of technology, more and more people begin to use AI tools to improve their work efficiency. Although AI has many advantages, but it also brings some problems."

After: "As technology advances, an increasing number of people are adopting AI tools to boost productivity. While AI offers significant advantages, it also presents new challenges."

Before: "I am writing this email to inform you that we need to have a meeting about the project. Please let me know your available time so that we can schedule it."

After: "I'd like to schedule a meeting to discuss the project. Could you share your availability this week?"

Before: "The reason why I chose this topic is because it is very interesting and nobody has researched it before."

After: "I chose this topic because it raises intriguing questions that remain underexplored in the literature."

Tips

  • Read the polished text aloud — if it sounds awkward to say, it's not fluent enough
  • Less is more: if a word doesn't add meaning, remove it
  • Prefer active voice unless passive serves a specific purpose (academic method descriptions, diplomatic language)
  • Keep the author's voice — don't rewrite their personality out of the text
  • For academic writing, prefer "this study demonstrates" over "it is demonstrated by this study"

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.