跳到正文
cccskills
免费在 GitHub 公开

proofreading

Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis. Use when the user requests proofreading or provides relevant inputs for this workflow.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md9.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Proofreading

This skill enables an AI agent to systematically proofread text, catching errors in grammar, spelling, punctuation, style, and consistency. The agent applies a structured multi-pass review process, supports standard style guides (AP, Chicago, APA, or custom house styles), and provides readability scoring alongside tone analysis. Output includes both the corrected text and an annotated summary of every change made.

Workflow

  1. Grammar Check Scan the text for grammatical errors including subject-verb agreement, incorrect tense usage, dangling modifiers, sentence fragments, run-on sentences, and misplaced clauses. Fix each error and record the original phrasing alongside the correction. Pay special attention to complex sentences where multiple clauses may introduce ambiguity.

  2. Spelling and Word Choice Identify misspelled words, commonly confused homophones (e.g., "affect" vs. "effect," "their" vs. "there"), and incorrect word forms. Verify proper nouns and domain-specific terminology against the provided context or glossary. Flag any words that are spelled correctly but likely used in the wrong context.

  3. Punctuation and Mechanics Review comma usage, semicolons, colons, em dashes, en dashes, hyphens, quotation marks, and apostrophes. Apply the rules of the specified style guide — for example, the Oxford comma for Chicago style but not for AP style. Correct misuse of ellipses, parentheses, and bracket nesting.

  4. Style and Consistency Enforce consistent formatting throughout the document: heading capitalization (title case vs. sentence case), number formatting (numerals vs. spelled-out), abbreviation usage (define on first use), and list punctuation. Check for passive voice overuse and recommend active alternatives where the meaning would be clearer. Ensure consistent use of terminology — if "user interface" appears in one place and "UI" elsewhere, unify them.

  5. Clarity and Readability Evaluate sentence length, paragraph structure, and overall readability. Flag sentences longer than 30 words for possible splitting. Identify jargon or overly complex vocabulary that could be simplified without losing precision. Calculate a readability score (Flesch-Kincaid or equivalent) and report it. Suggest structural improvements such as adding transition sentences or breaking up dense paragraphs.

  6. Tone Analysis and Final Review Assess the overall tone (formal, conversational, academic, persuasive) and verify it matches the user's stated intent. Flag any jarring tonal shifts — for instance, a casual phrase in an otherwise formal report. Perform a final read-through to ensure all corrections integrate smoothly and no new errors were introduced during editing.

Usage

Provide the text to proofread along with any relevant context. Optionally specify:

  • Style guide — AP, Chicago, APA, MLA, or a custom style reference
  • Audience — academic, professional, general public, technical
  • Tone — formal, informal, conversational, neutral
  • Focus areas — grammar only, style only, full proofread
  • Output format — corrected text only, corrected text with tracked changes, or annotated list of changes

Example prompt: "Proofread the following research abstract for APA style. Flag any passive voice usage and provide a readability score."

Examples

Example 1: Proofreading an Academic Paragraph

Input:

The study's participants was selected from a pool of undergraduate students, who where enrolled in a introductory psychology course. Data was collected over a 6 week period and analysed using a mix-methods approach. The researchers founded that participants that recieved the intervention showed signficant improvement, however those in the control group did not.

Corrected Output:

The study's participants were selected from a pool of undergraduate students who were enrolled in an introductory psychology course. Data were collected over a six-week period and analyzed using a mixed-methods approach. The researchers found that participants who received the intervention showed significant improvement; however, those in the control group did not.

Changes Made:

#OriginalCorrectionReason
1"participants was""participants were"Subject-verb agreement
2"who where""who were"Homophone error
3"a introductory""an introductory"Article agreement (vowel sound)
4"Data was""Data were""Data" is plural in academic writing (APA)
5"6 week""six-week"Spell out numbers under 10; hyphenate compound modifier
6"analysed""analyzed"American English spelling (APA default)
7"mix-methods""mixed-methods"Incorrect adjective form
8"founded""found"Wrong verb form
9"participants that""participants who"Use "who" for people
10"recieved""received"Spelling error
11"signficant""significant"Spelling error
12"improvement, however""improvement; however,"Semicolon before conjunctive adverb

Readability: Flesch-Kincaid Grade Level 14.2 (appropriate for academic audience).

Example 2: Proofreading Technical Documentation

Input:

Configration

To setup the SDK, first install the dependancies using npm. Run npm install @acme/sdk in your terminal. After installing you need to initialise the client by calling AcmeClient() constructor and passing you're API key. Make sure the api key is stored securly and is not hard-coded in your source code, we reccommend using environment variables.

Corrected Output:

Configuration

