Click AI Skills

Plugin writing-for-humans from marketplace skills in timharris707/skills. Commands read from the repo's manifest — 10 days ago.

Skills (30)

• ingest

  For 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.

• huh

  Decode 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 tr

• plainspoken

  Write 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.

• writing-for-agents

  Write 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-RULE

• writing-for-humans

  Write 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.

• advisory-board

  Convene 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

• decision-map

  Chart 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 othe

• grilling

  Interview 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 conv

• computer-use

  Hand 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,

• fit-audit

  Rank 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 whi

• retro

  Read 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

• review-loop

  Have a second model review a branch on this machine before its pull request opens, fix what holds up, and repeat until a round comes back clean or three rounds pass. Use when about to open a pull request or push a fix to one, when the user says review loop or asks for a second opinion before the PR,

• triage

  Work a repo's needs-triage backlog, and outside contributors' issues and pull requests, in batches the decider approves in one pass: each item gets a cheap check and one proposed move with a plain-words reason, and only approved moves are applied. Use when asked to triage or work through a needs-tri

• ts-module-boundaries

  Make 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 fin

• codebase-review

  Run 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.

• prototype

  Build 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.

• research

  Run 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.

• domain-memory

  Keep 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 n

• router

  Entry 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.

• setup

  Once-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 rele

• adversarial-review

  Run 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/bra

• blast-radius

  Find 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 sma

• diagnose

  The 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.

• handoff

  Write 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".

• implement

  How 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

• orchestrate

  Run 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/se

• pr-writing

  Write a pull request the decider can judge from its description alone: problem first, before-and-after evidence, a can-we-undo call. Use when filing a PR, updating a PR description, responding to PR review feedback, or writing a PR or review-thread comment on someone's behalf.

• show-me-your-work

  Keep 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 wit

• to-tickets

  Turn 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".

• wizard

  Generate 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

Similar plugins