owl-archive

Guide human-centric documentation writing through a five-phase workflow.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill owl-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: owl-archive
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/owl-archive
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill owl-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write clear, human-readable documentation and user-facing text by guiding you through observation, research, drafting, and refinement, while actively avoiding common AI writing patterns.

Core Features & Use Cases

  • Content Creation Guidance: Provides a structured process for writing various types of documentation (help articles, specs, landing copy).
  • AI Pattern Detection: Helps identify and remove common AI writing tells like em-dashes, overused adverbs, and repetitive sentence structures.
  • Voice & Tone Consistency: Ensures content aligns with the Grove's specific voice guidelines, including user terminology and queer-friendly language.
  • Use Case: When tasked with writing a new help article for a feature, you can use this Skill to ensure the article is clear, user-focused, and sounds like a human wrote it, not an AI.

Quick Start

Use the owl-archive skill to help write a new help article about the user dashboard.

Frequently Asked Questions about owl-archive

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

FAQPage Schema
How do I write technical documentation that doesn't sound like AI?

To write technical documentation that doesn't sound like AI, follow a structured process of observing, hunting, gathering, nesting, and teaching. This approach actively identifies and removes common AI writing anti-patterns like em-dashes, overused adverbs, and repetitive structures.

What are common AI writing anti-patterns to avoid in help articles?

Common AI writing anti-patterns to avoid in help articles include overusing em-dashes, relying on repetitive sentence structures, and inserting unnecessary adverbs. Identifying these patterns during the editing phase ensures your user-facing text reads naturally and maintains a human voice.

What is the best way to structure user-facing text for a feature release?

The best way to structure user-facing text for a feature release is using a five-phase documentation workflow: Observe, Hunt, Gather, Nest, and Teach. This process guides you from initial research through drafting to final refinement, ensuring clear and user-focused content.

Can I use this documentation writing process for marketing copy?

Yes, you can use this documentation writing process for marketing copy. The workflow supports various content creation types including help articles, technical specifications, and landing copy, while ensuring all outputs adhere to specific voice and tone guidelines.

How do I maintain voice and tone consistency across technical documentation?

To maintain voice and tone consistency across technical documentation, apply specific voice guidelines and user terminology during the drafting and editing phases. This ensures all content aligns with established communication standards, including queer-friendly language and human-centric phrasing.