원클릭으로
syft-news-skills
syft-news-skills에는 Solatrader에서 수집한 skills 18개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.
이 저장소의 skills
Use when the user wants a personalized daily news briefing from Syft CLI following topics in Codex or Claude Code without relying on local Python scripts. Also use when the user wants a profile-aware editorial edition, issue clustering, mainline plus supplement structure, stronger interest coverage, or a richer daily briefing from `syft top`.
Use when the user wants to capture long-lived preferences, editorial rules, branch preferences, or filtering instructions into a persistent rulebook in Codex or Claude Code without local helper scripts. Also use when the user wants a confirmation-first workflow before saving durable preferences.
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.
Build or refresh a high-dimensional user profile from `syft following` output. Use when Codex needs to turn a Syft CLI following list into reusable profile artifacts such as `following_topics.md`, raw interest or aversion blocks, and an interpretive `profile_summary.md`, especially when only Syft CLI output is available and richer dashboard or trace artifacts are missing.
Use when the user wants to extend an existing storyline trunk or branch with Syft search results across a time window in Codex or Claude Code without local Python scripts. Also use when the user asks to backfill a branch timeline, repair a thin storyline, derive keyword strategies, merge known events with search evidence on one timeline, or extend hobby-interest logic lines such as IP merch cadence or onsen destination updates.
Use when the user wants to turn Syft CLI news into a trunk-branch storyline tree, attach timelines, render markdown plus html plus json outputs, or prepare branches for later Syft search extension in Codex or Claude Code without local Python scripts. Also use when the user asks for event trees, storyline timelines, branch relationship mapping, hobby-interest logic lines, or a relationship-first reading view.
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.
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.
Use when the user wants a personalized daily news briefing from Syft CLI following topics in Codex or Claude Code without relying on local Python scripts. Also use when the user wants a profile-aware editorial edition, issue clustering, mainline plus supplement structure, stronger interest coverage, or a richer daily briefing from `syft top`.
Use when the user wants to capture long-lived preferences, editorial rules, branch preferences, or filtering instructions into a persistent rulebook in Codex or Claude Code without local helper scripts. Also use when the user wants a confirmation-first workflow before saving durable preferences.
Build or refresh a high-dimensional user profile from `syft following` output. Use when Codex needs to turn a Syft CLI following list into reusable profile artifacts such as `following_topics.md`, raw interest or aversion blocks, and an interpretive `profile_summary.md`, especially when only Syft CLI output is available and richer dashboard or trace artifacts are missing.
Use when the user wants to extend an existing storyline trunk or branch with Syft search results across a time window in Codex or Claude Code without local Python scripts. Also use when the user asks to backfill a branch timeline, repair a thin storyline, derive keyword strategies, merge known events with search evidence on one timeline, or extend hobby-interest logic lines such as IP merch cadence or onsen destination updates.
Use when the user wants to turn Syft CLI news into a trunk-branch storyline tree, attach timelines, render markdown plus html plus json outputs, or prepare branches for later Syft search extension in Codex or Claude Code without local Python scripts. Also use when the user asks for event trees, storyline timelines, branch relationship mapping, hobby-interest logic lines, or a relationship-first reading view.
Use when the user wants a personalized daily news briefing from Syft CLI following topics in Codex or Claude Code without relying on local Python scripts. Also use when the user wants a profile-aware editorial edition, issue clustering, mainline plus supplement structure, stronger interest coverage, or a richer daily briefing from `syft top`.
Use when the user wants to capture long-lived preferences, editorial rules, branch preferences, or filtering instructions into a persistent rulebook in Codex or Claude Code without local helper scripts. Also use when the user wants a confirmation-first workflow before saving durable preferences.
Build or refresh a high-dimensional user profile from `syft following` output. Use when Codex needs to turn a Syft CLI following list into reusable profile artifacts such as `following_topics.md`, raw interest or aversion blocks, and an interpretive `profile_summary.md`, especially when only Syft CLI output is available and richer dashboard or trace artifacts are missing.
Use when the user wants to extend an existing storyline trunk or branch with Syft search results across a time window in Codex or Claude Code without local Python scripts. Also use when the user asks to backfill a branch timeline, repair a thin storyline, derive keyword strategies, merge known events with search evidence on one timeline, or extend hobby-interest logic lines such as IP merch cadence or onsen destination updates.
Use when the user wants to turn Syft CLI news into a trunk-branch storyline tree, attach timelines, render markdown plus html plus json outputs, or prepare branches for later Syft search extension in Codex or Claude Code without local Python scripts. Also use when the user asks for event trees, storyline timelines, branch relationship mapping, hobby-interest logic lines, or a relationship-first reading view.