confident-language-guard

Rewrites draft text to replace absolute statements with measured, actionable ones.

Updated Dec 15, 2025

Search Tags:#documentation #writing #language #guidelines #directives #caution

Ready to run

npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill confident-language-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: confident-language-guard
Source: https://github.com/OpenSourceSam/v2_heras_garden/tree/main/.claude/skills/confident-language-guard
Command: npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill confident-language-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that documentation, especially directives and instructions, is written with appropriate caution and flexibility, avoiding overly confident or absolute language that might become outdated or incorrect.

Core Features & Use Cases

Promotes Nuanced Language: Encourages the use of qualifiers and scoped statements.
Distinguishes Recommendations from Requirements: Helps clarify the nature of guidance provided.
Reduces Fragile Directives: Minimizes the risk of documentation becoming a source of error due to rigid, unchangeable instructions.
Use Case: When updating a development roadmap or agent instructions, this Skill serves as a reminder to phrase tasks and expectations in a way that acknowledges potential changes or exceptions.

Quick Start

Review the draft of the new agent guidelines and ensure all directives are phrased cautiously and avoid absolute terms where possible.

Frequently Asked Questions about confident-language-guard

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

FAQPage Schema

How do I write cautious documentation that avoids absolute statements?▼

To write cautious documentation, you should use scoped, time-bound statements and qualifiers, distinguishing firm requirements from flexible recommendations to prevent instructions from becoming outdated or incorrect.

What is the best way to phrase directives and guidelines to reduce fragility?▼

Phrasing directives to reduce fragility involves replacing overly confident language with nuanced qualifiers, ensuring instructions acknowledge potential changes or exceptions rather than presenting rigid, unchangeable rules.

How do I distinguish recommendations from requirements in technical writing?▼

You can distinguish recommendations from requirements by applying cautious language guidelines that scope statements appropriately, clarifying the nature of the guidance provided so readers understand what is mandatory versus suggested.

Why does overly confident language cause errors in development roadmaps?▼

Overly confident language causes errors in development roadmaps because absolute directives become outdated or incorrect when exceptions occur, turning rigid documentation into a source of failure rather than reliable guidance.

When do I need to use scoped and time-bound statements in documentation?▼

You need to use scoped and time-bound statements when drafting directives or agent instructions that might face future changes, ensuring the documentation remains accurate by acknowledging potential exceptions instead of using absolute terms.