Solatrader/syft-news-skills / source-skills/syft-news-pipeline
syft-news-pipeline
VerifiedCoordinate Syft-only personalized news workflows in Codex or Claude Code using only `syft following`, `syft top`, and `syft search`. Use when Codex needs to decide or run the right path for building profile artifacts, capturing durable guidance, drafting daily briefings, generating trunk-branch storyline trees, or backfilling an existing storyline without local Python pipelines, dashboard artifacts, or trace URLs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.8 KB |
| agents/openai.yaml | config | 295 B |
| references/daily-briefing.md | markdown | 1.6 KB |
| references/guidance-rulebook.md | markdown | 1.3 KB |
| references/profile-summary.md | markdown | 1.5 KB |
| references/storyline-backfill.md | markdown | 1.9 KB |
| references/storyline-tree.md | markdown | 2.0 KB |
| references/workflow-map.md | markdown | 1.2 KB |
references/storyline-backfill.md
View on GitHub# Storyline Backfill Route
Use this route after a storyline tree already exists and the user wants one branch, one trunk, or the full tree extended with older or missing events.
## Preferred Inputs
- an existing storyline tree markdown file
- optional html or notes for the same tree
- `profiles/following_topics.md`
- `profiles/profile_summary.md`
- optional confirmed guidance rules
## Outputs
Create:
- `storylines/storyline_backfill_<date>.md`
- optionally updated storyline tree files
- optionally `storylines/backfill_keyword_strategy_<date>.md`
Treat `storyline_backfill_<date>.md` as a working memo.
Treat updated tree files as final-facing outputs.
## Workflow
1. Choose the target branch, trunk, or full tree scope.
2. Restate the branch logic in one sentence before searching.
3. Use the retrieval ladder:
1. existing known events
2. topic top
3. targeted search
4. Generate 3 to 6 query angles only when search is still necessary.
5. Triage results into primary evidence, secondary evidence, and discard.
6. Merge accepted events into the same branch timeline as known events.
7. Sort the merged timeline chronologically.
8. Preserve the existing tree identity unless the user explicitly asks for a reframe.
## Evidence Rules
Primary evidence:
- advances the branch storyline
- fills a missing step
- sharpens causality or escalation
- for hobby lines, marks a meaningful official release, collab, event, merch step, or destination update
Secondary evidence:
- adds surrounding context without advancing the core chain directly
Discard:
- wrong storyline
- generic commentary
- noisy duplicates
## Failure Modes
- drowning the branch in weak search hits
- separating known and backfilled events into different panes
- forgetting chronological ordering
- rewriting the whole taxonomy during a normal backfill run
- leaking working-note tone into final-facing markdown or HTML
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |