grove-documentation

Rewrite user-facing documentation in Grove's warm, clear voice.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/GroveScout --skill grove-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grove-documentation
Source: https://github.com/AutumnsGrove/GroveScout/tree/main/.claude/skills/grove-documentation
Command: npx skills add https://github.com/AutumnsGrove/GroveScout --skill grove-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grove documentation often lacks the warm, clear Grove voice that guides Wanderers through complex content. This skill ensures user-facing text is consistently warm, honest, and easy to understand.

Core Features & Use Cases

  • Write help center articles, onboarding copy, tooltips, and error messages in Grove's distinctive voice.
  • Draft specs or technical documentation that are precise, accessible, and aligned with Grove's tone.
  • Review and refine existing content for voice consistency, clarity, and inclusivity.

Quick Start

Rewrite the provided user-facing text in Grove's warm, clear voice.

Frequently Asked Questions about grove-documentation

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

FAQPage Schema
How do I rewrite help center articles to match a consistent brand voice?

Rewriting help center articles requires applying consistent tone guidelines that use inclusive language and concise rhythm while avoiding AI-like phrasing, ensuring user-facing text remains warm and clear. This skill rewrites provided text to match those specific voice standards.

What is the best way to write onboarding copy that sounds warm and natural?

Writing warm onboarding copy involves using inclusive language, concise rhythm, and avoidance of AI-like phrasing to guide users through complex content. This skill rewrites your onboarding text to conform to Grove's distinctive, honest voice guidelines.

How do I make technical documentation more accessible without losing precision?

Making technical documentation accessible requires drafting specs that are precise yet aligned with a warm, clear tone. This skill rewrites technical content to ensure it remains accessible and honest while conforming to Grove's voice guidelines.

Can I use this to refine error messages for clarity and inclusivity?

Yes, you can refine error messages for clarity and inclusivity by rewriting them to conform to Grove's voice guidelines. The skill applies inclusive language and concise rhythm to ensure error messages maintain a consistent, warm tone.

Why does my user-facing documentation sound robotic and how do I fix it?

User-facing documentation sounds robotic when it lacks a consistent, warm voice and uses AI-like phrasing. You can fix it by rewriting the text to apply inclusive language, concise rhythm, and avoidance of automated phrasing.

Are there limitations when reviewing existing content for tone consistency?

The primary limitation when reviewing existing content is that the skill focuses exclusively on conforming text to Grove's specific voice guidelines, meaning it rewrites for warmth and clarity rather than restructuring underlying technical accuracy.