ibm-sg-language-and-grammar

Review documentation for IBM Style Guide language, grammar, and terminology compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/redhat-documentation/redhat-docs-agent-tools --skill ibm-sg-language-and-grammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ibm-sg-language-and-grammar
Source: https://github.com/redhat-documentation/redhat-docs-agent-tools/tree/main/plugins/docs-tools/skills/ibm-sg-language-and-grammar
Command: npx skills add https://github.com/redhat-documentation/redhat-docs-agent-tools --skill ibm-sg-language-and-grammar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures documentation adheres to the IBM Style Guide's standards for language, grammar, and terminology, preventing common errors and promoting clarity.

Core Features & Use Cases

  • Grammar and Style Review: Checks for correct abbreviations, capitalization, active voice, and verb usage.
  • Inclusive Language: Identifies and suggests replacements for non-inclusive terms (e.g., master/slave, blacklist/whitelist).
  • Terminology Compliance: Ensures preferred terminology is used and avoids jargon or outdated words.
  • Use Case: A technical writer can use this skill to quickly scan a draft document for any deviations from the IBM Style Guide before publication.

Quick Start

Review the provided document for IBM language and grammar issues.

Frequently Asked Questions about ibm-sg-language-and-grammar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my technical documentation for IBM Style Guide compliance?

To check documentation for IBM Style Guide compliance, review the text for adherence to language, grammar, and terminology rules, focusing on active voice, abbreviations, capitalization, and preferred word usage to ensure consistency.

What is inclusive language review for technical writing?

Inclusive language review for technical writing identifies and suggests replacements for non-inclusive terms like master/slave or blacklist/whitelist, ensuring documentation aligns with established style guide standards.

How do I fix passive voice and anthropomorphism in my documentation?

Fix passive voice and anthropomorphism by scanning documentation to flag deviations from style rules, verifying correct verb usage, and enforcing active voice to promote clarity in technical writing.

Can I enforce specific terminology and avoid jargon in technical drafts?

You can enforce specific terminology and avoid jargon by reviewing drafts for preferred word usage, ensuring terminology compliance, and flagging outdated words that deviate from established style guide requirements.

Does documentation style review check capitalization and contractions?

Documentation style review checks capitalization and contractions by scoping for grammatical deviations, ensuring abbreviations are correct, and validating that preferred terminology is applied consistently throughout the text.