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 designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline configuration, bug-finding and coverage…
Install Issta Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills issta-experiments --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/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ISSTA-Skills/skills/issta-experiments .claude/skills/issta-experiments && 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 "issta-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISSTA-Skills/skills/issta-experiments into .claude/skills/issta-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issta-experiments", 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/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISSTA-Skills/skills/issta-experimentsType 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 brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills issta-experiments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ISSTA-Skills/skills/issta-experiments .agents/skills/issta-experiments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issta-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISSTA-Skills/skills/issta-experiments into .agents/skills/issta-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issta-experiments", 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 brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills issta-experiments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ISSTA-Skills/skills/issta-experiments .cursor/skills/issta-experiments && 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 "issta-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISSTA-Skills/skills/issta-experiments into .cursor/skills/issta-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issta-experiments", 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/brycewang-stanford/Awesome-Journal-Skills.git --path ISSTA-Skills/skills/issta-experiments--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 brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills issta-experiments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ISSTA-Skills/skills/issta-experiments .gemini/skills/issta-experiments && 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 "issta-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISSTA-Skills/skills/issta-experiments into .gemini/skills/issta-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issta-experiments", 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 brycewang-stanford/Awesome-Journal-Skills issta-experimentsInstalls 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 brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ISSTA-Skills/skills/issta-experiments .github/skills/issta-experiments && 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 "issta-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISSTA-Skills/skills/issta-experiments into .github/skills/issta-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issta-experiments", 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 brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills issta-experiments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ISSTA-Skills/skills/issta-experiments .opencode/skills/issta-experiments && 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 "issta-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISSTA-Skills/skills/issta-experiments into .opencode/skills/issta-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issta-experiments", 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
issta-experiments- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 499 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline configuration, bug-finding and coverage…
- Auditing ISSTA experiments
- SKILL.md covers Experiment audit, What experiments are for at…, Claim-to-evidence design table and Vignette: evaluating a…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering real subject programs and benchmarks like Defects4J
What it does
Issta Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline configuration, bug-finding and coverage metrics, non-parametric comparison with effect sizes, equal-budget protocols, repeated runs, and matching evidence to the claim being made.
Its SKILL.md is about 1.1k 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: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Auditing ISSTA experiments
- Covering real subject programs and benchmarks like Defects4J
- Fair tool-baseline configuration
- Bug-finding and coverage metrics
Example prompts
- “/issta-experiments”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. 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
No URLs in SKILL.md.
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
Issta Experiments loads about 1.1k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 499 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 brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 499 words, ~1,140 tokens.
Download SKILL.mdSave it as
.claude/skills/issta-experiments/SKILL.md (or your agent's skills folder).- name
- issta-experiments
- description
- Use when designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline configuration, bug-finding and coverage metrics, non-parametric comparison with effect sizes, equal-budget protocols, repeated runs, and matching evidence to the claim being made.
ISSTA Experiments
Use this before submission when the evaluation is not yet locked. ISSTA experiments earn or lose the paper on the evaluation criterion, and the reviewer pool knows the standard subjects, baselines, and statistics — so design the study to answer the exact claim, on subjects a reviewer recognizes.
Experiment audit
- Match each claim to its evidence: a bug-finding claim needs a benchmark with ground truth, a coverage claim needs a measurement protocol, a scalability claim needs a size sweep.
- Use real subjects and established benchmarks where they exist — Defects4J for Java faults, real-world CVEs for security bugs, standard fuzzing corpora — so results are comparable to prior work, not to a private subject set.
- Configure baselines fairly and at an equal budget: same time, same seeds, same subjects. A baseline throttled to lose is the fastest way to lose a reviewer's trust.
- Compare with proper statistics: non-parametric tests (e.g. Mann-Whitney U) and an effect size (e.g. Vargha-Delaney Â₁₂) rather than a single run, because testing and analysis results are stochastic and rarely normal.
- Report the stochastic protocol: seeds, timeout budgets, iteration counts, number of repeated runs, and hardware. State whether a table is a mean over runs and give the spread.
- Audit for the usual confounds: subject selection bias, overfitting to the benchmark, counting duplicate crashes as distinct bugs, and mismatches between what the metric measures and what the claim asserts.
What experiments are for at this venue
- ISSTA experiments exist to show a technique works on software that matters, evaluated fairly. One well-designed study on an established benchmark outweighs five extra ad-hoc subjects.
- The strongest evaluations separate finding from being right: a repair that passes tests is not a correct repair; a crash is not automatically a distinct bug. Report the gap between the easy metric and the property you care about.
- Reviewers check that the subjects and budget make the comparison meaningful — a fuzzer compared for one hour says little about a claim over 24-hour campaigns.
Show full SKILL.md (171 more words)Show less
Claim-to-evidence design table
| Claim | Matching evaluation | Reject pattern avoided |
|---|---|---|
| "Finds more true bugs" | Established benchmark with ground-truth labels; dedup by root cause | "Bugs counted by distinct crashes, not distinct faults" |
| "Higher coverage than baseline X" | Equal budget, same subjects, same instrumentation | "Baseline run in a weaker configuration" |
| "Scales to large programs" | Size sweep with wall-clock and memory reported | "Scalability asserted, never measured" |
| "Improvement is real, not noise" | Repeated runs + non-parametric test + effect size | "Single run presented as representative" |
Vignette: evaluating a test-generation tool
A paper claims a new generator achieves higher fault-detection than an existing one. The plan: run both on Defects4J at an equal per-subject time budget, repeat each configuration enough times to estimate variance, count detected faults (not generated tests), compare with a non-parametric test and report Â₁₂, and disclose the subjects where the tool underperforms rather than dropping them.
subjects Defects4J (pinned revision), N faults
budget equal wall-clock per subject, both tools
runs R repeats per subject; report mean and spread
metric faults detected (ground truth), not tests generated
statistic Mann-Whitney U + Vargha-Delaney A12
honesty report subjects where the tool losesStatistical reporting floor
- Repeated runs and seeds for every stochastic result; captions must say what the numbers summarize.
- Report the compute actually consumed, not vague feasibility language.
Output format
[Evaluation readiness] strong / adequate / weak
[Claim -> evidence map] <claim: benchmark/metric/statistic>
[Baseline fairness] equal-budget / configured-to-lose / unclear
[Statistical gaps] <runs / test / effect size / variance>
[Subject/benchmark gaps] <established benchmark used? subjects pinned?>
[Decision-critical next run] <one experiment>© brycewang-stanford, 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 ISSTA-Skills/skills/issta-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Issta Experiments 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 |
|---|---|---|---|---|---|---|
| Issta Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | 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 | 32 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| 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
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
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 brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Issta Experiments
What does Issta Experiments do?
A skill your agent uses when designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline configuration, bug-finding and coverage…. Issta Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline configuration, bug-finding and coverage metrics, non-parametric comparison with effect sizes, equal-budget protocols, repeated runs, and matching evidence to the claim being made.
When should I use Issta Experiments?
Issta Experiments fits situations like: auditing ISSTA experiments; covering real subject programs and benchmarks like Defects4J; fair tool-baseline configuration; bug-finding and coverage metrics.
How do I install Issta Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a claude-code`. Or copy the skill folder (ISSTA-Skills/skills/issta-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/issta-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Issta Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a codex`. Or copy the skill folder (ISSTA-Skills/skills/issta-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/issta-experiments in your project. Codex loads it when a task matches its description.
Can I use Issta Experiments 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 brycewang-stanford/Awesome-Journal-Skills --skill issta-experiments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issta-experiments, .gemini/skills/issta-experiments, .github/skills/issta-experiments and .opencode/skills/issta-experiments in your project.
What does Issta Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Issta Experiments is instructions for the agent only.
Does Issta Experiments 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 Issta Experiments 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 Issta Experiments use?
Issta Experiments 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 Issta Experiments use?
About 1.1k tokens (SKILL.md is roughly 4.6k 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 Issta Experiments?
Skills that share tags, products or a category with Issta Experiments: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 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 Issta Experiments?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.