refresh-cr-tracker

Stars9

Forks1

UpdatedJuly 4, 2026 at 14:17

Rebuild and republish the CR-task master tracker artifact. Use when the user says "refresh cr tracker", "update the CR task tracker", "/refresh-cr-tracker", or wants the conceptual-reasoning task master list re-pulled from live reasoning-tasks data + GitHub issues and redeployed to its claude.ai artifact.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

benthamite

benthamite/dotfiles

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	refresh-cr-tracker
description	Rebuild and republish the CR-task master tracker artifact. Use when the user says "refresh cr tracker", "update the CR task tracker", "/refresh-cr-tracker", or wants the conceptual-reasoning task master list re-pulled from live reasoning-tasks data + GitHub issues and redeployed to its claude.ai artifact.

Refresh the CR-task master tracker

Rebuilds ~/Trajectory/cr-scout-runs/cr-task-master-list.html from live sources and redeploys it to the existing claude.ai artifact (so newly-registered GitHub issues, new cohort tasks, and updated scores show up).

Must run in an INTERACTIVE session — the Artifact tool is not available in headless claude -p or cloud routines. Requires the local ~/Trajectory/reasoning-tasks/main worktree and a working gh/GitHub token (both present on Pablo's Mac).

Steps

Build. Run:
```
python3 ~/Trajectory/cr-scout-runs/cr-tracker/build.py
```
It re-derives every row from the reasoning-tasks branches (ryan/cr-collect-cohort results + crawler pools, ryan/collect-lw-gdocs, pablo/cr-scout-batch-1), fuzzy-matches gdoc tasks to source articles, re-queries GitHub issues via the REST API, verifies each task dir exists before linking, dedupes, regenerates the HTML, and prints a one-line JSON summary (rows / links / words / issues / task_links / html_sha). Takes ~1–2 min.
- If it exits non-zero (e.g. it can't read GitHub issues — it deliberately refuses to publish a tracker with zero issue links): report the error and STOP. Do not publish.
Redeploy (only on a successful build). Use the Artifact tool with:
- file_path: /Users/pablostafforini/Trajectory/cr-scout-runs/cr-task-master-list.html
- url: https://claude.ai/code/artifact/15852b96-f4b3-4838-b35f-e8b3fd941012
- favicon: 🎯
- label: manual-refresh
Report the JSON summary (rows / article-links / word-counts / issues) and confirm the artifact URL was redeployed.

Notes

Pipeline internals: ~/Trajectory/cr-scout-runs/cr-tracker/README.md.
Expected, non-error gaps: ~21 gdoc-sourced rows have no article link/word count (their sources aren't in the crawler's indexed pools), and batch ranks 41–50 are ungraded.
A git push of the regenerated HTML is not required — the artifact is the deliverable; pushing the repo is optional bookkeeping and stays gated on Pablo's explicit OK.

More from this repository

same repository

orchestrate-agent-review

benthamite/dotfiles

Coordinate a two-agent planner/reviewer loop across live Emacs agent sessions. Use when the user asks to orchestrate Claude/Fable and Codex, run paired model review, converge a plan through back-and-forth review, monitor agent sessions until completion, or make a multi-agent review process unattended.

2026-08-019

review-lulu-alert

benthamite/dotfiles

Use when a LuLu firewall alert is open on this Mac and the user asks whether to allow or block it, or asks to inspect, check, audit, or review the connection a LuLu alert is prompting about. Covers explicit $review-lulu-alert requests and questions like "should I allow this?", "what is this process connecting to?", or "is this LuLu prompt safe?".

2026-08-019

dotfiles-context

benthamite/dotfiles

Dotfiles and Emacs package routing context. Use when working in ~/My Drive/dotfiles, editing emacs/config.org or emacs/extras, choosing between the dotfiles repo and an elpaca source clone, or applying dotfiles documentation and commit conventions.

Audit a macOS .app before running it or granting permissions, especially when the user asks whether a Mac app is safe, suspicious, malware, from an unknown developer, or requests screen recording, accessibility, camera, microphone, input monitoring, or other sensitive permissions.

2026-07-319

security-audit

benthamite/dotfiles

Scan for exposed API keys and leaked credentials, audit dependency vulnerabilities, review macOS hardening settings, and evaluate Claude Code configuration risks. Use when the user wants a security review, vulnerability scan, dependency audit, secrets check, or periodic security posture assessment.

2026-07-319

name	refresh-cr-tracker
description	Rebuild and republish the CR-task master tracker artifact. Use when the user says "refresh cr tracker", "update the CR task tracker", "/refresh-cr-tracker", or wants the conceptual-reasoning task master list re-pulled from live reasoning-tasks data + GitHub issues and redeployed to its claude.ai artifact.

Refresh the CR-task master tracker

Steps

Build. Run:
```
python3 ~/Trajectory/cr-scout-runs/cr-tracker/build.py
```
It re-derives every row from the reasoning-tasks branches (ryan/cr-collect-cohort results + crawler pools, ryan/collect-lw-gdocs, pablo/cr-scout-batch-1), fuzzy-matches gdoc tasks to source articles, re-queries GitHub issues via the REST API, verifies each task dir exists before linking, dedupes, regenerates the HTML, and prints a one-line JSON summary (rows / links / words / issues / task_links / html_sha). Takes ~1–2 min.
- If it exits non-zero (e.g. it can't read GitHub issues — it deliberately refuses to publish a tracker with zero issue links): report the error and STOP. Do not publish.
Redeploy (only on a successful build). Use the Artifact tool with:
- file_path: /Users/pablostafforini/Trajectory/cr-scout-runs/cr-task-master-list.html
- url: https://claude.ai/code/artifact/15852b96-f4b3-4838-b35f-e8b3fd941012
- favicon: 🎯
- label: manual-refresh
Report the JSON summary (rows / article-links / word-counts / issues) and confirm the artifact URL was redeployed.

Notes

Pipeline internals: ~/Trajectory/cr-scout-runs/cr-tracker/README.md.
Expected, non-error gaps: ~21 gdoc-sourced rows have no article link/word count (their sources aren't in the crawler's indexed pools), and batch ranks 41–50 are ungraded.
A git push of the regenerated HTML is not required — the artifact is the deliverable; pushing the repo is optional bookkeeping and stays gated on Pablo's explicit OK.