All authors
Claude Skills by timharris707
github.com/timharris70750 skills0 installs45 views
- IngestFor a media file or URL shared with a goal, transcription requests, or takeaways from a call, demo, playtest, or video, build a transcript and timestamped visual evidence packet with a manifest and recommended next workflow.Votes: 0GitHub stars: 40
- HuhWhen a message did not land or pasted agent output needs translation, restate it plainly, expand shorthand, separate results from requests, and flag unsupported claims.Votes: 0GitHub stars: 40
- PlainspokenFor chat replies, status updates, review comments, and commit messages, write plainly without AI tells. Also use to revise generated-sounding drafts or review another agent's prose.Votes: 0GitHub stars: 40
- Writing For AgentsFor skills, standing agent instructions, recorded rules, or documents agents skip, write and prune reliable triggers and checkable steps. Use to author or revise SKILL.md, AGENTS.md, CLAUDE.md, rules and references, or diagnose unreliable invocation and skimming.Votes: 0GitHub stars: 40
- Writing For HumansFor public-facing drafts, pages that read like agent documentation, or a final AI-tell scrub, write clear human copy in the selected project voice. Covers landing pages, README introductions, launch posts, and profile pages.Votes: 0GitHub stars: 40
- Advisory BoardFor an explicitly requested advisory board, roundtable, panel, idea tournament, multi-model review or debate, red-team by several models, or consensus handoff, run an authorized multi-provider process with recorded seats, usage, and evidence.Votes: 0GitHub stars: 40
- Decision MapWhen asked to chart a decision map, work a map ticket, or plan work whose open decisions gate each other, map the unresolved choices before build slices. Use for a new primitive, milestone charter, or integration that cannot yet be specified in one sitting.Votes: 0GitHub stars: 40
- GrillingWhen asked to grill, stress-test, or pressure-test an idea, or before a decision map or spec rests on an untested conversation, interview the decision maker in small rounds to expose assumptions and settle material choices.Votes: 0GitHub stars: 40
- Codebase ReviewBefore an upcoming feature, when merged work crosses the recorded review threshold, or when implementation exposes structural friction, review the codebase state with independent skepticism. Deliver the report while keeping unresolved adoption decisions tracked.Votes: 0GitHub stars: 40
- PrototypeWhen discussion or static mockups cannot settle how something should look, behave, or feel, build a disposable interactive experiment: UI variants, a terminal UI, or shareable HTML over a small logic module.Votes: 0GitHub stars: 40
- ResearchFor factual investigations of vendor materials, regulations, upstream repositories, recorded calls, or other evidence, investigate primary sources and return cited findings. Ask targeted questions when missing facts are held by people; match the requested scope.Votes: 0GitHub stars: 40
- Domain MemoryWhen design decisions close, review findings are declined, the decider corrects a session's assumption, a new task starts in a repo with a bound memory home, work resumes in a bound repo, or memory exceeds its size bound, record or retrieve project terms and decisions, and propose consolidation when needed.Votes: 0GitHub stars: 40
- RouterWhen unsure which TeamWorkflow skill applies, or orienting a new task or repository, find the right planning, research, building, review, or recovery workflow. Reuse recorded project bindings and working mode.Votes: 0GitHub stars: 40
- SetupFor a new TeamWorkflow installation, binding refresh, or drift audit after a pack release, inspect and bind the project workflow. Reuse explicit recorded decisions with their sources; ask about missing, conflicting, or changed authority and bindings.Votes: 0GitHub stars: 40
- Adversarial ReviewBefore committing substantial work, at worker completion, before external review, or on an explicit adversarial/red-team request for a diff, branch, or PR, use independent finders and a skeptic to verify defects, disposition findings, and enforce the blocker gate.Votes: 0GitHub stars: 40
- Blast RadiusWhen asked for a change's blast radius, assessing whether it is safe to merge, or reviewing a small diff you distrust, trace effects beyond the diff and execute the checks that prove its safety assumptions.Votes: 0GitHub stars: 40
- DiagnoseFor a bug-fix brief, a bug resisting its first fix, or a fix about to ship without a proven cause, reproduce the failure, state its cause with evidence, and keep a regression check before shipping.Votes: 0GitHub stars: 40
- HandoffFor checkpoint, save-state, wrap-up, or handoff requests, meaningful milestones, impending compaction, or recovery, save or recover the current Codex task with authorization and ownership intact. Continue in the same task unless a transfer is requested.Votes: 0GitHub stars: 40
- ImplementFor a build brief, implementing a spec or tracked item, or mid-build discoveries tempting scope expansion, build thin verified slices with test-first checks at named boundaries, proportional validation elsewhere, and respect for scope and commit instructions.Votes: 0GitHub stars: 40
- OrchestrateFor orchestration mode, coordinating several workers or tasks, or an assigned lead-developer role, direct an agent team: route tracked work, monitor workers, independently verify results, and own integration while the human makes decisions.Votes: 0GitHub stars: 40
- Show Me Your WorkFor autonomous multi-phase or unattended work, a reviewer needing an evidence trail, or an explicit decision-log/show-your-work request, keep an append-only decision log with why, evidence, and result. Record decisions and corrections, not hidden reasoning transcripts.Votes: 0GitHub stars: 40
- To TicketsWhen asked to file tickets, break down approved work, or move a settled plan onto the board, turn the spec, closed decision map, or pressure-tested conversation into verifiable work items with real dependencies and non-ticket blockers.Votes: 0GitHub stars: 40
- WizardWhen work stalls on steps only a human can perform, or manual setup is tedious to repeat, create a guided script for dashboards, credentials, DNS, CI secrets, or cutovers. Check available tools first; perform agent-capable steps directly.Votes: 0GitHub stars: 40
- HuhDecode a message that didn't land: restate it in plain sentences, expand invented shorthand, split report from request, and flag claims stated without evidence. Use when the user signals your last message didn't land (\"huh?\", \"what do you mean\"), or pastes agent output from another session to translate.Votes: 0GitHub stars: 40
- PlainspokenWrite like a person in everything you emit. Plain words, concrete claims, no AI tells. Use when writing any chat reply, status update, close-out, review comment, or commit message (always on for those), when a passage you drafted reads generated, or when reviewing prose another agent wrote.Votes: 0GitHub stars: 40
- Writing For AgentsWrite and prune documents an agent consumes: a SKILL.md, an AGENTS.md or CLAUDE.md, a rules file, a reference file reached by a pointer. Use when authoring or revising a skill, editing standing agent instructions or recording a decision as a rule agents will follow (a CLAUDE.md, AGENTS.md, CODE-RULES, or conduct-rules entry), or diagnosing why a document fires unreliably or gets skimmed.Votes: 0GitHub stars: 40
- Writing For HumansWrite copy a human reads: a landing page, a README's front half, a launch post, a profile page. Use when drafting or revising public-facing prose, when a page reads like agent documentation, or when a finished draft needs its last-mile scrub for AI tells.Votes: 0GitHub stars: 40
- Advisory BoardConvene a multi-model advisory board: subscription-backed Claude, Codex, Gemini, and Grok CLIs reviewing the same material in formal, roundtable, or competitive mode. Use when the user asks for an advisory board, roundtable, panel, or idea tournament; a multi-model or cross-provider review or debate; a red-team of a plan, design, decision, or document by several models; or a consensus handoff from several frontier models.Votes: 0GitHub stars: 40
- Decision MapChart or work a decision map for genuinely foggy work before any build slice is written: a new primitive, a milestone charter, an integration nobody can spec in one sitting. Use when asked to chart a decision map, work a map ticket, or plan a decision-heavy effort whose open questions gate each other.Votes: 0GitHub stars: 40
- GrillingInterview the decider relentlessly to turn a half-formed plan, design, or idea into shared understanding: a design tree worked in rounds until nothing is silently assumed. Use when asked to grill, stress-test, or pressure-test thinking, and before charting a decision map or writing a spec off a conversation nobody has pressure-tested.Votes: 0GitHub stars: 40
- Fit AuditRank this catalog's skills by what each would have saved this specific adopter, every top pick citing a real incident from their own history, and for a team judge each skill against the incumbent stack as well. Use when someone is considering the catalog and has not run setup, when the user asks which skills would help them most, when recommending a starting subset to a new adopter, or when auditing the catalog for a team that already runs house skills, guidelines, or recorded review decisions.Votes: 0GitHub stars: 40
- Codebase ReviewRun a state review of the codebase: the counterpart to adversarial-review's change review. Use before building against an upcoming spec (make the change easy first), when lanes merged since the last review cross the repo's threshold, or when lanes or the orchestrator report the code fighting them.Votes: 0GitHub stars: 40
- IngestTurn a video, recording, voice memo, or media URL into an evidence packet of authoritative transcript, timestamped frames, and manifest, plus a routing recommendation. Use when the user shares a media file or URL with a goal, asks to process or transcribe a recording, or wants takeaways from a call, demo, playtest, or video.Votes: 0GitHub stars: 40
- PrototypeBuild throwaway prototype code that answers a design question: UI variants on a live route, or a terminal UI or single shareable HTML file over a pure logic module. Use when a question is \"how should this look / behave / feel in action\" and discussion or static artifacts cannot settle it.Votes: 0GitHub stars: 40
- ResearchRun an autonomous research lane against primary sources, ending in cited findings and, when the missing facts are human-held, a questionnaire. Use for investigations of vendor materials, regulations, upstream repos, recorded calls, or any fact-finding that should run fire-and-report.Votes: 0GitHub stars: 40
- Domain MemoryKeep per-repo institutional memory: a domain glossary plus lightweight decision records, written as side effects of work. Use when a grilling closes, a review rejection or declined finding is dispositioned, the decider corrects a session's wrong assumption, a session starts in a repo whose binding names a memory home, or the store passes its size bound.Votes: 0GitHub stars: 40
- RouterEntry point for the team-workflow pack: names every pack skill and when to reach for it. Use when unsure which team-workflow skill applies, or to orient a new session/repo on what the pack offers.Votes: 0GitHub stars: 40
- SetupOnce-per-repo binding interview for the team-workflow pack: records how the pack composes with this repo and seeds the binding doc the other skills read. Use when installing the pack into a repo, refreshing an existing installation's bindings, or auditing a consuming repo for drift after a pack release (audit mode).Votes: 0GitHub stars: 40
- Adversarial ReviewRun an adversarial review of a change before it ships: isolated finders trying to break it, a skeptic pass that kills unproven findings, and a gate on confirmed blockers. Use before committing substantial work, at lane close-out, when the user asks for an adversarial or red-team review of a diff/branch/PR, or before external reviewers see the change.Votes: 0GitHub stars: 40
- Blast RadiusFind what a change breaks somewhere else before it ships, beyond the diff and past where grep stops, and prove the one fact it is safe because of by running real code. Use when asked for the blast radius of a change, when deciding whether an in-flight change is safe to merge, or when reviewing a small diff you do not trust yet.Votes: 0GitHub stars: 40
- DiagnoseThe disciplined bug-fixing loop: no fix ships without a cause the fixer can state in one plain sentence, with evidence. Use when any fix is about to ship without a nameable cause, when a bug resists its first fix attempt, or when a bug-shaped lane brief points here.Votes: 0GitHub stars: 40
- HandoffWrite a structured session handoff so a fresh session resumes losslessly. Use when context is filling up (around half the window), when wrapping a work session, or when the user says "handoff", "checkpoint", "wrap up", or "save state".Votes: 0GitHub stars: 40
- ImplementHow a working lane builds an item: seam-scoped test-first, tracer-first sequencing, a green checkpoint per slice, and file-don't-fix scope discipline. Use when a build-shaped lane brief points here, when implementing a spec or tracked item, or when mid-build discoveries tempt a lane beyond its brief.Votes: 0GitHub stars: 40
- OrchestrateRun one session as the lead developer of an agent team: it takes tracked work, routes it into parallel lanes, audits what comes back, and owns the merge, so the human brings decisions and never implements. Use when the user says \"orchestration mode\", asks one session to coordinate several lanes/sessions, or hands over an orchestrator role.Votes: 0GitHub stars: 40
- Show Me Your WorkKeep a reviewable decision trail for long-running or unattended work: one append-only TSV log, one row per decision with its why, evidence, and result. Use when starting an autonomous, multi-phase, or loop run a human reviews after stepping away, when a reviewer needs the trail to trust a result without rerunning it, or when the user asks for a decision log or says show your work.Votes: 0GitHub stars: 40
- To TicketsTurn a plan, a spec, a closed decision map, or a pressure-tested conversation into tracer-bullet work items on the repo's tracker, each an issue-as-spec with its blocking edges wired. Use when asked to file tickets, break work down, or move from "we've decided" to "it's on the board".Votes: 0GitHub stars: 40
- WizardGenerate an interactive bash wizard that walks a human through a procedure only they can perform: third-party dashboards, credentials, DNS records, CI secrets, one-off cutovers. Use when a task stalls on steps an agent cannot take, or when a manual setup is tedious to re-explain every time. Not for steps the agent can perform itself.Votes: 0GitHub stars: 40
- Computer UseHand a GUI task on this Mac (click, type, read a window, move through an app) to Codex Computer Use, one bounded subtask at a time, and get back a result the runner has checked against what actually happened. Use when a task needs a desktop app driven or read and no API, CLI, or connector covers it, or when the user says use the computer, drive the app, or computer use.Votes: 0GitHub stars: 40
- RetroRead a sample of one repo's past agent sessions, Claude Code and Codex, find the friction the agents hit, and return a short ranked list of fixes in plain words, each labeled and routed to whoever owns the fix. Use when the user asks for a retro or retrospective on agent work, asks what keeps going wrong in a repo's agent sessions, or names past sessions to mine for friction.Votes: 0GitHub stars: 40
- Ts Module BoundariesMake each package in a TypeScript repo reachable only through its entry-point files, enforced by a dependency-linter check in CI and proven to bite with a deliberate bad import. Use when the decider asks for enforced module boundaries or deep modules, when a codebase-review boundaries-vs-reality finding is adopted for a TypeScript repo, or when code keeps importing past a package's entry points.Votes: 0GitHub stars: 40