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/guidance-rulebook.md
View on GitHub# Guidance Rulebook Route
Use this route when the user expresses a durable preference that may need to persist across future runs.
## Goal
Maintain a persistent guidance file, usually:
- `profiles/user_guidance_rulebook.md`
Reuse an existing rulebook format if the workspace already uses JSON or another stable structure.
## Confirmation-First Workflow
Never persist a durable rule from one raw sentence alone.
Always do this in order:
1. summarize your understanding
2. ask whether the summary is correct
3. ask whether the user wants it persisted
4. only then write it into the rulebook
## Good Candidates
- long-term content preferences
- editorial preferences
- storyline handling preferences
- recurring search preferences
- durable dislikes or red lines
## Bad Candidates
- one-off requests for today
- temporary formatting asks
- speculative guesses that were not confirmed
## Entry Shape
Preserve these fields in each stored rule:
- `id`
- `name`
- `scope`
- `kind`
- `priority`
- `status`
- canonical guidance text
- short rationale
- source note
- confirmed date
## Scope Bands
- `all`
- `editorial`
- `storyline`
- `syft_search`
- `recommendation`
## Priority Bands
- `85-100`: identity-defining
- `65-80`: meaningful preference
- `40-60`: soft preference
- `<40`: weak or situational preference
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 |