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.
Write session-based exploratory testing charters to find what scripted tests miss.
Install Exploratory Test Charter
$ npx skills add mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exploratory-test-charter --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/exploratory-test-charter .claude/skills/exploratory-test-charter && 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 "exploratory-test-charter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exploratory-test-charter into .claude/skills/exploratory-test-charter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploratory-test-charter", 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/mohitagw15856/pm-claude-skills/tree/main/skills/exploratory-test-charterType 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 mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exploratory-test-charter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/exploratory-test-charter .agents/skills/exploratory-test-charter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "exploratory-test-charter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exploratory-test-charter into .agents/skills/exploratory-test-charter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploratory-test-charter", 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 mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exploratory-test-charter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/exploratory-test-charter .cursor/skills/exploratory-test-charter && 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 "exploratory-test-charter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exploratory-test-charter into .cursor/skills/exploratory-test-charter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploratory-test-charter", 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/mohitagw15856/pm-claude-skills.git --path skills/exploratory-test-charter--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 mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exploratory-test-charter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/exploratory-test-charter .gemini/skills/exploratory-test-charter && 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 "exploratory-test-charter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exploratory-test-charter into .gemini/skills/exploratory-test-charter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploratory-test-charter", 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 mohitagw15856/pm-claude-skills exploratory-test-charterInstalls 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 mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/exploratory-test-charter .github/skills/exploratory-test-charter && 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 "exploratory-test-charter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exploratory-test-charter into .github/skills/exploratory-test-charter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploratory-test-charter", 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 mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exploratory-test-charter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/exploratory-test-charter .opencode/skills/exploratory-test-charter && 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 "exploratory-test-charter" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exploratory-test-charter into .opencode/skills/exploratory-test-charter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploratory-test-charter", 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
exploratory-test-charter- GitHub stars
- 1.4k
- Token cost
- ~912 tokens
- SKILL.md length
- 426 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write session-based exploratory testing charters to find what scripted tests miss.
- Asked to plan exploratory testing
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Write a test charter
What it does
Exploratory Test Charter is an agent skill from mohitagw15856/pm-claude-skills. Write session-based exploratory testing charters to find what scripted tests miss. Use when asked to plan exploratory testing, write a test charter, design a testing session, or do risk-based exploration of a feature. Produces focused charters — a mission, areas/risks to explore, tactics and oracles, and timeboxed sessions — so exploration is purposeful and accountable, not random clicking.
Its SKILL.md is about 910 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 QA and bug reports. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to plan exploratory testing
- Write a test charter
- Design a testing session
- Do risk-based exploration of a feature
Example prompts
- “/exploratory-test-charter”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
Exploratory Test Charter loads about 912 tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 426 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 426 words, ~912 tokens.
Download SKILL.mdSave it as
.claude/skills/exploratory-test-charter/SKILL.md (or your agent's skills folder).- name
- exploratory-test-charter
- description
- Write session-based exploratory testing charters to find what scripted tests miss. Use when asked to plan exploratory testing, write a test charter, design a testing session, or do risk-based exploration of a feature. Produces focused charters — a mission, areas/risks to explore, tactics and oracles, and timeboxed sessions — so exploration is purposeful and accountable, not random clicking.
Exploratory Test Charter Skill
Exploratory testing finds the bugs scripts don't — but only when it's chartered: a clear mission, a defined area, and a timebox, so it's purposeful and you can report what was covered. This skill writes session-based charters that point skilled testing at the riskiest areas, with the tactics and oracles to know when something is wrong.
Working from a brief
Given "explore the new checkout flow", write the charters anyway — infer the risk areas, useful tactics, and oracles, labelling assumptions. Prioritise by risk. Never hand back a question instead of charters.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- The target — the feature/area and what it does.
- Risk & concerns — what's new/changed, what's complex, and where failure would hurt most.
- Context — users, platforms, data, and integrations involved.
- Time available — to size and prioritise the sessions.
Output Format
Exploratory Testing Charters: [feature]
Risk overview — the few areas most worth exploring and why (new, complex, high-impact, historically buggy).
Charters — one per focused session (Session-Based Test Management style):
Charter: Explore [area] using [tactics/data] to discover [information about risk].
- Areas / things to cover: the specific surfaces, flows, inputs, states.
- Test ideas & tactics: how to probe it — boundary values, interruptions, bad data, concurrency, navigation, roles/permissions, network conditions, etc.
- Oracles (how you'll know it's wrong): the spec, consistency, comparable products, user expectations, "would a user be annoyed?".
- Timebox: ~60–90 min (short/long), priority.
- Data / setup needed.
Provide 3–6 charters, prioritised by risk.
Reporting — what to capture per session: bugs found, areas covered vs. not, new risks/questions, and follow-up charters.
Show full SKILL.md (165 more words)Show less
Quality Checks
- Each charter has a clear mission (explore X to discover Y about risk Z) — not "test the app"
- Charters are prioritised by risk, with the rationale stated
- Test ideas/tactics are concrete (boundaries, interruptions, bad data, roles…), not generic
- Oracles are named so the tester can recognise a problem
- Sessions are timeboxed and sized to the available time
- A lightweight reporting structure (coverage + findings) is included
Anti-Patterns
- Do not write "explore the feature" with no mission, areas, or oracles — that's aimless clicking
- Do not skip prioritisation — explore the riskiest areas first
- Do not turn charters into scripted step-by-step cases — exploration needs freedom within focus
- Do not omit oracles — without them a tester can't tell right from wrong
- Do not leave sessions open-ended — timebox them so coverage is accountable
Based On
Session-Based Test Management (exploratory testing) — chartered, risk-prioritised, timeboxed sessions with explicit tactics and oracles.
Example Trigger Phrases
- "Plan exploratory testing."
- "Write a test charter."
- "Design a testing session."
- "Do risk-based exploration of a feature."
© mohitagw15856, 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 skills/exploratory-test-charter of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Exploratory Test Charter 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 |
|---|---|---|---|---|---|---|
| Exploratory Test Charter this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~912 | Automated safety check: Pass | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Moav E2EMotherofallVPNs/MoaV | 449 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Creating A Coral TaskHuman-Agent-Society/CORAL | 1.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Launch Rlmarin-community/marin | 3.9k | — | ~894 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
Actionbook Web Test
actionbook/actionbook
Run browser-based web tests against websites using Actionbook CLI.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Exploratory Test Charter
What does Exploratory Test Charter do?
Write session-based exploratory testing charters to find what scripted tests miss. Exploratory Test Charter is an agent skill from mohitagw15856/pm-claude-skills. Write session-based exploratory testing charters to find what scripted tests miss.
When should I use Exploratory Test Charter?
Exploratory Test Charter fits situations like: asked to plan exploratory testing; write a test charter; design a testing session; do risk-based exploration of a feature.
How do I install Exploratory Test Charter in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a claude-code`. Or copy the skill folder (skills/exploratory-test-charter in mohitagw15856/pm-claude-skills) into .claude/skills/exploratory-test-charter in your project. Claude Code loads it when a task matches its description.
How do I install Exploratory Test Charter in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a codex`. Or copy the skill folder (skills/exploratory-test-charter in mohitagw15856/pm-claude-skills) into .agents/skills/exploratory-test-charter in your project. Codex loads it when a task matches its description.
Can I use Exploratory Test Charter 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 mohitagw15856/pm-claude-skills --skill exploratory-test-charter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exploratory-test-charter, .gemini/skills/exploratory-test-charter, .github/skills/exploratory-test-charter and .opencode/skills/exploratory-test-charter in your project.
What does Exploratory Test Charter need to run?
SKILL.md names no scripts, command-line tools or credentials: Exploratory Test Charter is instructions for the agent only.
Does Exploratory Test Charter 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 Exploratory Test Charter 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 Exploratory Test Charter use?
Exploratory Test Charter 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 Exploratory Test Charter use?
About 912 tokens (SKILL.md is roughly 3.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 Exploratory Test Charter?
Skills that share tags, products or a category with Exploratory Test Charter: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 449 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Exploratory Test Charter?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.