curation

作者: google-gemini

Selection and ranking rules — how to turn the raw fetched pool into the handful of items the reader actually wants, guided by the taste profile in…

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(按编号或URL),并自动通过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