Token导航 LogoToken导航

Agent Skill · 待分类

grammar(grammar 工具)

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

grammar 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 5,574。

总安装 546周安装 23GitHub Stars 2下载 191核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

grammar 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。它可结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。当前顶部介绍为空,原始 SKILL.md 摘录未提供。暂无其他已知细节。

来源仓库内路径:skills/grammar

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/williacj/claude-skills --skill grammar;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

grammar 怎么安装?

在终端执行 npx skills add https://github.com/williacj/claude-skills --skill grammar。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

grammar 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

grammar 需要什么权限?

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

grammar 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

grammar 用的人多吗?

公开数据是累计安装 546 次,近一周安装 23 次,下载 191 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

grammar 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
grammar

grammar 工具 · 本页

5462需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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

平台分布

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