Token导航 LogoToken导航TokenDH.com
待分类需要联网github未标认证来源可访问许可证需确认审计通过

grammargrammar 工具

Agent Skill

grammar 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

546

周安装

23

GitHub Stars

2

下载量

191
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:grammar(grammar 工具)
来源仓库:https://github.com/williacj/claude-skills
仓库路径:skills/grammar
安装命令:
npx skills add https://github.com/williacj/claude-skills --skill grammar
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/williacj/claude-skills --skill grammar

简介

grammar 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

  • 它可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前顶部介绍为空,原始 SKILL.md 摘录未提供。
  • 暂无其他已知细节。

SKILL.md

Grammar and Proofreading Skill

This skill provides comprehensive proofreading and editing for religious and theological writing, including sermons, devotionals, academic papers, and books.

When to Use This Skill

Use this skill when the user requests:

  • Grammar or spelling checking
  • Proofreading of biblical or theological content
  • Style improvements for clarity, conciseness, or tone
  • Editing sermons, sermonettes, devotionals, or blogs
  • Academic theological writing review
  • Book chapter editing

Core Capabilities

  1. Grammar and Spelling: US English corrections, subject-verb agreement, pronoun usage, verb tense consistency
  2. Style Enhancement: Clarity, conciseness, tone adjustment, flow improvement
  3. Specialized Formatting: Biblical citations, theological terminology, proper capitalization
  4. Writing Type Adaptation: Pastoral, academic, or creative devotional styles

Workflow

Step 1: Understand the Context

Ask the user (if not already specified):

  • Writing type: sermon, sermonette, devotional, blog, academic paper, book chapter, or other
  • Desired tone: pastoral (default), academic, creative, or mixed
  • Specific concerns: grammar only, style improvements, comprehensive edit, or specific issues
  • Document length: to set appropriate depth of review

Step 2: Load Relevant Style References

Based on writing type, read the appropriate reference files:

For pastoral sermons/sermonettes:

  • Read references/pastoral-style.md for tone, structure, and biblical integration guidance
  • Read references/us-grammar.md for grammar and spelling rules

For academic theological writing:

  • Read references/academic-style.md for formal tone, citation, and argumentation guidance
  • Read references/us-grammar.md for grammar and spelling rules

For creative devotionals/blogs:

  • Read references/creative-style.md for narrative, imagery, and voice guidance
  • Read references/us-grammar.md for grammar and spelling rules

For mixed or unclear types:

  • Read references/pastoral-style.md as baseline
  • Read references/us-grammar.md for grammar and spelling rules

Step 3: Review and Edit

Perform comprehensive review focusing on:

Grammar and Mechanics

  • Subject-verb agreement
  • Pronoun consistency and clarity
  • Verb tense consistency
  • Sentence fragments and run-ons
  • Punctuation (commas, semicolons, apostrophes, quotation marks)
  • Spelling (US English conventions)

Style and Clarity

  • Sentence variety and flow
  • Active vs. passive voice
  • Wordiness and redundancy
  • Paragraph structure and transitions
  • Tone consistency with intended audience

Specialized Elements

  • Biblical citations (format: Book Chapter:Verse Translation)
  • Theological terminology accuracy
  • Capitalization of religious terms (follow loaded style guide)
  • Scripture integration and quotation accuracy

Writing-Type Specific

  • *Pastoral*: warm tone, practical application, clear structure, vivid illustrations
  • *Academic*: formal tone, proper citations, logical argumentation, scholarly engagement
  • *Creative*: authentic voice, imagery, narrative flow, emotional resonance

Step 4: Present Corrections

Use one of two formats based on document length and user preference:

Format 1: Tracked Changes (Recommended for shorter works <2000 words)

  • Present the full corrected text
  • Use [Editorial note in brackets] to explain significant changes
  • Summarize major patterns of errors at the end
  • Highlight strengths of the writing

Format 2: Categorized Feedback (For longer works >2000 words)

  • Provide summary of main issues by category (grammar, style, structure)
  • Give specific examples with corrections
  • Suggest broader patterns to address throughout
  • Offer 2-3 overall recommendations
  • If requested, provide corrected sample sections

Step 5: Respond to Follow-up

Be prepared to:

  • Clarify specific corrections
  • Explain grammar rules or style choices
  • Provide alternative phrasings
  • Focus on specific sections
  • Adjust tone or style based on feedback

Key Principles

Respect the Author's Voice

  • Preserve unique phrasing and style choices when possible
  • Suggest rather than dictate style changes
  • Distinguish between errors and stylistic preferences

Context Matters

  • Sermons may use intentional fragments for emphasis
  • Academic writing requires formal precision
  • Devotionals allow creative flexibility
  • Match correction level to writing type

Biblical Accuracy

  • Verify Scripture quotations when possible
  • Ensure citations are complete and accurate
  • Respect theological nuance in terminology
  • Flag potentially confusing or misleading phrasing

US English Standards

  • Apply US spelling consistently (color, realize, theater)
  • Use Oxford comma in series
  • Follow US quotation mark conventions (periods inside quotes)
  • Apply standard US capitalization for religious terms

Common Issues to Watch For

In Pastoral Writing

  • Overuse of Christian clichés
  • Vague pronouns ("this," "that," "it" without clear antecedent)
  • Inconsistent verb tense when discussing Scripture
  • Missing or incorrect Scripture citations
  • Overly complex sentences that obscure meaning

In Academic Writing

  • Mixing informal and formal tone
  • Incomplete or inconsistent citations
  • Unsupported claims
  • Unclear thesis or argument structure
  • Colloquial language

In Creative Devotional Writing

  • Forced or mixed metaphors
  • Preachy or guilt-manipulative tone
  • Spiritual platitudes without depth
  • Unclear connection between story and spiritual insight
  • Inconsistent narrative voice

Examples

Example 1: Pastoral Sermon Correction

*Original*: "God is calling we to a deeper faith, its not about religion but relationship."

*Corrected*: "God is calling us to a deeper faith. It's not about religion but about relationship."

*Explanation*: Corrected pronoun case (we→us), added apostrophe (its→it's), split run-on sentence, added clarity ("about relationship").

Example 2: Academic Style Enhancement

*Original*: "Paul basically says that we should love each other in Romans 12."

*Corrected*: "Paul exhorts believers to express genuine love for one another (Rom. 12:9-10)."

*Explanation*: Removed informal "basically," used precise theological language, added specific verse citation, replaced vague "says" with "exhorts."

Example 3: Creative Devotional Refinement

*Original*: "I learned that God is always there for us no matter what happens in life."

*Corrected*: "I'm learning that even in the darkest moments—when the diagnosis comes, when the relationship fractures, when hope feels distant—God's presence remains steady, unshaken by the storms that shake me."

*Explanation*: Replaced cliché with specific examples, added concrete imagery, maintained authentic voice, created rhythm through parallel structure.

Tips for Best Results

  • Provide context about the intended audience
  • Specify if maintaining the author's voice is priority
  • Indicate any time constraints (light edit vs. comprehensive revision)
  • Flag any sections with particular concerns
  • Share if this is a first draft or near-final version

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.41%
按下载量换算71

Claude

26.29%
按下载量换算50

Cursor

19.27%
按下载量换算37

Gemini CLI

9.63%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills