testing
/testing
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
- Author
- OdradekAI ↗
- Repository
- bundles-forge ↗
- Licence
- Apache-2.0
- Last repository change
- 27.04.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.04.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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
Original author 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
How it works
- Overview
- Step 1: Resolve Input & Detect Scope
- Phase 1: Local Test Environment
- Phase 2: Hook Smoke Tests
- Phase 3: Component Discovery
- Phase 4: Cross-Platform Readiness
- Phase 5: Test Report
- Integration with Releasing
- Common Mistakes
- Inputs
SKILL.md preview
---
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
1. Create `../dev-marketplace/` adjacent to the project directory
2. 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>"
}
]
}
```
3. 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
---
## 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 in this package (2)
- SKILL.md 7 KB
- references/platform-test-guides.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · OdradekAI/bundles-forge | 100 | Apache-2.0 |
| iuliandita/skills | 100 | MIT |
| wrongstack/wrongstack | 100 | MIT |
| langwatch/langwatch | 100 | Apache-2.0 |
| mcouthon/agents | 100 | MIT |
| nteract/nteract | 100 | BSD-3-Clause |
| kettleofketchup/DraftForge | 100 | GPL-3.0 |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| TheBeardedBearSAS/claude-craft | 100 | MIT |
Database snapshot: 13.11.2026 · package version 53d477613d86 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95plugin-release-checker
Validate plugin content quality before release. Run skill-validator across plugins, verify marketplace.json completeness, check plugin.json version consistency, and detect broken documentation cross-references. Use when preparing a release, before running release.sh, or when… - 100hook-publisher
Hook スクリプトを claude-code-plugin リポジトリの正しい構造に配置するスキル。 hook の構造検証、既存 hook との重複チェック、plugin.json 生成、marketplace.json 登録を行う。 Use when: hook をプラグインリポジトリに公開したい、hook を移動したい、hook をパッケージ化したい。 Triggers: "hook を公開", "hook publish", "hook をプラグインに追加", "PostToolUse hook を配置", "hook をコピー", "hook publisher - 100plugin-marketplace
Guide for creating and managing Claude Code plugin marketplaces. Use when setting up a marketplace, validating marketplace.json, or distributing plugins. - 90create-plugin
Scaffold a new AI agent plugin directory with valid manifest, component directories, and marketplace wiring. Use when starting a new plugin, adding a plugin to a multi-plugin repository, or reviewing a plugin before submission. - 100cc-plugin-development
Build, validate, and publish Claude Code plugins — manifest schema, skill/command/agent/hook authoring, MCP server integration, marketplace publishing, version management. Use this skill whenever creating a new plugin, adding a skill/command/agent to an existing plugin,… - 100plugin-test-cycle
Builds, deploys, and tests the typemux-cc Claude Code plugin locally. Handles the full cycle from cargo build through cache clearing, marketplace registration, plugin install, and LSP verification. Triggers on: 'plugin test', 'test plugin', 'plugin cycle', 'deploy and test',…