Codex computer use

Skill Studio-Moser/skills-n-stuff/plugins/pm/skills/codex-computer-use

Product research, market intelligence, and content tools for AI-native teams

Install

npx -y skills add Studio-Moser/skills-n-stuff --skill codex-computer-use

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Ask the Codex CLI (running whatever model it's configured with) to run local app verification that needs computer use, browser automation, simulators, screenshots, app launching, or independent runtime inspection. This is how the Codex model is invoked for computer-use work. Use when the user asks Claude to test a flow, verify UI behavior, inspect a running app, capture screenshots, or report confirmation and feedback about implemented behavior that benefits from computer use functionality.

SKILL.md

2.8 KB, as published. Nobody here has run it

Codex Computer Use

Optional cross-vendor executor. Requires the OpenAI codex CLI. If command -v codex fails, this skill isn't available on this machine — say so and verify by another means. The model-orchestration doctrine (references/model-orchestration.md) routes here only when the CLI is present.

Use Codex as a separate local verification agent when the task needs real UI interaction, screenshots, simulator/browser/device state, or an independent runtime check outside Claude's current context.

Do not use this for ordinary code reading, typechecking, linting, or tests Claude can run directly. Launching apps, simulators, or browsers to verify the requested work is fine without asking; ask first only if the run could disrupt the user's environment beyond that (closing their apps, changing system settings, acting on real accounts or data).

Workflow

Define exactly what behavior to verify and on what platform.
Create a temporary artifact directory for screenshots, logs, and the report.
Write a self-contained prompt and run codex exec with the sandbox level the task needs.
Read the report and screenshots, and verify key claims before presenting them.

ARTIFACT_DIR="$(mktemp -d "${TMPDIR:-/tmp}/codex-computer-use.XXXXXX")"
REPORT="$ARTIFACT_DIR/report.md"
PROMPT="$ARTIFACT_DIR/prompt.md"

# Write a self-contained prompt to $PROMPT, then run:
codex exec \
  -C "$PWD" \
  -s danger-full-access \
  - < "$PROMPT" > "$REPORT"

Use -s danger-full-access for GUI automation, iOS simulators, desktop app launching, screenshots, or access outside the repo. For non-GUI checks that only need the repo and artifact directory, prefer -s workspace-write. Add --skip-git-repo-check when the working directory is not a git repository.

Prompt Requirements

Tell Codex:

The exact behavior to verify.
The platform and app type, such as iOS, macOS, web, Electron, CLI, or desktop.
Known launch commands, test credentials, seed data, deep links, or fixtures.
Whether source edits are allowed. Default to no edits.
Where screenshots, logs, and the final report should be saved.
To return pass, fail, or blocked, plus steps performed, observed behavior, screenshot paths, and actionable feedback.

Keep the prompt specific enough that Codex does not need the surrounding Claude conversation.

Gives 0 of the 12 instructions most quality gates skills give

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-06

read the output and check the exit codein 55 of 1195, across 14 files
verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
identify the verification command proving the claimin 53 of 1195, across 12 files
run the full verification commandin 51 of 1195, across 11 files
verify output confirms the claimin 49 of 1195, across 10 files
check version control diff after agent delegationin 45 of 1195, across 5 files
state claim with evidencein 43 of 1195, across 3 files
run the test suitein 32 of 1195, across 24 files
keep state in memory by defaultin 27 of 1195, across 6 files
make prototype runnable with one commandin 26 of 1195, across 5 files
detect the package manager from lockfilesin 24 of 1195, across 5 files
produce a verification reportin 23 of 1195, across 12 files

Said here and by no other author read

Define exact behavior to verify and platform
Create temporary artifact directory for outputs
Write self-contained prompt to file
Run codex exec with needed sandbox level
Use danger-full-access sandbox for GUI automation
Prefer workspace-write sandbox for non-GUI checks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.