Story Research Assistant

Creative research

by haowjy · Apache-2.0 license · ★ 506 on GitHub

Creative research cover

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…

---
name: creative-research
description: |
  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.
---

# 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.

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add haowjy/creative-writing-skills --skill creative-research -g -a claude-code
Claude Code (degit)npx degit haowjy/creative-writing-skills/cw/skills/creative-research#main ~/.claude/skills/creative-research
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.2 KB
Read SKILL.md here
haowjy/main1 file shown
SKILL.md
Show the full text74 lines
creative-research/SKILL.md74 lines · 3.2 KB

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.

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.

1---
2name: creative-research
3description: |
4 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.
5---
6 
7# Creative Research
8 
9Gather material the writer can use. Evaluate the evidence — source type,
10reliability, confidence, conflicts — but leave story-fit decisions to the
11writer.
12 
13## What to Look For
14 
15**Primary sources.** Historical records, period documents, first-person
16accounts, letters, diaries, court proceedings, field reports. These carry
17detail and texture that secondary summaries flatten.
18 
19**Reference works and published fiction.** Other novels, short stories, and
20narratives in the genre or period the author is working in. How have other
21writers handled similar material, settings, or problems?
22 
23**History, mythology, and lore.** Real-world events, folklore, cultural
24traditions, religious texts, oral histories. Look for the specific and
25surprising over the general and expected.
26 
27**Wikis and encyclopedias.** Fandom wikis for existing universes, Wikipedia
28for cultural and historical grounding, specialized references (weapons,
29ships, architecture, medicine, botany, legal systems).
30 
31**Community discussion.** Writing forums, book reviews, reader reactions,
32genre convention debates. These surface what readers notice, what they
33forgive, and what breaks immersion.
34 
35**Social media and interviews.** Author craft discussions, writing process
36threads, reader reception patterns, cultural commentary relevant to the
37story's setting or themes.
38 
39**Domain expertise.** How specific fields actually work — medicine, law,
40military, sailing, cooking, farming, forensics, finance. The operational
41details that make fiction feel grounded. Look for practitioner accounts over
42textbook summaries.
43 
44**Place and culture.** Geography, dialects, food, clothing, architecture,
45daily rhythms, social customs, weather patterns. The sensory and social
46texture of a setting.
47 
48## How to Search
49 
50Search for current sources over training-data recall. Cultural understanding,
51historical scholarship, and community consensus shift. Practitioner accounts
52and experience reports are higher-signal than encyclopedia summaries.
53 
54Surface conflicting information. When sources disagree on historical facts,
55cultural practices, or domain details, present both with citations. The
56writer needs to know where the record is contested.
57 
58Follow the specific. "Medieval weapons" is a starting point; "how a
5914th-century English longbowman carried and maintained arrows on campaign" is
60a finding. The writer needs concrete detail, not category overviews.
61 
62## Your Report
63 
64Structure your report:
65 
66- **Usable detail** — concrete findings organized by topic or question
67- **Source notes** — source type, reliability, and confidence for each finding
68- **Conflicts** — where sources disagree, with both sides cited
69- **Contradictions** — anything that conflicts with what the story currently assumes
70- **Gaps** — what you looked for and couldn't find
71 
72Include citations and enough context that the writer can evaluate relevance
73without re-researching. Your final message is your report.
74 
View all files on GitHub →

Details

License
Apache-2.0
Stars on the repo
★ 506
Checked
Source
haowjy/creative-writing-skills ↗
Creator
haowjy · 22 listings
View creator

Similar skills

See all →

More from haowjy

Character Voice Simulatorhaowjy/creative-writing-skills · by haowjySpeak as a specified character from their current knowledge, voice, and emotional state. Use for skill-only workflows that need in-character conversation, voice discovery, or relationship pressure tests.★ 506 GitHub starsFiction Writing Craft Guidehaowjy/creative-writing-skills · by haowjyCraft references for writing fiction well: prose, scenes, style, voice, and genre/page-level technique. Load when a writer, critic, or muse needs how-to-write guidance rather than a production mode.★ 506 GitHub starsWriting Mode Guidehaowjy/creative-writing-skills · by haowjyCreative-writing addendum to /llm-writing. Load when putting prose on the page: draft, revise, bridge, vary, or polish.★ 506 GitHub starsMulti-Mode Writing Studiohaowjy/creative-writing-skills · by haowjyLoad when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.★ 506 GitHub starsOutput Information Hierarchyhaowjy/creative-writing-skills · by haowjyLoad for large human-facing outputs: reports, docs, multi-section explanations, artifacts. Choose the right form for each beat (prose, diagram, table, mockup) and put the answer first, depth behind it. If the medium allows, use progressive disclosure.★ 506 GitHub starsIntent Modeling Interviewhaowjy/creative-writing-skills · by haowjyUse before acting on human instructions: separate what they said from what they meant.★ 506 GitHub stars