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를 위한 고성능, 빠른 실패(fail-fast)를 제공하는 특화된 스킬
official
critique
google-gemini
저장소 스크립트와 GitHub Actions 워크플로우를 감사하고 수정하여 기술적 견고성과 보안을 보장하는 전문성.
official