Skip to content
Agentmart
Submit a tool

identify-variables

Identify conditions, values, states, and paths that could influence software behavior during exploratory testing.

Skill by testobsessed

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/testobsessed-identify-variables

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Identify conditions, values, states, and paths that could influence software behavior during exploratory testing.

Use cases: testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/identify-variables

What's inside

Skill name
identify-variables
Description
Identify conditions, values, states, and paths that could influence software behavior during exploratory testing.
License
MIT
Instructions
17 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Identifying Variables

Identify anything whose value or condition could affect behavior. Look beyond visible inputs:

- data values, formats, sizes, counts, selections, and relationships;
- operation, input method, navigation path, order, repetition, and timing;
- current, prior, transitional, and persisted state;
- identity, random seed, cache, clock, and accumulated history;
- topology, configuration, permissions, resources, and external dependencies;
- loaded, restored, copied, imported, or interactively constructed origin;
- live runtime, saved representation, derived projection, and rendered view.

Use the variable map to choose meaningful variations; design comparisons around the current question rather than varying everything at once.

Use exploratory-session-log unless the caller opts out; reuse the active session and guidance already loaded. Capture raw evidence promptly, indexing at closure or handoff. Standalone requests need only a proportionate raw record; create supporting records when useful. If the logger is unavailable, append dated evidence in the caller's workspace.

From testobsessed/exploratory-testing-skills, MIT.

More from testobsessed/exploratory-testing-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 4, 2026 (25 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from testobsessed

Cite this page

identify-variables skill. Agent Mart. https://agentmart.dev/skills/testobsessed-identify-variables (last updated 2026-10-24)