DEDUPED Hot AI repos, turned into use cases Get 5 a day

Use cases for Codex

682 use cases whose repo README says it works with Codex.

Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full disclaimer

682 use cases

  • Explain a technical concept as an interactive HTML page

    Generate a standalone interactive isometric figure that explains a concept like a rate limiter.

    View prompt
    Using the skill from wheresryan22/anatomy, create an interactive standalone HTML figure explaining <concept>, with real numbers from <source notes>. Expected output: one HTML file plus a PNG preview. Verify that the readout values match the numbers you were given before reporting done.
  • Pull compound and protein records with source provenance

    Query public biology and chemistry databases and get each record with its source endpoint.

    View prompt
    Using the scientific-agent-skills repo, read skills/database-lookup/SKILL.md and query PubChem, ChEMBL, and UniProt for <target gene or compound list>. Return a table of identifiers and key properties, with the endpoint and access date for each row. Verify that every row names its source endpoint and flag any database that needs a key you do not have.
  • Compare agent results across parallel worktrees

    Send one prompt to several agents in separate worktrees, then compare results and merge the best one.

    View prompt
    In the stablyai/orca repo context, use Orca's Parallel Worktrees to run the prompt in <task-file> across three agents, each in its own git worktree. Output a short comparison of the three diffs, naming the one to merge. Verify that each worktree is isolated by checking that the three branches differ and that the original checkout is unchanged.
  • Draw an architecture diagram for a doc or post

    Turn a plain-words description of a system into one HTML diagram file you can open in a browser.

    View prompt
    Using the diagram-design skill from cathrynlavery/diagram-design, draw an architecture diagram of <system name> showing its components and connections. Write one self-contained .html file with inline SVG. Verify the file opens in a browser and that no labels are clipped or overlapping.
  • Hand off a half-finished task from Claude Code to Codex

    Quit one coding agent mid-task and resume in another in the same directory with the open questions intact.

    View prompt
    Using the ai-memory repo (github.com/akitaonrails/ai-memory), set up the tool, then start <target-agent> in the project at <project-path> through `ai-memory run`. Expected output: the new agent begins with a brief that lists the last session's status, failed approaches, and open questions. Verify the brief mentions the open questions from the previous session before continuing.
  • Map an unfamiliar codebase in one run

    Build a browsable graph and a highlights report for a project you have not worked in before.

    View prompt
    In the Graphify-Labs/graphify repo setup, run `/graphify <repo-path>` on the target repository at <repo-path>. Confirm that graphify-out/ contains graph.html, GRAPH_REPORT.md, and graph.json, then summarize the top concepts listed in GRAPH_REPORT.md.
  • Make a product launch video from a website URL

    Turn a product's website, brief, or script into a short launch video using the product-launch-video skill.

    View prompt
    Using the hyperframes repo at heygen-com/hyperframes, use the product-launch-video skill to create a 45-second launch video from <website URL>. Output an MP4 and a short list of the scenes used. Verify that the title and product name in the video match the text on the website.
  • Run Claude Code on DeepSeek instead of Claude

    Point Claude Code at a DeepSeek model through Magpie with one provider key and one command.

    View prompt
    Using the yetone/magpie repository, install magpie, add the provider <provider-name> with the API key <api-key>, and run `magpie claude <provider-name>/<model-name>`. Report the output of the command and confirm that a new Claude Code session answers from that model.
  • Trace network input to dangerous sinks in a binary

    Find functions reachable from network reads that feed risky command or sink calls.

    View prompt
    In the Ablation repo at ~/ablation, use the Network Sink Finder and Sink Arg Classifier on <binary path>, then trace taint from network sources to each reachable sink. Output a table of sink address, argument class, and taint path. Verify that every listed path has a callgraph edge chain from a recv, read, fgets, or accept call before you report it.
  • Keep one project context across coding agents

    Move between Claude Code, Codex, and Gemini CLI on the same project without re-setting context.

    View prompt
    Using the acryl repo at github.com/acryldev/acryl, set up ACRYL on this machine and open the project at <project-path> as a project. Report the project name shown in ACRYL and list which agents from the roster are available; verify the project appears in the left panel before you finish.
  • Install the Factory into an existing GitHub project

    Add the committed Claude and Codex Factory files to a repo and check the setup with doctor.

    View prompt
    Using the addyosmani/factory repository, install the factory into <target-repo-path> by running install.sh against it. Then run .factory/scripts/doctor.sh inside the target and report every finding. Expected output: a list of remaining setup gaps, or confirmation that none remain. Verify that docs/factory/CHARTER.md exists in the target.
  • Give an existing repo a memory the agent keeps

    Set up Operator on a real project so each new agent session starts from an indexed codebase and written specs.

    View prompt
    Use the Operator Memory repo at https://github.com/aerovato/operator-memory to set up Operator for the project at <project-path>. Run the install steps from its README, then ask the agent to write the first specifications for <module-name>. Verify that a .operator/ directory exists in the project and that it contains at least one specification file.
  • Run all installed coding agents from one desktop app

    Link the coding-agent CLIs already on your machine and start sessions for each from one place.

    View prompt
    Using the Agent Launcher repo at https://github.com/agent-launch/agent-launcher, detect the coding-agent CLIs already installed on this machine and link them, then start a session for <agent-name> in the project folder <project-path>. Expected output: a list of linked agents and a running session in that folder. Verify that the CLI was not reinstalled or updated.
  • Deploy a private messaging hub for your agents

    Set up your own Cloudflare-hosted Agent Peer Chat instance and install the shared CLI and skill.

    View prompt
    Deploy AgentPeerChat from https://github.com/AgenticsWorks/AgentPeerChat into my Cloudflare free account, install the CLI and skill, and return the real instance URL. Verify the homepage loads and the API responds, and do not claim success if any step fails; never ask me to paste credentials into chat.
  • Get a GTM diagnosis for your developer tool

    Answer five questions and get one prioritized next move for your go-to-market.

    View prompt
    Install the skills from https://github.com/AIDevGTM/gtm-cofounder and run 00-start-here for <product name>, then run 01-strategy-and-roadmap. Expected output: docs/gtm-cofounder/gtm-roadmap.md with one Now move, a Next list, and a Later list. Verify that the Now move names a specific piece of evidence to collect, not a list of marketing tactics.
  • Fill and submit a web form in your signed-in Chrome

    Have an agent complete a multi-step web form in a background tab using your existing login.

    View prompt
    Using the Chrome Relay repo at aindeev/agent-chrome-relay, run `chrome-relay do` with the goal "<goal>" on <site URL>, passing the values in <data> as --data options and --until "text:<success text>". Report the exit code and the final page text; exit code 2 means hand back to the user with the page state. Verify that the success text appears before reporting done.
  • Build a cut-open pump page for plant operator training

    Turn one line into a single HTML file of a cut-open process pump with curves and break modes.

    View prompt
    Using the repo AirsupHQ/machine-skill, build a cut-open refinery process pump for plant training as one HTML file. The expected output is a single .html file that opens from disk and shows the pump curve, NPSH available against required, and hover labels. Verify that the file opens in a WebGL 2 browser and that the cutaway and break modes respond.
  • Cut a launch film for your product from a template

    Turn your product name, prompts, screens and install lines into a scored launch film in four shapes.

    View prompt
    Use the anidoodle repo to create a launch film for <product name>. Fill the launch spec with the product's prompts, screens and install lines, then run launch.mjs ship and return the rendered files for all four shapes. Verify that the ship step reports no cut-off text and passes the audio sync and peak checks.
  • Hand an agent a task card with the graph context

    Turn a piece of work into a board card and give the agent a brief with the dependency facts attached.

    View prompt
    In the Flare board for <project>, call tasks_list for the first lane, then task_get on the card <task id> and carry out the brief it returns. Expected output: a progress note sent with task_update and the card moved to review. Verify that the card now shows the new status in the Tasks panel.
  • Run a long desktop task from the browser

    Start a multi-step computer task in a web dashboard and keep it running with checkpoints.

    View prompt
    Use the LongHorizon-Harness repo at <repo path>. Start the Dashboard with lh-harness web, create a task for <goal>, and let it run until it reports completion. Expected output: the final reply and the verified state for <goal>. Verify that every round the Auditor accepted is listed as a checkpoint before you report success.
  • Audit an app feature gate for CWE-602 authorization flaws

    Decide whether a client-side premium or feature check is local or enforced by the server.

    View prompt
    Using the Seep Reverse Lab workspace, audit the premium check in <path-to-apk> for CWE-602 authorization issues, but only for the app I am authorized to test. Expected output: a short report that says whether the gate is local or server-authoritative, with the evidence. Verify that the airplane-mode confirmation was run and recorded.
  • Take over an existing codebase with an agent in one pass

    Build a Git-versioned index of a codebase of up to about 500,000 lines so the agent can start working from known context.

    View prompt
    In the repo <project-path>, confirm the AOCI MCP server is connected, then build the AOCI index for the whole project. Report the coverage level for each area and give me the AOCI panel link. Verify that aoci.txt and aoci.code.txt exist after the build.
  • Build a mobile app's screens from top-grossing patterns

    Have an agent study top-grossing apps in a category, then build the screens for your new app to a simulator-checked bar.

    View prompt
    Using the appllama/appllama-skills repo, study the top-grossing apps in the <category> category through the Appllama MCP, then build the core screens of <app idea> in Expo / React Native. Output the screen list and simulator recordings, and verify that each screen was checked in the simulator before you report it done.
  • Check a web settings form saves correctly, offline

    Fill and save a settings form in a local browser run, then confirm the saved message and page state.

    View prompt
    Use the fast-browser-use repo at <repo path> to fill and save the settings form at <form URL> with the values in <values file>. Return the execution trace and whether the saved confirmation text matches <expected text>. Verify the page with the --expect-text assertion before reporting success.
  • Pair your phone to agents on your computer

    Install Pairfob once, scan a QR code, and open live agent sessions on your phone.

    View prompt
    In the arronKler/pairfob repo, follow the Quick start in README.md to install Pairfob and run `pairfob pair` on this computer. Report the output of `pairfob list` showing one paired device. Verify that `pairfob` prints a running status before you finish.
  • Summarize a YouTube video from its transcript

    Get the spoken text of one video and pull a summary or quotes from it.

    View prompt
    Using the youtube-skills repo, fetch the transcript of <video URL> with timestamps and write a five-bullet summary plus three quotes with their timestamps. Verify that each quote appears in the returned transcript text before you output it.
  • Turn a system description into an interactive architecture diagram

    Describe a request flow in plain words and get one HTML file that teammates can hover, click and walk through.

    View prompt
    Use the SeeCode skill from the Aryanutkarsh/SeeCode repo to diagram <describe the target system flow>. Produce one interactive HTML file that shows each component and its connections. Verify that every component named in the description appears as a node and that the file opens in a browser.
  • Watch your agent sessions as a live team call

    Open a live animated call that shows which Claude Code or Codex agent is working and who is waiting on whom.

    View prompt
    In the repo Atoll92/agent-standup, run `npx @double_geste/agent-standup@latest --open` and open the live call for my newest Claude Code or Codex session. Report which agents are shown as working and which are waiting. Verify that the sub-agent tree lists the lead and its sub-agents with their status.
  • Run Codex CLI on Atria Dawn as a text-only agent

    Point Codex at the Atria endpoint and stop it from sending images to the model.

    View prompt
    Using the atria-asi/Atria-Dawn README, configure Codex CLI to use the model Atria-Dawn through the provider at https://api.atria-asi.ai/v1 with text-only input. Write ~/.codex/atria-catalog.json and update ~/.codex/config.toml as described. Expected output: a Codex session that answers a text prompt without a 400 error. Verify that the catalog lists Atria-Dawn with input_modalities set to text.
  • Run coding agents on several machines in one window

    Link a laptop and a GPU box so Claude Code and Codex run in one command center.

    View prompt
    In the openharness repo at autonomous-ai/openharness, follow the Get started section to link the machine <machine-name> to the desktop app. Confirm that the daemon runs with `harness start` and that <machine-name> appears under Machines. Report the machine name and the list of harnesses running on it.
  • Gate agent commits so bad changes never land

    Run the commit gate on agent output to catch formatting, conflict markers, junk files, and secrets.

    View prompt
    In the azrtydxb/procoder-enabled repository at <repo-path>, run `procoder check` after your changes. Report the count of blocking findings and fix each one before you commit. Verify that the final run shows zero blocking findings.
  • Make a beat-synced launch video from a script

    An agent turns a release script into a 1920×1080 video with voice-over, captions and music.

    View prompt
    Using the motion-video skill from bestagentkits/motion-video-skill, make a <length>-second launch video for <release name> in the comic multiverse style with voice-over, captions and music. Follow the production pipeline in order and deliver the rendered 1920×1080 30 fps video. Verify that hyperframes lint and check pass and that the loudness is around -14 LUFS with a true peak no higher than -1 dBFS.
  • Find where Claude Code tokens are wasted

    Run one report on your local logs to see savings ranked by how sure they are, in dollars.

    View prompt
    Run `npx optimaizr` from the optimaizr repo (github.com/blendbunjaku/optimaizr) on this machine and report the Clear waste and Re-reading the conversation figures. Verify that the savings are reported per month and that the three savings tiers are not added together.
  • Turn chosen WeChat chats into cited personal notes

    Have a coding agent write a private wiki from your chats, with each fact tied to its source message.

    View prompt
    Use the GreenBubbles personal-memory skill in the repo bojieli/greenbubbles at <skill path>. Read chats from the last month through the greenbubbles CLI and write Markdown notes, one article per life topic, with each fact citing its source message. Verify that every note fact has a citation and that no passwords or keys appear in the output.
  • Approve Codex and Claude Code requests from your phone

    Pair your computer with your phone so you can approve commands and answer agent questions away from your desk.

    View prompt
    Using the BotBus setup described in botbus-io/botbus-protocol, confirm that the Mac app is paired with <phone name>. Report whether a Codex or Claude Code task on <computer name> is waiting for a request, and list the request kind and task ID without approving anything.
  • Let a coding agent operate a running Mac app

    Give an agent read and click access to a Mac app window, one shell command per step.

    View prompt
    Using the macos-harness repo at https://github.com/browser-use/macos-harness, run `macos-harness get_app_state --app <app name>` on the target app and list the numbered elements in its window. Verify that the output contains at least one numbered element and a screenshot path before you click anything.
  • Draw a flowchart or architecture diagram as lint-clean SVG

    Have your agent hand-place an SVG diagram in the house style and confirm it with svg-lint.

    View prompt
    Using the svg-diagram skill from bybit-exchange/svg-diagram, draw an architecture diagram of <system> as diagram.svg. Run node tools/svg-lint/bin/svg-lint.mjs diagram.svg and fix every finding until it reports 0 errors and 0 warnings.
  • Build a real-footage documentary montage for free

    Have an agent assemble a real-footage montage from free archives and stock with music and no narration.

    View prompt
    Use the OpenMontage repo at <repo-path> to make a 75-second real-footage montage about <topic> with no narration and an elegiac tone. Read AGENT_GUIDE.md, pick the matching pipeline, and render an MP4. Verify the output with ffprobe that it is about 75 seconds long and has an audio track.
  • Run an Expo app in a simulator beside your chat

    Install Mobile Dev, pick a simulator, and have Codex build and run your app in view.

    View prompt
    Using the callstackincubator/codex-mobile-dev-plugin Mobile Dev plugin, build and run the Expo app at <project path> on the simulator named <device name>. Expected output: the app launches on that simulator and is visible beside the chat. Verify the device panel shows the running app before reporting success.
  • Run Claude Code or Codex on a model you own

    Launch Claude Code or Codex so the model answers on your Mac instead of a vendor server.

    View prompt
    In the canivel/dynolab repo, read docs/coding-tools.md and launch Claude Code on the downloaded model <model-name> with `dyno launch claude --model <model-name>`. Expected output: a Claude Code session that answers a simple prompt using the model served on this Mac. Verify that the session replies and that the model is the one you started in Dyno Models.
  • Ask your coding agent questions from inside WoW

    Run the bridge, then send a task from the game and get pinged when the agent replies.

    View prompt
    In the wow-ai repo, follow the README install steps for your OS with the project path <project-folder>, start the bridge with npm start, then confirm the bridge light is green in the WoW window. Expected output: a short reply from the agent appearing in the game chat. Verify the reply arrived in the window before reporting success.
  • Keep a long Codex image task going by unchecking old images

    Uncheck past images in the Context Assets panel so later requests stay small and the task keeps running.

    View prompt
    Using the repo chipfighter/context-attachment-manager, install the plugin in the Codex desktop app for the task <task name>, then uncheck the images from turns older than <turn number> in the Context Assets panel. Report the estimated size of the next request shown in the savings card, and confirm that the unchecked images appear as placeholders in the next message.
  • Make an NPC in your own game answer you in character

    Install the skills, stand up the voice server and get one NPC replying in a cloned voice.

    View prompt
    Using the NPCTalk repo at https://github.com/christos-antono/NPCTalk, start the make-npcs-talk skill and make the NPC <npc-name> in <game-name> answer typed questions in a voice. Expected output: a working speak loop and a WAV from `npctalk say`. Verify that `npctalk health` reports the voice server up before testing the game.
  • Run a coding task from one sentence to a reviewed change

    Start a task from one prompt and approve the spec and diff at a human gate.

    View prompt
    Using the Grasp repo (cocofhu/grasp), start a run for <task description> from the home page of a local Grasp instance. Confirm the run reaches the human gate, then report the spec and the code diff summary the reviewer will see.
  • Stop a coding agent from breaking your written project rules

    Hook Abide into your agent so each edit is checked against your instruction files and violations are repaired in the same turn.

    View prompt
    In the repo <repo-path>, install Abide with `npx @coldtea/abide init` and confirm that `.abide/rubric.json` was created after the first agent turn. Then ask the agent for an edit that breaks one rule in AGENTS.md and report the rule id and file that Abide names.
  • Find the exact step that broke an agent run

    Replay a failed coding agent run offline and see which tool call changed a file or skipped a failing check.

    View prompt
    Use the OrcaReplay repo (Continuum-AI-Corp/OrcaReplay) to inspect the most recent failed run on this machine by running `orca show last` and `orca graph last`. Report the sequence number of the tool call that changed <target file> and the sequence number of any shell check that exited non-zero. Verify that `orca replay last` prints the run again with no model called.
  • Track which of many coding agents needs your input

    Run several agents at once and see which are working, waiting, or finished in one sidebar.

    View prompt
    Using the diri repo at github.com/cristicretu/diri, check that the sidebar marks each of my running sessions as working, waiting, or finished. Output a list of session names with their status, and confirm that the session in <target-session> is marked waiting when it asks a question.
  • Find a fact on a web page and confirm its source

    An agent opens a page, locates a named link or value, and reports where it points.

    View prompt
    Using the axuse MCP server from the repo at <repo path>, open <target URL>, find the link labeled <link text>, and report its destination. Check that the reported destination matches the link target shown in the accessibility snapshot before answering.
  • Plan a multi-step change before any code is written

    Make an agent research, ask, and plan a big change before it builds anything.

    View prompt
    Using the Da7-Tech/SureForge skill, research the unknowns in <task description> before asking me questions, then produce a plan that maps each acceptance criterion to a step and a verification method. Expected output: the plan and a plan gate result of READY, REPAIR, or BLOCKED. Verify that no build step appears before the plan gate is READY.
  • Coordinate Claude, Codex and Cursor windows on one project

    Give several AI coding windows shared tasks, acknowledgements and a review step on one codebase.

    View prompt
    Using the Squadra repo at https://github.com/dagoSte/squadra, set up a shared squad for the project at <project path> with Claude Code and Codex windows. Show the install plan first and wait for my approval. Expected output: a list of open tasks and any waits for each window. Verify that `squadra status --all` runs without errors and lists every registered window.
  • Run coding agents on your own Linux server

    Install the core on a VPS or home server so Claude Code and Codex run there, not on your laptop.

    View prompt
    Using the cloudroom-core repo, install the core on <server-host> following docs/setup.md, then create one session for Claude Code using the HTTP API in docs/api.md. Expected output: the session ID and the agent's first reply. Verify that the API rejects a request sent without the secret token.
  • Move a running agent task to the cloud before you leave

    Hand a half-finished coding task from your Mac to a cloud agent without losing the chat.

    View prompt
    Using the Cloudroom app in the cloudroom-gui repo, move the running thread for <project or task name> from the Mac to the cloud with Teleport. Expected output: the same thread running in the cloud with the same chat, model, and effort. Verify that the chat history and model match before you report success.
  • Generate a runnable TypeScript workflow from plain English

    Describe a multi-step job in one sentence and get a runnable TypeScript workflow module.

    View prompt
    Using the deer-workflow repository (deerwork-ai/deer-workflow), generate a runnable TypeScript Workflow for <target job description> with the deer-workflow create command, save it to workflow.ts, and run it with a sample input. Expected output: a workflow.ts file plus a run result. Verify that the run finishes and that the phases in the file match the steps described in the job.
  • Keep coding when one provider's quota runs out

    Route Claude Code, Codex or Cursor through one gateway that falls back to the next healthy model.

    View prompt
    Using the diegosouzapw/OmniRoute repo, configure <agent> to send chat requests to http://localhost:20128/v1 with model auto/thrifty. Run one test request with curl and report the completion text it returns. Verify that the request succeeds with the OmniRoute key and no provider error is returned.
  • Switch Codex and Claude Code to a new API provider

    Add a provider once with its API address and key, then switch between providers with one click.

    View prompt
    Using the uni-switch project at github.com/dieqiyun/uni-switch, add a provider with API address <api-address> and the API key stored in <key-env-var>, then confirm the provider appears in use for the chosen client. Expected output: the provider listed as in use, with a note to restart the client and start a new conversation. Verify that the local config backup was created before the change.
  • Find the one AI coding session that needs you

    See every Claude Code and Codex session in one picker and jump to the one waiting on you.

    View prompt
    Install Session Kit from https://github.com/dob323/session-kit using the latest release artifact, then run `session-kit doctor`. Confirm that `kit` opens a picker listing the Claude Code and Codex sessions on <host>, and report the state shown for each session.
  • Give your AI assistant the day's work without pasting it

    Register the app as an MCP server so your assistant can read the day's record and notes directly.

    View prompt
    Using the ambient-context MCP server from the dedupedai repo of dragthelake/ambient-context, read the day <placeholder> with the reading-days tools and summarise the work in five bullet points. Expected output: five bullets, each tied to a block in the record. Verify that every bullet names an app or file path that appears in the Days folder for that date.
  • Run several coding agents on one backlog in parallel

    Split a backlog into task cards and let agents work on them at once without write conflicts.

    View prompt
    In the dualface/kander repo, load the Kander rules and create one task card for the requirement <requirement description> with clear acceptance criteria, then confirm it was launched through the kanban flow. Report the card ID and its status. Verify that the card appears on the board with its own isolated workspace.
  • Find the code behind a behavior before an agent edits it

    Ask a repository question and get files, leads, and source excerpts to start an unfamiliar change.

    View prompt
    Use the jevgrep skill in this repository to run `jg` with the question "<question about the behavior>" against <target path>. Report the files, line references, and source excerpts it returns, and confirm each cited file exists before you propose any edit.
  • Generate a 3D CAD model from a text description

    Describe a part to your agent and get it back as a STEP, GLB, STL or 3MF file.

    View prompt
    Using the text-to-cad plugin from https://github.com/earthtojake/text-to-cad, build a 3D model of <part description> and export it as <STEP, GLB, STL or 3MF>. Return the output file path and confirm the file opens in the CAD Viewer.
  • Make a new video in the style of one you love

    Drop in a reference video and a one-line brief to get an original video with the same pacing and look.

    View prompt
    In the reelmimic repo, start the local web app, submit <reference video path or link> with the brief <one-line brief>, and approve the plan once it appears. Expected output: a finished video in the project folder with a final review result. Verify that the Production line tab shows every shot passed review before you report success.
  • Run several coding agents side by side in one app

    Keep projects and separate agent sessions from different CLIs in one native desktop window.

    View prompt
    In the waku repo at <path to Waku checkout or install>, confirm that Waku can see at least one agent CLI by opening the app and listing the detected agents for the project at <project path>. Expected output: a list of detected agents and the sessions created for each. Verify that each session shows its own transcript.
  • Make a game-ready Unreal crate with baked normals and LODs

    Have an agent optimize a crate model, bake its normal map, create LODs and export it for Unreal.

    View prompt
    Using the blender-skills repo, make <target crate model> game-ready for Unreal with baked normal maps and LODs, then export it. Expect the exported file, a list of LOD levels and the baked texture files. Verify that the export contains every LOD and that the normal map maps to the correct UV set.
  • Hand off a coding task between harnesses in one window

    Keep one Codex Desktop window and pass a task from one harness to another for a second pass.

    View prompt
    Using the repo emo-xiaoyu/harness-mix, set up Harness Mix on this machine and hand the current task at <task description> from the current harness to <target harness> with the independent review mode. Report the checkpoint created and confirm the target harness resumed its native session.
  • Check what an agent read before it edited a file

    Replay a session to see which files the agent opened before changing code, and which it never opened.

    View prompt
    In the agentplay repo at https://github.com/Entelligence-AI/agentplay, run `uvx agentplay` and open the session that edited <target file path>. Report which files the agent read before the first edit to that file and which related files it never opened. Verify by confirming each listed read appears earlier than the first edit on the timeline.
  • Plan a project and agree on which model does each part

    Get a plan, a model recommendation for each part, and your approval before any building starts.

    View prompt
    Using the codex-on-crack package in <project folder>, run the crack-plan skill to list my available models and propose a plan that assigns each phase to a model. Expected output: a written plan with one model recommendation per phase and no code changes. Verify that the plan waits for my approval before any build step begins.
  • Read a Claude Code or Codex session step by step

    Load one authorized agent session file and browse its events in a local timeline.

    View prompt
    Using the TraceCrate repo at <repo path>, run npm ci and npm run dev, then load the authorized session file <session file path> through Choose files. Expected output: a Timeline listing that session's events with search and kind filters working. Verify that token totals appear only where the file reports them and that missing values are shown as unknown, not zero.
  • Run Codex in Herdr from your phone

    Start a coding task on a remote machine from a phone and check its output in the Herdr terminal.

    View prompt
    Using the farlume/termish README, give step-by-step instructions to connect a phone to <host> over SSH, open Herdr, and start Codex with the task <task>. Expected output: a numbered checklist of app steps. Verify that the checklist includes host key verification before the first login.
  • Make a launch video from one sentence

    Describe a video in one line and get a rendered final.mp4 on your own machine.

    View prompt
    Using the showtime skill from the FavioVazquez/showtime repository, make a 20-second launch video with a voice-over for <project name>. Expect a new folder under showtime-out/ containing final.mp4, poster.jpg and share.txt. Verify that showtime qa reports no FAIL before you report the result.
  • Compare flight fares across a date range from your assistant

    Have your assistant check each date in a range on a booking site and report the cheapest fare per day.

    View prompt
    Using the invisible_playwright_mcp server from feder-cr/invisible_playwright_mcp, open <booking-site-url> and check the cheapest economy fare for one adult, one checked bag, from <origin> to <destination>, for each date from <start-date> to <end-date>, clicking the days in the calendar widget one at a time. Expected output: one line per date with the cheapest fare or the words no availability. Verify that no booking was submitted.
  • Make a 15-second product launch film with one camera

    Have a coding agent turn a short app description into a launch film where every beat carries into the next.

    View prompt
    Using the onetake skill in the feitangyuan/onetake repo, make a 15 second launch film for <app name and one-line description>. Output a 1080p30 draft video file and its beat sheet. Verify that the continuity check passes and that every boundary in the beat sheet names what carries across it before you report done.
  • Let a coding agent search your product docs

    Deploy Carrel locally and give Claude Code or Codex a search skill over your own document folders.

    View prompt
    Using the Carrel repo at https://github.com/FengZhenfei/carrel, set up the carrel-search skill for this agent and query the search endpoint at http://127.0.0.1:9810/search with a question about <topic>. Return the answer with the source passages cited. Verify that the response contains source passages before answering.
  • Add a polished message action bar to an AI chat

    Drop a finished copy, regenerate, feedback and read-aloud bar under each AI reply in one file.

    View prompt
    In the affectui repo context, install the message-actions item into the <project-path> Next.js or React 19 project using `npx shadcn@latest add https://www.affectui.com/r/message-actions.json`, then render it under the last assistant message in <chat-component-file>. Expected output: a MessageActions import and usage in that file with your existing handlers wired to props. Verify the project still builds and the bar renders with no console errors.
  • Resume an interrupted Claude or Codex coding task

    Find a stopped session in the local workbench, review its evidence, and prepare a continuation command.

    View prompt
    Using the Frankie-Xu/threadport repo built with Node 24, start the local workbench with `node dist/src/cli.js ui --no-open` and attach the session in <project-directory> as a task. Report the observed files, commands, and failures, and confirm that the continuation text contains no unconfirmed objective before any launch.
  • Point a human at the Allow button an agent cannot press

    An agent draws an arrow and sign at the permission button so the human clicks it.

    View prompt
    Use the bigarrow CLI from the repo franzenzenhofer/big-arrow-on-the-screen to point at the button labelled <button label> in the app <app name> with the sign text "<sign text>". Expected output: a JSON result from `bigarrow point ... --json` with an exit code of 0. Verify the exit code is 0, and if it is 4 run `bigarrow doctor` and report which app needs Accessibility.
  • Follow a running agent session as a live graph

    Watch the main agent, its subagents and their tool calls update live in your terminal.

    View prompt
    In the zoetrope repo (furkankly/zoetrope), install the zoe binary and run `zoe` from the project directory at <project-path> to follow its newest live session. Expected output: a live flow graph showing the main session and any subagents with their current tool. Verify that at least one agent card shows a status and tool count before reporting success.
  • Render a title card to MP4 from TypeScript

    Write one TypeScript file that builds a 1080p60 title card and renders it to a hardware-encoded MP4.

    View prompt
    Using the framefields repo, write a TypeScript script that builds a 1920x1080, 60 fps composition with a title card reading <title text>, renders it with renderVideo to output/<file name>.mp4, and runs it. Expected output: an MP4 at that path. Verify the file exists and that the printed Rendered to path matches it.
  • Set up a family TV with a clean, ad-free home screen

    Turn a sponsored-ad Android or Google TV into a clean home screen over Wi-Fi, with no root and nothing uninstalled.

    View prompt
    Using the Gathin23/cleanyourtv repo as context, follow PROMPT.md for the TV model <tv-model> on the local Wi-Fi network. Back up the installed package list and settings, disable the manufacturer ad and telemetry packages with pm disable-user, and install the launcher as the default home screen. Expected output: a backup of the package list, a list of disabled packages, and confirmation that the launcher is the default home. Verify that no packages were uninstalled.
  • Generate images from a text prompt in Codex

    Install the skill once, then create a finished GPT image from one natural-language request.

    View prompt
    Install GPT Image Skill from https://github.com/GENEXIS-AI/gpt-image-skill using the AGENT_INSTALL.md contract, then generate one image of <subject> at <aspect ratio> with high quality. Expect a PNG under /generated-images and a PATH=... line in the output. Verify the file exists and that the output did not use OPENAI_API_KEY or the Images API.
  • Connect an agent to the growth.engineer catalog

    Add the read-only MCP server so an agent can search workflows, tools and companies.

    View prompt
    Use the growth-engineer MCP server at https://www.growth.engineer/mcp to search for workflows about <goal>. Return the title and key of each match and open the first one with get. Check that the returned file has a title, inputs and steps before you report back.
  • Run a phone test from your AI IDE chat

    Describe a test in your AI IDE and have ARTEMIS run it on a connected Android device.

    View prompt
    In the google/artemis repo, use the ARTEMIS MCP tools to run this test on the connected Android device: <test scenario>. Expected output: a pass or fail status, screenshots of the final screen, and a list of any unexpected popups. Verify that the report states which device ran the test.
  • Give your coding agent the code graph and project memory

    Install Graphicle once and connect your coding agents to the repo's code graph and memory.

    View prompt
    In the Graphicle-AI/graphicle repository's setup, run `graphicle setup --yes` in <repo-path>, then list every file it changed. Expected output: a list of changed files and a confirmation that the Graphicle MCP server is connected. Verify by asking the agent to use graphicle to find <topic> and checking that the answer cites file names and line ranges.
  • Share one project memory across coding agents

    Install OwnMem in a repo so Claude Code, Codex, Cursor, and Gemini CLI read the same memory.

    View prompt
    In the repository grpcer/ownmem, install OwnMem into <target-repo> with the commands in its Quick start, using --hosts for the agents the team uses. Expected output: a .ownmem/ directory and host adapters created, with any one-time host steps listed. Verify that `npx ownmem recall -- "<a known project topic>"` returns a result or an abstention.
  • Make a short AI film from one character

    Create a reusable character, draw key stills, then shoot and join short clips into one film.

    View prompt
    Using the flow-mcp repo at <repo-path>, check the Flow session, create a character named <character-name>, draw three free stills with that character, and then shoot three 10-second 720p clips with max_credits set to <credit-cap> per clip. Expected output is a joined MP4 under ~/flow-mcp-out/. Verify that flow_status reports signed in and that the credit cap was not exceeded before shooting.
  • Keep a coding agent working until tests pass

    Give an agent a goal and a check command, and let it loop turn by turn until the check passes.

    View prompt
    Using the Bloks repo at hamedgitty/bloks, start a /goal in the agent conversation for the project at <project-folder>, with the check pnpm test. Expected output: the goal reports done, stuck or out of turns, and the test run result. Verify that pnpm test passes in <project-folder> before you call the goal done.
  • Find the cheapest listed API for a model

    Ask your agent for the lowest listed price for a model, with the site, group, unit and observation date.

    View prompt
    Using the Grandet Skill or the MCP server at https://grandet.ai/mcp, find the cheapest listed API for <model name>. Return the top three options with site, group, price, unit and observation date, and confirm that prices are shown in one currency unit only.
  • Catch agent-written PHP debt before the edit lands

    Install Sloppy hooks so Claude Code, Gemini CLI or Codex checks each PHP edit and fixes new findings.

    View prompt
    In the Heyosseus/sloppy project, install the agent hooks for this repository at <project path> by running the install command for the host agent. Then make a small edit to <target PHP file> that adds a try/catch block, and confirm the agent reports any new findings from that edit. Output the list of findings and whether the agent fixed them.
  • Cut Codex and Claude Code costs with difficulty routing

    Send routine reading and fact gathering to cheaper models while hard design work stays on your primary model.

    View prompt
    Using the HiRoute repo at https://github.com/higress-group/HiRoute, set up difficulty routing for <target agent client> so routine turns use the regular model group and hard turns use the primary group. Report the published routing plan name and the model group chosen for the last three turns in a session. Verify that the sessions view shows the actual model that ran and its cost.
  • Install agent-ready CLIs from CLI-Hub with pip

    Use the cli-hub package to browse and install community CLIs for desktop software in one command.

    View prompt
    Using the HKUDS/CLI-Anything repo, install the CLI-Hub package with pip, then install the harness named <target-cli> with cli-hub. Report the install result and the help output of the new CLI. Verify that the command runs without an error before you finish.
  • Run a one-off agent flow from your shell

    Send one question or task to a chat flow and get the agent's answer in your terminal.

    View prompt
    Using the humanize repo (hmz), run `hmz exec -f chat -a assistant=claude/claude-opus-5:high "Summarize the purpose of the repository at <repo-path>"` from a scratch directory. Output the agent's summary as plain text. Verify that the summary names at least one file or folder from <repo-path>.
  • Decompile your own N64 game with an AI agent

    Point your agent at a ROM you own and get C functions that compile to the same bytes.

    View prompt
    Using the decomp.wtf repo (i12bp8/decomp.wtf), import the N64 ROM at <path-to-your-rom> that I own, then run the agents until the live view shows matched functions. Report the number of functions matched and the number still open. Verify that every reported match is byte for byte against the ROM, and that no target assembly or build script was edited.
  • Redraw a figure in draw.io and export a 2000 px PNG

    Rebuild an uploaded figure on a live draw.io canvas and save an editable .drawio file.

    View prompt
    Using the scientific-illustrator plugin, connect to the live draw.io canvas and redraw the uploaded reference figure as editable shapes, connectors, and groups. Save an editable .drawio file and export a PNG preview at 2000 px width. Verify that the canvas screenshot matches the reference layout before saving.
  • Find where a Codex task spent its time

    Break one task's active time into tool, model/token, and unattributed shares to locate slow steps.

    View prompt
    Using the icesixgod/codex-trajectory repo, open the timing breakdown for the Codex task <task name or sessionId> with the show_codex_trajectory tool. Report the tool, model/token, and unattributed time shares with percentages. Verify that missing or invalid tool timing is listed separately from zero-duration events.
  • Learn why a branch change is written that way

    Step through a git branch as a guided tour that explains intent, risks and what to check.

    View prompt
    In the git repository at <path>, install diff-tour and confirm the `tour` command is on the PATH. Expected output: the path to the tour binary. Verify with `git status` that no tracked files changed.
  • Turn a game idea into a playable Web game

    Describe a game in plain language and get a reviewed, playable local Web project.

    View prompt
    Using the Noobi.ai repo cloned at <path>, run `npm ci` and `npm run dev`, then submit this game brief in the workbench: <game idea>. Expect a standalone Web project in the local workspace that passed the review and playtest gate; verify the completion status shown in the workbench before reporting success.
  • Build a landing page from shortlisted award-winning references

    Turn 2 to 5 Awwwards sites into a cited design brief your agent can build from.

    View prompt
    Use the awwwards-mcp server to search for portfolio references, shortlist 3 sites, then call create_design_brief with the slugs and the goal "<project goal>". Expected output: a cited Markdown direction plus versioned JSON that separates shared signals from one-site outliers. Verify that every color and motion cue in your build traces back to a cited signal in the brief.
  • Triage support tickets by urgency and owning team

    Have an agent score each ticket for urgency and pick the owning team with probabilities.

    View prompt
    Use the evaluate tool from the itsmostafa/system-one-connector repo to decide whether this ticket is urgent (noul question) and which team should own it (choice question with billing, technical and sales criteria): <ticket text>. Return the noul value and the department probabilities as JSON. Verify that the probabilities for the choice question sum to about 1.
  • Watch every agent's quota at the Mac notch

    Build the open-source HUD and see each agent's quota as a colour glow at the notch or a screen edge.

    View prompt
    In the agent-hud-open repository, run `make check`, `make test` and `make run`, then report whether build/Agent HUD Open.app opened. Verify that at least one agent quota shows a colour glow, and state which quota it is.
  • Find the worth-keeping sessions in your coding history

    Import local Claude Code and Codex history and rank the sessions that hold useful task evidence.

    View prompt
    Using the EvoTrace repo at https://github.com/jinzijian/EvoTrace, install it and run /init then /candidates in the DeepSeek Harness app on my local Claude Code and Codex history. Return the top 5 candidates with task intent, repository, and missing evidence for each. Verify that the candidate list loads with no model provider configured.
  • Break a multi-episode series into acts and act outs

    Get an act-by-act breakdown with act outs for each episode of your series, using the series structure skill.

    View prompt
    Using the screenwriting-skills repo (sw-series-structure), read the series outline in <path or pasted text> and produce an act breakdown for each episode with act-out and cliffhanger placements. Verify that every episode lists a teaser or cold open and at least one act-out before returning the result.
  • Build a distinctive portfolio site from one line

    Get a designed, browser-checked portfolio site from a single sentence instead of a template.

    View prompt
    Using the juliobsz/skills repo, run the /awwwards skill with the brief 'make me a portfolio, my name is <name>, I work as <craft>'. Expect a built site folder, a DESIGN.md file and a list of placeholder copy. Verify that no placeholder text remains in the final HTML before you report the site as done.
  • Run the full Xyne Spaces stack on your machine

    Clone the repo and start the dashboard, backend, Claw and Claw Auth with one command.

    View prompt
    Clone https://github.com/juspay/xyne-spaces.git into <target-folder>, run `pnpm run up` from the repo root, and report which phase failed if any. Expected output: the dashboard at http://localhost:5173 responds and the backend API at http://localhost:3001 responds. Verify both URLs return a page before reporting success.
  • Cut an interview into a 60-second Reels clip

    An agent keeps chosen segments of a long interview, fits them to 60 seconds in 9:16 and exports a Reels file.

    View prompt
    Using the ffmpeg-skill repo, take <interview file> and keep 0:45-3:10 and 5:00-6:30, make it exactly 60 seconds at 9:16 for Reels, and export it. Expected output: a Reels MP4 of about 60 seconds at 1080x1920. Verify the duration and resolution with probe.py before you report it done.
  • File your FY 2025-26 income tax return without a CA

    Turn Form 16 and AIS into a checked, regime-compared filing pack for the income tax portal.

    View prompt
    Using the itr-wala repo at <repo-path>, run the self-test, then extract income from the Form 16 and AIS in <documents-folder> into income.json for FY 2025-26. Produce the old and new regime comparison and the portal filing pack. Expected output: a comparison table and one final payable or refund figure; verify the self-test ends with OK and that TDS matches the AIS total before you report.
  • Get a second-model review of a pull request

    Run agy's reviewer persona on a PR to get severity-ranked findings before merging.

    View prompt
    Using the keli-wen/agy-staff plugin, run the reviewer persona on PR <PR number> in <repo>. Expect a severity-ranked list of findings. Verify that each finding names a file or line from the PR diff.
  • Review agent edits in Git and Diff views before committing

    Open a project, let an agent change files, then inspect staged and unstaged changes in the app before you commit.

    View prompt
    In the BetterC0de repo's Git and Diff views, open the project at <project-path> after an agent has edited it. List every staged and unstaged file with a one-line summary of each change, and flag any change you cannot explain. Verify that the list matches `git status` run in <project-path>.
  • Get a one-screen done-or-not report after each session

    Ask "are we done?" and get a verdict on done, needed input, new debt and whether it is safe to close.

    View prompt
    In the open-steps repo at <repo-path>, use the os-done-or-not skill to report on the work just finished for <task-name>. Expected output: a one-screen report with a Fully done row, an Anything needed from you row, a New debt row and a Safe to close row. Verify that each row states a verdict and does not rely on commit hashes alone.
  • Turn repeated agent prompts into slash commands

    Install the skill, find the requests you repeat, and save each one as a short slash command.

    View prompt
    In the cli-faq-shortcuts repo, install the faq-shortcuts skill as described in its Quick start, then run /faq-shortcuts in the project at <project_path>. Expected output: a table of repeated asks with how often each was typed. Verify that each chosen shortcut has a SKILL.md under .claude/skills/ in that project.
  • Make a 25-second launch teaser with sound

    Have an agent brand, direct, score and render a launch film from a short brief.

    View prompt
    Using the cinetic skill in the Leonxlnx/cinetic repo, make a 25-second launch teaser with sound for <product name>, using the brief <one-paragraph brief>. Render a 1920x1080 MP4 and report the seed printed by pick.py. Verify that the QA audio-sync audit and the ship gate pass before you hand over the file.
  • Gate a solo refactor with a verified GATES.md ledger

    Turn a substantial change into runnable gates and re-check them before claiming done.

    View prompt
    Use the unlazy skill in the repo <repo-path> to refactor <target-module>. Write GATES.md from templates/gates-leaf.md with one runnable gate per outcome, then run node /scripts/gate-check.mjs --reverify GATES.md. Report the gate results, and verify that every gate is marked met before you say the work is complete.
  • Ask an agent which skills are worth installing

    Give an AI agent the ranking guide so it can answer questions about top skills from current data.

    View prompt
    Read https://linkly.ai/skills/llms.txt, which describes the LinklyAI best-skills rankings. Answer this question: <your question>. Return the top three skills with their Worth-Installing Score, Cov value and per-platform counts. Verify one number against the matching CSV in data/ from the LinklyAI/best-skills repo.
  • Run a local model as the backend for a coding agent

    Serve Qwen3.8-27B on your Mac and point a coding agent at it without sending code to a hosted API.

    View prompt
    Using the lithos-metal repo at https://github.com/lithos-ai/lithos-metal, start the server with `lithos-metal serve --model nvidia/Qwen3.8-27B-NVFP4` on this Mac, then run `lithos-metal <client>` where <client> is the coding agent you want to use. Report the served model name and the first reply to a one-line test prompt. Verify that http://127.0.0.1:8000 answers before reporting success.
  • Connect a machine and dispatch agent work to it

    Attach a laptop, server, or cloud VM to your workspace and start agent sessions on it from the CLI.

    View prompt
    In the LodyAI/Lody repo, use the CLI to create a session in the workspace <workspace-name> on the connected machine using the agent config <agent-config> with the prompt <task>. Output the new session ID and its status from the session list command. Verify that the session appears in the output of `npx lody session list --workspace <workspace-name>`.
  • Trace which methods log a given string and who calls them

    Have an agent query an APK over MCP to map a log message to its methods and callers.

    View prompt
    Use the dexsql MCP server to open <path to APK>. Find every method that references the log message <message text>, list each caller of those methods, and show the relevant Smali. Before summarizing, confirm that each reported method name appears in the query results.
  • Check which modeling stages this machine can run

    Run the doctor check to see which stages work and which dependencies are missing.

    View prompt
    Use the Modeling Workbench repo in <tool folder> to check my environment. Read .agents/skills/cumcm-workflow/SKILL.md, run scripts/doctor.py, and list the available stages and missing dependencies. Do not install or change anything without my approval, and confirm the report names the tool folder and version.
  • Run a product launch with a GTM Engineer

    A scheduled employee drafts launch work and stages it for your review each morning.

    View prompt
    Using the ai-employees repo, install the GTM Engineer into <target folder> and confirm it builds a dashboard and schedules its routines. Expected output: a staged first set of drafts and a brief in the folder. Verify that nothing was sent, posted or submitted before you approved it.
  • Align an agent on a change before any code is written

    Run a grilling session so the agent asks detailed questions before it edits your repo.

    View prompt
    In the mattpocock/skills repo's grill-with-docs workflow, interview me about the change described here: <feature description>. Expected output: a short list of resolved decisions and updated GLOSSARY.md entries or ADRs. Verify that every new term in the output appears in the glossary file.
  • Scan a Kotlin change for known footguns before merge

    Run a 32-pattern scanner over the lines your branch adds and review each flagged trap.

    View prompt
    In the kotlin-footguns skills installed in <repo path>, run the footgun-scan script against origin/main and open the trap file for every likely hit. Expected output: each hit marked confirmed or dismissed with a one-line reason. Verify that every confirmed hit names a trap file that exists in the skill directory.
  • Resume a coding task with lessons from earlier sessions

    Recall verified fixes and failed approaches from past work before a new session starts changing code.

    View prompt
    In the <project path> repository, use the MemoraX Code skill to recall prior engineering lessons about <task area> before you edit anything. List each lesson you retrieved and state which one you will apply first. Verify that the list comes from the memory search result, not from your own assumptions.
  • Run a meaning-preserving final pass on a finished paper

    Have an agent make small wording edits to a draft and log every change for review.

    View prompt
    Use the game-the-llm-reviewer skill from the repository Michael-Jiahao-Zhang/game-the-llm-reviewer on <path to finished manuscript>. Read the included sections first, apply small meaning-preserving edits, and save a revised copy and changes.md. Verify that every change note entry keeps the same claims, numbers, and citations as the original.
  • See what your coding agents did and what it cost

    Install Agentacct once and review recent agent tasks, tool calls, tokens, and estimated cost on your machine.

    View prompt
    Install agentacct from https://github.com/mikehasa/agentacct on this machine using pipx, then run agentacct onboard. Report the most recent task names and their estimated costs in <project path>, and confirm that costs are marked as estimates. Verify that the Sessions view opens in agentacct tui.
  • Take an agent-built app live on your own accounts

    Detect what the app needs, approve a plan, and deploy it to your Vercel and Supabase accounts.

    View prompt
    Use the golive skill in the repo <repo-path> to detect what this app needs, then present the destination accounts and plan for Vercel hosting with Supabase before changing anything. After approval, report the live URL and the verification result, and confirm that the Vercel team and Supabase organization shown in the plan match the accounts I named.
  • Build a landing page free of generic AI UI

    Install antislop and have an agent build a UI with no invented numbers or filler decoration.

    View prompt
    Using the antislop rules from the anti-slop repo (https://github.com/miqdadbadjuber/anti-slop) and the DESIGN.md in <project-folder>, build a landing page for <product-name>. Finish with the Delivery Gate PASS/FAIL report. Verify that no statistic or testimonial appears on the page unless it is provided in the brief.
  • Turn a coding task into a verified patch

    Run a coding agent in an isolated microVM and get a patch plus gate results.

    View prompt
    In the ESF repo at <esf_path>, submit a run against <repo_url> at commit <full_sha> with the task in <task_file>, then poll `./bin/factory status <RUN_ID>` until it finishes. Report the patch location and gate results, and confirm the verification gates passed before calling the run successful.
  • Use ChatGPT Web models inside Codex without Codex quota

    Add ChatGPT Web models to Codex's native picker and keep Codex quota unused.

    View prompt
    Using the codex-chatgpt-web repo, check that the launcher is installed and that a model ending in (Web) appears in Codex's model picker for <account or workspace>. Report the model names you see and whether the browser smoke test passed. Verify that no Codex quota is used by running one short prompt on a (Web) model and confirming the reply arrives.
  • Add your API to Monid as a connector

    Write a provider and endpoint definition and open a pull request to add your API.

    View prompt
    In the monid repo, read AGENT.md and connectors/exa/, then write a provider and one endpoint for <your API docs URL>. Run deno task check && deno task test and report whether they pass with no network.
  • Turn a four-line poem into a vertical Chinese-art video

    Make a 1080x1920 video where each line of a short poem gets its own painted scene with moving elements.

    View prompt
    Use the classical-poem-silk-video skill from https://github.com/Mr-funny/hbg-classical-poem-silk-video to make a 1080x1920 video of <poem title>, one scene per line with a fixed camera and natural motion in the painted elements. Save the final MP4 and run final_media_qa.sh on it. Verify that ffprobe.json reports 1080x1920 at 30fps with H.264 video and AAC audio.
  • Run several AI agents on one folder at once

    Give several jobs to different agents in one workspace and watch each one work in its own pane.

    View prompt
    Using the Nami repo at mrdainami/nami, set up the desktop app on a Mac or Windows machine and give two separate jobs to two different agents in the same folder <target-folder>. Expected output: two panes running at the same time, each with its own result. Verify that both jobs report progress and that no file outside <target-folder> was read.
  • Catch conflicting agent plans before code is written

    Publish each agent's planned symbol changes and get a conflict warning before either agent edits files.

    View prompt
    In the <repo path> repository, register two agents with --no-worktree and publish intents that declare the same symbol:<target> scope with different operations. Expected output: a non-empty conflicts list in the second publish result with severity, explanation, and suggestion. Verify that the conflicts array is not empty before you report that the plans clash.
  • Install GPT with Taste hooks into Codex

    Add the recipe and scoped hook reminders to Codex for multi-turn work.

    View prompt
    Clone https://github.com/NB-Corp/gpt-with-taste into <target-folder>, run `node scripts/install.mjs --hooks` from that folder, and report the files written under the active CODEX_HOME. Verify that model_instructions_file now points to the main managed prompt file and that your model, provider and AGENTS.md settings were not changed.
  • Offload a research task to ChatGPT Pro from Codex

    Send a research question to ChatGPT Pro and get a summary back without spending Codex quota.

    View prompt
    Using the WebGPT repo (Nhahan/WebGPT), run `webgpt p` with the research question <topic>. Expect a written summary of the findings returned to Codex. Verify that the summary answers the question and says where its claims came from.
  • Build a feature from design to reviewed code

    Turn a feature idea into an approved design, a task plan, and code built one reviewed task at a time.

    View prompt
    Using the Superpowers skills from the obra/superpowers repo, take the feature described here: <feature description>. Run brainstorming, then writing-plans, then subagent-driven-development in the project at <project path>. Expected output: an approved design, a written plan, and code with a review after each task. Verify that every plan task lists exact file paths before any code is written.
  • Find where a photo without GPS was taken

    Give an agent a photo with no location data and get back camera position, heading and an evidence image.

    View prompt
    Use the geo-sleuth skill from the Oldcircle/geo-sleuth repo to find where <path to photo> was taken. Expect a camera position with an error radius, a heading, a satellite evidence image and a confidence grade. Verify that the conclusion names the commands run and the files they produced.
  • Check a package's version, license, and deps cheaply

    Get an npm package's version, license, engines, and dependencies in about 70 tokens.

    View prompt
    Use the only-cli/oc repo: run `oc npm pkg <package>` for the target package name. Expect a short block with version, license, engines, and dependencies. Verify that the package name in the output matches the target before using the data.
  • Make a short launch video with a coding agent

    Ask Codex or Claude Code for a short film, then watch it take shape in Studio.

    View prompt
    In the openfilm/openfilm repo, run the skill install, then ask the agent to make a 20-second launch video for <product>. Expect a film folder with a film.html that opens in Studio and renders to an MP4. Verify by running `openfilm look` on the film and confirming it reports no page errors, missing fonts or missing sound files.
  • Review a branch before merge and get a shareable HTML report

    Produce a bilingual REVIEW-REPORT.html with merge risk, call chains, and test gaps for a reviewer.

    View prompt
    Use the codexqa-code-reviewer skill in this repo to review the current branch against origin/main. Collect the CodexQA evidence pack (callers, blast radius, test edges) and write a bilingual REVIEW-REPORT.html. Verify that the report lists merge risk and the test gaps it found.
  • Catch an app crash and read live state at the throw

    Set exception traps, reproduce the crash, and read locals and frames without a GUI.

    View prompt
    Use the Debroid CLI on the Android app <package-name>. Set an uncaught exception trap, trigger the crash path <steps-to-reproduce>, and run `debroid poll --with-stacktrace` followed by `debroid pause-state`. Return the exception class, the frame where it was thrown, and the local values at that point as JSON. Verify that the exception class matches the crash in the bug report before proposing a fix.
  • Run a persistent task agent on your Mac

    Install Noodle, connect your AI account and give a bot a recurring task with its own workspace.

    View prompt
    Using the Noodle project at github.com/pdparchitect/noodle, guide a user through installing Noodle on macOS 26 and creating one bot for <task description>. Expected output: a bot named <bot name> with a backstory and one task started. Verify that the bot's workspace shows the files you attached.
  • Run a local Codex agent on a Strix Halo box

    Serve Qwen3.8-Flash-Next locally and point Codex at it through the Responses API.

    View prompt
    Using the repo peonist-ai/halogen-flash-server, configure Codex on <target machine> to use the local halogen server on port 8731, following docs/codex.md. Expected output: Codex completes a short test task against the local model and returns an answer. Verify that the server responds on port 8731 before running the test.
  • Audit past agent sessions without changing any config

    Scan existing agent session artifacts on a machine to list agents and surface findings.

    View prompt
    Use the repo perplexityai/numbat. Run `numbat agents` and then `numbat scan --agent <agent-name>` on this machine, and save the NDJSON output to a file. Report the number of findings and their rule_id values. Verify that the output contains no complete raw transcript and that secret values are redacted.
  • Edit an AI-written Markdown plan and send feedback in one batch

    Mark up a Markdown plan in the browser and send all edits and comments to your agent at once.

    View prompt
    Install the human-review skill from the petergyang/human-review repo, then open <path-to-markdown-file> with /human-review. After I click Send, confirm the agent applied every edit and comment to the Markdown source and report any change it could not make.
  • Remove AI tone from a work email without changing its commitments

    Rewrite an AI-drafted sales, support or HR message in a plain voice with every fact kept.

    View prompt
    Using the work-humanizer skill from the phuryn/work-humanizer repo, rewrite the AI-drafted email in <draft-file> in a plain human voice. Output the rewrite and the sentence-by-sentence fact audit. Verify that every price, date, offer, condition and caveat in the rewrite matches the original in meaning and strength.
  • Judge job postings against your resume

    Have your coding agent score matching postings against your resume and preferences.

    View prompt
    Using the pinloop-cli repo, search Pinloop for postings matching <target role and location>, then judge each match against my resume and preference files. Expected output: a ranked shortlist with a short reason for each score. Verify that each shortlisted posting links back to its original listing.
  • Run a coding agent on a real project from one desktop app

    Bring Codex, Claude Code, or Kimi into a project through ACP and review its plans and file changes.

    View prompt
    Using the Pinvou/pinvou-agent repo, start the desktop app with run-dev.sh, open Code mode, and attach the project at <project-path> to a Codex or Claude Code session over ACP. Expected output: a session bound to that folder that shows a plan and at least one file change. Verify that the session still appears after restarting the app.
  • Set up gates so agent code stays correct

    Generate contracts, gates, and ratchets for a repo so AI-written code is checked before commit.

    View prompt
    In the repo at <repo-path>, run `/gap-trap setup` after confirming gap-trap is installed with `npx skills add pliablepixels/gap-trap`. Report the list of contracts and gates the skill proposed and the commit it created. Verify that `git status` is clean and that no push happened.
  • Draw the real data model from a Prisma schema

    Turn a Prisma schema into a validated ERD that shows the tables that actually ship.

    View prompt
    In the repo <repo path>, import prisma/schema.prisma into docs/db.erd.json with vibeX, validate it, and render docs/db.erd.html. Report the table count and any validation errors. Verify that every foreign key in the schema appears as a relation in the ERD.
  • Scan a room from phone video and query it

    Upload a phone video and ask your AI assistant what objects are in the room and how big it is.

    View prompt
    In the openreality repo's MCP tools, upload <video path>, reconstruct it, then list the objects in the resulting scene and report the room size. Verify that the answer says whether dimensions are metric or relative, because the README states numbers are only called metres after calibration.
  • Turn a training config into a source-linked diagram

    Ask your assistant to map data, model, losses and validation as a clickable diagram.

    View prompt
    Using the MLView repo at <mlview-checkout>, install the mlview skill into <target-project> and ask the assistant to explain the training config in <target-project>. Expect a *.mlview.json file that opens as a diagram. Verify that the diagram lists unresolved items and that its cited files are reported as unchanged.
  • Ask a teammate's coding agent a question directly

    Message a specific teammate's open agent session and get the answer back in your terminal.

    View prompt
    In the reason-machines/reason-network repo, install Reason Network, run `reason-network who`, and send <teammate>/<session> the question "did the token format change?". Expected output: the session list followed by the teammate's reply after running `reason-network listen --as terminal`. Verify that the target session appears as idle or busy in the `who` output before sending.
  • Find where to change code without reading the repo

    Ask a question about a feature and get a ranked list of the code to touch.

    View prompt
    Use ripwire on the repo at <path>. Run ripwire . --for="<task description>" and list the top ranked symbols and files it returns. Verify that each named file exists in the repo before you open it.
  • Make a launch video from a plain-text brief

    Describe a launch video in chat and get an exported MP4 built by your own coding agent.

    View prompt
    Using the Remocn Studio project at <project folder>, describe a 30-second launch video for <product name> and let the studio's agent build it through its seven stages. Expect an exported MP4 and a docs folder containing script.md and review.md. Verify that review.md lists every note with evidence before you treat the video as done.
  • Learn AI engineering lesson by lesson in your agent

    Install the skills so a coding agent quizzes you, teaches one lesson at a time, and tracks progress.

    View prompt
    Using the repo rohitg00/ai-engineering-from-scratch, install the skills with npx skills add and run the start-learning skill for <target host>. Expected output: a LEARNING.md file with a phase-by-phase plan. Verify that LEARNING.md exists and names a starting phase.
  • Connect Codex to Ruflo's MCP server

    Give Codex Ruflo's MCP tools so it can use Ruflo's agent coordination from your project.

    View prompt
    Using the repo ruvnet/ruflo, set up the Ruflo MCP server for <target client> in the project at <project path>. Expected output: the MCP server entry with command npx and arguments ["-y", "ruflo@latest", "mcp", "start"]. Verify that the client lists Ruflo tools before reporting success.
  • Generate a project image from a text prompt

    Create an icon, mockup, or hero image with gpt-image-2 and save it to your repo.

    View prompt
    In the Sateezg/codex-bridge plugin setup, run codex-imagegen with the prompt "<prompt>" and save the result to <output-path>.png. Report the absolute path the wrapper prints. Verify that the file exists and opens as a PNG before reporting success.
  • Generate a matching set of game sprites and icons

    Have an agent produce sprites, icons, and props in one style, with transparent backgrounds, through Scenario.

    View prompt
    Using the scenario-labs/skills repo, generate a batch of sprites and icons from the list in <item-list-file>, keeping one art style and transparent backgrounds. Save the files to <output-folder> and report how many succeeded. Verify that each PNG opens and has an alpha channel.
  • Find what was agreed in past meetings by asking your agent

    Ask your agent a question and get the meeting, the decision, and a link back to the exact line.

    View prompt
    Using the seacen/meetcap repository and its agent skill, search my past meeting records for <topic or question> and report the meeting date, the agreed decision, and the transcript line it came from. Verify that the cited line actually contains the decision before you answer.
  • Resume a Codex engineering task from where you left off

    Link past Codex sessions to a task so you can pick up the work with its context.

    View prompt
    Using the repository sevensir888/codex-command-center, outline how to link existing Codex sessions to the task named <task name> for the project at <project path>. Output a numbered list of the linking steps. Verify that the task shows the linked sessions and the project's branch before resuming.
  • Score a prose draft for AI-writing tells

    Run a local 0-100 score on a .docx, .md or other prose file before you publish it.

    View prompt
    Using the sloptrim repo at <repo path>, run `python scripts/detect.py <draft file>` on <draft file> and report the 0-100 score, the band and the named patterns. Verify that the output is valid JSON and includes a score between 0 and 100.
  • Test a mobile app flow on a real phone with an agent

    An agent opens your app, follows a test script, and reports what the screen shows.

    View prompt
    Using the phone-harness repo at https://github.com/ShawnPana/phone-harness, open <app name> on the connected phone, follow the test script <script path>, and report each step with the screen text it read. Verify that the last screen matches the expected result in the script before reporting success.
  • Turn your illustration into an animated 2D avatar

    An agent builds a mesh avatar from your PNG, and you check it in the local editor.

    View prompt
    In the mesh-avatar-studio repository, follow docs/agent-guide.md to create an avatar from <path to your PNG>. Expect a project folder under projects/ that the editor can open. Verify by confirming that Pose test and Lip sync run in the preview.
  • Triage a source tree for reachable, unauthenticated sinks

    Let an agent scan your code and report sinks that are reachable without auth, with file and line references.

    View prompt
    Using the blitzstrike MCP server, call run_engagement with target <path to source tree> and max_files <number>. Return the findings grouped by chain, each with file and line references. Verify that every finding names a source and a sink that the tool traced, not only a matched pattern.
  • Install a Codex pet from two or more photos

    Turn your own photos into an installed Codex companion pet with one create command.

    View prompt
    Using the repo six-nut/PocketMen-with-you, run `pocketmen doctor`, then create a companion with `pocketmen create` from the two reference images at <photo-1> and <photo-2>, output to ./pocketmen-output with --install. Expected output: pet.json and spritesheet.webp in the output folder and an installed Codex pet. Verify the atlas is 1536x1872 with 8 columns and 9 rows.
  • Build a source-backed knowledge base from your documents

    Set up a separate Markdown workspace and file documents with the Codex backend after review.

    View prompt
    In the knowledge-base-kit repo, initialize a Codex workspace at <workspace-path>. Then open that workspace in Codex and use the local process_docs skill with the Codex backend on <document-path>, and show the proposed category and changed files before filing. Verify that the workspace passes `python kb.py check --backend codex`.
  • Get a cold second review from the other vendor's agent

    Have a fresh agent from the other vendor check your change before it lands.

    View prompt
    In the repo <repo-path>, use the peer-review skill from Sno Station Skills on the latest uncommitted change, preferring the other vendor's CLI in a fresh session. Output the findings list with each finding's trigger, impact and refutation attempt. Verify that the first line of the report states whether the review was same-vendor.
  • Hand off a half-finished task when one agent hits its limit

    Another agent picks up the same task from shared memory with context intact.

    View prompt
    In the sno-station repository, use `sno reach call` to hand the current task from the agent at <placeholder> to the other agent. Expected output: the receiving agent restates the task and the last completed step from shared memory. Verify it does not restart the task from the beginning.
  • Watch coding agents work live in a 3D kitchen

    Run Agenttrail Kitchen in your repo to see agent tasks, roles and completed work update as you code.

    View prompt
    In the repo <repo-path>, run `npx agenttrail-kitchen .` and confirm the browser opens at localhost:4780 or the next free port. Report the URL that is shown. Verify that the terminal stays running and that the view is in Live mode, not Example mode.
  • Stop an AI coding agent from reading your .env secrets

    Install the local guard so an agent is refused when it reaches for a .env file and every decision is logged.

    View prompt
    Install the SolonGate guard from https://github.com/solongate/agent-security by running ./scripts/shell/install.sh in a fresh terminal, then start <agent> in <project-path> and ask it to read the .env file. Expected output: the guard refuses the read and the agent reports the refusal. Verify by running `solongate audit` and confirming a deny entry for .env exists in ~/.solongate/local-logs/solongate-audit.jsonl.
  • Start a Next.js project from a product idea

    Turn a short product description into a configured Next.js foundation with product docs and checks.

    View prompt
    Read the repo soumatheusgomes/vibe-coding-toolkit at docs/prompts/11-next-project-bootstrap.md and execute the setup in this directory for the product described as <product description>. Report the generated files, the checks that passed, and the next MVP task. Verify that PRODUCT.md exists and that the validation step ran.
  • Watch every coding agent from one screen

    See each agent's status across all tabs and answer permission prompts without switching windows.

    View prompt
    Using the Tellurion repo at https://github.com/steventsvik/Tellurion, set up live status for Claude Code and Codex, then open Mission Control (⌃⌘M) with two agents running in <project-folder-1> and <project-folder-2>. Report the status shown on each card. Verify that a waiting agent appears first in the list.
  • Get an SMS verification code for an agent signup

    Let an agent order a number, read the SMS code and close the activation in one run.

    View prompt
    Using the sv-number/mcp-server MCP tools, order a number for service <service code> in country <country id>, then call wait_for_code on its activationId. Expected output: the verification code as returned by wait_for_code, followed by a finish_activation result. Verify that the code is parsed text and not a raw SMS body before you use it.
  • Build a playable 2D web game from one prompt

    Install Vibe Game, describe a game in plain language, and get a playable 2D browser game.

    View prompt
    Using the VibeGame repo at https://github.com/tettethu/VibeGame, set it up with ./setup.sh, create a project in my-game with vibegame init, and start it with vibegame start using the prompt "<game idea>". The expected output is a playable 2D web game in my-game, launched with vibegame run --port auto. Verify that the run command prints a local address and the game loads in a browser.
  • Build an AI IT department with Paperclip

    Install Paperclip, hire a CEO agent, and bring in specialist agents for IT work.

    View prompt
    Using the repo theNetworkChuck/paperclip-guide, follow chapters 2 through 5 to set up a Paperclip company on <target machine>. Report the list of hired agents with their harness and manager. Verify that every hire shows an approval by the board before it became active.
  • Connect Claude Code once, then switch upstreams in the gateway

    Point Claude Code or Codex at a local gateway once, then change providers without editing the client again.

    View prompt
    Using the repo ThinkWatchProject/ThinkWatch-Lite, connect <client name, e.g. Claude Code> to the local gateway, add the upstream <upstream name> in the gateway, and switch to it without editing the client's configuration again. Expected output: a test request from the client that completes through the new upstream. Verify that the client's original config file exists as a backup.
  • Check an AI-assisted paper before you sign it

    Run paper-author-pass to get questions only you can answer, a claim-evidence map, and verified references.

    View prompt
    Use the absent-author repo's paper-author-pass skill on <paper folder> in audit mode. Ask me the questions only the author can answer, then produce a claim-evidence map and a change log. Verify that every reference the skill marks as verified can be found by you in the bibliography.
  • Share one memory of decisions across Claude Code and Codex

    Let Claude Code and Codex read and write the same store so past decisions carry into new sessions.

    View prompt
    Use the agent-memory repo at <store path> to recall memories about <topic> with `mem recall` and `mem context`. Return the file paths and one-line abstracts that matched. Verify that the same paths come back when the query is run from Claude Code and from Codex.
  • Check a live site's SEO foundation in one run

    Give the agent a URL and get a crawler's-eye pass/fail report on 26 structural SEO checks.

    View prompt
    Using the tigerless-labs/seo-ops skill, check the SEO foundation of <target-url> as a live site. Return the pass/fail report for the 26 checks with evidence for each red item. Verify that the report lists every check as pass or fail and does not guess at checks it could not run.
  • Review AI-written changes and run a repair plan in an agent

    Mark up uncommitted AI changes in Reslop, save the review as a plan, then let a local agent work through it.

    View prompt
    In the reslop repository at <repo-path>, read the newest file in .plan/ with status editing and work through its unchecked items. Report which checkboxes you marked [x] and which items remain. Verify by confirming the frontmatter status is set to partial or done and no unchecked items were skipped silently.
  • Audit a whole repo for safe simplification candidates

    Get a ranked list of simplification candidates with proof records, counterexamples and blind spots, with no file changes.

    View prompt
    Use $simplify-codebase on the repository at <path to repo>. Run a broad read-only Survey and do not modify any files. Expected output: ranked proof records with coverage, counterexamples, open questions and the next evidence needed. Verify that every candidate names its consumers and its deletion boundary.
  • Give Codex a durable, size-capped memory of your repo

    Install the memory pack so Codex keeps a one-page project card and handoff per repo.

    View prompt
    In the ai-memory-skillpack repo, follow INSTALL.md to install the ai-project-memory skill for Codex on this machine, then enable the repo at <repo-path>. Report the install receipt location and the list of files created under docs/ai/ in <repo-path>. Verify that sha256sum -c SHA256SUMS passed before any install step ran.
  • Let Codex or Claude Code edit an Unreal project via MCP

    Connect an external coding agent to a running Unreal Editor so it can call engine tools.

    View prompt
    Using the UE Box MCP server in the ueboxai/uebox repo, count the light actors in the level <level name> and report the count. Then list the tool calls used and confirm the editor project is still open with no unexpected changes.
  • Keep CI and dependency PRs green while you work

    A repo-keeper agent watches CI and dependency PRs, fixes what breaks, and asks before anything ships.

    View prompt
    Using the Overtime repo at ukanwat/overtime, set up an agent named repo-keeper briefed to watch CI and dependency PRs for <target repo>. Expected output: a short list of failing checks and open dependency PRs, with a fix or a question for each. Verify that no merge happens without an approval question being answered.
  • Hand off a code fix and get a pull request back

    Send a bug or feature request from the web app and receive a pull request from an isolated agent workspace.

    View prompt
    Using the UseAgent hosted app, start a thread that asks the agent to fix <bug description> in the GitHub repository <owner/repo>, then open the pull request it creates. Expected output: a pull request URL for the change. Verify that the pull request diff touches only the files related to <bug description>.
  • Caption a video locally with WhisperX at no cost

    Transcribe a video offline with WhisperX and get a transcript.json for captioning.

    View prompt
    In the Open Edit repo at veedstudio/open-edit, use the @veedstudio/openedit-cli commands to transcribe <video path> locally with the whisperx provider. Expect a transcript.json under runs/ for that video. Verify that the file contains word-level timestamps before you continue.
  • Run several coding agents on one repo at once

    Start multiple agents on separate git worktrees so they can edit the same project without conflicts.

    View prompt
    Using the vicoa-ai/vicoa repo, set up three coding sessions on <target-repo>, each with a different task and agent (Claude Code, Codex, and Cursor). Confirm that each session runs on its own git worktree and branch and that all three appear in the Vicoa session list. Report the session names and their status.
  • Build an explorable 3D scene from a one-line idea

    Turn a short creative prompt into a Three.js scene an agent builds and checks on screen.

    View prompt
    Using the 3dviz-pro-max skill in the repository at <repo-path>, build a small fantasy village I can explore in Three.js. Choose a distinctive art direction, add a few moving creatures, and inspect the result. Report what you built and what you observed in the rendered frames.
  • Make a narrated explainer video from one topic

    Give a coding agent a topic and get a narrated MP4 with drawn scenes and subtitles.

    View prompt
    Use the explainroo repo at <repo folder> to make a short explainer video about <topic>. Read AGENTS.md and follow its steps so the agent writes script.md and scenes.js and renders an MP4. Expected output: one MP4 under videos/. Verify that the voice reads the script without wrong words before you report the file path.
  • Turn a topic into a narrated explainer video

    Give an agent a topic and get a 1280x720 MP4 with voiceover, subtitles and chapter progress.

    View prompt
    Using the anything2explainer skill in this repo, make a narrated explainer video about <topic>, in <language> and about <length> long. Stop at the four checkpoints for my approval. Verify that the final output is a 1280x720 H.264 MP4 with voiceover and subtitles, and that the research doc lists a URL for every number or claim.
  • Run several coding agents side by side in one app

    Manage Claude Code, Codex and other agents as sessions in one tree, with live status.

    View prompt
    Using the VelaTerm project at https://github.com/vlinx-io/VelaTerm, install the desktop app from velaterm.com/download and start one Claude Code session and one Codex session in a project named <project-name>. Expected output: both sessions listed under that project in the session tree with a live status. Verify that both sessions keep running in the background after you switch views.
  • Unblock a pipeline stage stalled by a stale marker

    Run a blocked stage by hand, validate it, publish it, and continue from the cursor.

    View prompt
    Using the forward-implementation-first skill in <pipeline-repo>, run the stage blocked only by a stale receipt for <stage-name> manually, validate its output against its consumer, and publish it. Report the stage output path and the cursor position after the run. Verify that no stages outside the smallest affected dependency cone were invalidated.
  • Draw a pixel sprite live in your open Aseprite

    Have your coding agent draw a sprite in the Aseprite window you already have open.

    View prompt
    Using the MCP server from with-pebbly/aseprite-ai-artist, draw a <subject, for example a 32x32 knight> in the Aseprite window that is already open. Expected output: the sprite appears in the open Aseprite document, and the agent ends with a short list of the compromises it made. Before drawing, verify that `doctor` reports all checks passing and that Aseprite is attached.
  • Install Oh My CPA by handing the setup to an agent

    A coding agent inspects the machine, picks an install method and sets up the console.

    View prompt
    Install Oh My CPA on this machine by following https://raw.githubusercontent.com/WizisCool/oh-my-cpa/master/docs/install-for-agents.md. Report which install method you chose and why. Verify that the console answers at http://127.0.0.1:8080/omc/ before you finish.
  • Plan a coding task in ChatGPT before Codex edits

    Use your ChatGPT web plan for reasoning while Codex keeps all the editing.

    View prompt
    Install the repo XiaoDuoYa/codex-with-chatgpt, run corepack pnpm install and corepack pnpm build, then run c2c setup and pair it with ChatGPT. Use the Codex Skill to have ChatGPT plan <task>, and report the final checklist to confirm the file read test passed.
  • Find Jev projects that match your coding agent

    Filter the list by coding agent tag to shortlist Jev tools for Claude Code or Codex.

    View prompt
    Using the repo yibie/awesome-jev, list every entry under the Claude Code tag in its README with its name and link. Expected output: a list of 18 entries with GitHub links. Verify that the count matches the 18 shown in the Find by coding agent section.
  • Map a request path through a repo as an interactive story

    Generate an evidence-cited HTML walkthrough of how one request moves through a codebase.

    View prompt
    Using the fireworks-open-eli5 Skill, explain how one request moves through <target repo path>, citing real files for each step. Render it to <output.html> with the render script and confirm the file validates with the validate script. Report the file path and any claim that lacks a source locator.
  • Score a website funnel and get prioritized fixes

    Get a weighted 0-100 funnel audit with a ranked list of fixes in one agent session.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the audit module on <target URL> and return the weighted 0-100 score with prioritized fixes. Verify that the report includes a what-I-couldn't-determine section and that the score is labeled as a heuristic.
  • Audit agent tools for poisoning and excess privilege

    Review an agent's tool definitions for poisoning, excess privilege, and deployment blast radius before rollout.

    View prompt
    Using the agent-surface-audit skill from the zero-lab-ai/skills repo, review the tool definitions for <agent-name> that I am authorized to assess. Return findings for poisoning, excess privilege, unsafe parameters, and deployment blast radius, each with the tool definition it cites. Verify that every finding quotes a definition I provided.
  • Rebuild a feature you saw, in your own project

    Have your agent study how another app does a feature, show the evidence, then build and test your own version.

    View prompt
    Use REA to understand how <feature> works in <app>, show me the evidence, then build a similar feature for my project at <project path> and test it. Mark anything you are guessing, and verify the result matches the behavior you observed.
  • Create a standalone SVG illustration for a landing page

    Produce a lone isometric SVG file with embedded styles for a web page or article.

    View prompt
    Using the skill in wheresryan22/anatomy, generate a dark-theme isometric SVG illustrating <concept> for <landing page>. Expected output: one .svg file with styles embedded and one PNG preview. Verify that the SVG still reads when opened on its own, without any WebGL layer.
  • Screen a compound list for drug-like properties

    Use RDKit-based skills to predict molecular properties and flag ADMET concerns in a candidate set.

    View prompt
    Using the scientific-agent-skills repo and its RDKit cheminformatics skill, compute molecular properties and ADMET flags for the SMILES in <file of SMILES strings>. Return a ranked table with the computed values and the code used. Verify that every input structure parses and that no row is silently dropped.
  • Match diagrams to your site's brand

    Onboard the skill to your site so every new diagram uses your palette and fonts.

    View prompt
    Using the diagram-design skill from cathrynlavery/diagram-design, onboard to <site URL> so it pulls the site's palette and fonts. Then draw a quadrant diagram of <topic> and write one self-contained .html file. Verify that the accent color and fonts match the site.
  • Answer architecture questions from the graph

    Ask plain-language questions and get scoped answers instead of grepping through files.

    View prompt
    Using the Graphify-Labs/graphify repo, run `graphify explain "<concept>"` on the target project at <project-path> and list its connections. Expected output is the node's source location, community, and connections with their EXTRACTED or INFERRED tags; verify that any claim you make from an INFERRED edge is labeled as inferred.
  • Turn a GitHub pull request into an explainer video

    Generate a changelog, feature reveal, or fix explainer video from a PR using the pr-to-video skill.

    View prompt
    Using the hyperframes repo at heygen-com/hyperframes, run the pr-to-video skill on <owner/repo#N> to produce a feature-reveal explainer MP4 read through the gh CLI. Verify that every claim in the video matches the pull request title, description, or diff.
  • Map how a website's front end works

    Let your agent watch a site in a browser and explain how its scripts and network requests drive a feature.

    View prompt
    Use REA to observe <website url> in a browser and summarize its page structure, scripts and network requests. Explain how <feature> works and verify every claim against an observed request.
  • Run Codex bash commands on Windows through Fauxnix

    Add Fauxnix as an MCP server in Codex so bash-style steps run on a Windows machine.

    View prompt
    In the 20000419/fauxnix repo context, call the fauxnix `bash` MCP tool with `find . -name '*.ts' | wc -l` in <project-dir>. Expect a single number as output with bash-style exit code 0, then confirm `fauxnix doctor` passes.
  • Build a Jev pull request grader in Codex

    Install the skill in Codex to build a Score-based check that grades pull requests.

    View prompt
    In this repo, use the building-with-typesafe-jev skill to write a script that sends a pull request diff and its spec to Jev as a Score question on a described scale, then flags results below a threshold. Show the question text and the threshold. Verify the script handles the Score result as a value on the scale you defined.
  • Scan an x86-64 ELF for heap and format string bugs

    Flag allocation overflows, use-after-free, and unsafe printf-family format arguments.

    View prompt
    Using the Ablation repo at ~/ablation, run the Heap Vulnerability Scanner and Format String Scanner on <binary path>, which is an x86-64 ELF. Output a grouped list of findings with function name, address, and finding type. Verify that each finding names the specific call site and that heuristic results are labeled as heuristics.
  • Have an AI agent build and open a 3D animation

    Paste one prompt into a coding agent and get an installed, rendered 3D animation back.

    View prompt
    Follow https://manimgx.academa.ai/llms.txt, install ManimGX, and make a 3D animation of <topic>. Expected output: a rendered MP4 that you open for the user. Verify that the video shows the <topic> scene from start to end.
  • Publish agent-written specs to your team via Git

    Promote the specs an agent wrote into the shared folder so teammates receive the same project knowledge.

    View prompt
    Using the Operator Memory repo (https://github.com/aerovato/operator-memory), ask the agent in <project-path> to write a spec for <feature-name> and promote it to Shared. Expected output: a document under .operator-shared/ describing that feature. Verify the file is present and tracked by Git before you push.
  • Preview, then install ECC into Claude Code and Codex together

    Use the multi-harness wizard to set up two coding agents in one reviewed flow.

    View prompt
    Using the ECC repo at github.com/affaan-m/ECC, preview a guided install for Claude Code and Codex with `npx [email protected] install --guided` and report the install channel and destination for each harness in <project-path>. Verify that the preview shows no writes before you confirm.
  • Set up an OpenAI-compatible provider profile for Codex CLI

    Add a provider profile, let the app check it with a real request, and keep native config in sync.

    View prompt
    Using the Agent Launcher repo at https://github.com/agent-launch/agent-launcher, create an OpenAI-compatible provider profile named <profile-name> for Codex CLI with endpoint <endpoint-url> and model <model-name>, then run its connectivity check. Expected output: a pass or fail result for endpoint, credentials, model, network, and account status. Verify that the masked native config preview shows no plaintext key.
  • Invite a new agent to the group from a chat

    Let one connected agent create a short invitation link for another agent after you confirm the code.

    View prompt
    Using the AgentPeerChat CLI, create a 10-minute invitation for <new-agent-name> and return only the link and the pairing ID. Verify that the invitation is open, and confirm the invitee's verification code with me before approving.
  • Find the communities where your users already talk

    Map the named places your target users gather, with links, and launch examples.

    View prompt
    Run research-the-market in the gtm-cofounder skills for <product name> and <target user role>. Expected output: docs/gtm-cofounder/market-research.md with linked communities ranked by fit and the rules each room has for self-promotion. Verify that every finding has a link and is tagged [researched], not treated as a real user statement.
  • Read a logged-in dashboard page step by step

    Let an agent open, read and screenshot a signed-in page one command at a time.

    View prompt
    Using the Chrome Relay repo at aindeev/agent-chrome-relay, open <URL> with chrome-relay open, read it with chrome-relay snapshot --text, and report the value of <element or text>. Expected output: the text found on the page plus the current URL. Verify the URL matches <URL> before reporting.
  • Record a 28 second film of a machine for social feeds

    Generate a machine and record a numbered-beat film with music, sized for a feed post.

    View prompt
    Using the repo AirsupHQ/machine-skill, build a watch movement page for <machine description> and record a 1080 x 1350 film with `scripts/record.mjs`. The expected output is an MP4 in out/ of about 28 seconds. Verify that `scripts/pinkscan.mjs` reports no pink frames and that the command exits zero.
  • Make a set of brand illustrations for your website

    Generate a hero image and matching spot art in one chosen style, as transparent PNGs at any size.

    View prompt
    Using the anidoodle repo, draw a hero illustration for <page name> in the <style name> style at 1600×900, plus three spot illustrations for its features. Return transparent PNG files and confirm all four share the same style.
  • Keep a coding session running during provider outages

    Set a fallback model list so FCC moves to your next model when a provider fails.

    View prompt
    In the repo Alishahryar1/free-claude-code, configure two providers and an ordered Fallback Models list in Model Config, then start `fcc-codex`. Expected output: a coding turn completes even when the first model is unavailable. Verify by checking the server log for the fallback model name.
  • Delegate a terminal task to a chosen agent

    Send a command-line job to a specific agent backend and collect normalized results.

    View prompt
    Use the LongHorizon-Harness repo at <repo path> to run a terminal task for <goal> with the --agent opencode option. Expected output: the normalized result file or summary for <goal>. Verify that the tests or commands named in the goal were actually executed and passed.
  • Give Codex CLI control of desktop apps on macOS or Linux

    Register LCU with Codex CLI so the agent can see windows, click, type, and capture screenshots.

    View prompt
    Using the amontlabs/lcu repo, set up LCU for Codex CLI on this machine by following docs/INSTALLATION.md. Ask me to approve the desktop app named <app name>, then have the agent list its windows and take one screenshot. Report the setup result and confirm the screenshot was taken.
  • Map a Windows PE binary's protections and key functions

    Get architecture, protections, and a function list for a PE file in one agent session.

    View prompt
    Using the seep MCP tools in the Seep Reverse Lab workspace, triage <path-to-pe-file> with seep_r2_info, seep_r2_functions, and seep_r2_decompile in summary mode. Expected output: architecture, bitness, protection flags, and the top functions by interest. Verify that the protection flags match the seep_r2_info output.
  • Resume a project in a new agent or chat without starting over

    Use the committed index so a new agent, host, or conversation picks up the system context in one read.

    View prompt
    Using only the AOCI index in <project-path>, describe the system, report your mastery of each area as a percentage, and say whether you can take over development. List any area below 80 percent and the source files you would read first.
  • Improve an existing app screen against category leaders

    Give an agent a screenshot, code, or Copy Screen ID and have it rebuild the screen to a higher bar.

    View prompt
    Using the appllama/appllama-skills repo, take the screen at <screenshot, code path, or Copy Screen ID> and improve it against the top-grossing apps in its category through the Appllama MCP. Output the revised screen code and a list of changed patterns, and verify the result in the simulator before reporting it.
  • Give a coding agent a fast local browser for page tasks

    Let Claude Code, Codex or Cursor handle planning while a local engine handles clicks, selects and scrolls.

    View prompt
    Using the fast-browser-use skill in <repo path>, complete the browser task <task description> on <start URL>. Return the step-by-step execution trace and the final page URL and title. Verify the final URL matches <expected URL> before marking the task done.
  • Point Codex CLI at a Kaggle-hosted open model

    Use the public endpoint from a Kaggle TPU session as the backend for Codex CLI.

    View prompt
    In the ARahim3/kaggle-tpu-lab repo, read the Codex CLI lines in the <model> folder README, run that model's notebook on Kaggle, and configure Codex CLI with the printed URL and API key. Expected output: a Codex CLI answer to a test question served from the TPU. Verify the request reaches the Kaggle endpoint, not a default provider.
  • Answer agent prompts from your phone

    See which agents are waiting for input and reply to them from a phone.

    View prompt
    In the arronKler/pairfob repo, read the section 'What you can do from the phone' in README.md. Summarize how the Needs you strip and the Auto, Control, Terminal and Chat modes work, and name the one mode to use for a full-screen TUI such as vim. Verify your answer against the README text.
  • Bulk export a channel's transcripts for a search index

    Collect video IDs from a channel or playlist and export transcripts in retrieval-sized chunks.

    View prompt
    Using the youtube-skills repo, list all video IDs for <channel or playlist>, then submit one bulk transcript job with segment=1000 and format=json. Report the job ID, the number of videos accepted and the credits charged, and confirm that each chunk has a start timestamp.
  • Redraw existing Mermaid or draw.io diagrams in See Code style

    Convert old diagram files into See Code diagrams, one per file, with an index page to browse them.

    View prompt
    Use the SeeCode skill from the Aryanutkarsh/SeeCode repo to redraw every diagram in <path to source file> as SeeCode diagrams in a folder. Expected output: one HTML file per diagram plus index.html. Verify that the count of diagrams matches the count of diagram blocks in the source and that the report lists anything dropped.
  • Find stuck or looping agents before they waste time

    Spot agents that are slow, quiet, failing or repeating work using the badges on each tile.

    View prompt
    In the repo Atoll92/agent-standup, open the live call for my running Claude Code or Codex session. Report each agent that shows a ⏳, 💤, ✗ or ♻ badge and the calls listed when you hover over that badge. Verify each badge against the session's real tool calls before you act on it.
  • Find what breaks before changing a function

    Ask an agent which files and tests a change to one function can affect.

    View prompt
    In the <repo> project, use the axiomcode impact tool on <function> and list the files that must change, the entry points that reach it and the test files that reach it. Expect a numbered list with file and line for each item. Verify that the output ends with a verified line showing the edges were looked up again.
  • Stop an agent from closing unfinished tasks

    Make todo close refuse until criteria are checked, evidence is recorded, and the gate is clean.

    View prompt
    In the procoder-enabled repository at <repo-path>, close the todo item <item-id> only after its acceptance criteria are checked and the gate is clean. Report the refusal text if the close is refused. Verify that the item shows as closed only when the gate result is clean.
  • Let an MCP agent edit the same timeline you see

    Connect a coding agent over local MCP so it updates Editor timelines, overlays, and captions in your open project.

    View prompt
    Using the BeatDesign MCP tools in <repo path>, open the latest project, add the clips in <clip folder> to a timeline, place the logo overlay at <logo file>, and style the SRT captions. Confirm the changes appear in the browser Editor and report what changed.
  • Make a second style edition of a release video

    Re-render an existing release video in the glass keynote style without touching the first edition.

    View prompt
    Using the motion-video skill from bestagentkits/motion-video-skill, create a glass keynote edition of <release name> in a new project directory named <new-project-name>, leaving the existing comic edition untouched. Expected output is a rendered 1920×1080 30 fps video in the new directory. Verify that the original project directory has no changed files.
  • Let an approved MCP agent revise an open CAD project

    Connect Codex to PartMode so the agent works on your open project after you approve it in the browser.

    View prompt
    Using the PartMode MCP server configured for this repository, call cad_capabilities, then inspect the open project at <project-name> and create a detached preview of the change <change-description>. Report the operations you proposed and the document revision they target, and verify that no commit happens until the person approves it in the browser.
  • Review agent screenshots, previews and changes on your phone

    Open what an agent built, including dev-server pages and working changes, without going back to your desk.

    View prompt
    Using the BotBus app paired to <computer name>, list the artifacts and dev-server previews attached to task <task ID>. Confirm that each item opens on the phone and report anything that does not load.
  • Fill fields in a desktop app that has no API

    Set field values and type text into a Mac app window using numbered elements from a read.

    View prompt
    Using the macos-harness repo at https://github.com/browser-use/macos-harness, read the window of <app name> with `macos-harness get_app_state --app <app name>` and set each field listed in <values file> with `macos-harness set_value`. Verify by reading the window again and reporting every field that does not match its expected value.
  • Lint an existing SVG and read findings as JSON

    Run svg-lint on a diagram and get each violation with its check id and repair line.

    View prompt
    In the svg-diagram repo, run node tools/svg-lint/bin/svg-lint.mjs <path/to/file.svg> --json and list each finding's check id and repair line. Confirm the file reports 0 errors and 0 warnings before calling it clean.
  • Turn a reference Short into a grounded production plan

    Paste a Short you like and get concepts, a tool path, and a cost estimate before generation starts.

    View prompt
    In the OpenMontage repo at <repo-path>, analyze the reference video <video-url-or-path> and produce 2-3 concepts about <topic>, each with a cost estimate at 60 seconds. Verify that each concept lists the tools available in the current environment.
  • Debug an app error from combined native and JS logs

    Read iOS, Android, and Metro logs together and send a failing stack trace to Codex.

    View prompt
    Using the callstackincubator/codex-mobile-dev-plugin Mobile Dev plugin, read the logs for the foreground app on <device name> and find the error matching <error text>. Expected output: a summary of the error with its stack trace and a proposed fix in <project path>. Verify the stack trace quoted matches the log entry before editing any file.
  • Get a numbered quest route drawn on your world map

    Ask the agent for a route and follow the navigator arrow from stop to stop.

    View prompt
    In the wow-ai repo, after the bridge is running, ask the chat agent to draw a numbered route for <list of quests or zones> on the world map. Expected output: numbered stops and marks visible on the world map with a navigator arrow. Verify the route appears on the map before telling the user it is ready.
  • Design a custom workflow with fail and rollback paths

    Edit the FSM canvas to add nodes, guards, and fail or rollback edges.

    View prompt
    Using the Grasp repo (cocofhu/grasp), create a workflow in <Grasp workspace> on the FSM canvas that adds a rollback edge from the test node to the implement node. Verify the rollback edge is saved and report the node list and edge list.
  • Fork a run at one step and compare models

    Keep the first steps of a recorded run fixed, switch to another model from a chosen checkpoint, and compare results.

    View prompt
    Use the OrcaReplay repo (Continuum-AI-Corp/OrcaReplay) to fork the recorded run `last` at checkpoint 4 onto the models <model-a> and <model-b> using `orca compare last --from 4 --models <model-a>,<model-b>`. Report one comparison table with the outcome for each model. Verify that turns before checkpoint 4 are identical across both forks.
  • Give each coding task its own Git worktree and branch

    Run parallel agent tasks in separate worktrees so their changes never collide.

    View prompt
    In the diri repo at github.com/cristicretu/diri, confirm that each agent session for <task-list> has its own Git worktree and branch. Output a table of session, worktree path, and branch name, and verify that no two sessions share a branch.
  • Fill a long web form in one call and submit it

    An agent sets every field of a multi-step web form and clicks submit, with typed errors on failure.

    View prompt
    Using the axuse MCP server, open <form URL> and fill the form with these values: <values as JSON>. Use one fill action, then read the accessibility snapshot to confirm each field holds the intended value before submitting. Report any field that returns an error code.
  • Run a high-stakes change in full mode with extra checks

    Use the skill's full mode for risky or hard-to-reverse work with more verification.

    View prompt
    Using the Da7-Tech/SureForge skill in full mode, plan and carry out <change description> in <repository path>. Expected output: a gate result for each phase, the tier used, and a coverage ledger listing what was verified and what was not. Verify that the agent states plainly if no independent reviewer was available.
  • Pick the next window for a task by token use and quota

    See what each AI window spent and which window or model should take the next task.

    View prompt
    Using the Squadra repo at https://github.com/dagoSte/squadra, rank the AI windows in the squad at <project path> for task <task ID>. Expected output: the output of `squadra balance --task` with the figures each suggestion rests on. Verify that the ranking lists every registered window and that no window is assigned automatically.
  • Run a Codex candidate on one Terminal-Bench task

    Score a candidate agent on a single Terminal-Bench 2.0 task and read the per-task result.

    View prompt
    In the rsi_eval repo, set target.model and the Codex login directory in examples/evaluate.json for <model-name>, then run `rsi-eval run --config examples/evaluate.json --output runs/<new-output-dir>`. Report status and per-task reward from result.json. Verify that the output directory did not exist before the run.
  • Try several fixes at once in isolated cloud branches

    Run separate cloud agent threads, each in its own sandbox and Git branch, and compare results.

    View prompt
    In the cloudroom-gui repo's Cloudroom app, start two Cloud threads for <repository and task>, each with a different approach. Expected output: two separate Git branches, one per thread. Verify that each branch has its own sandbox changes before choosing one.
  • Review agent changes per file and open a PR

    Check each diff the agent made, then commit, push, and open a PR or MR from the browser.

    View prompt
    Using the agentbox repo at github.com/devilcoolyue/agentbox, run a workspace on <server-host> against the repository <repo-url>. Ask the agent to make the change <task>, then list every changed file and its diff summary before any commit. Verify that nothing is pushed until the diffs are approved.
  • Sync a provider's models and set context limits

    Refresh the model list after a provider changes its models and set the default and context length for each.

    View prompt
    Using the uni-switch project at github.com/dieqiyun/uni-switch, sync the model list for the provider <provider-name> and report which models were removed and which default model was chosen. Expected output: a list of enabled models and the new default. Verify that the default model is still present in the synced list.
  • Keep AI coding sessions running through SSH drops

    Start Claude Code or Codex on a remote host and reconnect later without losing the session.

    View prompt
    On the remote host <host>, install Session Kit from https://github.com/dob323/session-kit using the latest release artifact, run `session-kit services enable`, then start a session with `sp new claude`. Verify with `kit` that the session is listed and still running after the SSH connection is closed and reopened.
  • Draft a standup from what you actually did

    Turn the day's written record into a standup update grounded in what was on screen.

    View prompt
    In the dragthelake/ambient-context repo, use the standup skill to draft a standup for <placeholder date> from the Summaries file for that day. Expected output: three short sections titled Yesterday, Today and Blockers. Verify that each item traces to a block in Days/<placeholder date>/ before it is spoken.
  • Hand a coding task to a built-in coding agent

    Use Wu's agent workspace with Claude Code or Codex to draft changes inside your project.

    View prompt
    In the dstrml/wu repo context, open <project-path> in Wu and use the built-in Claude Code or Codex agent to make this change: <task>. Expected output: a proposed edit to <file-path>. Verify by reading every changed line before saving.
  • Block agent changes that fail an independent review

    Send each agent's finished work to a separate reviewer agent before it is delivered.

    View prompt
    In the dualface/kander repo, read docs/review-disposition.md and then review the task card <TASK-ID> on the board. Report whether the review stage found must-fix issues and whether the completion gate passed. Verify that the reviewer result is recorded on the card before you call the task done.
  • Locate the tests that cover a specific behavior

    Ask which tests exercise a behavior so an agent can run or extend the right suite.

    View prompt
    In the repository at <target path>, run `jg` with the question "Which tests cover <behavior>?" and list each returned test file with its line references. Verify that each listed file exists and contains the test before you run the suite.
  • Check a generated part for manufacturing problems

    Run design for manufacturing checks on a model before you send it to fabrication.

    View prompt
    Using the text-to-cad plugin from https://github.com/earthtojake/text-to-cad, run design for manufacturing checks on <model file path> and list every issue with its location. Return the report and confirm whether a second check passes after fixes.
  • Build a narrated comic with Taiwanese Mandarin voice

    Turn a brief into a narrated comic video with Yating Taiwanese Mandarin narration.

    View prompt
    In the reelmimic repo, confirm YATING_KEY is set in the secrets file and run `cd app && npm run doctor`. Then submit a narrated comic brief for <topic> with <reference video path>, approve the plan, and wait for the final review. Expected output: a narrated comic video in the project folder. Verify the narration audio plays in the final file before reporting success.
  • Steer an agent mid-task with queued follow-ups

    Send follow-up instructions while an agent is still working, without starting over.

    View prompt
    Using the waku app at <Waku install location>, start a session on the project at <project path> with the task <task description>, then send one follow-up message while the agent is running. Expected output: a transcript showing the queued or steered message inside the same session. Verify that the session ID did not change.
  • Rig a character in Rigify and export a Unity walk cycle

    Rig a character with Rigify, add a walk animation and export the result to Unity.

    View prompt
    Using the blender-skills repo, rig <character model> with Rigify, add a looping walk cycle and export it for Unity. Expect a rigged .blend or exported file and the name of the walk action. Verify that the walk action loops and that the exported skeleton keeps the rig's bone names.
  • Run a multi-harness agent team on a code review

    Start a team template so a lead harness coordinates named member harnesses on one goal.

    View prompt
    Using the repo emo-xiaoyu/harness-mix, start the built-in 代码评审 agent team template for the project at <project path> with the goal <review goal>. Report each member harness, its assigned role, and the task state, and confirm that every member is using its own native session.
  • Find the commands an agent kept retrying and failing

    Use the Errors tab to see which failing command ran most often in a row and jump to it in the replay.

    View prompt
    Using the agentplay repo at https://github.com/Entelligence-AI/agentplay, run `uvx agentplay` and open the session <session name or id>. Open the Errors tab, list the top three error classes with their longest repeated failing command, and state the step where each run began. Verify that each count matches the error rows shown in the Errors tab.
  • Share one native build across agents on JS-only branches

    Cache native builds by fingerprint so many agents reuse one build and environment switches skip native rebuilds.

    View prompt
    Using the simfleet repo (entropyconquers/simfleet), set up the Expo build cache in <path-to-app> and run `simfleet native plan` to inspect the fingerprint. Expected output: a plan that lists the native inputs and whether a cached build exists. Verify that changing only a JavaScript file leaves the native fingerprint unchanged.
  • Have Opus plan and a native worker build, then review

    Split one assignment so Opus plans and reviews while a configured worker implements it.

    View prompt
    Use the codex-on-crack package in <project folder> to have Opus plan <feature name> and a configured native worker implement it, then return the result to Codex for review. Expected output: a plan, the worker's changes, and a review note from the lead. Verify that the review cites the worker results and host-tool evidence.
  • Compare two agent runs event by event

    Load two sessions and see recorded metric differences and aligned tool calls.

    View prompt
    Using the TraceCrate repo at <repo path>, start the dev server and load the two authorized session files <baseline file> and <changed file>. Expected output: the Compare view with recorded metric differences shown as B minus A and an event-by-event list. Verify that the comparison is described as descriptive, since repeated tool names can align ambiguously and this is not a controlled benchmark.
  • Chat with a coding agent in native phone chat

    Use a phone-native chat interface for Codex, Claude Code or another supported CLI on a remote host.

    View prompt
    Using the farlume/termish README, list the setup needed to use the Agents entry with <agent name> on host <host>. Expected output: a short list of prerequisites and the steps to start a chat. Verify that the list states that the remote host needs the agent's own login or a supported API provider configuration.
  • Rebuild a feature demo from screenshots, no recording

    Turn a set of app screenshots into a feature demo where the interface is rebuilt in HTML and the camera flies into it.

    View prompt
    Using the onetake skill in the feitangyuan/onetake repo, build a feature demo of <feature name> from the screenshots in <screenshot folder>, with no screen recording. Output a video file of the demo. Verify that the rebuilt interface matches the screenshots and that the camera moves between the steps without cuts.
  • Let an AI coding agent find and add UI items for you

    Connect the affectUI MCP server so Claude Code, Cursor or Codex can search items and install them.

    View prompt
    Use the affectUI MCP server at https://www.affectui.com/api/mcp to search for <component-need> and add the best match to the <project-path> React 19 project. Expected output: the new component file in components/ui and a short note naming the item chosen. Verify that the project builds after the file is added.
  • Hand off a Claude session to Codex through the CLI

    Extract a Capsule from a Claude session file and write a Codex handoff file with the handoff command.

    View prompt
    Using the Frankie-Xu/threadport repo after `npm ci` and `npm run build`, extract a Capsule from <session-file> with --from claude and --project <project-directory>, then create a Codex handoff at <handoff-path>. Report both printed output paths and confirm that `node dist/src/cli.js validate --handoff <handoff-path>` succeeds.
  • Walk someone through an app one control at a time

    Chain several arrows so a person learns each step of an app's interface.

    View prompt
    Use the bigarrow CLI from franzenzenhofer/big-arrow-on-the-screen to show three steps in <app name>, using the element labels <label 1>, <label 2> and <label 3> with the sign texts "1. <text 1>", "2. <text 2>" and "3. <text 3>". Expected output: three `bigarrow start` runs that each return at once. Verify each run exits with code 0 and that `bigarrow stop --all` clears the arrows afterwards.
  • Replay a finished agent run to review its subagents

    Scrub back through a completed session to see each agent and tool call in order.

    View prompt
    Using the zoetrope repo (furkankly/zoetrope), replay the finished session at <session-file-path> with `zoe` and step through each prompt era. Expected output: a graph showing each subagent and its tool calls at the point it ran. Verify that the tool counts fall when you scrub backwards before reporting the review as complete.
  • Teach a coding agent to author Framefields videos

    Install the Framefields agent skills so Claude Code, Cursor, or Codex can write and render compositions.

    View prompt
    Install the framefields agent skills from the gatewai-dev/framefields repo, then create a 3 second 1080p composition in <project folder> with the headline <headline text> and render it to output/<name>.mp4. Expected output: a rendered MP4 file. Verify the file exists and that the composition code imports from framefields.
  • Disable TV ad and tracking packages without uninstalling

    Stop sponsored rows and analytics on a Google TV or Android TV while keeping every package and a one-line restore.

    View prompt
    Using the Gathin23/cleanyourtv repo as context, disable only the ad, telemetry and content-row packages found for the TV model <tv-model>, using pm disable-user, and keep the restore script. Expected output: a list of disabled packages and the path to the restore script. Verify that every package still appears in the installed package list after the change.
  • Revise an existing image without losing prior edits

    Edit a picture you already have, or refine the last result, while keeping references attached.

    View prompt
    Using the GPT Image Skill in <repo path>, edit <existing image path> with the change <requested change> and keep the rest of the layout. Expect a new PNG in /generated-images and a PATH=... line. Verify that the previous output was the edit target for any follow-up request.
  • Let a coding agent build decks and workbooks locally

    Install the Genoffice skill so Claude Code, Codex or Cursor can create .pptx and .xlsx files on your machine.

    View prompt
    Install the genoffice skill from the genspark-ai/genoffice repo, then build an eight-slide deck about <topic> in <output folder> as a .pptx file. Expected output: one .pptx file and a rendered preview of each slide. Verify that the deck opens and that no slide text overflows or overlaps.
  • Ask Codex about a repo without allowing edits

    Explore an unfamiliar codebase with Codex in Plan only mode, with no file changes.

    View prompt
    Using the gitbot-hq/GitBot package, start it with gitbot start and create a Codex bot with Plan only permissions. Ask it to explain how <feature name> works in <repo folder>. Expected output: a written explanation that names the files it read, with no edits made. Verify that the working files are unchanged after the reply.
  • Check past failures before changing code

    Query project memory for a known failure before an agent edits the affected code.

    View prompt
    In the repository grpcer/ownmem, ask project memory about <the symptom or proposed change> using `npx ownmem recall -- "<query>"`. Expected output: one of the three delivery tiers, quoted memory, up to three file pointers, or an abstention that names the refusing gate. Verify that any quoted memory shows its trust status before you act on it.
  • Batch-render scene stills at zero credit cost

    Send up to 50 scene prompts to Flow's Agent mode and get matched image files back.

    View prompt
    Using the flow-mcp repo at <repo-path>, send these scene prompts from <prompt-file> to the agent image batch tool in one call. Expected output is one image per scene in ~/flow-mcp-out/ with file numbers that match the scene order. Verify that the returned results list every scene and that the credit count shown is 0.
  • Rehearse a risky file change before it touches your folder

    Let an agent do a task on a copy of your folder, compare attempts, and apply only the one you want.

    View prompt
    Using the Bloks repo at hamedgitty/bloks, rehearse the task <task-description> on a copy of the folder <target-folder> with the agent in Bloks. Expected output: a change card listing each changed file with its line count and diff, with Apply and Discard buttons. Verify that the real folder <target-folder> is unchanged until you press Apply.
  • Route drafting and review to separate model groups

    Use custom task branches so drafting and review each get the model that fits their category and difficulty.

    View prompt
    Using the HiRoute repo at https://github.com/higress-group/HiRoute, configure a routing plan with separate drafting and review custom task branches for <target project>. Report which model group each branch uses and the category HiRoute chose for two sample turns. Verify that a low drafting score does not change the review category.
  • Let an agent build and edit FreeCAD models from the terminal

    Point an AI agent at the FreeCAD CLI to run design commands without opening the GUI by hand.

    View prompt
    Using the HKUDS/CLI-Anything FreeCAD CLI, create a simple box model with the installed command set and save it to <output-path>. Report the command used and the file path. Verify that the output file exists and is not empty.
  • Run Implement and Review on one repo from the Windows app

    Use the portable Windows build to have one agent write in a worktree while another reviews.

    View prompt
    Using the Hoylon/peerbridge-mcp portable build, start an Implement + Review operation on <path-to-local-git-repo> with Codex as writer and Claude Code as reviewer. Report the worktree path and the Trust Timeline status, and verify that the review shows no stale-evidence warning.
  • Watch every epic on your machine in a browser

    Open one local web view that lists all epics on this machine.

    View prompt
    Using the humanize repo (hmz), run `hmz web` and open the local page it prints. Report the number of epics listed and their names as plain text. Verify that the count matches the epics you started earlier on this machine.
  • Let an AI agent draft a post with write approval

    Connect Claude Code, Cursor, or Codex to a site and enable writes once for that CLI.

    View prompt
    Use the Hycli MCP server (command `hycli`, args `mcp`) to prepare <site-url>, list its actions, and ask me before enabling writes. After I approve, create one draft post on <site-name>. Expected output: a confirmation that the draft was created. Verify the draft appears in the site account before anything is published.
  • Continue a community decomp using your own game copy

    Fork a decomp.dev project and let agents match more functions, committed to git for review.

    View prompt
    Using the decomp.wtf repo (i12bp8/decomp.wtf), fork the decomp.dev project <project-name> and add my own copy of the game at <path-to-game>. Run the agents and report how many functions were matched as git commits on the decomp-wtf branch. Verify that each commit only changes C or C++ sources and headers, and that no matched function broke.
  • Redraw a figure in WPS Presentation as an editable PPTX

    Build an editable PPTX working copy of a figure in WPS Presentation with checkpoint refreshes.

    View prompt
    Using the scientific-illustrator plugin with host_application set to wps, redraw the uploaded reference figure as an editable PPTX working copy in WPS Presentation. Verify that target_application is wps, microsoft_powerpoint_used is false, and refresh_verified is true for each region.
  • Check token use and estimated cost of a Codex task

    Review task and turn token totals, cache usage, and estimated cost in one viewer.

    View prompt
    Using the icesixgod/codex-trajectory repo, open the trajectory for the Codex task <sessionId> and report its token totals, cache usage, and estimated cost. Verify that the cost is labeled as an estimate based on bundled API prices, not a subscription bill.
  • Tour uncommitted changes before you commit them

    Read your own uncommitted work as a guided tour to catch risks before others review it.

    View prompt
    In the repository at <path>, run tour on the uncommitted changes and report which files the tour points to first. Expected output: a list of file names from the tour. Verify with `git status` that the working tree is unchanged after the run.
  • Build a Godot 4 game with engine checks

    Have Noobi AI build a Godot 4 project, then import, validate and export it through the host.

    View prompt
    In the Noobi.ai repo at <path>, install dependencies with `npm ci`, start the app with `npm run dev`, and submit a Godot 4 game brief: <game idea>. Expect a Godot 4 workspace with a Compatibility-renderer Web export; verify that the environment and export-template checks passed before counting the run as complete.
  • Score your build against a reference site and fix the gaps

    Band-map your page and diff its motion against a reference, then iterate to a passing score.

    View prompt
    Use the awwwards-mcp server to run verify_build comparing my local build at <build file:// path> against the reference <reference URL>. Expected output: a 0 to 100 score, a pass, warn, or fail verdict, and evidence lines naming each band or motion gap. Verify the score changes after you apply one fix and re-run the check.
  • Classify a dataset of records in one call

    Pass up to 500 records as items and ask the same questions of each one.

    View prompt
    Using the evaluate tool from the itsmostafa/system-one-connector repo, pass the records in <file path> as items (up to 500) and ask whether each one is negative in sentiment using a score question. Return one answer per record as CSV. Verify that the number of returned rows equals the number of input records, and list any that failed.
  • Answer agent approvals and questions from the HUD

    Allow, deny or answer an agent's request from the HUD and jump back to its session in one click.

    View prompt
    In the agent-hud-open repository, run `make run` and confirm the app is open. Trigger one approval request from Claude Code or Codex, then verify the request appears on the HUD with its command or diff and report what options it offers.
  • Compile a session into a Docker-validated coding task

    Review a candidate, build an executable bundle, and run two-state Docker validation on it.

    View prompt
    Using the EvoTrace repo at https://github.com/jinzijian/EvoTrace, run /review 1, /build 1, and /validate 1 in the DeepSeek Harness app for the candidate <candidate-number>. Report the asset status and the Docker validation result from /runs. Verify that the asset is marked Verified only if the base was rejected and the reference was accepted.
  • Rewrite on-the-nose dialogue in a scene

    Revise a scene whose characters say exactly what they feel, using the dialogue and scene craft skills together.

    View prompt
    Using the screenwriting-skills repo (sw-dialogue and sw-scene-craft), revise the scene in <pasted scene text> so that the characters stop stating their feelings directly and the conflict shows in action. Return the revised scene and a list of changed lines with reasons. Verify that the character names and the scene's facts are unchanged.
  • Score a live website like an Awwwards jury

    Get a scorecard with screenshots and measurements for any reachable site.

    View prompt
    Using the juliobsz/skills repo, run the /jury skill on <target URL>. Expect a .jury/scorecard.md file with screenshots, Core Web Vitals measurements and a ranked fix list. Verify that each score in the scorecard links to a screenshot or measurement in the .jury folder.
  • Audit an SVG logo against design principles

    Check an existing SVG logo for construction faults and test it at 16 px and in one colour.

    View prompt
    Using the audit and test tools in kaankiziltug/logo-design-skill, audit <path to logo.svg> against logo principles and build a 16 px and one-colour test sheet. Return the list of issues and the sheet image path. Verify that the audit was run on the same file you passed in.
  • Turn a talking-head video into a captioned TikTok

    One render command crops to 9:16, burns in your cue text and normalizes loudness for TikTok.

    View prompt
    Using the ffmpeg-skill repo, render <talk video> with the tiktok template and the cues file <cues.txt>. Expected output: a 9:16 TikTok MP4 with captions and a platform check written next to it. Verify the check result and the output resolution before reporting success.
  • Plan FY 2026-27 advance tax payments and due dates

    Get the next advance-tax amount and its due date from your expected income and TDS.

    View prompt
    In the itr-wala repo at <repo-path>, run the advance-tax validator and engine on a FY 2026-27 income file for <your-income-file>. Expected output: the amount to pay next and its due date, with late fees and interest excluded from the target; verify the validator accepts the file and that no future payment is counted as already paid.
  • Stress-test a plan or design doc before building

    Have agy challenge a plan from several angles before you commit to it.

    View prompt
    Using the keli-wen/agy-staff plugin, ask the reviewer persona to challenge <plan file path> in <repo>. Expect a multi-angle critique of the plan. Verify that each objection points to a specific section of the plan.
  • Compare Claude Code, Codex and Cursor on one project

    Run several coding agents side by side on the same project to see which one fits a task best.

    View prompt
    Using the BetterC0de repo's side-by-side conversations, give the same task text to Claude Code, OpenAI Codex and Cursor Agent for the project at <project-path>. Produce a short table of each agent's proposed file changes and one note per agent. Verify that each agent was connected and that every table row names a real file in <project-path>.
  • Turn agent requests into numbered steps you can follow

    When the agent needs you to run, paste, click or approve something, get exact numbered steps instead.

    View prompt
    In the open-steps repo at <repo-path>, use the os-step-by-step skill for the next action that needs a human on <project-name>. Expected output: numbered steps a non-technical person can follow, with only the actions that truly need the person listed. Verify that the agent tried every step it could do itself before asking.
  • Count and export your repeated prompts

    Run the extractor alone to list, count or export your prompts with no agent involved.

    View prompt
    Using the cli-faq-shortcuts extractor at ~/.agents/skills/faq-shortcuts/scripts/extract_asks.py, run it on <project_path> with --format jsonl and write the records to a file. Expected output: one JSON object per line with date, source and prompt fields. Verify the file line count matches the count from the default tsv output.
  • Let an agent zoom into one moment of a recording

    Give the agent the command set to pull dense frames around a timestamp, a spoken phrase, or a mark.

    View prompt
    Use the scrawl command on the capture at <bundle-path>. Run `scrawl inspect --marks`, then `scrawl zoom --at <timestamp>` for the first mark, and report what happens in those frames. Verify that the reported timestamp matches the summary.md timeline.
  • Probe a brand-new session before a long task

    Run the Fresh session probe to see which model a new Codex session gets right now.

    View prompt
    In the kiyoakii/is-gpt-nerfed repo, trigger a probe of the Fresh session from the menu bar app or with `nerfed probe now`, then report the verdict and the model you selected. Verify that the verdict is one of Match, Suspicious, Downgrade, Upgrade, Rerouted, Downgraded, Upgraded, Unlisted, or Invalid.
  • Approve or deny agent actions from your wrist

    Get a card on the watch when an agent asks for permission and allow or deny it in one motion.

    View prompt
    In the chums repo at <target-folder>, run bin/chums-permissions and confirm the permissions step completed for the agents. Expected output: the agents' permissions granted once. Verify by checking that bin/chums-doctor reports the permission check as passing.
  • Create a 12-second vertical video for Reels and TikTok

    Render a 1080x1920 product clip that follows your brand colours and typeface.

    View prompt
    Use the cinetic skill from the Leonxlnx/cinetic repo to make a 12-second 1080x1920 vertical video with sound for <app name>, using the brand colours <hex values> and typeface <font name>. Output an MP4 and confirm the brand colours and typeface were used exactly as supplied.
  • Split a large task into parallel agent leaves with scoped claims

    Run independent leaves in fresh agent contexts using scoped pipelines and ownership claims.

    View prompt
    Use the unlazy skill in the repo <repo-path> to split <large-task> into scoped leaves with disjoint OWNS: paths. Claim each ready leaf, then run node /scripts/gate-check.mjs --scope <scope-name> and report the reduced result. Verify that the output says ALL MET before you report success.
  • Install the ranking data as a skill for an agent

    Install the Best Skills repo as a skill so an agent keeps the rankings as standing context.

    View prompt
    Use the best-skills skill installed from https://github.com/LinklyAI/best-skills. Name the ranking list that answers this question: <your question>, then give the CSV file path and its top three rows. Verify that the file path exists in the repo's data/ folder.
  • Turn a research direction into a ranked proposal

    Use AutoVibeIdea to map literature, rank candidate ideas and draft a proposal.

    View prompt
    In the repo liyingze07-svg/EffectiveAutoResearch-EAR-, follow docs/getting-started.md to run AutoVibeIdea on the research direction <research-direction>. Expected output is a literature landscape, ranked candidates and a proposal draft in its own workspace. Verify that each candidate's novelty judgment cites retrieved prior work before you rank it highest.
  • Share a live agent conversation with teammates

    Open the same agent conversation with teammates to review the transcript, files, and changes.

    View prompt
    In the LodyAI/Lody repo, find the shared conversation <conversation-name> in the workspace <workspace-name> and summarize its transcript, runtime status, and code changes for a teammate. Output a short summary with the current status and the files changed. Verify the summary against the output of `npx lody session list --workspace <workspace-name>`.
  • Compare answers from Codex and Claude Code in one thread

    Ask one question, switch agents mid-thread, and dig into the answer that fits best.

    View prompt
    Using the longsurf-ai/endo repo, set up a chat where <my question> is answered first by Codex, then by Claude Code in the same thread. Expected output: two answers in one thread, with the second agent referring to the first. Verify that the Claude Code answer reflects the earlier history.
  • Track coding agents and approve them from iPhone

    See agent progress on your iPhone Lock Screen and approve permissions with Face ID when you step away from your Mac.

    View prompt
    Using the Louis-CFM/coucou repo, set up the Coucou Mac app and iPhone app so that a Codex session on <target Mac> shows as a Live Activity on <target iPhone>. Expected output: the agent state appears on the Lock Screen, and an Allow tap is confirmed with Face ID. Verify that the Mac applies only the decision for the request it is waiting on.
  • Start a contest project from official problem files

    Copy the official problem files into a new project folder with fixed file identities.

    View prompt
    Use the Modeling Workbench repo in <tool folder> to start a new contest project. Use <official material folder> as the official material and <new project folder> as the output folder. Confirm the contest name, year and paper language, then report the copied file list and the stage that comes next.
  • Publish one SEO article every weekday

    An SEO/AEO Employee researches keywords, publishes an article and reviews rankings on a schedule.

    View prompt
    Using the ai-employees repo, install the SEO/AEO Employee into <target folder> and confirm its routines are scheduled. Expected output: keyword research, a first article and a rank review in the employee's folder. Verify that each article is reviewed before it is published on your site.
  • Split a plan into tracer-bullet tickets with blockers

    Turn a conversation into a spec, then into ordered tickets that declare what blocks what.

    View prompt
    In the mattpocock/skills repo, use to-spec on our current discussion about <feature>, then use to-tickets to split the spec into tracer-bullet tickets. Expected output: a published spec and a ticket list where each ticket names its blocking tickets. Verify that no ticket is blocked by a ticket that depends on it.
  • Review a Compose screen against UI and state traps

    Have an agent check a Compose screen against the visuals, screens and state trap indexes.

    View prompt
    Using the installed kotlin-footguns skills, review <path to screen file> against the compose-visuals-footguns and compose-screens-footguns indexes. Expected output: a list of matched trap files with the line in the screen that triggers each one. Verify that each cited trap file exists and that its trigger description matches the code you point to.
  • Onboard to a repository with Repo Memory

    Build repository knowledge from recent issues, pull requests, and commits before making changes.

    View prompt
    Use the MemoraX Code skill to build Repo Memory for the <repository name> repository, retrieving only the latest 3 issues, pull requests, and commits. Report the architecture map, entry points, and module ownership you found. Verify that each claim is tied to an issue, pull request, or commit in the retrieved records.
  • Tighten an abstract to 200 words without losing results

    Get replacement abstract prose and a short change note from one prompt.

    View prompt
    Use the game-the-llm-reviewer skill from Michael-Jiahao-Zhang/game-the-llm-reviewer on the abstract text in <path to abstract file>, keeping it under 200 words. Work only from the supplied text, preserve both positive and negative results, and return replacement prose with a short change note. Verify that no result, number, or limitation is missing from the new version.
  • Check whether an agent's 'done' claim is verified

    Open a task receipt and separate the agent's own Reported result from checks that passed after the last change.

    View prompt
    Use the agentacct repo at https://github.com/mikehasa/agentacct to open the receipt for the task <task name> and report whether its result is Reported or Verified. Confirm that any passing checks ran after the last recorded change, and list any earlier failed checks that remain in the history.
  • Tear down a test launch and list what remains

    Remove the resources golive created, then get a handoff for anything it cannot delete.

    View prompt
    Use the golive skill in the repo <repo-path> to tear down only the resources golive created for this app, and show the plan before any deletion. Report the handoff list of leftovers that golive could not remove, and confirm the removal of the test host project.
  • Let ChatGPT use files and terminal in a Codex task

    Connect ChatGPT to a Codex task's files, terminal, and tools through MCP.

    View prompt
    Using the codex-chatgpt-web repo, guide the setup of Full harness mode for the Codex task in <project folder>. Confirm the connector name is exactly Codex Native2 and that Verify runtime reports it as attached and available. Do not enable auto-approve; report any approval prompts you see.
  • Turn your own footage into a scrubbing scroll page in Codex

    Use your own photos and video in Codex to build a page where scroll drives the footage.

    View prompt
    Using the scroll-craft skill in the nateherkai/scroll-craft repo, build a scroll-driven page from my own footage in <media folder> for <target product>. Do not use generated assets. Expected output: a page where the footage scrubs with scroll. Verify that the doctor script reports a full ffmpeg build and that no clip is stuck on a poster frame.
  • Set up Foremerge for a repo's coding agents

    Install Foremerge, initialize the repo, and wire up every agent client you use in one pass.

    View prompt
    In the <repo path> repository, install Foremerge, run `foremerge init`, then run `foremerge setup all` and `foremerge doctor --client all`. Expected output: a per-client result from setup and a doctor report. Verify that setup exited with status zero, since the README says it exits nonzero if any client failed.
  • Add the recipe to Codex with prompt files only

    Install the system instructions in Codex without hook reminders.

    View prompt
    In the repository at <repo-path>, run `node scripts/install.mjs` and confirm that the two managed prompt files were written to the active CODEX_HOME. Verify that the installed config still uses the same model, provider and permissions as before.
  • Point a coding agent at a Pooled room's model

    Run the Pooled bridge on your computer so Codex or Claude Code sends requests to the room's GPUs.

    View prompt
    In the Nehanth/pooled repository, run `npx @pooled/cli serve "<room-invite-link-or-code>"` and then send a chat request with curl to http://127.0.0.1:8080/v1/chat/completions using model 'pooled'. Expected output: a JSON chat completion from the room's model. Verify that the room's chat shows the request.
  • Build planned project features in parallel with subagents

    Split a project's planned features across Web GPT extra-high subagents that run at the same time.

    View prompt
    Using the WebGPT repo (Nhahan/WebGPT), ask Codex to run webgpt xh subagents on the planned features of <project path>. Expect one completed change per planned feature and a short report from each subagent. Verify each change with the project's existing tests before merging.
  • Score Codex changes against quality dimensions

    Install Jev Review for Codex so it scores a change before the final handoff.

    View prompt
    Use the jev-review MCP tool jev_review in the NiazMorshed2007/jev-review server to evaluate the current diff for <feature or file>. Return the 1 to 10 scores and confidence values for each applicable metric, and list the weakest dimensions by priority. Verify that each returned score has a confidence value between 0 and 1.
  • Split a coding task across Codex and Claude agents

    Give each agent its own workspace and queue, then delegate parts of a task between them.

    View prompt
    In the nightly-labs/openbot repo, set up a Codex agent and a Claude agent in the desktop app, each with a separate workspace under <project-path>. Expected output: both agents listed with queued tasks and one agent-to-agent message sent. Verify that each agent's queue shows the task before reporting success.
  • Confirm the services repo passes format, lint, tests, and schema checks

    Install dependencies and run make check to validate the code and the Prisma schema before editing.

    View prompt
    In the NuvexNetwork/nuvex-services repo, run `pnpm install` and then `make check`. Report which of the steps (format, lint, tests, Prisma schema validation) passed or failed, and quote the first error line if any. Do not start a database, since make check does not need one.
  • Find the root cause of a bug before fixing it

    Have the agent work through a four-phase root cause process, then confirm the fix with evidence.

    View prompt
    Using the Superpowers skills from the obra/superpowers repo, apply systematic-debugging to this bug: <bug description>, in the project at <project path>. Expected output: a root cause statement, the fix, and verification-before-completion evidence. Verify that the agent names the root cause before it edits any code.
  • Match a mountain skyline to a power line site

    Use nearby power lines and the ridge line in a photo to narrow a location in a region.

    View prompt
    Use the geo-sleuth skill from the Oldcircle/geo-sleuth repo to narrow where <path to photo> was taken, using power lines and the ridge line in the photo. Expect a single candidate site with its fit score and a satellite image of the line of sight. Verify that the score and the files produced by terrain.py fit are cited in the answer.
  • Find a Python function's docs by exact name

    Search the Python docs index and jump straight to the anchor for a named symbol.

    View prompt
    Use the only-cli/oc repo: run `oc py search <symbol>` with the target symbol name. Expect a numbered list of Python docs results, with an exact match linking to its anchor. Verify that the top result names the symbol you asked for before quoting it.
  • Scan a branch for bugs and security issues before merging

    Get a P0 to P3 HTML scan that merges SAST, lint, and secrets results with a semantic pass.

    View prompt
    Use codexqa-defect-analyzer on this branch in <repo-path>. Merge SAST, lint, and secrets results with one semantic pass and write a P0 to P3 HTML report. Verify that each finding shows its location, evidence, and suggestion.
  • Review your change before you push it

    Run a review of unpushed commits and uncommitted work, then choose which findings to fix.

    View prompt
    In the repo at <path>, run `~/.openqodex/bin/openqodex review` and show me the receipt verdict and each finding line. Verify that the output ends with a report.html path or a 'Review incomplete' message with the missing stages named.
  • Pause at a suspect line and inspect its variables

    Set a line breakpoint, hit it, and read the object state the agent needs to test a hypothesis.

    View prompt
    Use the Debroid CLI to set a breakpoint in <class-name> at line <line-number> of the app <package-name>. Trigger <user-action>, then run `debroid pause-state --pretty` and `debroid inspect --max-depth=2`. Return the local variables and relevant object fields as JSON, and verify that the paused line matches the breakpoint you set.
  • Monitor live Codex activity into a local record file

    Install a monitor-only Codex hook that writes events and findings to an NDJSON file.

    View prompt
    Use the repo perplexityai/numbat. Run `numbat hook install --agent codex --emit all` and then `numbat hook status --agent codex` on <target-machine>. Report the status output and the record_type values seen in ~/.numbat/records.ndjson after one short Codex task. Verify that the hook status output reports the Codex hook as installed, and remember that status checks configuration only, not delivery.
  • Mark up a localhost page and send fixes back to the app source

    Review a running local page in the browser and have your agent apply the changes to the code.

    View prompt
    Using the petergyang/human-review skill, open the localhost page at <localhost-url> with /human-review. After I click Send, check that the agent changed the app source for each comment and report which files were edited.
  • Get a specific work draft built from your answers, not guesses

    Answer a few questions so the rewrite contains your real example, number or outcome.

    View prompt
    Use the work-humanizer skill from the phuryn/work-humanizer repo in interview mode on <draft-file>. Ask up to five questions, then output the rewritten piece built only from my answers and the draft. Verify that the output contains no facts that appear in neither my answers nor the draft.
  • Count matching postings before pulling them

    Check how many postings match a search before spending your daily pull allowance.

    View prompt
    In the pinloop-cli repo, search Pinloop for <keywords and filters> and report only the number of matching postings, without pulling any. Expected output: one count per search tried. Verify that no postings were pulled by checking the plan usage before and after.
  • Find existing rule violations before they spread

    List current violations by contract and rule in a repo right after setup, without changing code.

    View prompt
    In the repo at <repo-path>, after `/gap-trap setup` has finished, answer yes to the framework check. Return the existing violations grouped by contract and rule. Verify that no files changed by running `git status` before and after.
  • Set up agent coordination in an existing repo

    Run Pullboard init in a git repo so a coordinator agent can take your requirements and fan out work.

    View prompt
    In the git repo <path>, run `pullboard init`, then commit the files it wrote with `git add -A && git commit -m "chore(repo): set up pullboard"`. Report the files created and confirm that SPEC.md and DOCTRINE.md exist at the repo root.
  • Map every API endpoint from an OpenAPI document

    Generate an endpoints diagram grouped by resource, with methods, auth, and status codes.

    View prompt
    In the repo <repo path>, import the OpenAPI file at <openapi file> into docs/api.endpoints.json with vibeX and render docs/api.endpoints.html. Report the number of endpoints per resource. Verify that the count matches the number of paths and methods in the OpenAPI document.
  • Calibrate a scan and measure distances in it

    Give one known real distance, then have your assistant measure between points in the scene.

    View prompt
    Using the openreality MCP tools on the scene <scene id>, calibrate with the known distance <distance in metres> between <point A> and <point B>, then measure <target measurement>. Verify that the result is reported in metres only after calibration succeeded, and flag it as relative otherwise.
  • Check each diagram claim against its cited lines

    Walk inferred and unresolved claims in the diagram and open their cited source beside it.

    View prompt
    In the repo <target-project>, open the MLView diagram <diagram-file>.mlview.json and list each inferred or unresolved claim with its cited file and line range. Expect a short review list. Verify that every listed quote points to a file that is marked unchanged.
  • Check what an edit breaks before calling it done

    Run the edit check to see blast radius, tests that reach the change and incompatible call sites.

    View prompt
    Use ripwire on the repo at <path>. After editing <symbol>, run the --edit-check flag on it and report the blast radius, the tests that reach it and any incompatible call sites. Verify each flagged site by compiling before you change anything.
  • Fix text and timing by clicking the element on screen

    Click a frame element in the preview to change its text, easing or position without hunting through code.

    View prompt
    In the Remocn Studio project at <project folder>, change the element selected as [Element #1] so that <describe the change>. Expect the scene source file to contain the new value and the preview to update. Verify that the edit appears in the scene's TSX file and in review.md.
  • Let a coding agent read and drive other terminal panes

    Install the Think Term skill so an agent can send input to and read output from other panes.

    View prompt
    In the RoversX/ThinkTerm repo, use `thinkterm cli get-text` to read the output of the pane labeled <pane label>, then summarize any failing test. Expected output: a short list of failing tests with file names. Verify that the summary matches the text returned by get-text before acting on it.
  • Check local Codex or Claude sessions for duplicate retries

    Inspect your own Codex or Claude Code session logs for duplicate records, retry amplification and token anomalies.

    View prompt
    Using the AgentMeasure repo, run `agentmeasure check --runtime claude` on this machine and report duplicate records, retry amplification and token anomalies, with any missing inputs listed separately. Verify that the report states which inputs were not found instead of marking them as passing.
  • Let a coding agent read and edit the open Blender scene

    Connect Claude Code, Codex or Cursor to the local scenario-blender MCP server.

    View prompt
    Using the scenario-labs/blender-plugin MCP server named scenario-blender at http://127.0.0.1:9876/mcp, read the open scene in Blender and list the objects named <object prefix>. Report the object list and the tools available. Verify that no paid generation is requested unless I confirm it.
  • Make seamless textures and 360 skyboxes for an engine

    Have an agent generate tileable PBR textures and equirectangular skyboxes sized for engine import.

    View prompt
    Using the scenario-labs/skills repo, generate a seamless <surface> texture with PBR maps and a 360 equirectangular skybox of <scene>. Save both to <output-folder>. Verify that the texture tiles without a visible seam when repeated.
  • Review Codex file changes and commit them in focused batches

    Inspect staged and unstaged changes per file, then commit only the related files.

    View prompt
    For the repository sevensir888/codex-command-center, describe how to group the uncommitted changes in <project path> by task and stage one group at a time. Output the file list for each group. Verify that no unrelated file is staged before committing.
  • Run a phone task on a rented cloud phone

    Rent a cloud Android or iPhone by the session and let an agent work on it without owning a device.

    View prompt
    Using the phone-harness repo at https://github.com/ShawnPana/phone-harness, start a cloud phone, complete the task <task description>, and return the final screen text. Verify with `cloud ls` that the session is stopped before you report completion.
  • Set up and launch the local game with Codex

    Install the entry skill and let Codex clone, build, and start the game on your machine.

    View prompt
    Use the infinite-pokemon entry skill from the Shellishack/infinite-pokemon repo to set up and start the game on this machine. Report the local address the game is running at and whether the starting map became playable after Codex verification. Verify that http://127.0.0.1:8788 loads in a browser.
  • Verify live web findings with marker and control tests

    Check a scope, then let the agent confirm live findings with marker reflection and a negative control.

    View prompt
    Using the blitzstrike MCP server, call scope_check for target <authorized URL> with scope <written scope>, then run_engagement on that target. For each candidate, call strike_verify and report only the findings with a live verdict. Verify that no request was sent to a host outside the scope.
  • Set up Codex CLI with gateway models in the /model picker

    Configure Codex CLI to use a Responses API gateway and list extra gateway models in /model.

    View prompt
    In the repo Sinholms/setup-gateway, run `node bin/setup-gateway.mjs codex --base-url <GATEWAY_BASE_URL> --api-key <API_KEY> --model <MODEL_ID> --yes`. Expect config.toml and gateway-catalog.json to be written in the Codex config directory. Verify that config.toml sets wire_api to responses and that model_catalog_json points to an existing gateway-catalog.json.
  • Keep an overnight build going when one agent runs out of quota

    Arm a handover so a second vendor's agent continues the task from the exact commit.

    View prompt
    In the repo <repo-path>, arm the rotate-agent skill from Sno Station Skills so that the task in <task-file> hands over to the other vendor's agent when quota reaches the threshold. Output the handover brief and the commit to continue from. Verify that the receiving agent confirmed the brief before touching any file.
  • Get a code review from a different agent

    Ask one agent to review another agent's work, so the reviewer does not share its habits.

    View prompt
    In the sno-station repository, ask the <placeholder> agent to peer-review the latest changes made by the other agent. Expected output: a review written by the reviewer, not the author. Verify that the reviewer names the specific files and lines it checked.
  • Let Codex run browser-grounded social research

    Install the Jev Social skill into Codex so it can run cited social research for you.

    View prompt
    With the jev-social skill installed in Codex, research <goal> on <platform> using the local socai CLI. Expected output: a short evidence summary with captured source URLs. Verify that login-gated or failed steps are reported as partial results.
  • Compare REA agent setups before a reverse-engineering project

    Use the LeanREA benchmark and related cases to choose between CLI and MCP for a coding agent.

    View prompt
    Read the LeanREA case in the songshikang0111/awesome-REA-cases repo and summarize its CLI versus MCP comparison for <target task>. Output the reported scores, time, and cost, and state whether the result was independently rerun. Check that the limits (one model, one machine) are included in your summary.
  • Bring an existing project up to the toolkit setup

    Diagnose a current codebase and add applicable agent configuration without breaking its stack.

    View prompt
    Read the repo soumatheusgomes/vibe-coding-toolkit at docs/prompts/12-existing-project-setup.md and execute the Prompt section in the project at <project path>, starting with brainstorming. Report the before and after state, the changes applied, and any pending work. Verify that existing stack, database, and contracts were preserved.
  • Build a multi-part feature with parallel Codex work

    Run a larger feature build in Codex with Autoprompt starting ready, independent work in parallel.

    View prompt
    Using the Spielewoy/autoprompt-skill repo, run `autoprompt activate codex --target <absolute project path> -- --concurrency wide "<your feature goal>"`. Expected output: a built feature across the layers named in the goal and a summary of what changed. Verify that the project's tests pass after the run.
  • Undo an agent turn that broke your files

    Restore project files to the snapshot taken before an agent's last turn, in one click.

    View prompt
    Using the Tellurion repo at https://github.com/steventsvik/Tellurion, run an agent turn in <project-folder> that makes a change, then use Undo last turn from the tab's ⋮ menu. Report the list of files the undo listed. Verify that the restored files match their state before the turn.
  • Continue polishing an existing Vibe Game project

    Point the agent team at a game you already built and direct its next round of edits.

    View prompt
    Using the VibeGame repo at https://github.com/tettethu/VibeGame, run vibegame start --project ./<project-folder> with the request "<change request>". Expected output is an updated game in <project-folder> with the requested change applied. Verify by running vibegame run --port auto and checking that the changed behavior appears in the browser.
  • Assign agent work with approvals and watchdog checks

    Create projects and tasks for agents, with human approvals and a watchdog that verifies done work.

    View prompt
    Using the repo theNetworkChuck/paperclip-guide, follow chapters 6 and 7 to create one project in Paperclip with a test task for <agent name>. Report the task status, any approval requests, and the Watchdog's verdict. Verify that the task cannot be closed without the required approval.
  • Hand single decisions to a System 1 agent from Claude Code

    Install the s1a skill so Claude Code or Codex sends one-off choices to a fast model.

    View prompt
    Using the system1-agents skill in this session, decide the best option for <task-description> with the s1a decide command. Report the chosen option, its probability and the command you ran. Verify that the reported choice is one of the options you supplied.
  • Grade a suspicious submission with evidence, not guesses

    Run paper-slop-screen to get W/R/Q grades, a quadrant, located findings, and a note to the AC.

    View prompt
    Use the absent-author repo's paper-slop-screen skill to triage <paper PDF or folder>. Return the W/R/Q grades, the quadrant, and each finding with its location and quote. Verify one finding by opening the cited location yourself before you rely on it.
  • Recover why a past decision was made and what it said then

    Pull the reasoning behind an old choice and check what the memory said on a given date.

    View prompt
    Use the agent-memory repo at <store path> to find the memory about <decision topic>, then show its outline and the version valid on <date>. Expected output: the memory path, its outline, and the as-of answer. Verify that the as-of answer differs from the current file when the memory was superseded.
  • Turn red SEO items into a P0, P1, P2 fix list

    Have the agent explain each failed check and rank the fixes so the team knows what to do first.

    View prompt
    Using the tigerless-labs/seo-ops skill, run the check on <target-url> and group every red item into P0, P1, and P2. For each item, give the fix and point to the evidence in the report. Verify that every red item appears exactly once in the priority list.
  • Decide if readiness flags are duplicate state

    Check whether several readiness flags express distinct lifecycle guarantees or just repeat the same state.

    View prompt
    Use $simplify-codebase in Focused Survey mode on <subsystem path> to decide whether the readiness flags <flag names> express different lifecycle guarantees or repeated state. Do not modify files. Expected output: one verdict per flag with its consumers and lifecycle owner. Verify that each verdict cites the readers and writers it traced.
  • Resume a repo in a new session from one handoff page

    Start a new Codex or Claude Code session from the repo's handoff instead of old chat logs.

    View prompt
    In the repo at <repo-path>, read docs/ai/project-card.md and docs/ai/handoff.md only, then search WARM files for <topic> with rg. Expected output: a three-line summary of the current task, the next step from handoff.md, and the file and section used. Verify that no COLD file under history/ was read unless I ask for it.
  • Review a planned design in Codex against arXiv prior art

    Install NeuroArxiv for Codex CLI and have it check a planned system design before implementation.

    View prompt
    Use the NeuroArxiv skill from the UditAkhourii/neuroarxiv repo on this problem: <your design problem>. Before writing code, return the recommended approach, the cited arXiv papers, the first step, and the pitfalls from each paper's limitations. Check that every paper id is a real arXiv id before you use it.
  • Review each PR as it opens, worst findings first

    A reviewer agent reads each new PR, splits large ones across helpers, and lists findings worst first.

    View prompt
    Using the Overtime repo at ukanwat/overtime, create a reviewer agent that reviews each new PR in <target repo>. Expected output: a findings list ordered worst first for one open PR. Verify that large diffs were split across helpers and that every finding names a file.
  • Send a finished edit to VEED's editor as a project

    Turn a finished plan into a VEED project a person can edit further, then pull it back.

    View prompt
    Using the Open Edit repo at veedstudio/open-edit, run veed-project on <plan file> and then open the resulting VEED project. Expect the editor to show footage, text, captions, and audio as separate items. Verify that the project opens in VEED before you tell the user it is ready.
  • Check and prompt running agents from your phone

    Start a session on your laptop, then follow and prompt it from the Vicoa mobile app.

    View prompt
    Using the vicoa-ai/vicoa repo, start a coding session on <target-project> with the Claude Code agent and a prompt to <task>. Confirm the session appears in the Vicoa mobile app under the same account and that a notification arrives when the agent asks a question or finishes. Report the session status seen on the phone.
  • Make an interactive product assembly for design review

    Model a product or mechanism, such as a gear pair or folding lamp, as an explorable scene.

    View prompt
    Using the 3dviz-pro-max skill in <repo-path>, build an interactive Three.js assembly of <product or mechanism>, with parts that connect and move. Reuse a suitable kit blueprint if one fits. Report which parts were modeled, what motion was observed, and which frames were captured.
  • Build a product demo that clicks through your app

    Rebuild your app's screens in Explainroo and film a pointer walking through them.

    View prompt
    In the explainroo repo at <repo folder>, make a product demo for <product name> using its site at <site URL>. Rebuild its screens with the same colors, fonts and button labels, then render an MP4. Expected output: one product demo MP4. Verify that every button label matches the real product before you publish.
  • Convert an article or document into a video

    Feed a written article or document to the skill and get a narrated video of its key ideas.

    View prompt
    Using the anything2explainer skill in this repo, turn the document at <path-to-document> into a narrated explainer video in <language>, about <length> long. Pause at the narration sign-off so I can edit the script. Verify that the narration covers the main points of the document and that the output is an MP4 with subtitles and chapter progress.
  • Add clearer-response checks to Codex sessions

    Install the Nopus Codex plugin so each completed answer gets a bounded check for abstract prose.

    View prompt
    Using the nopus repo at Vistyy/nopus, run `codex plugin marketplace add Vistyy/nopus` and `codex plugin add nopus@nopus`, then start a new Codex session in <project directory> and run `$nopus-configure medium`. Expected output: the plugin installed and the sensitivity set to medium. Verify that a long, abstract Codex answer triggers the message "nopus requested a clearer rewrite."
  • Split a large coding task across a team of agents

    Let a planner session split work into parts that executor sessions build in parallel.

    View prompt
    In the VelaTerm desktop app, open the project at <project-path>, start Plan / Execute mode, and give the planner this task: <task-description>. Expected output: a planner session with child executor sessions, each working in its own worktree, and a list of reports for review. Verify that each executor has a separate worktree before any edits begin.
  • Keep an agent building features over multi-day roadmaps

    Stop an agent from curating receipts and progress metadata instead of building.

    View prompt
    Using the forward-implementation-first skill, work through the roadmap in <roadmap-file> in the <repo-name> repository, building features and running focused validation without generating hashes, locks, or certification markers. Report each completed item with its validation result. Verify that every reported result comes from a test, benchmark, or end-to-end run rather than a receipt.
  • Add the HERO block to Codex's AGENTS.md

    Put the same contract in AGENTS.md so Codex follows the scope limits on each run.

    View prompt
    Confirm that the HERO SCOPE LIMITS block from RULES.md is appended once to <project>/AGENTS.md. Then complete <task> and report whether any change was made under rules 2, 3 or 4 that the task did not require.
  • Animate a sprite and export a spritesheet for your engine

    Turn a drawn character into a tagged animation and export it as a spritesheet.

    View prompt
    Using the aseprite-ai-artist plugin from with-pebbly/aseprite-ai-artist, animate the open sprite <sprite name> as a <number>-frame <idle or walk> cycle and export a spritesheet with its atlas for <engine>. Expected output: a tagged cycle in the Aseprite document and an exported spritesheet and atlas file. Verify that the frame count and cycle tags match the request before exporting.
  • Have ChatGPT review Codex changes without uploading the repo

    Send ChatGPT only the workspace lines it needs to review what Codex wrote.

    View prompt
    In the workspace at <workspace path>, with the codex-with-chatgpt bridge running, ask Codex to use ChatGPT to review the changes for <change>. Report the review findings and confirm that Codex made no edits without approval.
  • Build an incident walkthrough with failure paths and fallbacks

    Create an explainer showing impact, symptoms, and fallback behavior for an incident.

    View prompt
    Using the fireworks-open-eli5 Skill, build an incident explainer for <incident description> with impact, symptoms, fallback, and teach-back questions, grounded in the cited evidence. Render it to <output.html> and validate it. Report which failure steps lack a source locator.
  • Diagnose ad fatigue and brief the next creatives

    Find which ad concepts are fatigued and get a ranked brief for the next batch.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the paid-ads module on the performance data for <campaign name> and return a concept-level fatigue diagnosis with a ranked production brief. Verify that each ranked brief item names the concept it replaces and that no winner is declared from a handful of conversions.
  • Test RAG tenant boundaries with controlled fixtures

    Measure whether one tenant's documents can surface for another tenant using benign fixtures you control.

    View prompt
    Using the rag-data-exposure-audit skill from the zero-lab-ai/skills repo, test the retrieval endpoint <endpoint-url> with the canary fixtures I created in tenants <tenant-a> and <tenant-b>. Return one exposure state per boundary, with the query and the returned canary. Verify that every canary returned belongs to the tenant named in the result.
  • Build a figure with a WebGL fire or water effect

    Make an isometric explainer where a shader shows fire, water or light inside the drawing.

    View prompt
    Using the skill in wheresryan22/anatomy, build a figure of <apparatus> with a WebGL shader for <effect>. Expected output: an HTML file where the shader is inside the isometric camera. Verify that the SVG still renders with WebGL turned off.
  • Run a single-cell RNA-seq analysis with Scanpy

    Have an agent follow the Scanpy skill to process a single-cell dataset and report clusters.

    View prompt
    Using the scientific-agent-skills repo and its Scanpy single-cell skill, process the dataset at <dataset path> with quality control, clustering, and a cluster summary. Return a script and a short report of cell counts per cluster. Verify the cell and gene counts before and after filtering.
  • Redraw old Mermaid or draw.io diagrams

    Convert an existing Mermaid, draw.io or Excalidraw diagram into a styled HTML file.

    View prompt
    Using the diagram-design skill from cathrynlavery/diagram-design, redraw the existing diagram at <path to Mermaid, draw.io or Excalidraw file> as one self-contained .html file with inline SVG. Verify that every node and connection from the original appears in the output.
  • Add captions to a talking-head video without touching footage

    Overlay captions on an existing talking-head video using the embedded-captions skill.

    View prompt
    Using the hyperframes repo at heygen-com/hyperframes, apply the embedded-captions skill to <video path> with the verbatim rail style and output a captioned MP4. Verify that the original footage is unchanged apart from the caption overlay.
  • Pull apart a game's WASM web build

    Have your agent decode a game's .wasm file and explain its sections, imports and exports.

    View prompt
    Use REA to inspect the WASM artifact at <path to .wasm>, decode its sections and import and export forms, and explain what stands out. Verify against the decoded output and flag any guesses.
  • Move Claude Code and Codex sessions into DSH

    Use dsh-claude-move to bring sessions, memories, skills, and slash commands into DSH with approval gates.

    View prompt
    Using the repo 0xsline/awesome-deepseek-harness, install dsh-claude-move from github:PerryLink/dsh-claude-move into DSH. Run its migration wizard for <source tool: Claude Code or Codex> and report which sessions, memories, and skills were moved. Verify the migration is idempotent by running it a second time and confirming no duplicates appear.
  • Stop a long AI coding session from losing grounded facts

    Hand off a long task to a file-backed state so a fresh context keeps verified facts.

    View prompt
    Using the reverify repo at 2akouwu/reverify, run reverify rollover to hand off the current session, then run reverify ledger <target> and confirm the established and known-false facts appear in the new session before continuing.
  • Map entry points and sinks in a source repository

    Rank source files, map entry points, and trace risky sinks for a code audit.

    View prompt
    Using the Ablation repo at ~/ablation, audit the source repository at <repo path>. Produce a ranked file list, a table of entry points and sinks, and a coverage summary of reviewed versus unreviewed files. Verify that every listed sink has a traced path from an entry point, or is marked as untraced.
  • Sort an issue backlog into implement, spec, or wait

    Have a triage run classify each untriaged issue and write a handoff comment with its gate level.

    View prompt
    Using the addyosmani/factory skills in <target-repo>, run the triage stage on the open untriaged GitHub issues. Expected output: a list of issues with the factory:* label applied to each and a one-line reason. Verify that no code was changed and that every issue has exactly one queue label.
  • Carry your personal agent rules into every project

    Store your own standards and knowledge in a user partition that applies across all your repos.

    View prompt
    Using the Operator Memory repo (https://github.com/aerovato/operator-memory), set up the user partition and record this standard: <standard-text>. Expected output: a Markdown file under ~/.operator/user/ containing that standard. Verify by opening a different project and checking that the agent applies it.
  • Review local token usage and sessions across agents

    Check token counts, requests, sessions, and models for each agent from the local usage dashboard.

    View prompt
    Using the Agent Launcher repo at https://github.com/agent-launch/agent-launcher, open the usage dashboard and summarize token counts, request counts, sessions, and models for <agent-name> over <time-period>. Expected output: a short table of those figures per agent. Verify that the numbers come from local session records only and that no data was uploaded.
  • Keep an agent checking its inbox on a schedule

    Set up a recurring check so an agent picks up new messages from its durable inbox.

    View prompt
    Install the AgentPeerChat skill from the CLI, ask me for a sync interval, and create the recurring check only after I choose one. Return the task ID, interval and enabled state, and report connected but not listening if scheduling is unavailable.
  • Triage your task list with an agent, approving each edit

    Have a local agent sort Tasks.md while you approve every diff in Obsidian.

    View prompt
    In the Compass vault at <vault path>, read AGENTS.md and 08 Tasks/Tasks.md, then group the open tasks by project or person. Expected output: a proposed list of groups and moves, with no file changed yet. Verify that every proposed edit is shown as a diff and that no note outside 08 Tasks, 04 Projects, and 05 People was touched.
  • Plan your first 50 users and a launch

    Choose the channels to try first and decide how to launch without fear of getting flamed.

    View prompt
    Run first-50-users and then launch-it in the gtm-cofounder skills for <product name>. Expected output: a short channel plan for the first 50 users and a launch checklist with one recommended channel. Verify that the plan matches the Now move in gtm-roadmap.md.
  • Sign in to a site with 1Password, keeping secrets from the agent

    Have Chrome Relay type your 1Password credentials so the agent never sees them.

    View prompt
    Using the Chrome Relay repo at aindeev/agent-chrome-relay, sign in to <site URL> by filling the password field with an op:// reference from 1Password, never printing the value. Expected output: the signed-in page's title. Verify that the title matches <expected title> before reporting success.
  • Make a slowed mechanism to teach how it works

    Build a mechanism such as a Swiss lever escapement and slow it down to show each impulse.

    View prompt
    Using the repo AirsupHQ/machine-skill, build a Swiss lever escapement page slowed down for a classroom as one HTML file. The expected output is a single .html file with slow motion, live labels and a computed equations panel. Verify that the page opens in a WebGL 2 browser and that pausing stops the motion.
  • Add an interactive mascot to a web page

    Add a small illustration that follows the cursor, reacts to buttons and covers its eyes at password fields.

    View prompt
    Use the anidoodle repo to build an interactive mascot for <site URL or page file>, with cursor tracking, button reactions and a password-field reaction. Return the ES module and the custom element markup, then verify the page works with reduced motion and keyboard navigation.
  • Keep two agents from colliding on the same files

    Have agents announce the files they take in the Channel tab and check who wrote what.

    View prompt
    In the project <project>, before editing any file, call chat_post with kind taking and the paths you will change, then call chat_read when you finish. Expected output: a confirmed post and a short list of anything other agents said they were taking. Verify that no other agent has announced the same paths before you start editing.
  • Run a Codex session on a project folder in the browser

    Pick a folder in FCC's browser UI and run Codex there, switching models mid-session.

    View prompt
    Using the repo Alishahryar1/free-claude-code, start FCC, pick the folder <PROJECT_PATH> in the browser UI, and open a native Codex session. Expected output: Codex answers a question about the folder contents. Verify that the answer references files from <PROJECT_PATH>.
  • Split planning, execution, and auditing across models

    Assign a different model or backend to the Manager, Executor, and Auditor of one task.

    View prompt
    Use the LongHorizon-Harness repo at <repo path> to run a task for <goal> with a different model assigned to the Manager, Executor, and Auditor. Expected output: a verified result and a list of accepted checkpoints. Verify that the Auditor inspected the real files or logs rather than relying on the Executor's claim.
  • Add the Old Coder workflow to Codex or Cursor rules

    Paste the Old Coder SKILL.md into AGENTS.md or a rules file so the agent follows the same gates.

    View prompt
    Read skills/old-coder/SKILL.md in the <project-path> repo and follow it for the task <task-description>. Write the SPEC first and wait for my approval, then produce an EVIDENCE report that labels any unverified check as unverified. Verify that references/gauntlet.md was read before the gauntlet ran.
  • Map an APK's control flow without flooding the agent context

    Decompile an Android APK to a control-flow skeleton to save tokens during analysis.

    View prompt
    Using the Seep Reverse Lab workspace, triage <path-to-apk> and decompile it with seep_apk_decompile in fold mode. Expected output: a control-flow skeleton listing the main classes and their branches. Verify that the skeleton covers the classes the app's main activity calls.
  • Index PostgreSQL or MySQL table structures next to the code

    Add a table-level database index so the agent sees both code and schema before it changes either.

    View prompt
    In the repo <project-path>, using the declared PostgreSQL or MySQL source and its connection-string environment variable, build the AOCI database index. Confirm that aoci.database.txt was written and that no credential value appears in any AOCI file.
  • Research how top apps structure onboarding and paywalls

    Ask an agent how leading apps in a category run onboarding, what each step does, and where the paywall sits.

    View prompt
    Using the appllama/appllama-skills repo, research how the top-grossing apps in <category> structure onboarding and where they place the paywall, through the Appllama MCP. Output a comparison table with the flow length, the purpose of each step, and the paywall position for each app, and verify each claim against the screens you studied.
  • Find every mention of a topic inside one channel

    Search a single channel's videos for a keyword and get the matching videos.

    View prompt
    Using the youtube-skills repo, search inside the channel <channel handle> for the term <term> and list each matching video with its title and URL. Verify one match by opening its transcript and confirming the term appears.
  • Let an agent explore a new codebase without grep

    Give an AI agent a graph of the code so it queries structure instead of searching text.

    View prompt
    In the <repo> project, explore the code needed for <task> by querying the axiomcode graph instead of grepping. Report the functions involved, their file and line, and the number of tool calls used. Verify that each claimed call relationship appears in the graph output.
  • Run release checks before a version tag

    Use Procoder release to catch version drift, a missing changelog entry, and a red test suite before tagging.

    View prompt
    In the procoder-enabled repository at <repo-path>, run `procoder release` and fix every listed failure without tagging. Report the final list. Verify that the tag command is printed only when all checks pass and that you run it yourself.
  • Point the harness at your own model endpoint

    Connect the Claude Code harness to a self-hosted Anthropic-compatible model server.

    View prompt
    In the RoboHarness repo, set the model URL and model ID from the environment variables for <model server host>, send the small Messages test request from the README, and then run the task01 dry run. Report the model_url, model, gpu and port values from the dry-run output. Verify that the URL has no /v1 suffix before you run the test.
  • Pair a Linux machine running agents with your phone

    Install BotBus on a Linux computer and pair it so agents on that box can be followed from your phone.

    View prompt
    On the Linux host, run `botbus pair` and report the pairing status. Then list the tasks BotBus sees on that host, grouped by project, and note any host that is offline.
  • Check what an app window shows after each step

    Read a window, act once, then read again to see only what changed.

    View prompt
    Using the macos-harness repo at https://github.com/browser-use/macos-harness, read <app name> with `macos-harness get_app_state`, perform the action in <test steps>, and read the window again. Verify and report only the lines that changed between the two reads, and state whether the expected change appeared.
  • Draw a sequence or data-flow diagram with CJK labels

    Get an agent to size Chinese, Japanese or Korean labels correctly so text stays inside its boxes.

    View prompt
    Using the svg-diagram skill from bybit-exchange/svg-diagram, draw a sequence diagram of <process> with CJK labels in diagram.svg, sizing each label from the CJK width table. Run the linter and confirm 0 errors and 0 warnings, with no text overflow findings.
  • Point Codex at a UI element to fix it

    Select an element on the device and attach an instruction with component details.

    View prompt
    Using the callstackincubator/codex-mobile-dev-plugin Mobile Dev plugin, take the annotated element on <device name> with the instruction <instruction text> and apply the change in <project path>. Expected output: the component source edited to match the instruction. Verify the component named in the annotation is the file that changed.
  • Use Codex with a local model on your Mac

    Launch Codex against the Slotstream model so code tasks stay on your machine.

    View prompt
    In the carloslfu/slotstream repo, run `slotstream launch codex` from <project path>. Expected output: Codex opens connected to the local model. Verify by asking it for a one-line code explanation of <file name> and confirming it responds.
  • Turn a chat request into a macro on your action bar

    Ask for a macro, click Create macro, and drop it on an action bar from the cursor.

    View prompt
    In the wow-ai repo, with the bridge running, ask the chat agent for a WoW macro that <goal>. Expected output: a reply with a Create macro button. Verify the button is present and that the macro is on the cursor after clicking it.
  • Let the model fetch only the images it needs with Auto-select

    Keep Auto-select on so earlier images are left out by default and the model asks for the ones it needs by ID.

    View prompt
    Using the repo chipfighter/context-attachment-manager in Codex, keep Auto-select on for the task <task name> and mark <reference image ID> as Send every turn. Ask the model to continue the image work, then list which IDs it requested with need IMG-xxx and confirm that the fetched images are the only earlier ones sent that turn.
  • Record short gameplay clips of NPCs talking to each other

    Produce 5 to 10 second conversation clips with a fixed gameplay camera and lines rendered first.

    View prompt
    Using the NPCTalk repo at https://github.com/christos-antono/NPCTalk, run the npc-showcase-clips skill to plan a 5 to 10 second conversation between <npc-a> and <npc-b> in <game-name>. Expected output: a planned shot list and rendered line WAVs with timings. Verify that the clip stays within 5 to 10 seconds and that `npctalk check` passes before anything is shared.
  • Have one agent spawn and coordinate other agents

    Use the built-in MCP server so a lead agent can hand tasks to other agents and read their output.

    View prompt
    Using the diri repo at github.com/cristicretu/diri, have the lead agent spawn helper agents through the built-in MCP server to split <job-description> into subtasks. Output the list of helper agents, their tasks, and their results, and verify that each helper reported an output.
  • Pull matching lines from a long or endless web page

    An agent scrolls a feed until a term appears, then returns only the matching lines.

    View prompt
    Using the axuse MCP server, open <page URL>, scroll until the text <search term> appears, then observe only the lines matching that text. Return the matching lines as a list, and check that each line appears in the page when you observe it again.
  • Prove each change with parallel tests and a source-bound proof

    Run the test gate for a task, queue busy resources and attach proof tied to the frozen code.

    View prompt
    Using the Squadra repo at https://github.com/dagoSte/squadra, prove task <task ID> in the project at <project path>. Expected output: a proof record bound to the current source state. Verify with `squadra doctor --quick` that the registry is healthy before you rely on the proof.
  • Let a cloud agent read files on your Mac with set limits

    Give a cloud agent access to your Mac at the level you choose: Off, Read-only, Ask first, or Full.

    View prompt
    In the Cloudroom app from the cloudroom-gui repo, set Mac access to Read-only for a cloud thread and ask it to read <file path on the Mac>. Expected output: the file contents reported back, with no edits. Verify that the Mac access level shows Read-only during the run.
  • Run the Deep Research example to produce an HTML report

    Clone the repo and run a bundled example that researches angles in parallel and builds a report.

    View prompt
    Using the deer-workflow repository (deerwork-ai/deer-workflow), follow examples/deep-research/README.md to run the Deep Research example on the topic <target topic>. Expected output: an interactive HTML report. Verify that the report includes the claims verification step described in the example README.
  • Share agent accounts with a team and track usage

    Pool Claude and Codex accounts, scope them per user, and export usage costs as CSV.

    View prompt
    Use the agentbox repo at github.com/devilcoolyue/agentbox on the server <server-host> to scope the account pool to the users <user-list>. After a test request, open the Usage view and confirm that a record appears with tokens and a price snapshot, then export it as CSV.
  • Create an engineering drawing from a CAD model

    Ask your agent to turn a generated 3D model into an engineering drawing.

    View prompt
    Using the text-to-cad plugin from https://github.com/earthtojake/text-to-cad, generate an engineering drawing from <model file path>. Return the drawing file path and list the dimensions it shows so I can compare them with the model.
  • Rewind a Git-backed agent task to a checkpoint

    Roll an agent's Git-backed work back to an earlier conversation point when a change goes wrong.

    View prompt
    In the waku app, open the Git project at <project path>, run an agent task called <task name>, and rewind it to the checkpoint <checkpoint name>. Expected output: the project files and conversation match the checkpoint. Verify with `git status` in <project path> that the working tree reflects that earlier point.
  • Find z-fighting and floating parts, then export to Roblox

    Have an agent check a model for z-fighting, floating parts and bad normals before exporting it to Roblox.

    View prompt
    Using the blender-skills repo, check <model file> for z-fighting, floating parts, bad normals and bad weights, fix what it finds, then export it for Roblox. Expect a QA list before and after the fixes and the exported file. Verify that the second QA pass reports no remaining issues before the export runs.
  • Install one skill or MCP server for many harnesses

    Add a SKILL.md or remote MCP server once in Settings and use it across supported harnesses.

    View prompt
    Using the repo emo-xiaoyu/harness-mix, install the skill at <path to SKILL.md> at Global scope and register the remote MCP server at <server URL>. Report the install location for each harness and confirm that the skill is listed in one harness session.
  • Share a session map without prompt text or file contents

    Build a path-redacted map and export one session as a file that carries no prompts or file contents.

    View prompt
    In the agentplay repo at https://github.com/Entelligence-AI/agentplay, rebuild maps with `--path-mode dirs_only`, then export the session <session id> to <output file>.json. Report the repo names and the number of paths the export tool says it contains. Verify that the exported file has no prompt, assistant, or tool output text.
  • See which coding agent is using which simulator

    Track Claude Code and Codex device calls per session and claim devices so agents stop colliding.

    View prompt
    Using the simfleet repo (entropyconquers/simfleet), run `simfleet agents` from inside a Claude Code or Codex session in <path-to-app>. Expected output: the live agent sessions and the devices they have touched. Verify that after `simfleet claim <device-id>` the device is listed as held by this session.
  • Build with Opus through Claude Code, then check in Codex

    Let Opus implement a whole assignment, then have the Codex host verify it in the browser.

    View prompt
    With the codex-on-crack package in <project folder>, have Opus 5.5 implement <assignment> through Claude Code, then ask the Codex host to open the result in the browser and report any problems. Expected output: the implementation plus a browser check summary. Verify that the browser evidence comes from the Codex host, not from the Claude session.
  • Find failing and slow tool calls in an agent run

    Filter a session for reported errors and long durations, then review heuristic patterns.

    View prompt
    Using the TraceCrate repo at <repo path>, start the dev server and load <session file path>. Expected output: a Timeline filtered to reported errors or events above a chosen minimum duration, sorted longest first. Verify that events with missing duration are excluded when a minimum is set, and that heuristic flags are treated as hints, not confirmed causes.
  • Turn a failing Playwright test into a bug-report video

    Create a narrated film of the failing steps plus a Markdown summary for the issue.

    View prompt
    Using the showtime skill in the FavioVazquez/showtime repository, run `showtime repro` on the Playwright trace for <failing test>. Expect a narrated film and a Markdown summary in showtime-out/. Verify that no typed values appear in the film or the summary.
  • Diagnose a motion video that reads like a slideshow

    Run the continuity check on an existing motion video to find the cuts where nothing carries over, then fix them.

    View prompt
    Using the onetake skill in the feitangyuan/onetake repo, run the continuity check on <video file or source> and list every boundary where no element carries into the next beat. Output the failing boundaries with a carry score for each. Verify that the score is higher after you apply the proposed fixes.
  • Have two agents on one machine agree a work split

    Let a Codex session find a Claude Code session on the same repo and message it directly.

    View prompt
    Run `flopwire peers` in the flopwire/flopwire context and list the live sessions on this machine. Send <message text> to the session <session-id> with `flopwire send <session-id> -- "<message text>"`, then confirm the send by checking `flopwire messages` for the outgoing message.
  • Point at the right browser tab out of many

    Raise a Chrome window and point at one tab by its title.

    View prompt
    Use the bigarrow CLI from franzenzenhofer/big-arrow-on-the-screen to raise the Google Chrome tab titled "<tab title>" and point at it with the sign "<sign text>". Expected output: the tab is selected and the command exits with code 0. Verify the exit code and report the tab title that was selected.
  • Print a session's agent tree without opening the TUI

    Dump the session tree to the terminal headlessly for logs, notes or scripts.

    View prompt
    In the zoetrope repo (furkankly/zoetrope), run `zoe inspect` on the session file at <session-file-path> and save the output to <output-file>. Expected output: a printed session tree with the main session and its subagents, written without starting the TUI. Verify that the output file is not empty and lists at least the main session before reporting success.
  • Build beat-synced motion graphics for a short video

    Use BeatGrids and LayerAnimation to time text and shape motion to the beat of a music track.

    View prompt
    In the framefields repo, build a composition that places text from <lyrics or headline list> on the beats of <audio file>, animating each entrance with LayerAnimation, and render it to output/<name>.mp4. Expected output: an MP4 whose text moves start on beat frames. Verify by checking the BeatGrid timestamps against the keyframe start frames.
  • Remove Fire TV preloaded apps without a new launcher

    Disable preloaded Fire TV apps over Wi-Fi. The home screen stays as Amazon ships it, because Fire OS will not hand Home to a third-party launcher.

    View prompt
    Using the Gathin23/cleanyourtv repo as context, debloat the Fire TV at <tv-address> on the local network by disabling only the preloaded packages I approve with pm disable-user. Expected output: a backup of the package list and a list of disabled packages. Verify that the Fire TV home screen still loads and that no package was uninstalled.
  • Batch-create several distinct poster concepts at once

    Delegate five different poster designs and generate them in one bounded parallel run.

    View prompt
    Using GPT Image Skill in <repo path>, create <number> distinct poster concepts for <campaign brief> at <aspect ratio>. Expect one PNG per concept in /generated-images, each with its own filename. Verify that the prompts differ in composition and not only in wording.
  • Share a tested bot with a teammate by code

    Export a bot's settings and instructions so a teammate can import the same bot.

    View prompt
    Using the gitbot-hq/GitBot package, export <bot name> with Share with code and import it on a second machine with Import bot. Expected output: an imported bot with the same instructions and permissions and no chat history. Verify that the agent named in the bot is installed on the second machine before the first thread runs.
  • Capture a hard-won lesson as reviewed memory

    Turn a debugging finding into a scaffolded memory that goes through normal code review.

    View prompt
    In the repository grpcer/ownmem, scaffold a memory named <memory_slug> with `npx ownmem new <memory_slug>`, then fill in the cause and the fix from <the debugging session>. Expected output: a new .ownmem/<memory_slug>.md file that passes the gates. Verify that `npx ownmem recall -- "<a phrase from the memory>"` returns it with an advisory trust line until evidence is attached.
  • Archive a Flow project's media locally at no cost

    Download existing images, clips and stitched films from Flow, including 1080p upscales, without regenerating.

    View prompt
    Using the flow-mcp repo at <repo-path>, list the assets in the open Flow project and download all videos and images with the free download tool, including the 1080p upscale where available. Expected output is local media files in ~/flow-mcp-out/ with one stitched film per scene. Verify that the credits remaining shown by flow_status did not drop during the download.
  • Strip AI marks from files inside a Codex project

    Install the full skill into one project and call the local service from Codex.

    View prompt
    In Codex, use the remove-ai-marks skill from the watermarks-remover repo to inspect <file path> through the local service at http://127.0.0.1:8765. Report the provenance marks found, then clean the file and report whether a second inspection shows none.
  • Connect the cheapest API to your coding agent

    Store a key hidden in your terminal and let Grandet write a backed-up config change to your agent.

    View prompt
    Using the Grandet Skill connect program for <app name, for example Codex or Claude Code>, connect the chosen API for <model name>. Show the configuration change before writing, confirm the backup was made, and report the result of the key, group and model name check.
  • Search and convert a Calibre ebook library with an agent

    Have an agent search, read metadata from, and convert books in a Calibre library through its CLI.

    View prompt
    Using the HKUDS/CLI-Anything Calibre CLI, search the library at <library-path> for <search-term>, then convert one matching book to <format>. Report the matched titles and the output file path. Verify that the converted file opens or has a non-zero size.
  • Continue an earlier agent conversation in a writable room

    Import a Codex or Claude Code history and continue it in a normal room without changing the source.

    View prompt
    In the PeerBridge MCP control room, import only the Codex conversation <conversation-id> from the agent history list and use Continue from history to create a writable room. Report the new room ID, and verify that the source room remains read-only.
  • Try the terminal interface without installing

    Run the latest hmz release from uv's cache to test the terminal interface first.

    View prompt
    Using the humanize repo (hmz), run `uvx hmz@latest` inside <scratch-repo-path>. Report the first screen or prompt the interface shows, as plain text. Verify that the interface opened from the scratch repository and did not change any files in <scratch-repo-path>.
  • Watch figure objects draw live in Mac PowerPoint

    Set up the optional Office.js add-in so each object appears in Mac PowerPoint as it is drawn.

    View prompt
    In the scientific-illustrator repo on macOS, run the officejs-setup.mjs prepare and sideload steps, then confirm that powerpoint_officejs_status reports connected=true with the Scientific Illustrator Live task pane open. Verify the connection before asking the plugin to draw the uploaded figure in PowerPoint.
  • Locate failed and slow tool calls in past Codex runs

    Search and filter earlier task history to find failing or slow tool calls and inspect them.

    View prompt
    Using the icesixgod/codex-trajectory repo, search the history of the Codex task <sessionId> for failed or slow tool calls and list the matching events with their durations and status. Verify that each listed event has a status and that zero and sub-millisecond durations are not reported as failures.
  • Reopen a saved tour without waiting for the LLM again

    Return to a change you toured earlier and open its saved tour instantly.

    View prompt
    In the repository at <path>, open the saved tour for the branch <branch> with tour. Expected output: the tour opens without the writing step. Verify with `git status` that the repository is unchanged.
  • Turn a site's scroll animations into a runnable GSAP stub

    Census a live page's scroll motion and generate a single-file GSAP ScrollTrigger starting point.

    View prompt
    Use the awwwards-mcp server to run analyze_scroll_map on <target URL>, then pass the result to build_gsap_stub. Expected output: a runnable single-file GSAP plus ScrollTrigger stub with one timeline per census animation and a prefers-reduced-motion guard. Verify the stub opens without errors and that the timeline count matches the census.
  • Let an agent act only when it is confident

    Use Jev confidence scores to proceed on clear cases and escalate unsure ones.

    View prompt
    Use the evaluate tool from the itsmostafa/system-one-connector repo to answer this question about <case description>: <your question>. Proceed only if the top probability is at least <threshold>, otherwise return 'escalate'. Verify the returned confidence field matches the highest probability before deciding.
  • Audit token spend by agent, model and session

    Review 30 days of token history and estimated API cost per agent, model, session and turn.

    View prompt
    In the agent-hud-open repository, run `make run`, then open the statistics window and report the token total for the last 24 hours for each agent shown. Verify that the cost figures marked ≈ are labelled as estimates.
  • Make a verified task harder and measure its difficulty

    Derive a harder child task from a verified one, then measure it with fresh solver attempts.

    View prompt
    Using the EvoTrace repo at https://github.com/jinzijian/EvoTrace, run /harden 1 and then /calibrate on the resulting child asset in the DeepSeek Harness app. Report the calibration pass count out of attempts and the added behavior. Verify that the child task adds testable behavior, compatibility, edge cases, or failure constraints rather than only a longer patch.
  • Run the ASM workflow from the Codex project package

    Open the Codex project version and ask the agent to run an ASM modeling task.

    View prompt
    Open the autowwtp-asm-codex project at <repo-folder>/code/autowwtp-asm-codex in Codex and read AGENTS.md. Run the ASM modeling task described in <task-file> on the data in <input-file>. Expected output: a report and a final_result.json. Verify that the process checks file exists before reporting success.
  • Turn a long novel into a series episode outline

    Convert a long manuscript into a numbered episode outline with a series engine and bible, using the Chinese series skill.

    View prompt
    Using the screenwriting-skills repo (sw-chinese-series-practice and sw-series-engine-bible), read <novel synopsis or file> and produce a series engine statement plus a numbered episode outline for <target episode count> episodes. Verify that each episode has a distinct turn and that the engine statement is stated before the episode list.
  • Compare your site against a competitor's

    Score two sites side by side with the same rubric and evidence.

    View prompt
    Using the juliobsz/skills repo, run /jury on <your URL> vs <competitor URL>. Expect two scorecards in the .jury/ folder with the same categories. Verify that both sites were scored with the same rubric and that each score cites its screenshots.
  • Export a favicon, app icon and web manifest set

    Generate a complete favicon, app-icon and web-manifest set from a finished SVG logo.

    View prompt
    Using the export tools in kaankiziltug/logo-design-skill, generate a favicon, app-icon and web-manifest set from <path to logo.svg> into <output folder>. Return the file list. Verify that each expected icon file is present and that the manifest references them.
  • Export one edit to nine social platforms at once

    A single render command makes a file for each platform template and a summary table.

    View prompt
    Using the ffmpeg-skill repo, render <source video> with --template all so it covers every platform template. Expected output: one file per platform plus a _pack.md summary table. Verify the summary lists every destination and that each output probes correctly.
  • Recheck an old FY 2025-26 tax result after the 1.3.0 fix

    Recompute your FY 2025-26 tax to see whether an earlier install understated new-regime tax.

    View prompt
    Using the itr-wala repo at <repo-path>, update to version 1.3.0 or later, then recompute the FY 2025-26 tax for <your-income-file>. Expected output: a recomputed new-regime total and the difference from the earlier result; verify the engine version is 1.3.0 or later before comparing with the filed return.
  • Map how a feature works across an unfamiliar repo

    Use agy's researcher persona to survey a topic in a codebase you do not know yet.

    View prompt
    Using the keli-wen/agy-staff plugin, ask the researcher persona how <topic> works in <repo>. Expect a written report on that topic. Verify that the report cites specific files or functions it read.
  • Check another agent's "done" claims before accepting them

    Verify each claim from another session against what actually happened, then get a next action.

    View prompt
    In the open-steps repo at <repo-path>, use the os-check-work skill to verify the claims in the report from <other-session> about pull request <number>. Expected output: each claim marked against what actually happened, followed by one recommended action. Verify that no claim is accepted without a check.
  • Shortcut a repeated status check for your team

    Save a status-check request as a project slash command that reports and never writes.

    View prompt
    In the project at <project_path>, use the faq-shortcuts skill from cli-faq-shortcuts to create a shortcut for my repeated status check. Expected output: a SKILL.md under .claude/skills/ that names the existing script or query it uses and reports without re-sending. Verify that the shortcut runs its query and reports the result.
  • Stop tool use when a session shows a mismatch

    Turn on halt_on_mismatch so Codex blocks tools until you say resume after a mismatch.

    View prompt
    In the kiyoakii/is-gpt-nerfed repo, set halt_on_mismatch to true, then confirm the setting is saved with `nerfed config` output or the app Settings. Report the current value and whether a mismatch has blocked tools in any session.
  • Get hint-only /compact advice in Codex CLI on macOS or Linux

    Install the Compact Adviser hook in Codex CLI to see a compact hint after each finished turn.

    View prompt
    Install compact-adviser in Codex CLI on <target macOS or Linux machine>: add the kunchenguid/compact-adviser marketplace, add compact-adviser@compact-adviser, then restart and trust the hook in /hooks. Expected output: a Compact adviser hint line appears after a completed turn. Verify the hook is trusted before reporting success.
  • Run a Codex agent next to your Claude Code agents

    Switch one character from Claude Code to Codex and follow its terminal on the Mac.

    View prompt
    In the chums repo at <target-folder>, run bin/chums-codex and confirm a Codex terminal opens on the same conversation as the watch agent. Expected output: a Codex session you can follow on the Mac. Verify with bin/chums-doctor that the Codex path reports no failures.
  • Build a seamless 10-second muted loop for a landing page

    Render a looping feature animation that autoplays without sound on your site.

    View prompt
    Using the cinetic skill in Leonxlnx/cinetic, make a 10-second 1920x1080 feature loop with no sound that shows <feature name> from <product name>. The loop must join seamlessly at the end frame. Verify the first and last frames match before you report the file path.
  • Have a main agent delegate bug work to parallel chats

    Use one coordinating conversation to split a bug into investigation, fix, and test conversations.

    View prompt
    In the LodyAI/Lody repo, act as the coordinating conversation for the bug <bug-description> in the workspace <workspace-name>. Create or reuse child conversations for investigation, implementation, and testing, then report each child conversation's status. Verify the statuses against the output of `npx lody session list --workspace <workspace-name>`.
  • Test two candidate models before choosing one

    Run both candidates as cheap exploratory runs and record why one was selected.

    View prompt
    Use the Modeling Workbench repo in <tool folder> to compare two candidate models for the problem in <project folder>. Record an exploratory run for each candidate, select one with a written rationale, and run the model-design check. Verify the comparison table lists both candidates and the selected one cites its runs.
  • Compare Codex and Claude Code on the same capture

    Run the same capture with both supported agents and compare the resulting poses.

    View prompt
    In the agenticSTAR repo, run tools/run_kf.sh on examples/garden_shears/capture:0 once with --agent codex and once with --agent claude. Expect two runs/ directories, each with mesh/pose.json. Verify that both runs finished or hit their timeout before comparing outputs.
  • Triage the customer inbox with drafted replies

    A Customer Satisfaction Employee sweeps your inbox and drafts replies, hardest cases first.

    View prompt
    Using the ai-employees repo, install the Customer Satisfaction Employee into <target folder> and confirm it sweeps the inbox on schedule. Expected output: replies drafted hardest first and churn flags with evidence. Verify that no reply is sent until you approve it.
  • Fix a bug with a failing test before the fix

    Diagnose a bug in phases, then drive a red-green-refactor loop to fix it.

    View prompt
    In the mattpocock/skills repo, use diagnosing-bugs on this failure: <bug description>, then use tdd to write a failing test before any fix. Expected output: a root-cause note and a red test that turns green after the fix. Verify that the test fails on the unfixed code before you accept the change.
  • Audit desktop packaging, signing and CI config

    Check a desktop JVM build for packaging, code-signing and CI traps before a release.

    View prompt
    Using the desktop-and-build-footguns skill from kotlin-footguns, audit the build and CI files at <project path>. Expected output: a table of matched traps with file and line, and a verification result for each. Verify that every verification command you run is one the trap file lists, and that you did not invent any new command.
  • Carry your preferences and procedures into new sessions

    Keep your language, tone, and checklist habits available to the agent in every new session.

    View prompt
    Use the MemoraX Code skill to remember my preferred result format and my review procedure for <task type>. In a new session in <project path>, apply both before you answer and list which saved preference and procedure you used. Verify that the procedure's validation gate is stated in your answer.
  • Tune a theory paper's stance, keep theorems and assumptions

    Adjust contribution wording in a theory paper while leaving formal statements unchanged.

    View prompt
    Use the game-the-llm-reviewer skill from Michael-Jiahao-Zhang/game-the-llm-reviewer on paper/main.tex in <path to project>. Adjust contribution stance only, and preserve theorem assumptions, quantifiers, and the distinction between an upper bound and an optimal rate. Verify with a diff that no theorem, lemma, or assumption text changed.
  • Review token use and cost by agent and model

    Filter usage by date, agent, model, or provider to see where tokens and estimated spend went.

    View prompt
    Use the agentacct repo at https://github.com/mikehasa/agentacct to report token totals and estimated cost by agent and by model for the last 7 days on this machine. Verify that cost figures are labeled as estimates and that the local data freshness stamp is shown.
  • Connect a custom domain and transactional email

    Point a domain you own at the live app and set up sending through Resend.

    View prompt
    Use the golive skill in the repo <repo-path> to plan a custom domain DNS change through Porkbun or GoDaddy and transactional email through Resend. Show the zone and each record in the plan before any write, then report what was applied and what remains manual.
  • Audit existing code and remove AI-slop comments

    Run antislop in After mode to get a numbered list of comment fixes you approve.

    View prompt
    Using the antislop-code rules from the anti-slop repo (https://github.com/miqdadbadjuber/anti-slop), audit the comments in <project-folder>. Return a numbered findings list, then wait for approval before editing. Verify that no approved fix changes code behavior, only comments.
  • Send prepared prompts to ChatGPT with Zero Risk mode

    Use a manual paste-and-send flow when you do not want the launcher to operate the ChatGPT page.

    View prompt
    Using the codex-chatgpt-web repo, prepare a Zero Risk prompt for <task description> and list the exact model and Codex Zero Risk connector the user should select. Expected output is the prompt text and a checklist of manual steps. Verify that you did not send the prompt yourself and that the user confirms Sent in the launcher afterward.
  • Check commit messages and staged changes against AGENTS.md

    Judge each commit message against its diff and each change against repo instructions.

    View prompt
    In the repository <repo-path>, with TYPESAFE_API_KEY set, run `npx jev-lint commits --base main` and then `npx jev-lint commits --staged`. Report each finding that cites an AGENTS.md instruction or a commit message mismatch, and confirm each cited instruction exists in the file.
  • Repair weak image-to-video clips in a poem project

    Find clips with broken animals, rebuilt buildings, or bad transitions and redo only those clips.

    View prompt
    Use the classical-poem-silk-video skill from https://github.com/Mr-funny/hbg-classical-poem-silk-video to review the image-to-video clips in <project folder>. Name each failing clip and rebuild only those clips without changing the camera. Verify with final_media_qa.sh that the rebuilt final MP4 has no black frame at the transition midpoints.
  • Draft a blameless postmortem with the Codex plugin

    Write a postmortem that names mechanisms, timestamps, and owned action items.

    View prompt
    Using the sepia repo, run its write operation to draft a postmortem from <timeline notes file>. Expected output: a postmortem with timestamps, dead ends, and owned action items. Verify that every timestamp matches the timeline notes.
  • Have a coding assistant install and check GPT with Taste

    Give a coding agent the repo and install guide so it handles setup.

    View prompt
    Use the repository at <repo-path> and follow docs/install-for-ai.md. Run `node scripts/check-updates.mjs`, then install with `node scripts/install.mjs --hooks`, and list every file written under the active CODEX_HOME. Verify that the hook definitions are still untrusted until a person reviews them under Settings → Hooks.
  • Open ChatGPT with terminal access to a project

    Open ChatGPT in the browser with terminal access to the current project or a folder you name.

    View prompt
    Using the WebGPT repo (Nhahan/WebGPT), run `webgpt open /path/to/project` with the project path <project path>. Expect ChatGPT to open with terminal access to that folder. Verify the session is pointed at the correct project before giving it any task.
  • Refactor in scored steps until deltas plateau

    Use previousEvaluation so the agent sees which dimensions improved or regressed.

    View prompt
    Refactor <module path> with the jev_review tool from NiazMorshed2007/jev-review. Call it for a baseline, then after each change call it again with previousEvaluation set to the prior result. Report the per-dimension deltas and any regressions, and confirm that the project's existing tests still pass after each step.
  • Isolate agent work on a branch and finish it cleanly

    Keep agent changes in their own worktree and branch, then merge, open a PR, keep, or discard them.

    View prompt
    Using the Superpowers skills from the obra/superpowers repo, create an isolated worktree on a new branch for the approved change <change name> in the project at <project path>. Expected output: a new branch with a clean test baseline and, at the end, a finishing-a-development-branch summary of the options. Verify that the test baseline result is reported before any code is changed.
  • Pin a city street photo using public street-tree data

    Use a city's open street-tree records and street features to find the block in a street photo.

    View prompt
    Use the geo-sleuth skill from the Oldcircle/geo-sleuth repo to find the block where <path to street photo> was taken, starting from public street-tree data for <city>. Expect a block with an error of a few metres and a list of the trees and checks behind it. Verify that each claim names the file or command that supports it.
  • Look up security advisories for a dependency

    Query the OSV database for a GHSA, CVE, or ecosystem id and read a compact result.

    View prompt
    Use the only-cli/oc repo: run `oc osv vuln <advisory-id>` with the id from the dependency alert. Expect a compact advisory view with the affected package and versions. Verify the id in the output matches the alert before acting on it.
  • Map a diff's impact and generate tests for uncovered paths

    Get an impact report and runnable test files for the paths a change left untested.

    View prompt
    Use codexqa-change-analysis on the diff between <base-branch> and the current branch in this repo. Write one HTML change-impact report and add runnable test files for uncovered points without editing existing test files. Verify that the report lists which methods changed, the entries that reach them, and the uncovered paths.
  • Find which code writes a field that goes wrong

    Watch a field for access and modification, then read the stack at each change.

    View prompt
    Use the Debroid CLI to watch the field <field-name> in <class-name> of the app <package-name>. Run <user-flow> and then run `debroid poll --with-stacktrace`. Return each access or modification with its stack trace as JSON, and verify that the watched field name matches the one you set with `debroid points`.
  • Block a risky Codex action with a custom deny rule

    Copy a shipped rule, mark it enforce: true, and install it on a Codex pre-action hook.

    View prompt
    Use the repo perplexityai/numbat. Copy the shipped YAML for <rule-id> from rules/ into ./numbat-policy, set enforce: true and a new version, then run `numbat rules check --rules-dir ./numbat-policy`. Report whether validation passes and which rule ids are active. Verify that the enforcement record uses mode "enforce" only for the rule you marked, and that all other shipped rules remain monitor-only.
  • Cut extra copy and rewrite CTAs across several pages

    Click through linked pages in the review tool and trim copy without losing feedback between them.

    View prompt
    Use the petergyang/human-review skill to open <path-to-start-html-file> and review the linked pages. After I click Send, verify that the agent removed the repeated copy and updated each call to action in the HTML files, and list the files changed.
  • Turn your notes or transcript into a human-sounding work piece

    Build a post or memo on your own argument, order and examples instead of an AI draft.

    View prompt
    Use the work-humanizer skill from the phuryn/work-humanizer repo on my notes in <notes-file>. Build the piece on my claims, in my order, with my examples, and ask only about gaps. Output the piece and the fact audit. Verify that each claim in the piece matches a claim in my notes at the same strength.
  • Schedule automatic scans for new postings

    Set a Pro routine that saves new matching postings on Pinloop's servers.

    View prompt
    Using the pinloop-cli repo, read the output of `pinloop guide`, then set up a Pinloop routine that scans for <target role> on <schedule or new-posting trigger>. Expected output: a saved routine ID and a first set of saved postings. Verify that the routine is listed as active and that the saved postings match the search.
  • Refine rules after incidents and keep gates current

    Find rules without gates and stale contracts, then turn lessons from commit history into one PR.

    View prompt
    In the repo at <repo-path>, run `/gap-trap refine`. Return the list of rules without gates, stale contracts, and proposed playbook lessons. Verify that each lesson cites a real commit from `git log`.
  • Ship one approved feature with a second-agent check

    File a spec-linked item, let a builder claim and submit it, then have a verifier accept or reject the exact commit.

    View prompt
    In the repo <path>, file a Pullboard item linked to approved spec row G1, have a builder agent claim and submit it, then have a separate verifier agent run `pullboard verify <id> accept` or reject with a reason. Report the verdict and the note. Verify that the verifier checked out the exact submitted commit before deciding.
  • Document a service and fail CI when the docs drift

    Write checkable docs whose claims are anchored to code and re-verified on every build.

    View prompt
    In the repo <repo path>, write a claims-based document for the <service name> service in system.docs.json, run vibeX docs with --check, and report how many claims are verified. Verify that the check exits with code 1 when you change an anchored line in a test copy.
  • Switch between Codex accounts and API-key sign-ins

    Save each Codex sign-in, including separate ChatGPT plans and API keys, and swap them from the menu bar.

    View prompt
    Using the Janus repo at RamitVishwakarma/Janus, explain how to save each Codex sign-in on this Mac, including ChatGPT and API-key accounts, and switch to <target account email or key suffix>. Report the saved Codex accounts with their plan or key suffix. Verify that the live file at ~/.codex/auth.json now belongs to the target account.
  • Plan a walking route through a scanned space

    Ask your assistant for a path through the scanned free space from one point to another.

    View prompt
    Using the openreality MCP tools on the scene <scene id>, plan a path from <start point> to <target point> through the scanned free space and describe it step by step. Verify that the description names the start and target you asked for and notes any uncertainty the tool reports.
  • Update a workflow diagram after the code changes

    Ask the assistant for a refined revision and see what was added, removed or changed.

    View prompt
    In the repo <target-project>, refine the MLView diagram <diagram-file>.mlview.json to reflect my recent edits to <changed-file>. Expect a new revision whose Changes since summary lists the affected steps. Verify that the new revision's changed items all cite lines that exist in the current files.
  • Find the real callers before changing a behavior

    Use the callers flag to see whether production code actually reaches a function.

    View prompt
    Use ripwire on the repo at <path>. Run the --callers flag on <function name> and report every production caller it finds. Verify the result by opening each reported call site.
  • Keep every new video on brand with saved components

    Set a project brand once and save animations as components to reuse in later videos.

    View prompt
    In the Remocn Studio project at <project folder>, create a new video called <video name> that uses the saved project brand and the component named <component name>. Expect a new folder under src/videos with an index.tsx scene. Verify that the colors and fonts in the scene match the brand in brand.md.
  • Shoot product packshots and scenes from a real photo

    Turn one real product photo into packshots and lifestyle scenes with label checks.

    View prompt
    Using the scenario-labs/skills repo, create packshots and lifestyle scenes from the product photo <photo-path> for the scenes in <scene-list>. Save approved images to <output-folder>. Verify that the label text in each approved image matches the original photo.
  • Get live summaries and minutes from your background agent

    Let MeetCap run your existing agent in the background to catch you up mid-meeting and write minutes after.

    View prompt
    Using the seacen/meetcap repository, configure MeetCap to run <agent name> in the background and record the meeting <meeting name>. Expected output: a live summary during the meeting and minutes when it ends. Verify that the minutes open with the reason for the meeting and that each point links to a transcript line.
  • Build the desktop app from source and run native checks

    Compile the Tauri desktop app and run the Rust and frontend checks listed in the README.

    View prompt
    In the repository sevensir888/codex-command-center, run the native checks listed in its README and report the result of each as pass or fail. Output a table with one row per command. Verify that `npm run check:secrets` reports no tracked-file secrets before any commit.
  • Add a prose contract to AGENTS.md and Cursor rules

    Write the Sloptrim contract into a project so Codex or Cursor agents follow it.

    View prompt
    In the project at <project path>, run `/sloptrim init` and report which files were written. Verify that AGENTS.md exists and that a Cursor rule exists under .cursor/rules/.
  • Have an agent order from your iPhone via Mac mirroring

    Let an agent drive your iPhone through the Mac's iPhone Mirroring window to finish an app errand.

    View prompt
    Using the phone-harness repo at https://github.com/ShawnPana/phone-harness, use the iPhone Mirroring window on this Mac to complete the errand <errand description>. Stop before the final payment confirmation and report the screen text, then verify the order details match the request before approving the last step.
  • Build and run the game from source on your computer

    Install dependencies, build, and start the local server from the repository.

    View prompt
    In the cloned Infinite Pokémon repository, run npm install, npm run build, and npm start, then confirm that http://127.0.0.1:8788 responds. Report the build result and any Node SQLite experimental warning that appears.
  • Score, dedupe, and report findings for a write-up

    Turn a raw findings list into a deduplicated, CVSS-scored report with an integrity hash.

    View prompt
    Using the blitzstrike MCP server, call dedup_findings on <findings list>, then cvss_score for each group, then generate_report in <markdown or json>. Return the report with a summary and the SHA-256 integrity hash. Verify that every group has a CVSS base score and severity.
  • Fan a task wave out to parallel Codex or Claude Code sessions

    Claim conflict-free tasks and run each in its own sandboxed agent process.

    View prompt
    In the Hyperfide repository, run `hyperfide spec run` for wave <wave number> using Codex CLI or Claude Code. Report each claimed task, its log location, and its final status. Verify that no two tasks declare overlapping paths before the run starts.
  • Create a Codex pet with no OpenAI API key

    Generate a companion through local open-weight editing and avoid hosted image APIs entirely.

    View prompt
    Using the repo six-nut/PocketMen-with-you, run `pocketmen create` with --engine neural --backend flux2-klein-4b on the references at <photo-1> and <photo-2>. Expected output: pet.json and spritesheet.webp, with no OPENAI_API_KEY set. Verify that the final package contains only pet.json and spritesheet.webp.
  • Read a one-page brief when you come back to the desk

    Get one page of what got done, what is stuck, and what waits for your answer.

    View prompt
    In the repo <repo-path>, produce an away brief with the away brief skill from Sno Station Skills covering the last <time-window> of agent activity. Output at most 60 lines with done, stuck, waiting-for-you and quota-cost sections. Verify that every stuck item names a reason.
  • Review the skill changes Self Learning proposes each morning

    Read the nightly proposals and accept only the ones you want applied to your agents' skills.

    View prompt
    In the sno-station repository, review the proposals from the last Self Learning run and accept only the ones I approve using `sno rem-reflect accept`. Expected output: a list of accepted and rejected proposals. Verify that no skill changed for a proposal you did not accept.
  • Scope a firmware or driver fix from a documented case

    Adapt a published exact-build patch or driver fix to your own device after checking its limits.

    View prompt
    Using the songshikang0111/awesome-REA-cases repo, open the case for <device and problem>. List the exact build, hardware, and test conditions it reports, then compare them with my device build <build number>. Output a go or no-go decision with reasons, and state which claims the README marks as not independently reproduced.
  • Prepare a development machine for agent-driven work

    Install and record the tools, agents, and integrations needed before starting projects.

    View prompt
    Read the repo soumatheusgomes/vibe-coding-toolkit at docs/prompts/10-development-environment-setup.md and execute the entire Prompt section on this computer. Report installed versions, backups made, validations passed, and any required manual steps. Verify that the manifest of versions and scopes was written.
  • Hand off a stuck task to another agent

    Pass a session's task, diff and failed commands to a new Claude Code or Codex session.

    View prompt
    Using the Tellurion repo at https://github.com/steventsvik/Tellurion, hand off the Claude Code session in <project-folder> to a new Codex session with the Review action. Report the diff size included in the handoff. Verify that the handoff message lists the failed commands from the first session.
  • Install the SyncSo skill into coding agents

    Use npx skills add to load the SyncSo skill into Claude Code, Codex or Cursor in one command.

    View prompt
    Install the SyncSo skill from SyncSo-Inc/syncso into this project with npx skills add SyncSo-Inc/syncso. Then ask the installed agent for three live events in New York this weekend. Verify that the result includes times, prices and booking links, and that the skill was loaded from the repo.
  • Give Codex threads in T3 Code shared project memory

    Run the T3 Code installer so Codex and Claude Code providers in T3 Code get Claude Mem memory.

    View prompt
    Run `npx claude-mem install --ide t3code` on this machine, then restart T3 Code and start a new Codex thread in <project path>. Report which providers the installer discovered and whether the new thread shows prior context. Verify the installer output lists the Codex provider.
  • Cut off dangerous tool calls from a relay before the client runs them

    Stop answers that download code, read credentials or add startup items before Claude Code or Codex executes them.

    View prompt
    Using the repo ThinkWatchProject/ThinkWatch-Lite, enable the Dangerous commands protection for the upstream <upstream name> and report which rules are in Monitor mode and which are enforcing. Expected output: a list of rules with their action. Verify that a test answer containing a flagged tool call is recorded in the request history.
  • Install the Jev Harness skill in Codex

    Add the jev-harness skill to Codex and use it to plan a harness for your task.

    View prompt
    In Codex, install the jev-harness skill from https://github.com/TianyuCodings/JevHarness and then run it on the task: route <ticket type> to the right team. Expected output: a list of clarified inputs, legal actions, examples, and success criteria. Verify that the skill is discovered before the task is sent.
  • Correct a stale memory without losing its history

    Update or replace a wrong memory while keeping the old version for lookup.

    View prompt
    Use the agent-memory repo at <store path> to correct the memory at <memory path> so it reflects <new fact>, keeping the old version for as-of recall. Expected output: the new memory path and the superseded status of the old one. Verify that a normal recall returns only the new version.
  • Audit a site before launch, regardless of its framework

    Test a React, Vue, Next, WordPress, or static site with the same checks before it goes live.

    View prompt
    Using the tigerless-labs/seo-ops skill, check <target-url> and save the pass/fail report as a baseline. After the migration, check the new URL with the same skill and list every check whose result changed. Verify that both reports cover the same 26 checks before comparing them.
  • Review and merge simplification findings from a PR

    Check simplification suggestions from a pull request or another agent, keeping the evidence and dropping the rest.

    View prompt
    Use $simplify-codebase to review and consolidate the simplification suggestions in <PR link or notes file>. Keep only findings with evidence and reject the rest with a reason. Expected output: a consolidated list with proof records and rejected items. Verify that every kept finding names its consumers and deletion boundary.
  • Wake an on-call agent the moment logs or metrics spike

    A watch on your logs or metrics wakes an agent within seconds to find the cause and fix or roll back.

    View prompt
    Using the Overtime repo at ukanwat/overtime, create an on-call agent with a watch on <log or metric source>. Expected output: after a test alert, a cause summary, the action taken, and a postmortem file. Verify that the agent wakes within the watch interval and asks before any change it has not been permitted to make.
  • Render an HTML motion graphic to a frame-exact video

    Turn an HTML page with animations into a silent H.264 video, frame by frame.

    View prompt
    In the veedstudio/open-edit repo, render <page.html> to out.mp4 with the render command and a duration matching the page timing. Expect a silent MP4 that matches the animation timing. Verify that the output is not a single flat colour before you deliver it.
  • Run coding agents on a VPS or remote server

    Connect a remote Linux machine so agents run there while you start them from your desktop or phone.

    View prompt
    Using the vicoa-ai/vicoa repo, connect the VPS at <server-address> as a Vicoa machine and start a Codex session on <remote-project-path>. Confirm the VPS appears as a machine option and the session starts there. Report the machine name and session status.
  • Create an interactive lesson on eigenvectors or Bloch spheres

    Build a runnable visual study for a math or quantum topic from the catalog.

    View prompt
    Using the 3dviz-pro-max skill in <repo-path>, build a runnable interactive Three.js study on <topic, for example eigenvectors or the single-qubit Bloch ball>, starting from a matching recipe or example study. Report which catalog entry was used and which frames show the key points.
  • Build a video from your own narration audio

    Use the Remotion template with finished audio and a hand-filled timeline instead of the built-in TTS.

    View prompt
    In the anything2explainer repo, scaffold a new Remotion project at ~/work/<slug> with template/scripts/new_project.sh, add my finished audio file <path-to-audio> with a hand-filled timeline and subtitles, and render a 30-second preview. Verify that the preview plays with the audio and that subtitles line up with the spoken words.
  • Let agent sessions search and message each other

    Use vsearch, vrefer and vtell so one agent can pull in work from another session.

    View prompt
    In the VelaTerm project at <project-path>, have one agent session use vsearch to find earlier work on <topic>, then vrefer to read the best match. Expected output: a short summary of the matched conversation with its session name. Verify that the summary cites a real session from the tree before you act on it.
  • Coordinate parallel agents with one writer for publication

    Let workers prepare and inspect while one writer owns publication and cursor movement.

    View prompt
    Using the forward-implementation-first skill in <repo-name>, assign one agent as the single writer for publication and cursor movement, and have the other workers prepare and inspect <target-task>. Report the worker outputs that were verified before consumption and the final publication. Verify that no worker output was merged without a check.
  • Keep .env and key files out of ChatGPT reviews

    Use the default sensitive-file rules plus your own .c2cignore patterns to protect secrets.

    View prompt
    In the workspace at <workspace path>, add the pattern <pattern> to .c2cignore, then run c2c status and c2c doctor and report their output. Confirm that the sensitive-file rules still deny .env files.
  • Export an explainer as slides or a document for a briefing

    Turn a rendered explainer into PPTX, DOCX, PDF, or PNG output for a team meeting.

    View prompt
    Using the fireworks-open-eli5 Skill, render <spec.json> to <output.html> and report the export options available for a team briefing. Confirm the rendered HTML validates with the validate script before any export.
  • Generate and grade 20 copy variants before review

    Produce 15-20 copy variants, score them with an expert panel, and strip AI-sounding phrasing.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the copy module on the brief for <product or offer> and return 15-20 variants with expert-panel scores and de-slopped text. Verify that the top variants are ranked by score and that the scores are described as heuristics.
  • Plan an authorized engagement and assemble findings

    Turn your rules of engagement into a plan, then build evidence-backed findings and a report draft.

    View prompt
    Using the engagement-operations skills from the zero-lab-ai/skills repo, draft an engagement plan for <client-name> based only on the rules of engagement I provide. Return the plan, a findings list with evidence references, and a report outline. Verify that no target or action appears that is outside the scope I gave.
  • Get readable pseudocode from a native binary

    Use Hopper, Ghidra or IDA through your agent to see what one routine in a compiled program does.

    View prompt
    Use REA with my installed <Hopper, Ghidra or IDA> to analyze the binary at <path>, explain what <function or behavior> does, and show the pseudocode and references. Verify claims against the shown output.
  • Let a coding agent run voice jobs through the local API

    Have Claude Code, Codex or Cursor call Voice Studio's local API or MCP to generate audio.

    View prompt
    Install the VoiceStudio Electron app from github.com/debpalash/VoiceStudio following docs/install/agent.md, then use its local API or MCP to generate speech for <text> with the <voice name> voice. Expected output: an audio file at <output path>. Verify the file plays and the spoken words match the input text.
  • Generate a React component of a figure for a docs site

    Create a React or Next.js component version of an explainer figure for a documentation site.

    View prompt
    Using the skill in wheresryan22/anatomy, create a React component of <concept> for a Next.js docs page, with a static HTML preview. Expected output: one component file and one HTML preview. Verify that the component imports cleanly into your existing project before committing it.
  • Draft a literature review with traceable citations

    Synthesize papers on a topic and keep each claim linked to a citable source.

    View prompt
    Using the scientific-agent-skills repo and its evidence-traceable writing and literature synthesis skills, write a literature review on <topic> from the papers listed in <paper list>. Return a draft with a citation after each claim and a matching bibliography. Verify that every cited claim appears in the named source.
  • Export a finished diagram to PNG or SVG

    Save a generated diagram as a PNG or SVG file for slides, docs or a website.

    View prompt
    Using the diagram-design skill from cathrynlavery/diagram-design, export the diagram at <path to .html file> to PNG and to SVG. Verify that both files open and that text and lines are not clipped.
  • Create a short motion graphic or transparent overlay

    Build a sub-10-second unnarrated motion graphic as MP4 or a transparent overlay with the motion-graphics skill.

    View prompt
    Using the hyperframes repo at heygen-com/hyperframes, use the motion-graphics skill to create an 8-second logo sting with the text <headline> as a transparent overlay. Output the file and confirm the background is transparent in the render.
  • Reuse confirmed findings on a new binary

    Replay stored finding descriptions and successful queries against a later target.

    View prompt
    In the Ablation repo at ~/ablation, replay the stored confirmed finding descriptions and successful semantic queries against <new binary path>. Output each candidate match with the source finding it came from and a similarity note. Verify that every candidate is checked in the disassembly before it is reported as a finding.
  • Review and correct what the agent has written

    Read, update, or delete the Markdown memory files an agent produced to keep the project knowledge accurate.

    View prompt
    Using the Operator Memory repo (https://github.com/aerovato/operator-memory), review the Markdown documents in <project-path>/.operator/ for the module <module-name>. Expected output: a list of documents that conflict with the code, with each one corrected or removed. Verify by starting a new session and checking the agent cites the corrected spec.
  • Hand file edits on your Mac to Codex or Claude Code

    Let Comma read files on your Mac and delegate changes to an agent you already use.

    View prompt
    On a Mac with the Comma Mac app connected to Salix, ask Comma to read the files in <project folder> and pass the change <describe change> to Codex or Claude Code. Report the files changed and the commands run. Verify the result by reviewing the diff before accepting the Task.
  • Recover owner sign-in through a trusted agent

    Let one trusted agent mint a one-time sign-in link after you ask, if you have granted that permission.

    View prompt
    Run `agentpeerchat web --login` for me only when I explicitly ask, send the one-time link to me privately, and report whether the link was created. Never store the link in logs, reports or Git commits.
  • Set a price for your developer tool

    Stop guessing a number and see how to charge without giving the product away.

    View prompt
    Run pricing and market-to-devs-sell-to-buyers in the gtm-cofounder skills for <product name>. Expected output: a pricing recommendation with the reasoning and the evidence still missing. Verify that the recommendation names what real users need to confirm before the price is locked.
  • Approve agent browser actions from your iPhone

    Receive and approve browser actions on your iPhone with Face ID while away from the Mac.

    View prompt
    Using the Chrome Relay repo at aindeev/agent-chrome-relay, start a browser task on <site URL> that needs approval, and wait for the approval on the iPhone app. Expected output: the approval result. Verify that the request shows the page you expect before approving.
  • Turn a drawing into a step-by-step drawing lesson

    Create a captioned timelapse and step sheet that teaches how a picture is built.

    View prompt
    Using the anidoodle repo, rebuild <subject or drawing file> as a drawing lesson with a step sheet and a captioned timelapse. Return both files and confirm each step lists what to look for, how to do it and the common mistake.
  • Generate a Frida verification hook that fixes its own errors

    Create a Frida hook script for an APK and let the agent retry failed runs up to three times.

    View prompt
    Using the Seep Reverse Lab workspace, generate a Frida hook for <class-name> in <path-to-apk> with seep_apk_gen_hook and run it on the connected device. Expected output: hook_verify.js and the captured stdout. Verify that the run stops after three attempts if it does not succeed.
  • Keep the codebase index current as the agent changes code

    Let the MCP workflow flag changed files and have the agent update their entries after each verified task.

    View prompt
    In the repo <project-path>, make the requested change, run the tests, then update the AOCI entries for every changed managed file so the index is aligned. Report the list of updated entries and confirm the index is aligned.
  • Turn a playlist into study notes

    Read every video in a playlist and produce notes per lecture.

    View prompt
    Using the youtube-skills repo, list every video in the playlist <playlist URL>, fetch each transcript, and write one set of study notes per video with timestamps. Verify that the number of notes equals the number of videos returned.
  • Make diagrams match your brand from your site or CSS

    Point See Code at your website, stylesheet or colour list so diagrams use your palette in light and dark modes.

    View prompt
    Use the SeeCode skill from the Aryanutkarsh/SeeCode repo to learn the brand palette from <your website URL or CSS path> and then draw <describe the diagram> with it. Expected output: a diagram in the brand palette with light and dark versions. Verify that the palette shown before saving matches the brand and that label text stays readable.
  • Replay a past session and get a recap

    Scrub through an earlier session to see who worked when and get a recap of tool calls and files changed.

    View prompt
    In the repo Atoll92/agent-standup, open a past Claude Code session in replay and produce its recap. Report the agents, tool calls, commands, files changed and busiest agent. Verify the files-changed count against the session's own record before reporting it.
  • Wrap your team's toolchain as a harness

    Copy the hello-world example, check it, and install it as your own harness.

    View prompt
    In the openharness repo, copy store/examples/hello-world to ../<harness-name>, update its harness.json and AGENTS.md for <team-toolchain>, then run `harness dsh check ../<harness-name>`. Report the check result and confirm the harness installs with `harness dsh install ../<harness-name> --link`.
  • Use one project memory across Cursor and Codex

    Point Cursor or Codex at the same JEVMEM.md so the agent reads the same saved lines.

    View prompt
    In the repo at <project-folder>, run `jevmem init --tool codex` and then confirm that jevmem watch starts without errors. Expected output: a running watch process and no setup errors. Verify that a decision made in a Codex chat appears as a line in JEVMEM.md.
  • Audit an existing codebase with a triaged scorecard

    Onboard a legacy repository and get a triaged scorecard of its quality before an agent edits it.

    View prompt
    Run the procoder audit command in the repository at <repo-path> and summarize the triaged scorecard. Pick the highest-priority blocking item and propose a fix without editing files yet. Verify that the audit output reports which mode it ran in.
  • Let Claude Code or Codex make and tweak 3D assets

    Connect AssetFurnace as an MCP tool so your coding agent makes, checks and adjusts 3D assets locally.

    View prompt
    Using the AssetFurnace MCP server in the repo at <install folder>, make a 3D model of <subject>, check the run status, and open the result in the studio. Verify that the agent asks before downloading any model weights and that the output file exists on disk.
  • Check whether compacting at 200K actually saved money

    Apply the change, wait several days, then compare cost per prompt and each trade-off to the days before.

    View prompt
    In the optimaizr repo, after context compaction has been applied for several days, run `optimaizr results` on this machine and report cost per prompt before and after. Verify that every row that got worse is marked as a trade-off before you draw a conclusion.
  • Let a coding agent build screens from BoardUI through MCP

    Connect the BoardUI MCP server so your agent can browse the catalog and install components.

    View prompt
    Using the BoardUI MCP server from the repo BoardUI/boardui, add the <component-names> components to my project at <project-path>. Expected output: installed component source and a page that uses them with BoardUI tokens. Verify that the AGENTS.md rules were followed and the app builds.
  • Audit a draft's prose and bibliography with the skills

    Install the skills repository so an agent can check claims, quoted numbers, and bibliography entries.

    View prompt
    Using the BootLoops skills repository at ../skills, apply the prose-editing and bibliography-verification skills to my draft <path to draft>. Report each unsupported claim, each quoted number that cannot be traced to a source, and each bibliography entry that fails verification. Verify that you did not add any claim that is absent from the draft.
  • Approve scenes on a live storyboard before rendering

    Review takes, prompts, cost, and quality scores in Backlot before the final render starts.

    View prompt
    In the OpenMontage repo at <repo-path>, start a production for <topic] and open its Backlot board. Stop at the asset approval gate and report the per-asset costs. Verify that no final render has started until approval is given.
  • Record CPU, memory, and FPS and compare two runs

    Capture an interaction on a device and ask Codex to compare it with an earlier run.

    View prompt
    Using the callstackincubator/codex-mobile-dev-plugin Mobile Dev plugin, record CPU and memory on <device name> during <interaction> before and after my change in <project path>, then compare the two runs. Expected output: a comparison of CPU, memory, and Display FPS between the runs. Verify both recordings cover the same interaction length before drawing a conclusion.
  • Find a past image by what it shows or what you said about it

    Search the panel by description or your earlier comment, then check the right image before sending.

    View prompt
    Using the repo chipfighter/context-attachment-manager, open the Context Assets panel for the task <task name> and search for <phrase from memory>. Report the ID, turn, and source of the matching image, then check Send on it and confirm the next request includes that image.
  • Push an agent branch and open a PR or MR

    Let a run push a branch and open a pull or merge request through gh, glab, or SSH.

    View prompt
    Using the Grasp repo (cocofhu/grasp), run a delivery workflow for <repository URL> that pushes a branch and opens a PR after human confirmation. Verify the branch name and PR link, and report both.
  • Give every teammate the same rule enforcement through the repo

    Install Abide into the project so the hooks travel with the checkout instead of each person's machine.

    View prompt
    In the repo <repo-path>, install Abide into the project with `init --project` for the agent in use, then list the files that were created or changed and confirm which ones should be committed. Report any file that is outside .abide/ or the agent's project extension path.
  • Build Hermes Office from source for an unsupported platform

    Compile the suite yourself when no published build exists for Intel Mac, Windows, or Linux.

    View prompt
    Clone github.com/criptogus/HermesOffice, follow the Development section of its README to build the app for <platform>, and report the build command that succeeded and the path of the built shell. Verify that the built shell opens <path to a test .docx>.
  • Let an agent work inside your own logged-in Chrome

    An agent uses your daily Chrome or Edge session through the extension bridge.

    View prompt
    Using the axuse MCP server with the extension backend, open <site URL> in the user's logged-in Chrome session and report the account name or main heading shown on the page. Confirm the bridge is connected with the bridge verify command before acting.
  • Get a delivery report of what was checked and what was not

    Receive agent-written work with a clear list of verified, reused, and unchecked items.

    View prompt
    Using the Da7-Tech/SureForge skill, freeze the candidate for <deliverable path>, inspect every agreed unit on that exact version, and report what was verified, what was reused, and what was not checked. Expected output: a delivery gate result and a coverage ledger. Verify that every item in the report is backed by evidence or marked as not checked.
  • Resume a long task in a fresh window without a full log dump

    Prepare a bounded resume packet so an agent can continue a long task from its references.

    View prompt
    Using the Squadra repo at https://github.com/dagoSte/squadra, prepare a resume packet for task <task ID> in the project at <project path>. Expected output: a read-only packet listing the task, scope and proof references. Verify that the packet contains references and not full conversation or log text.
  • Connect the Cloudroom desktop app to your core

    Point the Mac desktop app at your own core using a URL and token, with no account.

    View prompt
    Using the cloudroom-core setup guide in docs/setup.md, connect the Cloudroom desktop app on <mac-host> to the core at <core-url> with the token <token>. Expected output: the app lists the core as connected. Verify that an agent started from the app appears in the core's saved history.
  • Reopen an AI conversation after closing its session

    Close a session from the picker and later restore the exact conversation it held.

    View prompt
    Using Session Kit from https://github.com/dob323/session-kit, close the session numbered <n> from the picker, then reopen the conversation after running `kit`. Verify that the restored conversation matches the closed one and report which session number it appears under.
  • Add a new messaging channel with an AI coding agent

    Point a coding agent at AGENTS.md and the channel contract to build one new channel as a declarative definition.

    View prompt
    In the Dpro-at/Tel-Agent repo, read AGENTS.md and CLAUDE.md, then implement the open channel issue <issue number> using the declarative setup contract. Expected output: a focused branch with the new channel definition and transport, and a pull request description that references the issue. Verify that the change follows the rules in CLAUDE.md and that the project tests pass locally.
  • Build a cited knowledge base of people and commitments

    Get six cited pages on people, commitments, threads, products, issues and reading from one day.

    View prompt
    Using the dragthelake/ambient-context knowledge folder, read KB/<placeholder date>/commitments.md and list each commitment with its owner and cited block. Expected output: a table with columns commitment, owner and source block. Verify that every row has a citation that exists in Days/<placeholder date>/.
  • Prepare a part file for a 3D printing or CNC service

    Export a generated part in a format a 3D printing or CNC fabrication service can take.

    View prompt
    Using the text-to-cad plugin from https://github.com/earthtojake/text-to-cad, export <model file path> as <format the service accepts>. Return the exported file path and confirm the file opens correctly in the CAD Viewer.
  • Turn a street scene into a rainy night with puddles

    Set a street scene to night with rain, wet surfaces, puddles and lightning using agent-run skills.

    View prompt
    Using the blender-skills repo, change <street scene .blend> to a rainy night with puddles and lightning, then render one test frame. Expect the rendered image and a short list of the lighting and weather changes made. Verify that the puddles sit on flat ground and not on slopes, and that the lightning flash is visible in the render.
  • Follow and review agent work in the Codex on Crack panel

    Watch phases, handoffs, and tool activity, then leave feedback without interrupting the agent.

    View prompt
    Connect the workspace at <workspace path> to the Codex on Crack panel and list its registered phases, agents, and handoffs. Expected output: a summary of the run with timing and available token counters, with missing values shown as unknown. Verify that no feedback has been treated as approval.
  • X-ray a real clip to draw its hidden inside

    Film a working object and draw its mechanism on the frames its sound describes.

    View prompt
    Using the showtime skill in the FavioVazquez/showtime repository, analyze <clip.mp4> with `showtime xray analyze`, then build an X-ray project with `showtime new xray`. Expect a rendered film and a receipt. Verify that `showtime xray verify` reports the events on their frames.
  • Plan a motion film beat by beat before rendering

    Use the rhythm and carry method to write a beat sheet where shot lengths vary and every boundary has a carried element.

    View prompt
    Using the onetake skill in the feitangyuan/onetake repo, write a beat sheet for a <length> teaser for <product>. Output one sentence per concept, then the chosen beat sheet with shot lengths and a named survivor at every boundary. Verify that shot lengths vary by at least four times and that no boundary is left without a carried element.
  • Show a code on a sign that the person can copy and paste

    Put a PIN or code on a sign with a copy button and point at the field to paste it into.

    View prompt
    Use the bigarrow CLI from franzenzenhofer/big-arrow-on-the-screen to point at the text field <field label> in <app name>:<window title> and show the sign "<sign text with {{<code>}}>". Expected output: a sign with a copy button and an exit code of 0. Verify the exit code and do not repeat the code in any other output.
  • View a session graph in the browser with no install

    Drop a transcript onto the hosted page and get the same graph without installing anything.

    View prompt
    Using the hosted zoetrope app at https://zoetrope.furkankly.dev/app, load the transcript at <transcript-file-path> by dropping it on the page. Expected output: the same agent graph the zoe binary would show for that session. Verify that at least one agent appears in the graph before reporting success.
  • Render a glTF model in a lit 3D scene

    Load a glTF or GLB model into a Framefields 3D scene with a LookAt camera and render it to MP4.

    View prompt
    In the framefields repo, create a composition that loads <model file>.glb into a 3D scene with a LookAt camera and studio lighting, and render it to output/<name>.mp4. Expected output: an MP4 of the model. Verify the file exists and that the model is visible in the first and last frames.
  • Make transparent-background icons for app projects

    Generate an icon with a transparent background and check that the PNG really has alpha.

    View prompt
    Using GPT Image Skill in <repo path>, generate a flat icon of <icon subject> at 1:1 with a transparent background. Expect a transparent PNG under /generated-images with a PATH=... line. Verify the file has an alpha channel before it is used in <project path>.
  • Publish a bot to Marketplace after review

    Draft a public Marketplace listing with your bot and approve it before any pull request.

    View prompt
    Using the gitbot-hq/GitBot package, open <bot name> and run Publish to Marketplace in its conversation. Expected output: a draft listing and a final diff shown to the user before any pull request is prepared. Verify that copying the prompt alone published nothing and that the bot waited for approval.
  • Approve or reject agent memories in the Graphicle app

    Review the memories your agents propose and keep only the ones you approve.

    View prompt
    In the Graphicle-AI/graphicle repository, run `graphicle open` for <repo-path> and review the memories waiting for approval. Expected output: a browser view of the graph, sources and memory with pending memories listed. Verify that a memory you approved is shown as reviewed and that a memory you rejected does not appear in new sessions.
  • Build the repo from source and run compatibility checks

    Clone the source, build it, and check a card against the local compatibility benchmark.

    View prompt
    In the repo hewzhew/dsh-agent-rp, clone the source, run `pnpm install` and `pnpm run build`, then follow docs/compatibility-benchmark.md to test the card at <path-to-card>. Report the build result and any failing compatibility checks. Verify that the build succeeds before running the benchmark.
  • Audit which model ran each agent step and what it cost

    Check per-session model, usage and cost so you can tune routing with real execution data.

    View prompt
    Using the HiRoute repo at https://github.com/higress-group/HiRoute, review the most recent session for <target agent client> and list each turn's task category, actual model group, usage and cost. Verify that the model shown is the one that actually ran, not the one the routing plan intended.
  • Launch Codex through the local gateway

    Start Codex with the gateway as its backend using the built-in launcher.

    View prompt
    In the my-free-code repository, confirm the codex command is on PATH, start the gateway with python -m my_free_code, then run python -m my_free_code.cli.mfc codex. Expected output: Codex starts and completes a short test task. Verify that the gateway log records the request.
  • Have an agent manage Zotero library items and citations

    Let an agent handle Zotero collections and citations through a CLI built for the Zotero desktop app.

    View prompt
    Using the HKUDS/CLI-Anything Zotero CLI, list the collections in my library and generate a citation for the item titled <item-title>. Report the collection names and the citation text. Verify that the citation includes the author and year.
  • Let an agent read a task's trajectory through MCP

    Have Codex call the trajectory tools to pull a safe structured summary of a specific task.

    View prompt
    Using the icesixgod/codex-trajectory repo, call get_codex_trajectory with the sessionId <sessionId> and return a safe summary of that task's steps and timing. Verify that the reply has no tool inputs, outputs, or raw metadata, since those stay hidden in the safe summary.
  • Get alerts when new award winners match your watched studios or tags

    Poll new winners and watch studios or tags, then report only what changed since the last check.

    View prompt
    Use the awwwards-mcp server to call new_winners to set a baseline, then add a watch_site entry for the tag <tag name>. Expected output: a list of new winners and per-watch NEW since last check deltas. Verify that a second new_winners call reports only winners that were not in the first listing.
  • Test whether compressed experience transfers to a new task

    Compress execution experience from one task and score it on an independent held-out task.

    View prompt
    Using the EvoTrace repo at https://github.com/jinzijian/EvoTrace, build two independent verified assets from the same repository, then run /evolve <source-asset> <held-out-asset> in the DeepSeek Harness app. Report baseline and conditioned Docker reward results from /runs. Verify that the held-out asset was built independently and that a run with only one asset is treated as a wiring smoke test, not transfer evidence.
  • Track a screenplay project's stage across sessions

    Use the workflow orchestrator and a story bible file to keep your screenplay's stage and decisions between chats.

    View prompt
    Using the screenwriting-skills repo (sw-workflow), set up a project for <project name> and create a story bible file that tracks the current stage, settled decisions and open questions. Verify at the start of each new session that the agent reads the file and states the current stage before writing anything.
  • Redesign an existing landing page in your project

    Rebuild a landing page inside your own project and check it before shipping.

    View prompt
    Using the juliobsz/skills repo, run /awwwards inside <project folder> to redesign the landing page at <page path>. Expect updated page files, a DESIGN.md and screenshots for desktop, mobile and reduced motion. Verify that the production build still succeeds before you report the redesign as complete.
  • Strip dead air and set loudness to -14 LUFS

    An agent removes silent gaps from a recording and sets its loudness to the -14 LUFS target.

    View prompt
    Using the ffmpeg-skill repo, remove silences from <recording> with a -35 threshold, then normalize loudness to -14 LUFS with a -1 true peak. Expected output: a cleaned MP4 with the target loudness. Verify the result with probe.py and report the duration change.
  • Compare old and new tax regimes with exact rupee savings

    See the tax under each regime side by side and which one saves more.

    View prompt
    In the itr-wala repo at <repo-path>, validate <your-income-file> for FY 2025-26, then run the tax engine on it. Expected output: old and new regime totals with the recommended regime and the rupee saving; verify the validator passes before you report the comparison.
  • Generate a project image with agy's staffer persona

    Ask the general staffer persona to create an image and save it into the repo.

    View prompt
    Using the keli-wen/agy-staff plugin, ask the staffer persona to generate <image description> and save it to <output path> in <repo>. Expect a PNG at that path. Verify that the file exists and opens as an image.
  • Keep a plain-language status file for the whole project

    Maintain one BIG-PICTURE.md with every feature, its progress, unused parts and queued work.

    View prompt
    In the open-steps repo at <repo-path>, use the os-big-picture skill to update BIG-PICTURE.md for the project at <project-path>. Expected output: a plain-language file listing each feature with its progress, any unused parts and the queued work. Verify that no task was invented and nothing was deleted.
  • Give a coding agent Jev skills for decision steps

    Install the TypeSafe agent skill so Claude Code or Codex can build Jev calls.

    View prompt
    Using the repo kraayenjon/awesome-jev and the TypeSafe agent skill from typesafe-ai/skills, add one Jev Choice decision step to <target function> in this project. The step should return a typed label that the existing code branches on. Verify that the project's test suite passes after the change and that the new call reads the API key from TYPESAFE_API_KEY.
  • Let a coding agent run Perch on its own changes

    Install Perch instructions for your AI coding assistant so it can scan its own edits.

    View prompt
    In the perch repo at <project path>, after you finish editing, run `perch scan` and then `perch issues`. Fix the top finding if it is a real defect, then run `perch check <id>`. Verify that the final scan lists no new problems introduced by your edits.
  • Review agent output and charts on your iPhone

    Read the same agent conversations on iPhone and open charts, pages and files the agent made.

    View prompt
    In the chums repo at <target-folder>, run bin/chums-doctor and report whether the iPhone app can reach the hub with the same address and token. Expected output: a read-only check of the whole chain with a fix for each failure. Verify that the hub check passes before using the iPhone app.
  • Design a logo and a 6-second sting with alpha exports

    Get a logo sting with sound plus transparent versions for video editors.

    View prompt
    Use the cinetic skill from Leonxlnx/cinetic to design a logo for <product name> and make a 6-second logo sting with sound, plus ProRes 4444 alpha versions for light and dark footage. Confirm each alpha file has a transparent background before you report the output paths.
  • Draft evidence-linked replies to reviewer comments

    Use AutoRebuttal to tie each reviewer concern to paper evidence before writing replies.

    View prompt
    In the repo liyingze07-svg/EffectiveAutoResearch-EAR-, follow docs/getting-started.md to prepare a rebuttal for the paper <paper-path> and reviewer comments <comments-path>. Expected output is evidence-linked replies, an AC comment and an unresolved-concern ledger as separate files. Verify that every reply cites a specific passage or result in the paper before you report it as supported.
  • Run parallel agent changes in separate Git worktrees

    Give each session its own Git worktree and review diffs and pull request status beside the chat.

    View prompt
    In the LodyAI/Lody repo, start two sessions in the workspace <workspace-name> against the repository <owner/repo>, each with its own Git worktree and a different task <task-a> and <task-b>. Output the worktree and diff summary for each session. Verify that the two sessions show separate diffs in their own tabs.
  • Track Claude and Codex plan limits in the notch

    See your 5-hour and weekly Claude limits and Codex limits in small pills in the notch header.

    View prompt
    Using the Louis-CFM/coucou repo, enable the Claude and Codex plan usage pills in the Coucou Mac app on <target Mac>. Expected output: the notch header shows a Claude pill with 5-hour and weekly limits and a Codex pill with its limits. Verify that the pills match the limits shown in your Claude and Codex accounts.
  • See where a modeling project stands and what needs your sign-off

    Get a status report of stages, evidence problems and pending confirmations.

    View prompt
    Use the Modeling Workbench repo in <tool folder> to check the status of the project in <project folder>. Run the project status tool, list the evidence problems and pending confirmations, and do not record any decision unless I confirm it in my own words.
  • Watch site health and triage errors automatically

    A Web Dev Employee checks site health, triages errors and reviews dependencies on a schedule.

    View prompt
    Using the ai-employees repo, install the Web Dev Employee into <target folder> and confirm its health and error routines are scheduled. Expected output: a health report, a triaged error list and any branch changes. Verify that changes stay on a branch until you review them.
  • Check a Room migration against data-layer traps

    Have an agent review schema changes and migration SQL against the data-layer trap index.

    View prompt
    Using the data-layer-footguns skill from kotlin-footguns, review the Room migration in <migration file path> and its schema diff. Expected output: each matched migration trap with the SQL line that triggers it and the verification result. Verify that each verification command you run appears verbatim in the matched trap file.
  • Add this as the last pass after another writing skill

    Chain the skill after a drafting tool, reusing an existing claim-evidence map.

    View prompt
    The draft in <path to manuscript> is already polished. Use the game-the-llm-reviewer skill from Michael-Jiahao-Zhang/game-the-llm-reviewer as the final pass, reusing the attached claim-evidence map at <path to map>. Keep the meaning and scientific assessment unchanged, skip style-only rewrites, and return a revised copy and change note. Verify that every claim in the map still matches the revised text.
  • Follow one project folder across every agent

    Point a work group at a project folder to see which agents worked there and in what order.

    View prompt
    Using the agentacct repo at https://github.com/mikehasa/agentacct, open the Work group for the folder <project path> and list the agents that worked there and their most recent sessions. Verify that group totals are shown as sums of the participating sessions, with partial coverage labeled.
  • Check a UI for contrast, focus, and mobile layout

    Use the accessibility and responsive skills to review a UI before release.

    View prompt
    Review the UI in <project-folder> against the antislop-human and antislop-layoutmobile skills from the anti-slop repo (https://github.com/miqdadbadjuber/anti-slop). Return a numbered list of contrast, focus, and overflow findings with the Delivery Gate report. Verify that each contrast finding names the ratio it measured.
  • Set cross-backend subagent delegation in Codex

    Choose between Compatibility V1 and Native subagent delegation for Codex tasks.

    View prompt
    Using the codex-chatgpt-web repo, run the subagents status command and report the current protocol. Then set the protocol to <compatibility-v1 or native> and confirm the new value by running status again. Expected output is the two status results and a note to restart Codex.
  • Generate an Apify actor endpoint from its input schema

    Scaffold a static zod input schema for an Apify actor and review it before committing.

    View prompt
    In the monid repo with APIFY_CREDENTIALS_API_KEY set, run deno task apify:scaffold for <actor name>, then review the generated schema/inputs.ts. Report any fields you would change before committing and whether deno task check passes.
  • Recover GPT with Taste after a broken or changed install

    Restore the managed Codex files using the recovery guide.

    View prompt
    In the gpt-with-taste checkout at <repo-path>, follow docs/recovery.md to restore the managed state under the active CODEX_HOME. Report which files were restored and confirm that model_instructions_file points to the main managed prompt file.
  • Let an agent route its next work phase via skill

    Link the model-router skill so an agent can route the next phase of your work through the router.

    View prompt
    Using the model-router skill from the agent-router repo, route the next phase of the plan at <plan path> and report which agent, model, and effort the router selected. Verify that the router decision card appears in the output before any work starts.
  • Find out why an agent session went wrong

    Have the agent review a session transcript for skill failures and optionally package a bug report.

    View prompt
    Using the diagnosing-superpowers skill from the obra/superpowers repo, review the session <session name or 'this session'> and report what went wrong with superpowers. Expected output: a report with line-level evidence and an offer to package a scrubbed bundle. Verify that each finding cites a specific point in the transcript.
  • Skim Hacker News top stories in a few hundred tokens

    Open the Hacker News front page as a numbered list and drill into one story.

    View prompt
    Use the only-cli/oc repo: run `oc hn top` to list current top stories. Expect a numbered list of headlines. Verify the list has entries before picking one to open with `oc do <n>`.
  • Find PRD gaps and conflicts before anyone writes code

    Get one P0/P1 register of gaps and conflicts from a PRD, with verification steps.

    View prompt
    Use codexqa-requirement-analyzer on the PRD at <prd-path>. Produce one P0/P1 gap-and-conflict register, with preconditions, stimulus, expected result, and evidence for each high-priority row. Verify that every high-priority row has an executable verification step.
  • Catch tests that pass against old code in CI

    Run every new test against the old code in CI and fail any test that passes there.

    View prompt
    In the repo at <repo-path>, after gap-trap setup, open a PR that adds one new test. Report the result of the proven red CI job for that PR. Verify that the job ran in CI and not only locally.
  • Check which services call which, and catch broken links

    Record each cross-service call once and fail when a client, handler, or endpoint moves.

    View prompt
    Using the repos at <repo paths>, write system.links.json describing the calls between services, then run vibeX links with --check. Report any broken client, handler, or endpoint, and list endpoints nothing calls. Verify the check fails when a handler is renamed in a test copy.
  • Export a scan as robot-training data

    Turn a scanned space into a LeRobot or GR00T dataset, or an Isaac Sim or MuJoCo scene.

    View prompt
    Using the openreality MCP tools, export the scene <scene id> as robot-training data in the <format: LeRobot, GR00T, Isaac Sim, or MuJoCo> format and save the zip to <local path>. Verify that the zip exists locally and that the export format matches your request.
  • Catch quality regressions before a task is marked done

    Run the quality delta check so only what got worse is reported.

    View prompt
    Use ripwire on the repo at <path>. After your changes, run the --quality-delta flag and list every quality kind that got worse. Verify each one by reading the flagged code before you fix it or record a reason to keep it.
  • Build Remocn Studio from source and run its tests

    Clone the repo, install dependencies, and run the app in development mode with the test suite.

    View prompt
    Clone the repo https://github.com/Remocn/remocn-studio into <target folder>, install dependencies with bun, and run the test suite. Expect bun run test to finish with a pass or a list of failing tests. Verify the result by reporting the exact test summary before editing any file.
  • Prepare a redacted Healthcheck summary to review

    Create a local summary file from a check report, inspect it, and validate it before choosing to send it.

    View prompt
    Using the AgentMeasure repo, run `agentmeasure check --json report.json`, then `agentmeasure share report.json --out summary.json`, then `agentmeasure validate summary.json`. Report whether validation passed and list the fields in summary.json. Verify that no upload happened and that report.json was not attached to any message.
  • Run a GPT-5 review of a branch diff

    Pipe a branch diff into Codex and get a single final answer back.

    View prompt
    In the Sateezg/codex-bridge plugin setup, pipe the diff of <branch> against main into codex-run with -C . and --timeout 1200, and report Codex's final answer. Verify that each finding names a real file and line in the repo before reporting it.
  • Build a side-scroller sprite kit with parallax layers

    Generate side-view hero and enemy sprite strips, parallax layers, and platform tiles.

    View prompt
    Using the scenario-labs/skills repo, generate side-view sprite strips for <hero-description> with run, walk, attack, and hurt poses, plus three parallax layers for <level-theme>. Save everything to <output-folder>. Verify that the hero strip frames are the same size.
  • Check the local Codex CLI, Skills, and MCP setup before starting work

    See the detected Codex CLI version, Skills, and MCP server summaries in one view.

    View prompt
    Using the repository sevensir888/codex-command-center as a reference for what its Codex environment view shows, list the items I should verify on <machine name> before starting Codex work on <project name>. Output a checklist with one line per item. Verify that the Codex CLI version matches the version I expect.
  • Let a coding agent find, install, and edit Shaders

    Install the Shaders skill and MCP server so your agent can add and change effects in your project.

    View prompt
    Using the shader-effects-inc/shaders skill and MCP server, find a shader that matches <effect-description> and install it into <project-path>. Expected output: a new component file and a summary of the props set. Verify that the component is imported from the correct framework path.
  • Host a shared world session for friends

    Run the game as host so friends can join the same world by IP address or URL.

    View prompt
    On the host machine running Infinite Pokémon, start a Multiplayer host session and report the address a guest should enter. Verify that a second client can choose Join session and reach the host's starting map.
  • Look up CVEs and known issues for a tech stack

    Query NVD and the tech correlation data to see which known issues match a product or version you run.

    View prompt
    Using the blitzstrike MCP server, call nvd_lookup for <CVE ID> and tech_correlation for <technology name>. Return the matching CVEs with their severity and the related product. Verify that each listed CVE is confirmed against the version you run before you act on it.
  • Run a supervised agent fleet across a spec hierarchy

    Start a detached supervisor that drives every wave, manager, and worker until work merges.

    View prompt
    In the Hyperfide repository, start the fleet with `hyperfide fleet up` and follow `hyperfide events --follow` for <N> minutes. Report which waves merged, which tasks were escalated, and whether any approval gate is waiting. Verify that completion is reported only for merged work.
  • Validate a knowledge base before sharing it

    Run the structure, link, and TeX checks on a workspace before you hand it to others.

    View prompt
    In the my-kb workspace, run `python kb.py check --backend codex`. List each reported structure, link, archive folding, or TeX problem with its file path, fix only those files, and confirm the check passes again.
  • Hand off a job with a charter that defines done

    Write one charter with success checks, then let any agent deliver it.

    View prompt
    In the repo <repo-path>, write a charter with the work-orders skill from Sno Station Skills for the job described in <job-description>. Output one charter file with deliverables, out-of-bounds areas, decided items and a proof method for each success check. Verify that every success check names a real run that can pass or fail.
  • Review every tool call an AI coding agent made

    Read the local audit trail and watch live tool calls to see what an agent tried and what the guard decided.

    View prompt
    Using https://github.com/solongate/agent-security, run `solongate audit` after a session with <agent> in <project-path>. Expected output: a list of tool calls with their allow or deny decisions. Verify that ~/.solongate/local-logs/solongate-audit.jsonl contains one JSON object per decision, matching what the audit view shows.
  • Delegate a feature to an agent with checks at each stage

    Use the toolkit's workflow to move a request from design to verified, reviewed code.

    View prompt
    In the repo soumatheusgomes/vibe-coding-toolkit workflow, implement the feature <feature description> in this project at <project path>. Follow understand, design, plan, implement, verify, and review in order, and keep changes to the smallest complete change. Report the diff summary and the checks run. Verify that the checks passed and that pending work is listed.
  • Pair one agent with a reviewer that checks each turn

    Have one agent write changes while another approves them or returns findings, round by round.

    View prompt
    Using the Tellurion repo at https://github.com/steventsvik/Tellurion, start a review loop in <project-folder> with Codex as writer and Claude Code as reviewer, with a round limit of 3. Report the reviewer's answer for each round. Verify that no message reached an agent before you clicked Send.
  • Generate an authenticator code locally for your own account

    Compute a time-based one-time code on your machine using the totp_code tool.

    View prompt
    Using the sv-number/mcp-server totp_code tool, compute the current authenticator code for <account name> from its secret. Expected output: the current time-based code computed locally by RFC 6238. Verify that the secret is not echoed in the response or in any log before you use the code.
  • Give coding agents a queue for the GPU instead of killing processes

    Install the Berth skill so Claude Code or Codex asks for the card rather than killing GPU jobs.

    View prompt
    On the machine with the Berth repo, run `berth skill install` and then `berth status`. Expected output: the skill is installed for the agent and the card's holder is listed. Verify that a GPU task started by the agent runs through `berth run` and does not kill other GPU processes.
  • Use Codex CLI through the router's responses endpoint

    Point Codex CLI at the /v1/responses surface so it runs on free-tier models.

    View prompt
    In the freellmapi repo (tashfeenahmed/freellmapi), configure Codex CLI in <project-path> to use http://localhost:3001/v1 with the unified key from the Keys page. Expected output: Codex CLI completes a small task. Verify that the router logs a /v1/responses request.
  • Run the standard build workflow for a full game goal

    Give an agent one end-to-end game development goal using Vibe Game's standard build workflow.

    View prompt
    Using the VibeGame repo at https://github.com/tettethu/VibeGame, run the /vibegame-build workflow in my-game with the goal "<end-to-end game goal>". Expected output is a built game in my-game that matches the goal. Verify by running vibegame run --port auto and confirming the goal's main encounter is playable.
  • Improve a harness with reliable rewards and reflection

    Use reward-based evaluation and GEPA reflection to evolve a harness from full execution traces.

    View prompt
    Using the JevHarness skill from https://github.com/TianyuCodings/JevHarness, plan an evaluation and reflection loop for <task> with a trusted reward, a training batch, and an Eval set. Expected output: a plan naming the selection split, the reflection inputs, and how accepted proposals are checked on Eval. Verify that the plan keeps Eval separate from the reflection inputs.
  • Generate an interactive Cleanup Map from an audit

    Turn a confirmed audit into a desktop HTML map with linked findings and evidence drawers.

    View prompt
    Use $simplify-codebase to audit <repo path> and generate a Cleanup Map with Finding deep links after I confirm. Do not present reachable relationships as runtime impact. Expected output: a validated interactive HTML file alongside the text proof records. Verify that every node on the map matches a confirmed finding in the text report.
  • Upgrade an older memory install and keep your own edits

    Move a machine to a newer pack while receipt hashes protect edited files.

    View prompt
    In the new ai-memory-skillpack checkout, follow INSTALL.md and the migration/ procedure to upgrade the memory install on this machine. Expected output: a list of files replaced, files kept because of local edits, and the archive path of the old pack. Verify that no file with a receipt hash mismatch was overwritten.
  • Get a sourced research digest on a schedule

    A research agent reads papers, docs or competitors on a schedule and reports only when something matters.

    View prompt
    Using the Overtime repo at ukanwat/overtime, create a research agent that reads <list of sources> on a schedule. Expected output: one report with a source link for each item. Verify that every claim in the report links to a source the agent actually read.
  • Cut dead air and keep existing captions in sync

    Find speech ranges, apply a cut list in one encode, and retime the transcript to match.

    View prompt
    In the veedstudio/open-edit repo, probe speech in <video path>, write an edl.json with the kept ranges, then run apply-edl and retime-transcript. Expect cut.mp4 and a retimed transcript under runs/cut. Verify that the retimed transcript timings fall inside the cut duration.
  • Check a built 3D scene by capturing its real frames

    Drive a built scene through named views and clicks, then review the saved PNGs and console log.

    View prompt
    Using the 3dviz-pro-max skill in <repo-path>, run the capture helper on the built scene at <scene-path> and save the named views as PNG frames with the console log. Report whether each claimed feature appears in the frames and list any mismatch.
  • Render explainer videos on a Raspberry Pi 5

    Run the full pipeline on ARM Linux with system Chromium and a local or cloud voice engine.

    View prompt
    On this Raspberry Pi 5 with the anything2explainer repo cloned, set REMOTION_BROWSER_EXECUTABLE to the system Chromium and generate voiceover with TTS_ENGINE=piper, then render a short test video. Verify that the render finishes and produces an MP4 that plays with audio.
  • Rewrite one agent response on demand

    Invoke the Nopus simplify skill to request a clearer rewrite when automatic checks did not trigger.

    View prompt
    Using the nopus repo at Vistyy/nopus, run `/nopus:nopus-simplify` in Claude Code or `$nopus-simplify` in Codex in <project directory> right after the response you want rewritten. Expected output: a revised version of that response. Verify that technical terms, commands, identifiers, and conditions appear unchanged in the revision.
  • Audit a codebase with bundled security workflows

    Run Codex Security workflows on your own code and get evidence-backed reports.

    View prompt
    Using the VelaTerm repo at https://github.com/vlinx-io/VelaTerm, read docs/manuals/code-audits_20260908.md and run a code audit on the project at <project-path> that I own. Expected output: a Markdown or JSON report with source evidence and coverage limits. Verify that every finding links to a file and line in the source before you trust it.
  • Install the skill for Claude Code and Codex

    Clone the repo and run the install script to add the skill to both agents.

    View prompt
    Using the forward-implementation-first repository, install the skill for Claude Code and Codex on this machine. Report which skill directories now contain SKILL.md. Verify that both ~/.claude/skills/forward-implementation-first/ and ~/.codex/skills/forward-implementation-first/ exist after the install.
  • Keep the HERO block active on overnight agent runs

    Put the block in an always-loaded file so long unattended runs keep the scope limits.

    View prompt
    Check that the HERO SCOPE LIMITS block is in the always-loaded config for this project. Then run <long task> and, at each checkpoint, list any hashing, extra review or scaffolding step and state which rule it falls under.
  • Bring Claude Code, Cursor or Codex setup and chat history into DSH

    Translate another AI coding agent's MCP servers, skills, instructions and conversations into a DSH import.

    View prompt
    Use the DSH Config Manager plugin to import the <source-agent> configuration and chat history on <machine> into DeepSeek Harness. Stop at the preview step, list the MCP servers, skills and conversations that would be imported, and state which secret key names need re-entry.
  • Build a hook matrix from 18 hook tactics

    Turn one offer into a hook matrix and a diagnostic funnel for testing openings.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the hooks module on <product or offer> and return the 18-tactic hook matrix and the diagnostic funnel. Verify that no hook claims proof that is absent from brand-context.md.
  • Review AD certificate template exposure from exports

    Audit certificate templates, CA policy, and enrollment controls from supplied directory exports.

    View prompt
    Using the adcs-exposure-audit skill from the zero-lab-ai/skills repo, audit the certificate template and CA policy exports for <domain-name> that I provide. Return each control with an exposure rating and the export line it cites. Verify that every rating cites a line from the exports I supplied.
  • Port an existing Remotion composition to HyperFrames HTML

    Convert a React-based Remotion composition into HyperFrames HTML with the remotion-to-hyperframes skill.

    View prompt
    Using the hyperframes repo at heygen-com/hyperframes, run the remotion-to-hyperframes skill on the Remotion source in <folder path> and output the ported HyperFrames HTML. Verify that the timing of the first and last scenes matches the original composition.
  • Stress-test your GTM claims before you ship

    Have the agent review your landing page or launch copy as a skeptic.

    View prompt
    Run review-the-work and value-prop-that-converts in the gtm-cofounder skills on this draft for <product name>. Expected output: a list of flagged claims and a revised value prop. Verify that every remaining claim can be backed by something the user can check.
  • Score a film with original music and check it before release

    Compose a score for your film and run the music check to catch loudness, masking and copied-sounding material.

    View prompt
    Using the anidoodle repo, compose an original score in the <music style> style for <film name> and run node tools/music.mjs check on it. Return the audio file and the check report, and confirm it passes key, loudness, masking, balance and novelty.
  • Review an app's animations and produce a fix plan

    Have an agent audit motion in your app and list what to delete, move off the JS thread, or add velocity to.

    View prompt
    Using the appllama/appllama-skills repo, review the animations in <project folder> against the motion bar in appllama-app-design-skill. Output a fix plan that lists what to delete, what runs on the wrong thread, and what lacks finger velocity, and verify the plan's changes in the simulator recording.
  • Check agent subscription quota from the computer

    List the quota each agent on the computer can report, and turn on Claude collection.

    View prompt
    In the arronKler/pairfob repo, run `pairfob quota list` on this computer and report which subscription quotas it lists and any reason given for missing ones. Verify the command output matches the list of agents named in the README's quota feature.
  • Record a Codex CLI run that cannot be redirected

    Use opt-in TLS interception to capture a Codex CLI session that talks to its own backend.

    View prompt
    Use the OrcaReplay repo (Continuum-AI-Corp/OrcaReplay) to record a Codex CLI session with TLS interception enabled, following the README section on when the harness will not be redirected. Report whether `orca show last` lists model turns from the session. Verify that hosts not on the intercept list are listed in the trace as tunnelled.
  • Upgrade an old DSH plugin to a new DSH release

    Use an upgrade skill pack so Claude Code or Codex can migrate a plugin to a newer DSH version.

    View prompt
    Using the upgrade skills in github.com/oh-my-dsh/dsh-plugin-upgrade-skill, migrate the DSH plugin at <plugin-path> to the target DSH version <target-version>. Report the list of breaking changes applied and the test result. Verify by running the plugin's tests and confirming they pass.
  • Tighten capture rules after reviewing a day

    Use the record to set rules that stop capturing apps, sites or text you do not want kept.

    View prompt
    In the dragthelake/ambient-context app, use the tune rules skill to review the Context records for <placeholder date> and propose capture rules for apps or sites that should not be kept. Expected output: a short list of proposed rules, each naming the app or site and the action. Verify each proposal against the block it came from before applying it.
  • Open the live graph over a Herdr agent pane

    Press one key in Herdr to open the exact session running in a pane as a live graph.

    View prompt
    In the zoetrope repo (furkankly/zoetrope), install the herdr-plugin with the Herdr commands in its README, then focus the agent pane <pane-name> and press prefix+shift+z. Expected output: the live graph of that pane's session opens over the pane. Verify that the graph matches the session running in that pane before reporting success.
  • Keep one character consistent across new scenes

    Reuse a character reference file to place the same person or mascot into several new scenes.

    View prompt
    Using GPT Image Skill in <repo path>, generate <number> scenes using <character reference path> as the reference in each job, with the scene descriptions <scene list>. Expect one PNG per scene under /generated-images. Verify the reference file is attached in every job, not replaced by a text description.
  • Plan a huge project as a map of decision tickets

    Use wayfinder to resolve decisions one at a time across several agent sessions.

    View prompt
    In the mattpocock/skills repo, use wayfinder to map the work needed to reach <destination>. Expected output: a set of decision tickets on the issue tracker and the first one to resolve. Verify that each decision ticket is stored in the tracker and not only in the chat.
  • Let a coding agent install the skill and run Jev Lint

    Install the Jev Lint skill so an agent can run checks and write project rules.

    View prompt
    In the repository <repo-path>, install the skill with `npx skills add mizchi/jev-lint --skill jev-lint`, then run `npx jev-lint check src --dry-run` and report the planned request count and price. Only after a human approves, run `npx jev-lint review --base main` and list findings with file, line and score.
  • Apply Prismantis styling to Codex output

    Follow the Codex guide to get themed code, tables and diagrams in Codex sessions.

    View prompt
    Read codex/README.md in the NahumLitvin/prismantis repository, install prismantis for Codex as that file describes, then start a Codex session and request a markdown table. Expected output: a table with a themed header row. Verify the output against the list of what works today in that file.
  • Give a coding agent cheap web reading in one step

    Install the web-browsing skill and add one line to your agent instructions file.

    View prompt
    Use the only-cli/oc repo: after the skill and instructions line are in place, ask the agent to read a page using `npx @only-cli/oc open <url>`. Expect a numbered compact view with an actions line. Verify the agent used oc instead of a raw fetch.
  • Replay a browser flow and check the evidence it shows

    Run a UI case in Playwright Chromium and get a report with marked screenshots per step.

    View prompt
    Use codexqa-jev-browser to replay the case at <case-path> against <target-url>. Write a report under reports/<run-id>/report.html with a marked screenshot per step. Verify that the final screenshot shows the visible evidence named in the goal.
  • Check prices before running a generation batch

    Have an agent price a planned batch in Scenario before spending credits on it.

    View prompt
    Using the scenario-labs/skills repo, price a batch of <count> generations described in <batch-file> before running any of them. Report the total cost and the cost per item. Verify that no generation starts until I approve the total.
  • Branch a run from a checkpoint to try another path

    Create a checkpoint, then branch from an earlier point into a separate world.

    View prompt
    In Infinite Pokémon, create a checkpoint in a run, branch from it, and report whether the branch has its own world database and whether later events from the original run appear in it. Note any generation status shown for unfinished destinations.
  • Add drawn eyes and mouths with Codex

    Have Codex draw closed eyes, vowel mouths and expressions so blinking and talking look more natural.

    View prompt
    In the mesh-avatar-studio repository, use Codex to draw the eye and mouth variants for <project name> as described in the copied editor message. Expect the drawn variants imported into the project. Verify that the editor reloads them and that blinking and vowel mouths use the new images.
  • Review nightly lessons from your own sessions before they stick

    Let the nightly loop propose lessons and skill changes, and accept only the ones you want.

    View prompt
    In the repo <repo-path>, run the rem-reflect skill from Sno Station Skills over the last <day-count> days of Claude Code and Codex sessions. Output a list of proposed lessons and skill changes, each with the session evidence. Verify that no change is applied until it is explicitly accepted.
  • Use one skill source for both Codex and Claude Code

    Keep one copy of the memory skills and point Claude Code at it with symlinks.

    View prompt
    On this machine, after installing the ai-project-memory skill for Codex per INSTALL.md, confirm that the Claude Code skill directory contains symlinks to the Codex skill files and not copies. Expected output: a list of each skill path with its link target. Verify that no skill file exists as a separate copy in the Claude Code directory.
  • Mix narration, music, and effects into one finished video

    Build one loudness-levelled audio track from many pieces and mux it onto a render.

    View prompt
    In the veedstudio/open-edit repo, run mix-audio on the run folder <run>, then mux-audio onto the silent render. Expect final.mp4 with the mixed audio. Verify from the command output which loudness correction ran before you report success.
  • Let a coding agent set up and launch training jobs

    Point Claude Code or Codex at the repo skills to choose parallelism and launch a Halo run.

    View prompt
    In the whitecircle/halo repo, use the skills/parallelism and skills/launch guides to choose settings for <target-config> and then run `halo launch sft` with --dry-run inside the Halo image. Expected output: a printed launch command with the chosen parallelism flags. Verify that the flags match one of the allowed EP, CP, TP, or ETP combinations before any real run.
  • Check how citable a page is for AI search

    Assess a page for AI-search citability across ChatGPT, Perplexity and AI Overviews.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the geo module on <target URL> and return a citability assessment with specific edits. Verify that the report separates what was determined from what could not be determined.
  • Generate a new region with the region skill

    Install the region generation skill so an agent can propose new places for the world.

    View prompt
    Use the infinite-pokemon-region skill from the Shellishack/infinite-pokemon repo to prepare the next region from the immutable run snapshot for <run name>. Report which maps passed validation, which failed, and confirm that visited maps were not changed.