Tamircohen28
UserA portable agent toolkit — 29 skills, 10 specialist agents, worktree hooks and MCP stubs — shipped from one canonical source to six agent surfaces across five platforms: Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI and OpenCode.
Categories
Indexed Skills (34)
algorithmic-art
Use when the user wants to create generative art, algorithmic art, creative coding, or code-driven visuals — including flow fields, particle systems, noise-based art, Lissajous figures, recursive trees, Voronoi patterns, L-systems, fractals, or any interactive p5.js sketch. Trigger phrases: 'generative art', 'algorithmic art', 'flow field', 'particle system', 'make art with code', 'creative coding', 'p5.js sketch', 'procedural art', 'noise art', 'make something visual with code', 'code art'.
platform-sync-claude
Internal companion to platform-sync. Fetches live Claude Code docs, reads the local .claude-plugin config (plugin.json, skills/, hooks/hooks.json), identifies features in the latest docs NOT yet used, and returns structured improvement steps. Not user-invocable — called by the platform-sync umbrella skill.
platform-sync-codex
Internal companion to platform-sync. Fetches live OpenAI Codex CLI docs (github.com/openai/codex), reads the local .codex-plugin/plugin.json, identifies features not yet leveraged, and returns structured improvement steps. Not user-invocable — called by the platform-sync umbrella skill.
platform-sync-cursor
Internal companion to platform-sync. Fetches live Cursor docs (docs.cursor.com), reads the local .cursor-plugin/plugin.json, identifies new Cursor features not yet used, and returns structured improvement steps. Not user-invocable — called by the platform-sync umbrella skill.
run-tamirs-superpowers
Use when running, validating, or testing the tamirs-superpowers Claude Code plugin — checks JSON validity, shellcheck hooks, SKILL.md frontmatter, statusline output, hook wiring, and absence of hardcoded paths or internal references. Trigger phrases: 'run the plugin health check', 'validate the plugin', 'test tamirs-superpowers', 'smoke test the plugin', 'check the plugin', 'is the plugin clean'.
field-notebook-ui
Use when a UI, explainer, dashboard, diagram or artifact should carry this repo's engineer's field-notebook look — warm stone-paper, hand-annotated margins, graph-paper grid. Trigger on: "field-notebook style", "warm stone-paper aesthetic", "the usual notebook look", "make it look like the field notebook", or when a second artifact must visually match one already built in this style. Not for a generic UI with no stated aesthetic.
targeted-debug
Use when the user pastes a stack trace, traceback, panic, crash log, or error message with a file:line and wants the root cause. Triggers: 'debug this error', 'look at this stack trace', 'why does X crash', 'what causes this exception', 'why is this panicking', 'look at this file:line', and error types (NullPointerException, AttributeError, TypeError, nil pointer dereference, unwrap on None, index out of bounds, segfault, unbound variable, cannot read properties of undefined). Not for vague 'something is broken' or 'why is it slow' with no concrete error signal.
decision
Use when the user must pick between options — an agent has finished work and needs them to choose how to proceed, the user was told "waiting for your decision about X", or they say "display decision", "what's the decision on/about X", "show me my options for X", "let me choose", "walk me through the open decisions", "what are my action items", "give me a menu of choices", or give a GitHub issue/PR number or URL.
plan-dev
Use when informal work — a task, a feature request, a spec, a review doc, a list of features to implement — must become a structured plan before any code is written. Invoke for: 'plan this', 'plan-dev', 'break into phases', 'break this into phases', 'create issues for this', 'decompose this spec/task', 'turn into tickets', 'turn this into tickets', 'structure this feature', 'what order should I tackle these'. Not architecture analysis of existing code or a direct coding request — the output is a roadmap, not code.
pr-dev
Use when an open PR must be driven to completion — 'finish this PR', 'address review comments', 'land the PR', 'ship/land/close the PR', 'drive PR #N to merge', 'fix CI and merge', 'clean up this PR', 'the checks are red, get it green and merged', 'pr-dev 42'.
start-dev
Use when a task must be implemented, built, coded or shipped — from a GitHub issue number, free-text task description, or spec file. Triggers: 'implement issue #N', 'start coding X', 'build the feature', 'work on this spec', 'create a PR for this', 'ship issue #N', 'code up the feature', 'begin implementation of X', 'start-dev #17'.
switch-dev
Use when switching AI coding platforms mid-task without losing context — Claude Code, Cursor, Codex, Gemini CLI, OpenCode. Triggers: switch agent, hand off issue, resume issue, rate limited — switch platform, continue on Cursor, continue on Gemini, continue in OpenCode, pick up where I left off, update the resume block, cross-platform handoff, switch-dev, agent handoff, which issues each agent owns.
changelog-review
Use when a Claude Code plugin project needs auditing against live official docs — hooks.json, SKILL.md, plugin.json, MCP config — for misuse, broken hook paths, stale patterns and missed capabilities. Invoked by repo-standards polish phase 6; also callable by any skill needing a live-doc-grounded answer about Claude Code hooks, skills, plugin.json or MCP. Version agreement across manifests and badges is delegated to plugin-version.json + scripts/check-version-truth.sh. Never invoke directly — use repo-standards.
dark-terminal-doc
Use when a single-file HTML technical document should carry a dark developer / terminal aesthetic — monospace, terminal-green on near-black. Trigger on: "dark terminal doc", "terminal-style HTML", "developer-terminal aesthetic", "make it look like a terminal", "dark developer-facing HTML page", or a comparison table, reference sheet, changelog, release notes or API cheatsheet in that look, or one matching a document already in this style. Not for a doc with no stated aesthetic.
docs-review
Use when README.md and docs/** need a full documentation audit — a sweep for broken links, stale counts, template conformance, agent-instruction consistency, install-command accuracy and generated skill and platform tables. Invoked by repo-standards polish phase 6; not for direct user invocation.
platform-sync
Use when this repo may have fallen behind the AI coding platforms it targets — Claude Code, Codex CLI, Cursor, Gemini CLI, OpenCode. Triggers: 'what new features am I missing', 'am I up to date with the latest docs', 'check my repo against the latest docs', 'is my plugin using current best practices', 'sync my plugin', 'audit every platform', 'did they ship anything new I should adopt', '/platform-sync'. Also when a platform manifest or CHANGELOG is being bumped, when a release is being cut, or when it has been more than a day since the last check.
mcp-builder
Use when building or scaffolding an MCP (Model Context Protocol) server wrapping a REST API, database, or service as tools for an MCP client. Triggers on: 'build an MCP server', 'create MCP tools', 'write an MCP server for', 'integrate X with Claude via MCP', 'expose API via MCP', 'add MCP support for', 'make Claude able to call X', 'MCP server for Stripe/GitHub/Postgres', 'scaffold MCP', 'wrap this API in MCP', 'Claude tool for X API', 'FastMCP server', 'TypeScript MCP', 'MCP server for Cursor/Codex/Gemini/OpenCode'. Not for inspecting an existing MCP server, or client config only.
mcp-pagination
Internal guardrail invoked by mcp-builder only — audits MCP tool schemas with list_*, search_*, find_*, get_all_* or SQL-executing operations for missing pagination, limit, offset or cursor parameters and unbounded results. Not for general MCP questions, single-item getters, or mutation-only tools.
cleanup
Use when the user wants to clean up, tidy, or reset a GitHub repo — even if they name only one part. Triggers: repo cleanup, repo housekeeping, prune merged branches, delete stale remote branches, tidy my worktrees, drive all open PRs to merge-ready, wipe build and cache artifacts, reset local checkout to match remote.
multi-agent-repo
Use when auditing or setting up a repository for multi-agent development across Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, and OpenCode. Triggers: multi-agent repo, audit agent setup, AGENTS.md gaps, make this repo work with Claude and Cursor, add Codex, Gemini CLI or OpenCode support, generate cursor rules from AGENTS.md, capability registry, agent drift, canonical AGENTS.md, multi-agent-repo review, plan or dev.
repo-scaffold
Use when creating a brand-new GitHub repository from scratch with production-ready infrastructure. Triggers: 'scaffold a repo', 'create a new repo', 'set up a new project', 'new github repo', 'bootstrap a project', 'forge a repo', '/repo-scaffold', 'start a new repo', 'initialize a project', 'make me a repo', 'agent-kit', 'plugin marketplace'. Not repo-standards (existing repo polish) or docs-only requests.
repo-standards
Use when auditing or polishing a repository to Tamir Cohen standards — README badges, Makefile install/update/uninstall, docs tree, CI/CD, changelog and versioning policy, branch protection, employer IP scan, repo hygiene, multi-agent setup. Triggers: repo standards, polish this repo, prepare this for GitHub, world-class repo, publish-ready, scan employer IP, fix repo hygiene, standards audit.
find-skill
Use when the user asks 'find a skill for X', 'is there a plugin that does Y', 'what skill should I use for Z', 'recommend an agent for W', 'compare skills for ...', or 'search for a Claude Code skill'. Trigger words: find plugin, mcp server for, skill discovery.
retro
Use when a session should become durable rules, hooks or memory — the user asks ('/retro', 'run a retrospective', 'postmortem', 'what went wrong this session', 'find friction', 'capture lessons', 'lessons learned'), OR a session is wrapping up after friction (repeated failures, rework, multiple corrections). Offer it proactively at session end; it only proposes and never writes without approval.
session-report
Use when the user asks what they are spending on Claude or where the tokens went. Triggers: 'session report', 'token usage', 'how many tokens', 'what did that cost', 'am I burning tokens', 'cache hit rate', 'why is this session so expensive', 'which project costs most', 'show my usage', 'usage this week', 'last 7 days', 'claude stats', 'claude analytics', 'token breakdown', 'subagent cost breakdown', 'expensive prompts'. Also use proactively after a long or context-heavy session when the user wonders where the budget went.
skill-creator
Use when creating or improving an Agent Skill (SKILL.md) for Claude Code, Cursor, Codex, Gemini CLI or OpenCode, fixing a skill that isn't triggering, or running skill evals/benchmarks. Triggers: 'make this a skill', 'turn this into a skill', 'write a SKILL.md', 'my skill isn't triggering', 'skill keeps missing', 'add evals to my skill', 'benchmark my skill', 'improve this skill', 'create a new skill for X'.
deliver-dev
Use when an integrated objective must become a delivery — 'deliver this objective', 'ship it', 'open the PR for objective X', 'all tasks are done, create the PR', 'turn the integration branch into a PR', 'run the pre-PR gates', 'review the combined diff and ship'. Not for driving an already-open PR — that is pr-dev.
orchestrate-dev
Use when an implementation request is bigger than one unit of work — a spec or plan file, a multi-part feature, a review doc with several items, 'implement all of this', 'build X end to end', 'do these N things', 'orchestrate this', 'run these in parallel', 'split this across agents'. A single small change is not orchestration — that falls through to start-dev.
worker-dev
Use when executing exactly ONE task inside an objective already planned by orchestrate-dev — 'run task-002', 'do your assigned task', 'implement task-001 of objective X', 'work this task and hand off', 'resume task-003', or a task-NNN.json exists under .dev-files/objectives/. A whole user request is not a worker task — that is orchestrate-dev or start-dev.
github-policy
Use when a repository's branch protection, rulesets, required checks, or PR-run cancellation may not match the canonical policy — never set up, hand-configured, or a merge blocked or allowed unexpectedly. Triggers: github-policy, branch protection, ruleset audit, required approvals, organization ruleset, classic branch protection, repos with no branch rules, branch is out of date on every PR, cancel superseded PR runs when I push again, bring repositories into compliance.
capture-config
Use when a hand-edit to a global, machine-level agent config should become permanent everywhere — the user edited ~/.claude/settings.json, ~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, ~/.cursor/, ~/.gemini/ or ~/.config/opencode/ by hand and says 'make this permanent', 'save this to the repo', 'keep this setting', 'add this rule everywhere', 'sync my machine back to the repo', 'capture my config', 'I tweaked a permission, don't lose it', 'put this on all my platforms' — or setup/doctor reports the machine has drifted from the repo and the machine is right. Offer it proactively right after helping the user hand-edit one of those files.
notify-setup
Use when the user wants Claude Code to reach them on their phone, or phone notifications have stopped arriving — 'notify me on my phone when Claude needs me', 'send notifications to my phone', 'set up push notifications', 'set up Pushover', 'ping me when Claude needs input', 'I keep missing when Claude finishes', 'phone alerts for Claude', 'push notifications stopped working', 'make notifications less noisy', 'change notification priority', 'turn off phone alerts'.
diagnose-refusal
Use when a coding-agent session refused, blocked, filtered, or returned HTTP 403/401/429 instead of doing the asked work, and the user needs to know WHICH LAYER refused — harness policy, project instructions, LiteLLM guardrail/routing, upstream provider filter, model refusal, tool permission, or context contamination. Triggers: 'diagnose refusal', '/diagnose-refusal', 'why did it refuse', 'where did the refusal come from', 'GLM refused', 'LiteLLM blocked', 'provider filter', 'model refused', 'HTTP 403 from the model', 'safety refusal', 'cannot tell if this is the model or the proxy'.
usage-capture
Use when local Claude Code or OpenCode LLM requests should be recorded or inspected on this machine — daily JSONL usage logs, API body sidecars, latency bottlenecks. Triggers: 'usage capture', 'enable usage capture', 'local usage log', 'record LLM requests', 'LLM latency', 'which model was used', 'request duration', 'usage metrics'.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.