Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
A skill your agent uses when a single DAE artifact has ambiguities to resolve.
Install Clarify
$ npx skills add swingerman/engineer --skill clarify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swingerman/engineer clarify --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/swingerman/engineer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineer/skills/clarify .claude/skills/clarify && 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 "clarify" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/clarify into .claude/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", 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/swingerman/engineer/tree/master/engineer/skills/clarifyType 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 swingerman/engineer --skill clarify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swingerman/engineer clarify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineer/skills/clarify .agents/skills/clarify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clarify" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/clarify into .agents/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", 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 swingerman/engineer --skill clarify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swingerman/engineer clarify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineer/skills/clarify .cursor/skills/clarify && 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 "clarify" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/clarify into .cursor/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", 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/swingerman/engineer.git --path engineer/skills/clarify--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 swingerman/engineer --skill clarify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swingerman/engineer clarify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineer/skills/clarify .gemini/skills/clarify && 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 "clarify" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/clarify into .gemini/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", 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 swingerman/engineer clarifyInstalls 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 swingerman/engineer --skill clarify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineer/skills/clarify .github/skills/clarify && 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 "clarify" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/clarify into .github/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", 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 swingerman/engineer --skill clarify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swingerman/engineer clarify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineer/skills/clarify .opencode/skills/clarify && 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 "clarify" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/clarify into .opencode/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", 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
clarify- GitHub stars
- 154
- Token cost
- ~620 tokens
- SKILL.md length
- 265 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a single DAE artifact has ambiguities to resolve.
- Works in 6 steps: Resolve + load — resolve the methodology… → Identify ambiguities — within this one… → Resolve one at a time — per ambiguity,… → …
- A single DAE artifact has ambiguities to resolve
- SKILL.md covers When to use, Workflow, Handoff and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clarify is an agent skill from swingerman/engineer. Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec", "resolve ambiguities", "this is vague — tighten it".
Its SKILL.md is about 620 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. The repository describes itself as: Disciplined Agentic Engineering — a methodology kit for Claude Code: acceptance-test-first specs, explicit checkpoints, and autonomy you can actually leave running. The engineer… The licence is MIT.
When your agent uses it
- A single DAE artifact has ambiguities to resolve
- — /engineer.clarify
- Clarify this spec
- Resolve ambiguities
Example prompts
- “/engineer.clarify”
- “clarify this spec”
- “resolve ambiguities”
- “/clarify”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Resolve + load — resolve the methodology root + manifest via ${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md)…
- Identify ambiguities — within this one artifact: language interpretable two ways, underspecified requirements, undefined domain terms…
- Resolve one at a time — per ambiguity, quote the ambiguous line and ask one question — multiple-choice (AskUserQuestion) when bounded…
- Edit in place — encode each resolution into the target artifact; show old→new, confirm before writing. Edit only the target artifact.
- Flag downstream staleness — do NOT cascade. Identify downstream artifacts a resolution may have invalidated; list them in the handoff…
- Handoff — emit a summary.
What it can do on your machine
Read from SKILL.md and the folder at commit 32947eb. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
notion.so
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Clarify loads about 620 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 265 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
The full file from swingerman/engineer at commit 32947eb, republished under its MIT licence (© swingerman). 265 words, ~620 tokens.
Download SKILL.mdSave it as
.claude/skills/clarify/SKILL.md (or your agent's skills folder).- name
- clarify
- description
- Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec", "resolve ambiguities", "this is vague — tighten it".
clarify
Resolve ambiguities in one DAE artifact through an iterative interview. A cross-cutting quality gate — runs on any artifact at any pipeline stage.
The clarify pattern is also embedded inside artifact-producing skills for their own in-flight ambiguities; this standalone skill is for ad-hoc cleanup after the fact.
When to use
On any one of: feature.md, acs.md, spec.md, plan.md, CHARTER.md. Invoked as /engineer.clarify <slug> <artifact> or /engineer.clarify <path>.
Not for: cross-artifact contradictions (consistency-check); changing what a feature does (feature-edit); resolutions that cascade across files (clarify the source here, then feature-edit).
Workflow
- Resolve + load — resolve the methodology root + manifest via
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md); locate the target artifact. Also load its parent contract for grounding (feature.mdfor acs/spec/plan;CHARTER.mdfor feature.md). - Identify ambiguities — within this one artifact: language interpretable two ways, underspecified requirements, undefined domain terms, unclear scope boundaries, internal contradictions. Cross-artifact contradictions are out of scope (→
consistency-check). If none found, say so and stop. - Resolve one at a time — per ambiguity, quote the ambiguous line and ask one question — multiple-choice (AskUserQuestion) when bounded, open-ended otherwise. Iterate until resolved or the user stops.
- Edit in place — encode each resolution into the target artifact; show old→new, confirm before writing. Edit only the target artifact.
- Flag downstream staleness — do NOT cascade. Identify downstream artifacts a resolution may have invalidated; list them in the handoff; recommend
feature-edit(which owns cascade). - Handoff — emit a summary.
Handoff
Emit per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null. If downstream staleness flagged: human_action_needed: yes, recommended_next: "/engineer.feature-edit to propagate".
References
- Foundation Design — artifact schemas
- The DAE methodology page — clarify as embedded pattern + standalone skill
© swingerman, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in engineer/skills/clarify of swingerman/engineer.
Open the folder on GitHubat commit 32947eb
Compare with similar skills
Clarify 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 |
|---|---|---|---|---|---|---|
| Clarify this skillswingerman/engineer | 154 | — | ~620 | Automated safety check: Pass | MIT | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 31 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDfossasia/eventyay-interpretation | 1.6k | 28 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
TDD
fossasia/eventyay-interpretation
Test-driven development. An agent skill from fossasia/eventyay-interpretation.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
More from swingerman/engineer
All 27 skills in this repoCrap Analyzer
swingerman/engineer
A skill your agent uses to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods.
Atdd Mutate
swingerman/engineer
A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.
Fix
swingerman/engineer
A skill your agent uses to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end.
Atdd
swingerman/engineer
A skill your agent uses to drive feature work through the Acceptance Test Driven Development workflow — Given/When/Then specs before code, a project-specific test pipeline, and two parallel test…
Harden
swingerman/engineer
Use after a feature passes Light Verify (CP7), to prove the tests actually catch bugs and, where the code warrants it, to formally check its invariants — Checkpoint 8.
Next
swingerman/engineer
Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project.
Related
Categories
Questions about Clarify
What does Clarify do?
A skill your agent uses when a single DAE artifact has ambiguities to resolve. Clarify is an agent skill from swingerman/engineer. Use when a single DAE artifact has ambiguities to resolve.
When should I use Clarify?
Clarify fits situations like: A single DAE artifact has ambiguities to resolve; — /engineer.clarify; clarify this spec; resolve ambiguities.
How do I install Clarify in Claude Code?
Run `npx skills add swingerman/engineer --skill clarify -a claude-code`. Or copy the skill folder (engineer/skills/clarify in swingerman/engineer) into .claude/skills/clarify in your project. Claude Code loads it when a task matches its description.
How do I install Clarify in Codex?
Run `npx skills add swingerman/engineer --skill clarify -a codex`. Or copy the skill folder (engineer/skills/clarify in swingerman/engineer) into .agents/skills/clarify in your project. Codex loads it when a task matches its description.
Can I use Clarify 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 swingerman/engineer --skill clarify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clarify, .gemini/skills/clarify, .github/skills/clarify and .opencode/skills/clarify in your project.
What does Clarify need to run?
SKILL.md names no scripts, command-line tools or credentials: Clarify is instructions for the agent only.
Does Clarify access the network?
SKILL.md names 1 domain. As links in the text: notion.so. This is read from the text; nothing was executed.
Is Clarify 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 Clarify use?
Clarify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clarify use?
About 620 tokens (SKILL.md is roughly 2.5k 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 Clarify?
Skills that share tags, products or a category with Clarify: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (fossasia/eventyay-interpretation, 1.6k stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clarify?
swingerman (a GitHub user) maintains it in swingerman/engineer, which has 154 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 23, 2026.
Source: swingerman/engineer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.