Creative Research logo

Creative Research

Community
haowjy
creative-research

Load when a story needs factual grounding the writer doesn't have: historical detail, cultural texture, domain accuracy, or how other authors handled similar material. Pass the question and story context; returns a sourced report the writer can draw from.

Overview

Publisherhaowjy
Repositorycreative-writing-skills
Skill namecreative-research
Stars
511
Forks
69
Bundled files
Instructions only
LicenseApache-2.0
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

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

Installation

Install the Creative Research 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.
    https://github.com/haowjy/creative-writing-skills/tree/main/cw/skills/creative-research
  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/haowjy/creative-writing-skills.git /tmp/creative-writing-skills
mkdir -p .claude/skills
cp -r /tmp/creative-writing-skills/cw/skills/creative-research .claude/skills/creative-research
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Creative Research 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 Creative Research 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 Creative Research 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.

Creative Research

Gather material the writer can use. Evaluate the evidence — source type, reliability, confidence, conflicts — but leave story-fit decisions to the writer.

What to Look For

Primary sources. Historical records, period documents, first-person accounts, letters, diaries, court proceedings, field reports. These carry detail and texture that secondary summaries flatten.

Reference works and published fiction. Other novels, short stories, and narratives in the genre or period the author is working in. How have other writers handled similar material, settings, or problems?

History, mythology, and lore. Real-world events, folklore, cultural traditions, religious texts, oral histories. Look for the specific and surprising over the general and expected.

Wikis and encyclopedias. Fandom wikis for existing universes, Wikipedia for cultural and historical grounding, specialized references (weapons, ships, architecture, medicine, botany, legal systems).

Community discussion. Writing forums, book reviews, reader reactions, genre convention debates. These surface what readers notice, what they forgive, and what breaks immersion.

Social media and interviews. Author craft discussions, writing process threads, reader reception patterns, cultural commentary relevant to the story's setting or themes.

Domain expertise. How specific fields actually work — medicine, law, military, sailing, cooking, farming, forensics, finance. The operational details that make fiction feel grounded. Look for practitioner accounts over textbook summaries.

Place and culture. Geography, dialects, food, clothing, architecture, daily rhythms, social customs, weather patterns. The sensory and social texture of a setting.

How to Search

Search for current sources over training-data recall. Cultural understanding, historical scholarship, and community consensus shift. Practitioner accounts and experience reports are higher-signal than encyclopedia summaries.

Surface conflicting information. When sources disagree on historical facts, cultural practices, or domain details, present both with citations. The writer needs to know where the record is contested.

Follow the specific. "Medieval weapons" is a starting point; "how a 14th-century English longbowman carried and maintained arrows on campaign" is a finding. The writer needs concrete detail, not category overviews.

Your Report

Structure your report:

  • Usable detail — concrete findings organized by topic or question
  • Source notes — source type, reliability, and confidence for each finding
  • Conflicts — where sources disagree, with both sides cited
  • Contradictions — anything that conflicts with what the story currently assumes
  • Gaps — what you looked for and couldn't find

Include citations and enough context that the writer can evaluate relevance without re-researching. Your final message is your report.

Frequently asked questions

What does the Creative Research AI skill do?

Load when a story needs factual grounding the writer doesn't have: historical detail, cultural texture, domain accuracy, or how other authors handled similar material. Pass the question and story context; returns a sourced report the writer can draw from.

Why use Creative Research on TypingMind?

Because you install it once and use it with any model. Creative Research 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 Creative Research in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/haowjy/creative-writing-skills/tree/main/cw/skills/creative-research. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Creative Research?

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 Creative Research?

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

Is the Creative Research AI skill free?

Yes. It is published on GitHub by haowjy under the Apache-2.0 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 👇