cli
Type-safe CLI argument parsing with commander and @commander-js/extra-typings, the standard parser for this repo's Bun scripts.…
Harvest agent-tooling ideas from prominent developers.
Claude Code
$ npx -y skills add bendrucker/claude --skill agent-ideas --agent claude-code
Codex
$ npx skills add bendrucker/claude --skill agent-ideas -a codex -y
Cursor
$ npx skills add bendrucker/claude --skill agent-ideas -a cursor -y
Gemini CLI
$ npx skills add bendrucker/claude --skill agent-ideas -a gemini-cli -y
GitHub Copilot
$ npx skills add bendrucker/claude --skill agent-ideas -a github-copilot -y
OpenCode
$ npx skills add bendrucker/claude --skill agent-ideas -a opencode -y
Windsurf
$ npx skills add bendrucker/claude --skill agent-ideas -a windsurf -y
name: agent-ideas
description: Harvest agent-tooling ideas from prominent developers.
disable-model-invocation: true
allowed-tools:
- Bash(bun ${CLAUDE_SKILL_DIR}/../../../packages/agent-ideas/fetch.ts:*)
- Read
- Grep
- Glob
- WebFetch
- Agent
- Write
- Skill(things:url)
- mcp__claude_ai_Zapier__things_create_to-do
- mcp__claude-in-chrome__tabs_context_mcp
- mcp__claude-in-chrome__tabs_create_mcp
- mcp__claude-in-chrome__navigate
- mcp__claude-in-chrome__get_page_textHarvest agent-tooling ideas from a curated list of thinkers and map them to concrete artifacts in this repo (a skill, hook, setting, or rule). The harvest runs in two phases: a feed pass that fetches, mines, and delivers a digest, and a local pass that fills the X-only gap and files the keepers. As the weekly routine these run headless-then-local, bridged by a teleport doorway item. Run on-demand at your own terminal, they collapse into one pass with no doorway (see [Deliver the Doorway Item](#deliver-the-doorway-item)).
[`packages/agent-ideas/sources.ts`](../../../packages/agent-ideas/sources.ts) is the prunable core: a version-controlled list of thinkers, each with a feed URL, or marked `x-only` when no usable feed exists. Edit it directly to add, drop, or retune sources. Keep it small and high-signal; a source earns its place by regularly producing ideas that map to artifacts in this repo.
Pull the last 8 days of posts across all feed sources:
bun ${CLAUDE_SKILL_DIR}/../../../packages/agent-ideas/fetch.ts > tmp/agent-ideas-posts.jsonEach result is `{source, sourceType, feedUrl, posts:[{title,url,date,excerpt}], error?}`. Sources with `error` set could not be fetched; note them but don't block. `x-only` sources are absent here by design (the local phase handles them after teleport).
Narrow to specific sources or widen the window with flags:
bun ${CLAUDE_SKILL_DIR}/../../../packages/agent-ideas/fetch.ts --days 14 --source simon --source marioTurn posts into repo-mappable idea cards. The bar is high: a card must name a real surface in this repo it would refine, or make a clear case for a net-new artifact. See [references/mining.md](references/mining.md) for the card schema, the proven heuristics (per-source cap by depth, auto-demote 404 sources, dedupe against existing repo surfaces), and the fan-out flow.
Fan out one mining `Agent` call per source (batch thin sources together). Give each the source's posts, the schema, the heuristics, and a read-only view of the repo so it can fill `repoOverlap` and dedupe. Collect the cards, verify each `sourceUrl` resolves (demote 404s), then dedupe across agents.
Write the digest to `tmp/agent-ideas-digest-<YYYY-Www>.md`:
Keep the digest in this session's context as well. The local phase reads it from here.
Skip this section on a local on-demand run. The doorway exists only to bridge the headless weekly routine to a local terminal; `claude --teleport ${CLAUDE_SESSION_ID}` minted from a session you are already in points at itself. When the browser and Things are reachable (you invoked the skill yourself), go straight from Synthesize to [Fill the X-Only Gap](#fill-the-x-only-gap). The doorway is the remote routine's handoff, nothing more.
For the weekly routine, create exactly one Things inbox item. It is the routine's only notification, so make its notes self-sufficient:
claude --teleport ${CLAUDE_SESSION_ID}Pick the delivery path by environment:
Do not tag the doorway item `claude-code`. Tagging happens per keeper in the local phase, so the whole digest doesn't land in the `improve-claude-code` backlog as one blob.
The local phase fills the X-only gap and files the keepers. You reach it two ways. The weekly routine gets here when you tap the doorway item: `claude --teleport` pulls the cloud session into a local terminal where the browser and Things are reachable. A local on-demand run flows straight here from Synthesize, with no doorway in between.
The digest is already in this session's context. After a teleport into a fresh terminal it may not be, so read the latest `tmp/agent-ideas-digest-*.md` to recover the feed-derived cards.
`x-only` sources were skipped in the remote fetch. Read their recent timelines in the browser and mine them into cards with the same bar as the feed path. See [references/browser.md](references/browser.md) for the tool-loading sequence, the per-author flow, and the failure modes (extension not connected, logged-out wall). If the browser is unavailable, note which authors went unread and proceed with the feed cards.
For each keeper card, create one Things todo via the `things:url` skill's inbox capture, tagged `claude-code` so `improve-claude-code` picks it up:
Type-safe CLI argument parsing with commander and @commander-js/extra-typings, the standard parser for this repo's Bun scripts.…
Turn the user's labels on repo prose, or their notes from reviewing a document in Plannotator, into calibrated Vale rules.
Report real device usage from ActivityWatch. Covers per-app time, window titles, and active vs idle spans. Use when asked "what…
Orchestrating Claude Code agent teams. Use when creating teams, spawning teammates, assigning tasks, configuring teammate modes,…
Hand the current conversation off to a fresh background agent that picks up the work immediately, so you can step away and track…
Report shell history from atuin's local capture. Covers what commands ran, when, where, and how they exited. Use when asked "what…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.