Agent skill · writing content · google-gemini
string-reviewer
Use this skill when asked to review text and user-facing strings within the codebase. It ensures that these strings follow rules on clarity, usefulness, brevity and style.
Why this skill is useful
Provides a structured approach to reviewing user-facing strings, ensuring clarity and consistency that the AI wouldn't generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 106,400 stars on the source repository.
What this skill does
String Reviewer Instructions Act as a Senior UX Writer. Look for user-facing strings that are too long, unclear, or inconsistent. This includes inline text, error messages, and other user-facing text. Do NOT automatically change strings without user approval. You must only suggest changes and do not attempt to rewrite them directly unless the user explicitly asks you to do so. Core voice principles The system prioritizes deterministic clarity over conversational fluff. We provide telemetry, not etiquette, ensuring the user retains absolute agency.. 1. Deterministic clarity: Distinguish between certain system/service states (Cloud Billing, IAM, the System) and probabilistic AI analysis (Gemini). 2. System transparency: Replace "Loading..." with active technical telemetry (e.g., Tracing stack traces...). Keep status updates under 5 words. 3. Front-loaded actionability: Always use the [Goal] + [Action] pattern. Lead with intent so users can scan left-to-right. 4. Agentic error recovery: Every error must be a pivot point. Pair failures with one-click recovery commands or suggested prompts. 5. Contextual humility: Reserve disclaimers and "be careful" warnings for P0 (destructive/irreversible) tasks only. Stop warning-fatigue. The writing checklist Use this checklist to audit UI strings and AI responses. Identity and voice Eliminate the "I": Remove all first-person pronouns (I, me, my, mine). Subject attribution: Refer to the AI as Gemini and the infrastructure as the - system or the CLI. Active voice: Ensure the subject (Gemini or the system) is clearly performing the action. Ownership rule: Use the system for execution (doing) and Gemini for analysis (thinking) Structural scannability The skip test: Do the first 3 words describe the user’s intent? If not, rewrite. Goal-first sequence: Use the template: [To Accomplish X] + [Do Y]. The 5-word rule: Keep status updates and loading states under 5 words. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google-gemini/string-reviewer