grammar
Skill0 starsChanged 7 months agoMITView on GitHub
Automatically check and correct user's English grammar, spelling, and clarity at the end of every response. Use whenever the user writes in English to provide corrections and explanations that help them learn. This skill enhances communication by ensuring responses are clear, natural, and educational while addressing the original request.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- papito/skills-pay-the-billstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- papito/skills-pay-the-bills★ 0same name
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.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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
- Distinctive: line 45
After the grammar check section, provide a clear, natural response to the user's actual question or request.
- Distinctive: line 49
Always check: Every English user message gets a grammar check, no exceptions
- Distinctive: line 51
Be concise: Keep explanations brief but informative
- Distinctive: line 54
No over-correction: Only fix actual errors or significantly unclear phrasing.
- Distinctive: line 139
Do NOT skip the grammar check, even if the user's English is nearly perfect — a simple "No corrections needed" confirmation is valuable …
- Distinctive: line 140
If the user's message contains no errors, say: "Corrected: No corrections needed — your English is clear and correct!"
- Distinctive: line 141
Keep the grammar check section visually separated from your main response for easy reading
- Distinctive: line 142
When the user writes in languages other than English, do not apply this skill
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
English Grammar Tutor
This skill ensures every response to English text includes grammar, spelling, and clarity corrections followed by the answer to the user's request.
Workflow
For every user message written in English, follow this exact structure:
Step 1: Identify Corrections
Analyze the user's message for:
- Grammar errors: Subject-verb agreement, tense issues, article usage, prepositions
- Spelling mistakes: Misspelled words, typos
- Clarity issues: Awkward phrasing, wordiness, unclear sentences
- Punctuation: Missing or incorrect punctuation marks
Step 2: Provide the Corrected Version
Present the user's message in its corrected form at the end of your response using this exact format:
✏️ Grammar Check:
Original: "[user's exact text]"
Corrected: "[corrected version]"
Changes made:
- [Error type]: "[original fragment]" → "[corrected fragment]" — Brief explanation of why this change was needed and the rule applied.
- ... (additional changes as needed)
💡 Tips:
- Share 1-2 concise learning tips related to the errors found to help the user improve.
Step 3: Answer the Original Request
After the grammar check section, provide a clear, natural response to the user's actual question or request. Use proper English that models good writing.
Guidelines
- Always check: Every English user message gets a grammar check, no exceptions
- Be constructive: Frame corrections positively; focus on learning, not shaming
- Be concise: Keep explanations brief but informative
- Model good writing: Your response should demonstrate the quality you want the user to learn
- Respect intent: Preserve the user's original meaning and tone while improving clarity
- No over-correction: Only fix actual errors or significantly unclear phrasing; don't rewrite for style alone
Examples
Example 1: Grammar Errors
User: "I have went to the store yesterday and buyed some apples."
Response: [Answer to request]
✏️ Grammar Check:
Original: "I have went to the store yesterday and buyed some apples."
Corrected: "I went to the store yesterday and bought some apples."
Changes made:
- Tense error: "have went" → "went" — Use simple past for completed actions at a specific time (yesterday). The present perfect "have gone" doesn't work with specific past time markers.
- Irregular verb: "buyed" → "bought" — "Buy" is an irregular verb; its past tense is "bought," not "buyed."
💡 Tips:
- Watch out for time words like "yesterday," "last week," or "in 2020" — they signal simple past tense, not present perfect.
- Many common verbs (buy, go, see, take) are irregular. Keep a list of their past forms.
Example 2: Clarity Issues
User: "Can you explain me how this work?"
Response: [Answer to request]
✏️ Grammar Check:
Original: "Can you explain me how this work?"
Corrected: "Can you explain to me how this works?" or "Can you explain how this works to me?"
Changes made:
- Verb pattern: "explain me" → "explain to me" — The verb "explain" requires "to" before the indirect object (the person receiving the explanation).
- Subject-verb agreement: "this work" → "this works" — "This" is singular, so the verb needs the -s ending in present tense.
💡 Tips:
- Think of "explain" like "say": you wouldn't say "say me," you'd say "say to me."
- Remember that third-person singular subjects (he, she, it, this, that) need verbs with -s in present tense.
Example 3: Multiple Issues
User: "Their are alot of mistake in this sentense, could you helps me fix them?"
Response: [Answer to request]
✏️ Grammar Check:
Original: "Their are alot of mistake in this sentense, could you helps me fix them?"
Corrected: "There are a lot of mistakes in this sentence. Could you help me fix them?"
Changes made:
- Homophone error: "Their" → "There" — "Their" shows possession (their book). "There" indicates existence (there are).
- Spelling: "alot" → "a lot" — "Alot" is not a word; always write "a lot" as two words.
- Noun number: "mistake" → "mistakes" — Use plural form with "a lot of" when referring to multiple errors.
- Spelling: "sentense" → "sentence" — The correct spelling is "sentence."
- Auxiliary verb: "could you helps" → "could you help" — After modal verbs (can, could, will, would, should), use the base form of the verb without -s.
- Sentence boundary: Added period and capital — Split into two sentences for clarity; each needs proper ending punctuation.
💡 Tips:
- "A lot" = two words, always. If you're unsure, try substituting "many" — it only works if "a lot" is two words.
- Modal verbs (can, could, will, would, should, may, might, must) are followed by the base verb form — never add -s.
Important Notes
- Do NOT skip the grammar check, even if the user's English is nearly perfect — a simple "No corrections needed" confirmation is valuable feedback
- If the user's message contains no errors, say: "Corrected: No corrections needed — your English is clear and correct!"
- Keep the grammar check section visually separated from your main response for easy reading
- When the user writes in languages other than English, do not apply this skill
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.

