AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Creative Research

skill-haowjy-creative-writing-skills-creative-research · by haowjy

>

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-haowjy-creative-writing-skills-creative-research

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-haowjy-creative-writing-skills-creative-research)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Creative Research? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.