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/profile-summary.md
View on GitHub# Profile Summary Route
Use this route when Codex needs to turn `syft following` into reusable profile artifacts.
## Goal
Create or refresh:
- `profiles/following_topics.md`
- `profiles/raw_interest_block.txt`
- `profiles/raw_aversion_block.txt`
- `profiles/profile_summary.md`
- optionally `profiles/profile_notes.md`
Reuse an existing profile directory if the workspace already has one.
## Steps
1. Run `syft status`.
2. Run `syft following`.
3. Save the following list with only light cleanup into `profiles/following_topics.md`.
4. Treat the following list as the canonical source artifact in Syft-only environments.
5. If a raw interest block is useful, infer broad score bands rather than fake precision.
6. Do not invent aversions from follows alone.
7. Draft `profile_summary.md` as an interpretive layer, not a mechanical restatement.
8. Before treating the profile as stable, summarize your inferred axes and note uncertainty caused by missing aversion data.
## Scoring Guidance
If a raw interest block is needed, use stable score bands such as:
- `100`: defining axis
- `85`: strong recurring axis
- `70`: meaningful secondary axis
- `55`: supporting but not central
- `35`: light or occasional interest
Keep the file honest about being heuristic rather than user-authored.
## Output Rules
- Write user-facing content in Simplified Chinese unless asked otherwise.
- Call out the tension directly when the follow graph shows hard macro tracking alongside softer refuge interests.
- Keep `following_topics.md` closer to raw truth than `raw_interest_block.txt`.
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 |