Template Selector logo

Template Selector

Community
jamditis
template-selector

Selects the correct CLAUDE.md or LESSONS.md template via decision trees. Use when starting a project or unsure which fits.

Overview

Publisherjamditis
Repositoryclaude-skills-journalism
Skill nametemplate-selector
Stars
397
Forks
64
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by jamditis on GitHub. Read the source before you install it.

Installation

Install the Template Selector AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git /tmp/claude-skills-journalism
mkdir -p .claude/skills
cp -r /tmp/claude-skills-journalism/project-templates-toolkit/skills/template-selector .claude/skills/template-selector
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Template Selector in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Template Selector on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Template Selector is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Template Selector AI skill do?

Selects the correct CLAUDE.md or LESSONS.md template via decision trees. Use when starting a project or unsure which fits.

Why use Template Selector on TypingMind?

Because you install it once and use it with any model. Template Selector is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Template Selector in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jamditis/claude-skills-journalism/tree/master/project-templates-toolkit/skills/template-selector. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Template Selector?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Template Selector?

As many as you like. As long as a model supports skills, you can use Template Selector with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Template Selector AI skill free?

Yes. It is published on GitHub by jamditis under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