essay

Draft, review, and revise voice-grounded essays through a three-phase lifecycle.

1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/rjwalters/bucket-brigade --skill essay-rjwalters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: essay
Source: https://github.com/rjwalters/bucket-brigade/tree/main/.anvil/skills/essay
Command: npx skills add https://github.com/rjwalters/bucket-brigade --skill essay-rjwalters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing short-form essays and blog posts that sound like you—not like an AI—is hard. Most tools focus on grammar or length but miss the voice that makes writing distinctive. This skill solves that by making voice fidelity the central, owned dimension of its review rubric, and by enforcing a strict draft to review to revise lifecycle that catches coherence failures, numeric inconsistencies, and generic AI cadence before publication.

Core Features & Use Cases

  • Voice-Grounded Lifecycle: Draft, review, and revise essays through a canonical three-phase lifecycle ending at a READY state with a documented publish handoff.
  • Corpus-Grounded Voice Fidelity: The skill scores voice as the highest-weighted rubric dimension (weight 7/44) and requires every voice deduction to quote a corpus exemplar.
  • Deterministic Pre-Flight Gates: Runs blocking numeric-consistency and hyperlink-resolution checks before expensive content review, plus advisory rhetoric lint, to catch mechanical errors early.
  • Use Case: A blogger or technical writer can use this skill to produce a 500–1500 word essay that passes a 9-dimension rubric (≥35/44), preserves their unique voice signatures across revisions, and arrives at a .latest-resolvable markdown body ready for their site's TSX deploy pipeline.

Quick Start

Use the essay skill to draft a short-form voice-grounded essay from your project's brief and voice docs, then run the review and revise commands until the thread reaches READY with an advance score of at least 35 out of 44.

Frequently Asked Questions about essay

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

FAQPage Schema
How do I write markdown essays that preserve my personal voice instead of sounding like AI?

To write markdown essays that preserve your personal voice, use a draft-review-revise lifecycle that scores voice fidelity against a 9-dimension rubric. This ensures your unique style signatures remain intact across revisions before publication.

How do I review and score a blog post draft for voice fidelity?

You review and score a blog post draft for voice fidelity by running it through a 9-dimension /44 rubric where voice is the highest-weighted dimension at 7/44. Every voice deduction requires quoting a corpus exemplar to justify the score.

What is the best way to automate pre-flight checks for numeric consistency and broken links in markdown prose?

The best way to automate pre-flight checks for numeric consistency and broken links in markdown prose is to enforce deterministic blocking gates before content review. This catches mechanical errors and hyperlink resolution failures early in the lifecycle.

Can I use a voice-grounded essay workflow for 500 to 1500 word technical blog posts?

Yes, you can use a voice-grounded essay workflow for 500 to 1500 word technical blog posts. The lifecycle produces a resolvable markdown body ready for a TSX deploy pipeline, requiring a project BRIEF with an optional voice block declaring style values.

What score does an essay need to pass the review rubric and reach the READY state?

An essay needs an advance score of at least 35 out of 44 to pass the review rubric and reach the READY state. This threshold ensures the markdown prose artifact meets quality standards across all 9 dimensions, including voice fidelity.

When should I not use a canonical three-phase essay lifecycle for my writing?

You should not use a canonical three-phase essay lifecycle for writing outside the 500 to 1500 word range or when voice fidelity is not your primary success criterion. The strict draft-to-review-to-revise flow is designed specifically for short-form markdown prose artifacts.