Phoenix Pxi Playwright
Arize-ai/phoenix
Write, extend, and debug PXI Playwright E2E tests for Phoenix.
Write or extend an E2E journey spec in evals/specs that proves a PR's change to a human reviewer.
Install Write A Spec
$ npx skills add different-ai/openwork --skill write-a-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install different-ai/openwork write-a-spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/write-a-spec .claude/skills/write-a-spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-a-spec" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/write-a-spec into .claude/skills/write-a-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-a-spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/different-ai/openwork/tree/dev/.opencode/skills/write-a-specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add different-ai/openwork --skill write-a-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install different-ai/openwork write-a-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/write-a-spec .agents/skills/write-a-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-a-spec" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/write-a-spec into .agents/skills/write-a-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-a-spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add different-ai/openwork --skill write-a-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install different-ai/openwork write-a-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/write-a-spec .cursor/skills/write-a-spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-a-spec" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/write-a-spec into .cursor/skills/write-a-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-a-spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/different-ai/openwork.git --path .opencode/skills/write-a-spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add different-ai/openwork --skill write-a-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install different-ai/openwork write-a-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/write-a-spec .gemini/skills/write-a-spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-a-spec" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/write-a-spec into .gemini/skills/write-a-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-a-spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install different-ai/openwork write-a-specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add different-ai/openwork --skill write-a-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/write-a-spec .github/skills/write-a-spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-a-spec" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/write-a-spec into .github/skills/write-a-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-a-spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add different-ai/openwork --skill write-a-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install different-ai/openwork write-a-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/write-a-spec .opencode/skills/write-a-spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-a-spec" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/write-a-spec into .opencode/skills/write-a-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-a-spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
write-a-spec- GitHub stars
- 24k
- Token cost
- ~3.3k tokens
- SKILL.md length
- 1,438 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write or extend an E2E journey spec in evals/specs that proves a PR's change to a human reviewer.
- A PR changes user-visible behaviour
- SKILL.md covers Map: from change to reviewed…, Do not write one when…, The proof shape and Same story in three places, plus 3 more sections
- Calls pnpm; needs FREESTYLE_API_KEY
- A reviewer asks show me
What it does
Write A Spec is an agent skill from different-ai/openwork. Write or extend an E2E journey spec in evals/specs that proves a PR's change to a human reviewer. Use when a PR changes user-visible behaviour, when a reviewer asks "show me", or when the coverage decision says a journey is missing.
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering LLM evaluation and End-to-end testing. The repository describes itself as: The open-source alternative to Claude Cowork (powered by opencode).
When your agent uses it
- A PR changes user-visible behaviour
- A reviewer asks show me
- The coverage decision says a journey is missing
Example prompts
- “show me”
- “/write-a-spec”
Requirements
- A credential in FREESTYLE_API_KEY
What it can do on your machine
Read from SKILL.md and the folder at commit e7d03dd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
FREESTYLE_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Write A Spec loads about 3.3k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 1,438 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,438 words (~3,308 tokens).
“Every evals/specs/**/*.e2e.test.ts a PR adds or changes runs in CI on the PR head and is published as that PR's proof (private report + one PR comment). Write the spec for the person who will read that report in thirty…”
- name
- write-a-spec
Files
Just SKILL.md in .opencode/skills/write-a-spec of different-ai/openwork.
Open the folder on GitHubat commit e7d03dd
Compare with similar skills
Write A Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write A Spec this skilldifferent-ai/openwork | 24k | — | ~3.3k | Automated safety check: Pass | Custom licence | |
| Phoenix Pxi PlaywrightArize-ai/phoenix | 12k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Run Evalslycorp-jp/sim-use | 1.4k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Paperclip Evalspaperclipai/paperclip | 98k | — | ~839 | Automated safety check: Pass | MIT | |
| Run EvalsDevin-AXIS/iPolloWork | 6.7k | — | ~851 | Automated safety check: Pass | Custom licence | |
| Create Taskmelandlabs/openloomi | 1k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Run Evals
lycorp-jp/sim-use
Prepare the environment and run the LLM-driven agent evals (e2e/agent-evals/) against a chosen sim-use binary.
Paperclip Evals
paperclipai/paperclip
Choose, inspect, validate, and report Paperclip Runner or Product E2E evaluations while preserving evidence, provenance, cost, and failure classification.
Run Evals
Devin-AXIS/iPolloWork
do e2e tests, run e2e, validate feature, prove it works, PR proof, frame proof, pnpm evals.
Create Task
melandlabs/openloomi
Create an end-to-end Continual Learning Bench task. An agent skill from melandlabs/openloomi.
Evaluation
PrimeIntellect-ai/prime-envs
Install and run a verifiers environment — smoke testing during development and full benchmark evals.
More from different-ai/openwork
All 32 skills in this repoOpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
Fake Model Provider Faults
different-ai/openwork
Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.
OpenWork Model Alias Manager
different-ai/openwork
Manages OpenWork's inference model aliases, discounts and overlays over the upstream OpenRouter catalog, and triggers the GitHub workflow that refreshes base models.
Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
OpenWork Electron Browser Automation
different-ai/openwork
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
Daytona Sandbox Operations
different-ai/openwork
Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.
Related
Categories
Questions about Write A Spec
What does Write A Spec do?
Write or extend an E2E journey spec in evals/specs that proves a PR's change to a human reviewer. Write A Spec is an agent skill from different-ai/openwork. Write or extend an E2E journey spec in evals/specs that proves a PR's change to a human reviewer.
When should I use Write A Spec?
Write A Spec fits situations like: A PR changes user-visible behaviour; A reviewer asks show me; the coverage decision says a journey is missing.
How do I install Write A Spec in Claude Code?
Run `npx skills add different-ai/openwork --skill write-a-spec -a claude-code`. Or copy the skill folder (.opencode/skills/write-a-spec in different-ai/openwork) into .claude/skills/write-a-spec in your project. Claude Code loads it when a task matches its description.
How do I install Write A Spec in Codex?
Run `npx skills add different-ai/openwork --skill write-a-spec -a codex`. Or copy the skill folder (.opencode/skills/write-a-spec in different-ai/openwork) into .agents/skills/write-a-spec in your project. Codex loads it when a task matches its description.
Can I use Write A Spec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add different-ai/openwork --skill write-a-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-a-spec, .gemini/skills/write-a-spec, .github/skills/write-a-spec and .opencode/skills/write-a-spec in your project.
What does Write A Spec need to run?
Going by SKILL.md and its folder, Write A Spec needs the command-line tools its instructions call (pnpm) and credentials named FREESTYLE_API_KEY. Our summary lists: A credential in FREESTYLE_API_KEY.
Does Write A Spec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write A Spec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Write A Spec use?
Write A Spec has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Write A Spec use?
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Write A Spec?
Skills that share tags, products or a category with Write A Spec: Phoenix Pxi Playwright (Arize-ai/phoenix, 12k stars), Run Evals (lycorp-jp/sim-use, 1.4k stars), Paperclip Evals (paperclipai/paperclip, 98k stars) and Run Evals (Devin-AXIS/iPolloWork, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write A Spec?
different-ai (a GitHub organization) maintains it in different-ai/openwork, which has 23,920 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 7, 2026.
Source: different-ai/openwork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.