Skip to content
Agentmart
Submit a tool
This entry duplicates creative-research, which is the one we list in search.

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…

Skill by FiredMosquito831

IndexedApache-2.0★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/firedmosquito831-creative-research

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: documents, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill 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.
License
Apache-2.0
Instructions
69 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

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

From FiredMosquito831/my-writing-companion, Apache-2.0.

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Sep 9, 2026 (1 month ago)
Last release
Sep 11, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from FiredMosquito831

Cite this page

creative-research skill. Agent Mart. https://agentmart.dev/skills/firedmosquito831-creative-research (last updated 2026-10-24)