本文へ移動
cccskills
無料GitHub で公開

curator

Triage the content corpus against the latest GSC snapshot and produce a prioritized refresh report. Read-only: reports, never edits.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Curator — content refresh triage

Read-only analytical skill. Joins GSC traffic data with the content collection and produces a prioritized triage report. Spec: specs/content-curator/spec.md.

Boundaries

  • In scope: reading snapshots, running the triage, and reporting what it finds.
  • Out of scope: editing articles. This skill never edits content. It reports; the human decides what to hand to dev or assess.

When to invoke

  • Periodic content reviews (weekly / monthly).
  • Drill-down on a single article: --page /patterns/typed-handoffs.
  • After publishing several new articles, to refresh the discoverability list.

Workflow

  1. Check snapshot freshness. Run ls -lt data/gsc/*.jsonl | head -1. If the latest snapshot date is older than 14 days (STALE_SNAPSHOT_DAYS in tools/curator/rubric.ts), warn the user and offer to run with --live. Do not block — stale-but-present is still useful.

  2. Run the triage.

    • Default: pnpm curator
    • Single article: pnpm curator -- --page <path>
    • Live refresh: pnpm curator -- --live (re-runs pnpm gsc:snapshot first)
  3. Surface the report. The runner writes reports/curator/YYYY-MM-DD.md. Read it back, summarize the Top 10 in one paragraph plus per-bucket counts, and link to the file. Highlight any "insufficient data" notice or staleness warning.

  4. Hand off, don't fix. For each Top 5 item, name the appropriate next skill:

    • Polish → assess, then dev for the title/meta rewrite
    • Upgrade → assess for a depth-and-structure plan, then dev
    • Refresh → dev to update examples
    • Discoverability → geo-audit

Contract reminders

  • All thresholds live in tools/curator/rubric.ts. Do not quote magic numbers from memory — read the file if asked.
  • Bucket precedence: Polish > Upgrade > Refresh. Discoverability is a separate path (inverse join: article file exists, no snapshot rows).
  • Refresh requires ≥ 120 days of snapshot history. If the snapshot covers less, Refresh reports "insufficient data" and is skipped — this is correct behaviour, not a bug.
  • Reports are not committed — reports/curator/*.md is gitignored. They are GSC-derived (they quote query strings) and regenerable from the snapshot + rubric. Retros run against locally-retained snapshots. See ADR 0002.

Task

$ARGUMENTS

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

assemble

無料

Dev-Critic loop: implement, review, fix — repeat until clean

日本語の概要は準備中です。原文の説明を表示しています。

villetakanen/asdlc-io422026年10月9日 更新

assess

無料

Assess source material against the ASDLC Knowledge Base and produce an evidence-calibrated Content Review Report.

日本語の概要は準備中です。原文の説明を表示しています。

villetakanen/asdlc-io422026年10月9日 更新

critic

無料

Perform an adversarial review of the current uncommitted changeset, validating it against project contracts and architectural intent.

日本語の概要は準備中です。原文の説明を表示しています。

villetakanen/asdlc-io422026年10月9日 更新

dev

無料

Implement features, fix bugs, and keep the codebase healthy and maintainable. Works from a defined PBI, issue, or task description.

日本語の概要は準備中です。原文の説明を表示しています。

villetakanen/asdlc-io422026年10月9日 更新

geo-audit

無料

GEO+SEO audit of asdlc.io — analyzes the codebase for Generative Engine Optimization across AI citability, technical infrastructure, content quality, schema markup, and knowledge base discoverability. Produces a composite GEO Score (0-100) with prioritized action plan.

日本語の概要は準備中です。原文の説明を表示しています。

villetakanen/asdlc-io422026年10月9日 更新

lead

無料

Produce written specs and atomic PBIs that an implementation agent can execute independently. Authors specs and Linear issues.

日本語の概要は準備中です。原文の説明を表示しています。

villetakanen/asdlc-io422026年10月9日 更新

villetakanen のスキルをすべて見る

このスキルの問題を報告する