$npx -y skills add jamditis/claude-skills-journalism --skill template-selectorChoose the correct CLAUDE.md or LESSONS.md template for journalism projects. Use when starting a new project, setting up documentation, or unsure which template category fits best. Provides decision trees and selection guidance for 6 journalism-focused template types.
| 1 | # Template selector |
| 2 | |
| 3 | Match projects to the correct template category. Don't guess—use the decision tree. |
| 4 | |
| 5 | ## Quick reference |
| 6 | |
| 7 | | Project type | Template category | |
| 8 | |-------------|-------------------| |
| 9 | | Newsroom AI tool, fact-checker | editorial-tool | |
| 10 | | Conference, summit, workshop | event-website | |
| 11 | | Newsletter, podcast, blog | publication | |
| 12 | | Investigation, data journalism | research-project | |
| 13 | | CMS workflow, syndication | content-pipeline | |
| 14 | | Historical collection, archive | digital-archive | |
| 15 | |
| 16 | ## Decision tree |
| 17 | |
| 18 | ``` |
| 19 | Is it for journalism/publishing? |
| 20 | ├── Yes → |
| 21 | │ ├── Has specific end date/event? → event-website |
| 22 | │ ├── Ongoing content series? → publication |
| 23 | │ ├── Historical/preservation? → digital-archive |
| 24 | │ ├── Newsroom tool/AI? → editorial-tool |
| 25 | │ ├── CMS/automation? → content-pipeline |
| 26 | │ └── Investigation with scope? → research-project |
| 27 | │ |
| 28 | └── No (general software) → |
| 29 | Use general template or another collection |
| 30 | ``` |
| 31 | |
| 32 | ## Detailed category descriptions |
| 33 | |
| 34 | ### editorial-tool |
| 35 | **Use when:** Building newsroom tools, writing assistants, fact-checkers, AI-powered research tools, moderation systems, workflow automation for journalists |
| 36 | |
| 37 | **Not for:** Generic productivity tools, non-journalism software |
| 38 | |
| 39 | **Signs it's an editorial tool:** |
| 40 | - Primary users are journalists, editors, or producers |
| 41 | - Helps with a specific editorial workflow step |
| 42 | - Requires accuracy/trust for publication decisions |
| 43 | |
| 44 | ### event-website |
| 45 | **Use when:** Building sites for conferences, summits, workshops, or events with specific dates |
| 46 | |
| 47 | **Not for:** Ongoing content, organization websites without events, event management software (that's editorial-tool) |
| 48 | |
| 49 | **Signs it's an event website:** |
| 50 | - Has a specific event date (or date range) |
| 51 | - Registration/attendance is involved |
| 52 | - Content includes speakers, schedule, venue info |
| 53 | |
| 54 | ### publication |
| 55 | **Use when:** Building newsletters, podcasts, blogs, magazines, or ongoing content series with regular publishing schedule |
| 56 | |
| 57 | **Not for:** One-off articles, static content sites, CMSes that power publications (that's editorial-tool) |
| 58 | |
| 59 | **Signs it's a publication:** |
| 60 | - Regular publishing cadence (daily, weekly, monthly) |
| 61 | - Growing subscriber/reader base |
| 62 | - Consistent voice and format |
| 63 | |
| 64 | ### research-project |
| 65 | **Use when:** Building investigative journalism projects, data journalism, analysis with defined scope and end date |
| 66 | |
| 67 | **Not for:** Ongoing research operations, general data analysis, tools that support research (that's editorial-tool) |
| 68 | |
| 69 | **Signs it's a research project:** |
| 70 | - Answers a specific question or hypothesis |
| 71 | - Has a defined end point (publication date) |
| 72 | - Involves data collection, analysis, and findings |
| 73 | |
| 74 | ### content-pipeline |
| 75 | **Use when:** Building CMS workflows, publishing automation, content syndication systems, feed aggregators, cross-posting tools |
| 76 | |
| 77 | **Not for:** Manual publishing workflows, single-site content management, publications themselves |
| 78 | |
| 79 | **Signs it's a content pipeline:** |
| 80 | - Automates content movement between systems |
| 81 | - Transforms content formats |
| 82 | - Handles scheduling and distribution |
| 83 | |
| 84 | ### digital-archive |
| 85 | **Use when:** Building historical collections, preservation projects, research databases, document repositories |
| 86 | |
| 87 | **Not for:** Active news sites, CMS platforms, search engines |
| 88 | |
| 89 | **Signs it's a digital archive:** |
| 90 | - Primary focus is preservation |
| 91 | - Collection has defined scope (time period, topic) |
| 92 | - Users are researchers, historians, or the public seeking historical content |
| 93 | |
| 94 | ## Common mistakes |
| 95 | |
| 96 | | Project | Wrong choice | Right choice | Why | |
| 97 | |---------|-------------|--------------|-----| |
| 98 | | Newsletter dashboard | editorial-tool | publication | It's about the publication, not the tech | |
| 99 | | AI fact-checker | research-project | editorial-tool | It's a tool, not a one-off investigation | |
| 100 | | Event registration system | event-website | editorial-tool | It's a tool that serves events | |
| 101 | | Podcast website | content-pipeline | publication | It's a publication, not automation | |
| 102 | | Document search tool | digital-archive | editorial-tool | It's a tool, not the archive itself | |
| 103 | | FOIA tracking system | research-project | editorial-tool | It's a tool that supports research | |
| 104 | |
| 105 | ## The litmus test |
| 106 | |
| 107 | If you're still unsure, ask: |
| 108 | |
| 109 | 1. **Is this a tool that helps journalists do X, or is this X itself?** |
| 110 | - Tool → editorial-tool |
| 111 | - The thing itself → other categories |
| 112 | |
| 113 | 2. **Does it have a specific end date?** |
| 114 | - Yes, event dates → event-website |
| 115 | - Yes, publication date → research-project |
| 116 | - No, ongoing → publication, content-pipeline, or digital-archive |
| 117 | |
| 118 | 3. **Is preservation the primary goal?** |
| 119 | - Yes → digital-archive |
| 120 | - No → other categories |
| 121 | |
| 122 | ## Using templates |
| 123 | |
| 124 | ### For project memory (CLAUDE.md) |
| 125 | 1. Identify project category |