curation

作者: google-gemini

選擇與排名規則——如何將原始抓取的內容池轉化為讀者真正想要的少數項目,並以品味檔案作為引導……

npx skills add https://github.com/google-gemini/gemini-managed-agents-templates --skill curation

Curation Skill

Curation is editing, not summarizing. From the candidate pool in new_items.json, choose the items this specific reader should see today.

Selection Rules

  1. The taste profile decides. Re-read interests.json before selecting. preferences.more entries boost an item; preferences.less entries drop it unless it is genuinely major; preferences.notes carry dated, specific guidance from past feedback — treat recent notes as the strongest signal.
  2. Cap the briefing at 10 news items total across all topics, and up to 4 community-buzz items. Fewer is fine; padding is not. If a topic produced nothing worth including, say so in one line rather than including filler.
  3. Prefer, in order: primary sources and official announcements → original reporting → high-engagement community discussion → aggregation/commentary. Drop listicles and rumor pieces by default (they are on the default less list).
  4. Collapse duplicates of one story. When several outlets carry the same development, pick the strongest single link and mention coverage breadth in the why-it-matters line ("also covered by Reuters and The Verge") — breadth itself is a signal the story matters.
  5. Genre feeds are the serendipity channel. Pick at most 2-3 genre items the reader did not explicitly ask about but would plausibly care about, given their profile. Label them as discoveries.
  6. Community items are for signal, not noise. Select a Hacker News item only when it adds something the news coverage lacks: practitioner experience, technical pushback, or early buzz on something not yet covered.
  7. Longform earns its slot with depth. Select at most 2 Medium pieces per briefing, and only for genuine substance — tutorials, architecture write-ups, first-hand experience reports. Medium has no engagement signal in the feed, so judge entirely on title substance and taste-profile fit; skip anything that reads as engagement-bait or paywalled teaser fluff.

Ranking Within the Briefing

Lead with the item that best combines: relevance to an explicit topic, recency, source quality, and taste-profile fit. Genre discoveries and community buzz always come after the reader's explicit topics.

What Never Gets Selected

  • Items you cannot link.
  • Items whose headline alone is too thin to say why it matters — do not pad with invented detail.
  • Pure engagement-bait framed as news, regardless of topic match.

來自 google-gemini 的更多技能

greeter
google-gemini
一個友善的問候技能
official
code-reviewer
google-gemini
針對本地變更與遠端拉取請求的自動化程式碼審查,提供涵蓋正確性、可維護性及安全性的結構化分析。支援本地檔案系統變更(包含暫存與未暫存)及遠端 PR(依編號或網址),並自動透過 GitHub CLI 進行檢出。從七個面向分析程式碼:正確性、可維護性、可讀性、效率、安全性、邊界情況處理及測試覆蓋率。可執行選用的前置驗證套件(例如 npm run preflight)以提前發現問題。
official
review-duplication
google-gemini
在程式碼審查期間使用此技能,主動檢查程式碼庫中是否存在重複功能、重複造輪子或未能重複使用現有…
official
reconciliation
google-gemini
將已載入的費用與預先解析的發票資料庫進行比對,標記出金額不符、遺漏發票及商家不匹配等差異…
official
agent-tui
google-gemini
Main Agents: Do NOT use this skill directly. If you need to test the TUI, invoke the `tui_tester` subagent. Drive terminal UI (TUI) applications…
official
async-pr-review
google-gemini
當使用者想要開始非同步的 PR 審查、對 PR 執行背景檢查,或查看先前開始的非同步 PR 狀態時,觸發此技能…
official
ci
google-gemini
專為 Gemini CLI 設計的高效能、快速失敗的專業技能
official
critique
google-gemini
專長於審計和修復儲存庫腳本及 GitHub Actions 工作流程,以確保技術穩健性與安全性。
official