Skip to content

Solatrader/syft-news-skills / source-skills/syft-storyline-backfill

syft-storyline-backfill

Verified

Use when the user wants to extend an existing storyline trunk or branch with Syft search results across a time window in Codex or Claude Code without local Python scripts. Also use when the user asks to backfill a branch timeline, repair a thin storyline, derive keyword strategies, merge known events with search evidence on one timeline, or extend hobby-interest logic lines such as IP merch cadence or onsen destination updates.

FileKindSize
SKILL.mdskill md6.7 KB
references/keyword-strategy.mdmarkdown1.9 KB
references/merge-template.mdmarkdown1.0 KB

references/merge-template.md

View on GitHub
# Backfill Merge Template

Use this structure when presenting backfill work.
This template is for the backfill memo, not for the final user-facing tree render.

## Target

- trunk / branch id
- branch meaning restatement
- time window

## Queries used

- query 1
- query 2
- query 3

## Primary evidence kept

- `YYYY-MM-DD | 事件标题`
- why it belongs

## Secondary evidence kept

- `YYYY-MM-DD | 事件标题`
- why it is only secondary

## Discarded patterns

- what kinds of results were dropped and why

## Merged timeline

Show one combined timeline with:

- known_pool events
- syft_search_primary events
- syft_search_secondary events

in strict chronological order.

## Important separation

Keep these two layers separate:

- working memo:
  can mention queries, triage decisions, dropped patterns, and retrieval reasoning
- final tree:
  should inherit only the cleaned timeline results and polished prose

Do not paste memo labels such as:

- `thin`
- `discard_note`
- `topic top 路`
- `targeted search 路`

into the final tree outputs.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall