tacoda/tack

tack-eval

Prove the repo's committed context actually makes agents effective — run canary tasks that a fresh agent must complete using only the text files (AGENTS.md, docs, ADRs), measure pass/fail, and feed every failure back into the context in the same PR.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/tacoda/tack --skill tack-eval

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

tack-eval: prove the context works

"Agent-ready" should be measured, not asserted. A canary task is a small, realistic, verifiable piece of work an agent must complete using only the committed text — no oral context. If agents pass the canaries, the text represents the truth well enough to work from; if they fail, the failure points at exactly which file is stale or missing.

Procedure

  1. Pick canaries from templates/canary-tasks.md — small, realistic, and

mechanically checkable (commands to run, tests that must pass, files that must exist with expected properties).

  1. Run each canary with a fresh agent that sees only the repo (plus its

normal harness). Record pass/fail + where it got stuck.

  1. Every failure is a context gap: fix the SSOT text file in the same PR

(same-commit rule), not the agent's memory.

  1. Re-run the failed canaries until green.
  2. Track the score (passed/total) in the characterization report

(docs/agent-ready/characterization-report.md) — it should trend up. Optionally run a canary subset in CI on a schedule or on changes to AGENTS.md/docs.

Details: references/eval-practice.md. Canary template: templates/canary-tasks.md.

Exit criteria

  • [ ] A canary set exists and is run on demand (and ideally in CI)
  • [ ] Current score recorded in the characterization report
  • [ ] Every known failure has a same-PR context fix or an owned backlog item