ideation
Front stage for /data2story-pro when the reader has no dataset — only a vague idea. Converges the idea into a concrete, data-backed topic through a sparring-partner dialogue (anti-sycophantic, feasibility-pressure-tested), then acquires a REAL dataset through find-data, with a user checkpoint after each. Returns a validated DATA_DIR for the main pipeline. Not a newsroom role — runs upstream of Detective, before any dataset exists. Real data only; never a reason to synthesize data.
npx skills add QinghongLin/data2story-skill --skill ideation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Ideation — from a vague idea to a data-backed topic + a real dataset The `/data2story-pro` orchestrator routes here in **IDEA MODE**: the reader handed over a hunch, a question, or a half-formed angle instead of a dataset. Your job is to turn that into a concrete topic that *real, findable data* can support, fetch that data, and hand a validated folder back to the pipeline. You do this WITH the reader, not for them — two real checkpoints, no railroading. You are not a pipeline role (no `*_NN` provenance prefix, no place in the 7 teams). You run once, before Detective, and produce nothing that reaches the HTML except the dataset + a `story_brief`. ## Inputs - `$1` = the reader's raw idea text (may be empty → open by inviting it). - `$2` = `DATA2STORY_ROOT` (resolved by the orchestrator; where `data/<slug>/` will live). ## Return contract (how the orchestrator continues) - **Success:** emit a final line `DATA_DIR=<absolute path to the validated dataset folder>`. The `story_brief.json` sits at `<DATA_DIR>/meta/story_brief.json`. The orchestrator sets `DATA_DIR`/`DATA_NAME` from this and enters the normal pipeline (Detective → … → Inspector). - **Abort:** emit `IDEATION_ABORTED: <one
- Inputs
- Return contract (how the orchestrator continues)
- The flow — 3 steps, 2 checkpoints
- Step 1 — Converge the idea (reuse sparring-partner)
- CHECKPOINT 1 — confirm the brief
- Step 2 — Acquire a REAL dataset (reuse find-data, web-first)
- CHECKPOINT 2 — confirm the dataset
- Step 3 — Finalize + hand off
- Guardrails
- Reference files
mkdir -p "OUT_DIR/meta" && # write story_brief.json there (valid JSON matching references/schema.json)
What does the ideation skill do?
Front stage for /data2story-pro when the reader has no dataset — only a vague idea. Converges the idea into a concrete, data-backed topic through a sparring-partner dialogue (anti-sycophantic, feasibility-pressure-tested), then acquires a REAL dataset through find-data, with a user checkpoint after each. Returns a validated DATA_DIR for the main pipeline. Not a newsroom role — runs upstream of Detective, before any dataset exists. Real data only; never a reason to synthesize data.
How do I install it?
Run `npx skills add QinghongLin/data2story-skill --skill ideation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From QinghongLin/data2story-skill, a repository with 149 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.