Agent skill

Testing

A skill your agent uses when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating…

Apache-2.0Auto-check passedTesting & QA

Install Testing

skills CLI

$ npx skills add OdradekAI/bundles-forge --skill testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install OdradekAI/bundles-forge testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/OdradekAI/bundles-forge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/testing .claude/skills/testing && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "testing" agent skill from https://github.com/OdradekAI/bundles-forge/tree/main/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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

$skill-installer install https://github.com/OdradekAI/bundles-forge/tree/main/skills/testing

Type 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.

skills CLI

$ npx skills add OdradekAI/bundles-forge --skill testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install OdradekAI/bundles-forge testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OdradekAI/bundles-forge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/testing .agents/skills/testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "testing" agent skill from https://github.com/OdradekAI/bundles-forge/tree/main/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.

skills CLI

$ npx skills add OdradekAI/bundles-forge --skill testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install OdradekAI/bundles-forge testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OdradekAI/bundles-forge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/testing .cursor/skills/testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "testing" agent skill from https://github.com/OdradekAI/bundles-forge/tree/main/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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

$ gemini skills install https://github.com/OdradekAI/bundles-forge.git --path skills/testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add OdradekAI/bundles-forge --skill testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install OdradekAI/bundles-forge testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OdradekAI/bundles-forge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/testing .gemini/skills/testing && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "testing" agent skill from https://github.com/OdradekAI/bundles-forge/tree/main/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.

GitHub CLI

$ gh skill install OdradekAI/bundles-forge testing

Installs 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).

skills CLI

$ npx skills add OdradekAI/bundles-forge --skill testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/OdradekAI/bundles-forge.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/testing .github/skills/testing && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "testing" agent skill from https://github.com/OdradekAI/bundles-forge/tree/main/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.

skills CLI

$ npx skills add OdradekAI/bundles-forge --skill testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install OdradekAI/bundles-forge testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OdradekAI/bundles-forge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/testing .opencode/skills/testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "testing" agent skill from https://github.com/OdradekAI/bundles-forge/tree/main/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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: testing
GitHub stars: 229
Used in: 1 other repo
Token cost: ~1.8k tokens
SKILL.md length: 687 words
Files: 2 (incl. references)
Skills in repo: 8
Repo updated: Apr 27, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating…

Works in 6 steps: Resolve Input & Detect Scope → Local Test Environment → Hook Smoke Tests → …
Testing a bundle-plugin locally before release — generating dev-marketplace environments
SKILL.md covers Overview, Step 1: Resolve Input & Detect…, Phase 1: Local Test Environment and Phase 2: Hook Smoke Tests, plus 8 more sections
Calls bash

What it does

