Skip to content

Solatrader/syft-news-skills / codex-skills/syft-news-pipeline

syft-news-pipeline

Verified

Coordinate 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.

references/workflow-map.md

View on GitHub
# Workflow Map

Use this file when the user request spans more than one Syft workflow stage.

## Default End-to-End Order

1. Build or refresh profile artifacts.
2. Capture durable guidance only if the user expresses stable preferences.
3. Produce a daily briefing.
4. Build a storyline tree when the user wants relationship-first reading.
5. Backfill the tree when a branch or trunk needs more chronology.

## Short Routes

- Request is only about profile understanding:
  run profile summary only.
- Request is only about a one-off personalized briefing:
  run profile summary, then daily briefing.
- Request is only about storing a long-term rule:
  run guidance rulebook only.
- Request is about turning today's pool into structured storylines:
  run daily briefing, then storyline tree.
- Request is about deepening an existing tree:
  run storyline backfill only.

## Shared Assumptions

- `syft following` is the first declared-interest source in Syft-only mode.
- `profile_summary.md` is an interpretation layer, not a stronger truth source than follows.
- Topic-local retrieval should usually come before free-text search.
- Final-facing outputs should be polished deliverables, not debug artifacts.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall