Skip to main content
skill CX Codex

template-selector — Claude Code skill: what it does, how to install

template-selector maps journalism and publishing repositories to instruction or LESSONS.md templates using structured decision trees.

MIT 175 installs ★ 458 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jamditis/claude-skills-journalism --skill template-selector -a claude-code
Open on GitHub

What template-selector does

The skill categorizes publishing repositories into one of six categories: editorial-tool, event-website, publication, research-project, content-pipeline, or digital-archive. It guides the agent to locate matching files from project-memory/templates/ and project-retrospective/templates/.

Decision rules include concrete litmus tests and distinctions for common edge cases. For instance, an AI fact-checker is treated as an editorial tool rather than an investigation. If your repository is general software unrelated to newsrooms or publishing, this decision tree routes you out to standard generic templates.

What it helps with

  • select the matching project instruction template for a newsroom repo
  • differentiate between an editorial tool and a one-off investigation
  • pick the right structure for a LESSONS.md retrospective file
  • categorize digital archives, feeds, and event sites without guesswork

Example prompts for the agent

  • Help me pick a project template for an investigative data journalism series.
  • Which template category fits an automated syndication pipeline between CMSes?
  • Categorize our newsroom fact-checking tool using your decision tree.

How to install template-selector

1Skills CLI (Vercel)

npx skills add jamditis/claude-skills-journalism --skill template-selector -a claude-code

2Manually: put the files in place

~/.claude/skills/template-selector/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/template-selector/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about template-selector

How to install template-selector in Claude Code?

Run npx skills add jamditis/claude-skills-journalism --skill template-selector -a claude-code.

What does template-selector do?

It evaluates project attributes against a decision tree to choose instruction and retrospective templates for journalism software.

Can I use template-selector for non-journalism software?

The decision tree identifies general software and points to standard templates outside this specific collection.

Source text

SKILL.md · MIT
---
name: template-selector
description: Selects the correct project instruction or LESSONS.md template via decision trees. Use when starting a project or unsure which fits.
---

# Template selector

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

## Quick reference

| Project type | Template category |
|-------------|-------------------|
| Newsroom AI tool, fact-checker | editorial-tool |
| Conference, summit, workshop | event-website |
| Newsletter, podcast, blog | publication |
| Investigation, data journalism | research-project |
| CMS workflow, syndication | content-pipeline |
| Historical collection, archive | digital-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

| Project | Wrong choice | Right choice | Why |
|---------|-------------|--------------|-----|
| Newsletter dashboard | editorial-tool | publication | It's about the publication, not the tech |
| AI fact-checker | research-project | editorial-tool | It's a tool, not a one-off investigation |
| Event registration system | event-website | editorial-tool | It's a tool that serves events |
| Podcast website | content-pipeline | publication | It's a publication, not automation |
| Document search tool | digital-archive | editorial-tool | It's a tool, not the archive itself |
| FOIA tracking system | research-project | editorial-tool | It'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 instructions
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.*

© jamditis · MIT · jamditis/claude-skills-journalism

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set35

The whole set →
project-retrospective project-retrospective creates LESSONS.md files that capture project knowledge and failures. Use when closing a project or investigation to record what worked, what didn't, and specific action items before the team moves on. CX Codex +1 189installs python-pipeline python-pipeline is a Claude Code skill for modular Python data pipelines, batch jobs, content routing, and Google Sheets or Drive integrations. CX Codex +1 189installs api-hardening api-hardening is a Claude Code skill for hardening APIs built with Express, FastAPI, or serverless. It activates for work on rate limits, CORS, input checks, API keys, and OWASP API risks. CX Codex +1 186installs project-memory project-memory generates project instruction files like AGENTS.md or CLAUDE.md to pass institutional knowledge to AI agents without generic clutter. CX Codex +1 180installs mobile-debugging mobile-debugging hands the agent a method for opening a JS console on a phone or tablet and debugging pages without desktop DevTools: Eruda, vConsole, USB inspection. CX Codex +1 176installs accessibility-compliance accessibility-compliance is a Claude Code skill that provides accessibility patterns for newsrooms and academic publishers, including a WCAG 2.2 AA checklist, alt text rules, and chart markup for assistive tech. CX Codex +1 174installs web-ui-best-practices web-ui-best-practices is a Claude Code skill that sets rules for building and reviewing web interfaces. It covers dashboards and SaaS apps. CX Codex +1 172installs one-way-door one-way-door catches irreversible architecture decisions before commit, targeting data models, infra setups, auth boundaries, and API schemas. CX Codex +1 168installs

Project sponsors

Companies that keep this analytics open