How to Use Séance Stock

A human playbook for developers, builders, and storytellers who want to resurrect the right open-source ghosts.

Why this matters

GitHub is a graveyard of near-miss ideas. Kiro surfaces the ones worth saving and gives you a plan, not just a link.

Every card is a decision: revival potential, abandonment score, quick wins, and a ready-to-ship plan you can copy, export, or send to Kiro.

Summon: Search for what you care about—“react libraries,” “game engines,” “python cli.” Add a language if you want.
See the truth: Each card shows stars, forks, haunted age, and whether it’s a fork or demo data. No surprises.
Read the plan: Tap “View Spell” to see a resurrection plan tuned to the project type and language. Copy, export to markdown, or grab a Kiro prompt.
Act fast: Use the quick-win chips (top 3 steps) to know what to do first—tests, deps, or docs.
Go live: With a token in `.env.local`, you’re using real GitHub data. No token? Demo mode keeps the story flowing.

Skip the spelunking: scoring highlights repos with high potential and clear abandonment risk.
Language-aware plans: JS/TS, Python, Go, Rust, Java all get tailored upgrades and security steps.
CI-ready: Plans call out lint, tests, and GitHub Actions so you can ship confidently.

Validate in minutes: Revival potential and quick wins tell you if a repo is worth the weekend.
Community leverage: Fork and outreach steps help you tap existing stars and contributors.
Ship a story: Export the plan to markdown, drop it into your roadmap or pitch deck.

Curate with context: Cards show why a repo stalled and how to revive it—perfect for content threads.
Show the craft: The “why this score” tooltip and badges make your audience see the signal, not just the stars.
Hands-on demos: Use quick wins as live coding prompts; export plans as show notes.

Revival potential

Stars + forks + issues + language signal. Higher = better candidates.

Abandonment score

Dormant age, issues, forks, archived state. Higher = more haunted.

Badges that matter

Fork? Demo data? Project type? Difficulty? All visible so you never guess.

Quick wins

Top 3 steps from the plan so you can act without scrolling a wall of text.

Live data when you have a token; curated demo data when you don’t—no dead ends on stage.
Project-type detection steers plans: CLI vs API vs UI vs Bot vs Game—all get different spells.
One-click exports: markdown plan, fork link, and Kiro prompt for instant handoff to coding.

Pick a search term, open a card, and run the first quick win. That’s how you turn a haunted repo into a headline.