Testing is an agent skill from OdradekAI/bundles-forge. Use when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating cross-platform readiness

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/platform-test-guides.md`).

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: An agentic skills framework & bundle-plugin engineering toolkit that works. The licence is Apache-2.0.

When your agent uses it

Testing a bundle-plugin locally before release — generating dev-marketplace environments
Verifying component discovery
Running hook smoke tests
Validating cross-platform readiness

Example prompts

“/testing”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Resolve Input & Detect Scope
Local Test Environment
Hook Smoke Tests
Component Discovery
Cross-Platform Readiness
Test Report

What it can do on your machine

Read from SKILL.md and the folder at commit c1b0e10. 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:
- bash
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

Testing loads about 1.8k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 687 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~51
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.8k

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 OdradekAI/bundles-forge at commit c1b0e10, republished under its Apache-2.0 licence (© OdradekAI). 687 words, ~1,831 tokens.

Download SKILL.mdSave it as .claude/skills/testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: testing
description: Use when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating cross-platform readiness

Testing Bundle-Plugins

Overview

Dynamic verification of a bundle-plugin project: install it locally, confirm components are discoverable, validate hooks fire correctly, and run cross-platform smoke tests. Complements bundles-forge:auditing (static analysis) with runtime validation.

Core principle: Audit tells you if the structure is correct; testing tells you if it actually works.

Skill type: Flexible — adapt the test scope based on target platforms and project maturity.

Announce at start: "I'm using the testing skill to verify this plugin works correctly."

Step 1: Resolve Input & Detect Scope

Input Normalization

The target must be a local bundle-plugin project (has package.json + skills/). Remote URLs and archives are not supported — testing requires a local working directory.

Scope Detection

Target	Mode
Project root with multiple platforms	Full testing — all 5 test phases
Project root with single platform	Platform testing — phases 1-4 for the target platform
Single skill directory	Skill-only testing — phase 3 (component discovery) only

Phase 1: Local Test Environment

Generate a temporary dev-marketplace for local installation testing.

For Claude Code

Create ../dev-marketplace/ adjacent to the project directory
Generate .claude-plugin/marketplace.json pointing to the project:

json

{
  "name": "<project-name>-dev",
  "owner": { "name": "dev" },
  "plugins": [
    {
      "name": "<project-name>",
      "source": "../<project-directory-name>"
    }
  ]
}

Instruct the user:

Dev marketplace created at ../dev-marketplace/

To install locally:
  /plugin marketplace add ./dev-marketplace
  /plugin install <project-name>@<project-name>-dev

To reload after changes:
  /plugin marketplace update <project-name>-dev

To clean up when done:
  /plugin marketplace remove <project-name>-dev

For Cursor

Cursor plugins are installed from local paths directly:

To test locally in Cursor:
  1. Open Cursor Settings → Extensions → Install from Path
  2. Select the project root directory
  3. Reload Cursor to pick up changes

For Other Platforms

Codex: Symlink skills/ into ~/.agents/skills/ per INSTALL.md
OpenCode: Register the plugin path in .opencode/plugins/
Gemini CLI: Point the extension config to the local directory

See references/platform-test-guides.md for platform-specific setup instructions.

Phase 2: Hook Smoke Tests

Verify hooks execute without errors by running them directly.

SessionStart Hook

bash

bash hooks/session-start

Expected: Exits 0, prints a one-line prompt containing the project name and available skills. No stderr output.

Verify output format:

If CLAUDE_PLUGIN_ROOT is set: valid JSON with hookSpecificOutput.additionalContext
If CURSOR_PLUGIN_ROOT is set: valid JSON with additional_context
Neither: plain text

Custom Hooks (if configured)

If the project defines PreToolUse or PostToolUse hooks in hooks.json, run each referenced script directly and verify:

PreToolUse scripts: exit 0 on a valid project, exit 2 to block writes on critical issues
PostToolUse scripts: always exit 0, warnings go to stderr

OpenClaw Hook-Pack (if present)

Verify hooks/openclaw-bootstrap/HOOK.md has valid YAML frontmatter with events declaration, and handler.js uses ESM export default.

Phase 3: Component Discovery

Verify that all declared components can be found by the host platform.

Skills

For each directory under skills/:

Contains SKILL.md
Frontmatter has name and description
name matches directory name
description starts with "Use when..."

Agents

For each .md file under agents/:

Has YAML frontmatter
Body has 5+ non-empty lines (self-contained protocol)

Platform Manifests

For each target platform:

Manifest file exists and is valid JSON
Paths in manifest resolve to existing files/directories
Version matches package.json version

Show full SKILL.md (263 more words)Show less

Phase 4: Cross-Platform Readiness

Generate a platform-specific test checklist based on references/platform-test-guides.md and known limitations from bundles-forge:scaffolding — references/platform-adapters.md.

Known Limitations to Verify

Platform	Limitation	Test
Claude Code	Plugin caching breaks `../` paths	Verify no `../` in hook commands or manifest paths
Cursor	Bootstrap lost after `/clear`	Verify session-start runs independently of prior context
Codex	No hook bootstrap	Verify AGENTS.md or INSTALL.md has manual setup instructions
OpenCode	Plugin JS must use ESM	Verify `export default` in `.opencode/plugins/*.js`
Gemini CLI	Extension needs `contextFileName`	Verify `gemini-extension.json` has `contextFileName` field
OpenClaw	Hook-pack wiring uncertain	Document as known risk in test report

Phase 5: Test Report

Generate a test report summarizing all findings.

Report Structure

markdown

# Test Report: <project-name>

**Date:** YYYY-MM-DD
**Scope:** [Full / Platform / Skill-only]
**Platforms tested:** [list]

## Results

| Phase | Status | Details |
|-------|--------|---------|
| 1. Local Environment | PASS/FAIL/SKIP | ... |
| 2. Hook Smoke Tests | PASS/FAIL/SKIP | ... |
| 3. Component Discovery | PASS/FAIL/SKIP | N skills, K agents |
| 4. Cross-Platform | PASS/FAIL/SKIP | ... |

## Issues Found

### Critical
- (blocks release)

### Warnings
- (should fix before release)

## Recommendations

- ...

Report location: .bundles-forge/audits/<timestamp>-test-report.md

Integration with Releasing

In the releasing pipeline, testing runs after auditing and before version bump:

audit → test → version bump → publish

If testing reveals critical issues, the release pipeline is blocked until they are resolved.

Common Mistakes

Mistake	Fix
Skipping local install test	Always test with a real dev-marketplace — file discovery differs from file existence
Testing only on one platform	Run cross-platform checklist for every target platform
Ignoring hook exit codes	Hooks must exit 0 to avoid blocking the host; test all code paths
Not cleaning up dev-marketplace	Always remove dev-marketplace after testing
Testing after version bump	Test before bumping — avoid releasing a broken version

Inputs

project-directory (required) — bundle-plugin project root

Outputs

test-report — comprehensive test results written to .bundles-forge/audits/
dev-marketplace (temporary) — local marketplace directory for installation testing

Integration

Called by:

bundles-forge:releasing — pre-release dynamic verification (after audit, before version bump)
User directly — standalone local testing during development

Calls:

(none — testing is a pure executor, does not dispatch other skills)

Files

SKILL.md and 1 other file (references) in skills/testing of OdradekAI/bundles-forge.

SKILL.md
references/platform-test-guides.md

Open the folder on GitHubat commit c1b0e10

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in OdradekAI/bundles-forge, which our catalogue first saw on October 7, 2026.

majiayu000/claude-skill-registryskills/bash/testing

Compare with similar skills

Testing 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.

Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Testing this skillOdradekAI/bundles-forge	229	1 repos	~1.8k	Automated safety check: Pass	Apache-2.0	5 mo ago
Reproduce Chat Statesdifferent-ai/openwork	24k	—	~673	Automated safety check: Pass	Custom licence	today
Dynamo Jira TicketDynamoDS/Dynamo	2k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Minimal Run And Auditlllllllama/RigorPilot-Skills	497	2 repos	~691	Automated safety check: Pass	MIT	14 days ago
Moav E2EMotherofallVPNs/MoaV	448	—	~1.9k	Automated safety check: Notes	MIT	today
Anchor Reprolynxlangya/techne	105	1 repos	~1.2k	Automated safety check: Pass	MIT	3 mo ago

Similar skills

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.
24k GitHub stars~673 tokensUpdated today
Testing & QAAuto-check passed
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
2k GitHub stars~1.1k tokensUpdated today
Testing & QAAuto-check passed
Minimal Run And Audit
lllllllama/RigorPilot-Skills
Rigor Run skill for README-first deep learning repo reproduction.
497 GitHub starsUsed in 2 repos~691 tokens
Testing & QAAuto-check passed
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.
448 GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check: notes
Anchor Repro
lynxlangya/techne
Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.
105 GitHub starsUsed in 1 repo~1.2k tokens
Testing & QAAuto-check passed
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…
1k GitHub stars~2.2k tokensUpdated 29 days ago
Testing & QAAuto-check passed

Questions about Testing

What does Testing do?

A skill your agent uses when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating…. Testing is an agent skill from OdradekAI/bundles-forge.

When should I use Testing?

Testing fits situations like: testing a bundle-plugin locally before release — generating dev-marketplace environments; verifying component discovery; running hook smoke tests; validating cross-platform readiness.

How do I install Testing in Claude Code?

Run `npx skills add OdradekAI/bundles-forge --skill testing -a claude-code`. Or copy the skill folder (skills/testing in OdradekAI/bundles-forge) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.

How do I install Testing in Codex?

Run `npx skills add OdradekAI/bundles-forge --skill testing -a codex`. Or copy the skill folder (skills/testing in OdradekAI/bundles-forge) into .agents/skills/testing in your project. Codex loads it when a task matches its description.

Can I use Testing 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 OdradekAI/bundles-forge --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.

What does Testing need to run?

Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (bash).

Does Testing 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 Testing 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 Testing use?

Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.

What are the alternatives to Testing?

Skills that share tags, products or a category with Testing: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

OdradekAI (a GitHub organization) maintains it in OdradekAI/bundles-forge, which has 229 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on April 27, 2026.

Source: OdradekAI/bundles-forge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Testing Bundle-Plugins

Overview

Step 1: Resolve Input & Detect Scope

Input Normalization

Scope Detection

Phase 1: Local Test Environment

For Claude Code

For Cursor

For Other Platforms

Phase 2: Hook Smoke Tests

SessionStart Hook

Custom Hooks (if configured)

OpenClaw Hook-Pack (if present)

Phase 3: Component Discovery

Skills

Agents

Platform Manifests

Phase 4: Cross-Platform Readiness

Known Limitations to Verify

Phase 5: Test Report

Report Structure

Integration with Releasing

Common Mistakes

Inputs

Outputs

Integration

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from OdradekAI/bundles-forge

Related

Questions about Testing