Solatrader/syft-news-skills / codex-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 |
|---|---|---|
| LICENSE.txt | markdown | 9.0 KB |
| 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-tree.md
View on GitHub# Storyline Tree Route
Use this route when the user wants a relationship-first reading view rather than a flat briefing.
## Preferred Inputs
- an aggregated daily news pool
- a finished daily briefing
- `profiles/profile_summary.md`
- `profiles/following_topics.md`
- optional confirmed guidance rules
## Outputs
Create:
- `storylines/storyline_tree_<date>.md`
- `storylines/storyline_tree_<date>.html`
- `storylines/storyline_tree_<date>.json`
- optionally `storylines/storyline_notes_<date>.md`
Visible outputs must be polished deliverables.
Do not leak retrieval notes, query wording, or route jargon into user-facing prose.
## Core Model
Organize information into:
1. facts
2. events
3. branches
4. trunks
Each trunk should express one structural storyline.
Each branch should express one interpretable angle attached to that trunk.
## Build Order
1. Identify 3 to 8 candidate trunks from the cleaned pool.
2. Test whether each candidate really deserves trunk status.
3. Create branches only after trunk identity is coherent.
4. Use topic top or search extension only after the base tree is stable.
## Admission Rules
A trunk usually needs at least two of:
- structural consequence
- multi-event continuity
- a clear causal chain
- strong match to declared macro or identity interests
- capacity to support more than one meaningful branch
Thin but relevant material should stay visible as a branch, watch item, or orphan highlight rather than being silently dropped.
## Hobby and Culture Rules
- Do not merge unrelated IPs or collector logics.
- Keep Fate, EVA, cameras, and Japan travel separate when they are independently meaningful.
- Allow branch logic based on recurring cadence, not only macro-style causality.
## Quality Gate
Before finalizing, verify:
1. trunk and branch titles read like names
2. merged timelines are chronologically sorted
3. visible Chinese reads naturally
4. HTML looks like an editorial card page, not a debug dashboard
5. thin but relevant interests remain visible somewhere
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 |