tighten

Review documents for information density and structural organization.

2|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/zachmayer/skills --skill tighten-zachmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tighten
Source: https://github.com/zachmayer/skills/tree/main/.claude/skills/tighten
Command: npx skills add https://github.com/zachmayer/skills --skill tighten-zachmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of document accretion, where information becomes scattered, inconsistent, or bloated over time, making it difficult for readers to extract key insights efficiently.

Core Features & Use Cases

  • Information Density Review: Evaluates content to ensure every line provides maximum signal per token.
  • Structural Optimization: Reorganizes information to match the reader's needs and ensures canonical homes for facts.
  • Use Case: Use this when you have a complex README, technical specification, or project proposal that feels cluttered and want to ensure it is concise, consistent, and well-structured.

Quick Start

Ask the agent to tighten this document for information density and structural clarity.

Frequently Asked Questions about tighten

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

FAQPage Schema
How do I improve the information density of a technical README?

Improving information density in technical documentation requires a multi-model studio critique that evaluates every line for maximum signal per token, reorganizes structural elements, and ensures canonical homes for scattered facts.

What is the best way to refactor a cluttered project specification?

Refactoring a cluttered project specification involves performing a panel-based review to synthesize structural optimizations and formatting consistency findings into a single diffable commit.

How does a multi-model critique process work for technical documentation?

A multi-model critique process works by facilitating a panel-based review on finished artifacts to evaluate information density, structural organization, and formatting consistency, synthesizing the findings into a single diffable commit.

Can I use this approach to refine a PR description for high-signal communication?

Yes, you can refine a PR description for high-signal communication by applying a multi-model studio critique that targets information density and structural organization to reduce document accretion.

Do I need a discussion-partners skill to coordinate a panel-based document review?

Yes, coordinating a panel-based document review requires the discussion-partners skill to facilitate the review process and synthesize the structural and density critique findings into a single diffable commit.