To set up the SDK, first install the dependencies using npm. Run npm install @acme/sdk in your terminal. After installing, you need to initialize the client by calling the AcmeClient() constructor and passing your API key. Make sure the API key is stored securely and is not hard-coded in your source code. We recommend using environment variables.

Changes Made:

#OriginalCorrectionReason
1"Configration""Configuration"Spelling error in heading
2"To setup""To set up""Set up" is a verb phrase; "setup" is a noun/adjective
3"dependancies""dependencies"Spelling error
4"After installing you""After installing, you"Missing comma after introductory phrase
5"initialise""initialize"American English spelling for consistency
6"calling AcmeClient()""calling the AcmeClient()"Missing article
7"you're""your"Homophone error ("you're" = "you are")
8"api key""API key"Acronym should be capitalized
9"securly""securely"Spelling error
10"source code, we""source code. We"Comma splice — use a period to separate independent clauses
11"reccommend""recommend"Spelling error

Best Practices

  • Use a multi-pass approach. Never try to catch all error types in a single read. Separate passes for grammar, spelling, punctuation, and style yield more thorough results.
  • Preserve the author's voice. Correct errors without rewriting the text in a different style. The goal is to polish, not to replace the author's expression.
  • Show your work. Always provide an annotated list of changes so the author can review, learn from corrections, and accept or reject individual edits.
  • Apply the correct style guide consistently. AP and Chicago have different rules for commas, numbers, and capitalization. Confirm which guide applies before starting.
  • Flag subjective suggestions separately. Distinguish between objective errors (misspellings, grammar mistakes) and subjective suggestions (word choice, sentence restructuring) so the author can prioritize.
  • Consider the audience. A technical document for developers can tolerate jargon that would be inappropriate in a public-facing blog post. Calibrate simplification suggestions accordingly.

Edge Cases

  • Intentional style deviations: Creative writing, dialogue, and marketing copy may intentionally break grammar rules for effect. Ask for clarification before "correcting" sentence fragments or colloquialisms that appear purposeful.
  • Mixed languages: Documents containing code snippets, foreign phrases, or brand names in another language should have those sections excluded from spelling checks.
  • Regional English variants: Distinguish between American, British, Australian, and other English variants. "Colour" is not a misspelling in British English; "analyze" is not a misspelling in American English.
  • Highly technical or domain-specific text: Medical, legal, and scientific texts contain specialized terminology that may trigger false positives. Cross-reference flagged terms against domain glossaries before marking them as errors.
  • Very short text: For single sentences or headlines, readability scoring may not be meaningful. Focus on correctness and clarity instead.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Audit web interfaces against WCAG 2.1 AA/AAA standards, identify violations, and produce actionable remediation reports with code fixes. Use when the user requests accessibility testing or provides relevant inputs for this workflow.

中文简介正在准备中。当前显示原文说明。

seb1n/awesome-ai-agent-skills2232026年8月10日 更新

Design reproducible evaluations for AI agents with representative task sets, explicit rubrics, appropriate graders, baselines, regression gates, and failure analysis. Use when defining agent quality, comparing prompts or models, validating a release, measuring tool-use reliability, investigating regressions, or deciding whether an agent is ready for production.

中文简介正在准备中。当前显示原文说明。

seb1n/awesome-ai-agent-skills2232026年8月10日 更新

Design privacy-aware observability for AI agents using traces, spans, structured events, metrics, cost attribution, dashboards, alerts, and investigation workflows. Use when instrumenting an agent, debugging intermittent tool or model failures, defining service-level objectives, analyzing latency or spend, auditing agent decisions, or preparing production monitoring.

中文简介正在准备中。当前显示原文说明。

seb1n/awesome-ai-agent-skills2232026年8月10日 更新

Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings. Use when defining red-team rules of engagement, assessing prompt injection or excessive agency, testing tool and identity boundaries, evaluating memory or cross-agent attacks, scoring a campaign, or verifying remediation in an approved environment.

中文简介正在准备中。当前显示原文说明。

seb1n/awesome-ai-agent-skills2232026年8月10日 更新

Generate comprehensive marketing analytics reports by collecting KPIs, analyzing trends, and delivering actionable insights with attribution modeling and funnel analysis. Use when the user requests analytics reporting or provides relevant inputs for this workflow.

中文简介正在准备中。当前显示原文说明。

seb1n/awesome-ai-agent-skills2232026年8月10日 更新

Design RESTful APIs with proper resource modeling, HTTP method semantics, status codes, pagination, versioning, and documentation. Use when the user requests api design or provides relevant inputs for this workflow.

中文简介正在准备中。当前显示原文说明。

seb1n/awesome-ai-agent-skills2232026年8月10日 更新

查看 seb1n 的全部技能

报告此技能的问题