Claude-skill-registry catskill-writer

Write Catskill Crew newsletter content in Michael's voice. Use when writing HAPPENINGS, REPORT, BULLETIN sections or assembling a complete newsletter edition.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/catskill-writer" ~/.claude/skills/majiayu000-claude-skill-registry-catskill-writer && rm -rf "$T"
manifest: skills/data/catskill-writer/SKILL.md
source content

<essential_principles>

The Catskill Crew Voice

Persona: A friendly local who genuinely loves the Catskills, knows everyone, and is excited to share what's happening. Think of a well-connected neighbor with the inside scoop.

Tone: Casual, warm, enthusiastic (but not over-the-top), insider-y

Audience: "Locals, Weekenders, and Wanderers" - Mix of full-time residents and NYC folks with second homes.

Voice Rules (Apply to ALL Writing)

1. First Person, Direct Address

  • Use "I" and "my friends" frequently
  • Speak directly to reader as a friend
  • Personal interjections and opinions

2. Casual Language

  • Contractions always (don't, won't, I'll, ya)
  • "Ya" instead of "you" sometimes
  • Informal phrases: "hop to it", "tis the season", "have fun"
  • NO corporate speak

3. Punchy Descriptors After event links, add brief insider notes in brackets:

  • [strong name]
    ,
    [cinematic & mysterious]
    ,
    [soulful]
  • [lizard pose]
    ,
    [aprés ski]
    ,
    [sip sip]
  • [nice]
    ,
    [love it]
    ,
    [enjoy]
    ,
    [don't sleep on this]

4. Enthusiasm Without Excess

  • Genuinely excited but not hyperbolic
  • Let events speak for themselves
  • Don't oversell

Words to Use vs Avoid

UseAvoid
grabpurchase
check outview
yayou (sometimes)
folkspeople
my friendsreaders
hop to ithurry
let's get into itlet's begin
famfamily/community
</essential_principles>
<intake> What would you like to write?
  1. HAPPENINGS - Weekly events section (Tue → Mon)
  2. REPORT - Conditions table + optional categories
  3. BULLETIN - Announcements, merch, giveaways
  4. Full newsletter - Assemble all sections into complete edition

Wait for response before proceeding. </intake>

<routing> | Response | Workflow | |----------|----------| | 1, "happenings", "events" | `workflows/write-happenings.md` | | 2, "report", "conditions" | `workflows/write-report.md` | | 3, "bulletin", "announcements" | `workflows/write-bulletin.md` | | 4, "full", "newsletter", "assemble" | `workflows/assemble-newsletter.md` | </routing>

<reference_index> All domain knowledge in

references/
:

Formats: section-formats.md Examples: newsletter-examples.md </reference_index>

<workflows_index>

WorkflowPurpose
write-happenings.mdEvents organized by day with featured section
write-report.mdConditions table + PETS/SKY/PROPERTY
write-bulletin.mdMerch, announcements, giveaways
assemble-newsletter.mdCombine all sections into full edition
</workflows_index>

<success_criteria> Writing is complete when:

  • Voice is consistent (casual, first-person, insider-y)
  • All sections follow proper format
  • Punchy descriptors on event links
  • No corporate language
  • Newsletter saved to
    output/newsletter_YYYY-MM-DD.md
    </success_criteria>