Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jamditis avatar

Template Selector

  • 129 installs
  • 353 repo stars
  • Updated August 2, 2026
  • jamditis/claude-skills-journalism

Pick the right journalism or corporate writing template—press release, brief, editorial, FAQ—before drafting so structure, tone, and required sections match the story.

About

Journalism-focused template selector that routes writers to the appropriate document pattern—press release, crisis brief, feature outline, or FAQ—based on audience, urgency, and distribution channel so drafts start with correct sections and editorial conventions.

  • Maps story intent to proven journalism formats
  • Reduces rework from mismatched document structures
  • Surfaces required sections per template type
  • Speeds editorial handoffs with consistent scaffolds
  • Supports repeatable newsroom and comms workflows

Template Selector by the numbers

  • 129 all-time installs (skills.sh)
  • +6 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #302 of 688 Office & Documents skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jamditis/claude-skills-journalism --skill template-selector

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs129
repo stars353
Last updatedAugust 2, 2026
Repositoryjamditis/claude-skills-journalism

What it does

Pick the right journalism or corporate writing template—press release, brief, editorial, FAQ—before drafting so structure, tone, and required sections match the story.

Files

SKILL.mdMarkdownGitHub ↗

Template selector

Match projects to the correct template category. Don't guess—use the decision tree.

Quick reference

Project typeTemplate category
Newsroom AI tool, fact-checkereditorial-tool
Conference, summit, workshopevent-website
Newsletter, podcast, blogpublication
Investigation, data journalismresearch-project
CMS workflow, syndicationcontent-pipeline
Historical collection, archivedigital-archive

Decision tree

Is it for journalism/publishing?
├── Yes →
│   ├── Has specific end date/event? → event-website
│   ├── Ongoing content series? → publication
│   ├── Historical/preservation? → digital-archive
│   ├── Newsroom tool/AI? → editorial-tool
│   ├── CMS/automation? → content-pipeline
│   └── Investigation with scope? → research-project
│
└── No (general software) →
    Use general template or another collection

Detailed category descriptions

editorial-tool

Use when: Building newsroom tools, writing assistants, fact-checkers, AI-powered research tools, moderation systems, workflow automation for journalists

Not for: Generic productivity tools, non-journalism software

Signs it's an editorial tool:

  • Primary users are journalists, editors, or producers
  • Helps with a specific editorial workflow step
  • Requires accuracy/trust for publication decisions

event-website

Use when: Building sites for conferences, summits, workshops, or events with specific dates

Not for: Ongoing content, organization websites without events, event management software (that's editorial-tool)

Signs it's an event website:

  • Has a specific event date (or date range)
  • Registration/attendance is involved
  • Content includes speakers, schedule, venue info

publication

Use when: Building newsletters, podcasts, blogs, magazines, or ongoing content series with regular publishing schedule

Not for: One-off articles, static content sites, CMSes that power publications (that's editorial-tool)

Signs it's a publication:

  • Regular publishing cadence (daily, weekly, monthly)
  • Growing subscriber/reader base
  • Consistent voice and format

research-project

Use when: Building investigative journalism projects, data journalism, analysis with defined scope and end date

Not for: Ongoing research operations, general data analysis, tools that support research (that's editorial-tool)

Signs it's a research project:

  • Answers a specific question or hypothesis
  • Has a defined end point (publication date)
  • Involves data collection, analysis, and findings

content-pipeline

Use when: Building CMS workflows, publishing automation, content syndication systems, feed aggregators, cross-posting tools

Not for: Manual publishing workflows, single-site content management, publications themselves

Signs it's a content pipeline:

  • Automates content movement between systems
  • Transforms content formats
  • Handles scheduling and distribution

digital-archive

Use when: Building historical collections, preservation projects, research databases, document repositories

Not for: Active news sites, CMS platforms, search engines

Signs it's a digital archive:

  • Primary focus is preservation
  • Collection has defined scope (time period, topic)
  • Users are researchers, historians, or the public seeking historical content

Common mistakes

ProjectWrong choiceRight choiceWhy
Newsletter dashboardeditorial-toolpublicationIt's about the publication, not the tech
AI fact-checkerresearch-projecteditorial-toolIt's a tool, not a one-off investigation
Event registration systemevent-websiteeditorial-toolIt's a tool that serves events
Podcast websitecontent-pipelinepublicationIt's a publication, not automation
Document search tooldigital-archiveeditorial-toolIt's a tool, not the archive itself
FOIA tracking systemresearch-projecteditorial-toolIt's a tool that supports research

The litmus test

If you're still unsure, ask:

1. Is this a tool that helps journalists do X, or is this X itself?

  • Tool → editorial-tool
  • The thing itself → other categories

2. Does it have a specific end date?

  • Yes, event dates → event-website
  • Yes, publication date → research-project
  • No, ongoing → publication, content-pipeline, or digital-archive

3. Is preservation the primary goal?

  • Yes → digital-archive
  • No → other categories

Using templates

For project memory (CLAUDE.md)

1. Identify project category using decision tree above 2. Copy appropriate template from project-memory/templates/ 3. Fill in bracketed placeholders with your specifics 4. Delete sections that don't apply 5. Add project-specific gotchas as you discover them

For retrospectives (LESSONS.md)

1. Identify project category 2. Copy appropriate template from project-retrospective/templates/ 3. Fill in as the project progresses or at completion 4. Be specific about failures—that's the valuable part

Template locations

claude-skills-journalism/
├── project-memory/templates/
│   ├── editorial-tool.md
│   ├── event-website.md
│   ├── publication.md
│   ├── research-project.md
│   ├── content-pipeline.md
│   └── digital-archive.md
│
└── project-retrospective/templates/
    ├── editorial-tool.md
    ├── event.md
    ├── publication.md
    └── research-project.md

---

Pick the specific template that fits. "General" is a last resort.

Related skills

Office & Documentsworkflownotespm

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.