test-nodebridge-handler
Run and validate NodeBridge message handlers via the test-nodebridge script.
Install
mkdir -p .claude/skills/test-nodebridge-handler && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4710" && unzip -o skill.zip -d .claude/skills/test-nodebridge-handler && rm skill.zipInstalls to .claude/skills/test-nodebridge-handler
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when testing NodeBridge handlers using `bun scripts/test-nodebridge.ts`, including listing available handlers and passing parametersKey capabilities
- →List available NodeBridge handlers
- →Execute specific handlers
- →Pass parameters via key-value pairs
- →Pass complex data via JSON
How it works
It runs a test script that interfaces with NodeBridge handlers, allowing for parameter injection and response validation.
Inputs & outputs
When to use test-nodebridge-handler
- →Testing specific nodebridge handlers
- →Listing available system handlers
- →Passing complex data to handlers
- →Debugging handler logic
About this skill
Test NodeBridge Handler
Overview
This skill guides the process of testing NodeBridge message handlers using the test script.
Usage
List All Available Handlers
bun scripts/test-nodebridge.ts --list
Test a Specific Handler
bun scripts/test-nodebridge.ts <handler> [options]
Parameter Passing
Key-Value Format
bun scripts/test-nodebridge.ts handler.name --key=value --flag=true --count=42
- Values are auto-converted:
true/false→ Boolean, numbers → Number - Boolean flags without value:
--verbosebecomes{ verbose: true }
JSON Data Format
For complex data, use --data with JSON (takes priority over --key=value):
bun scripts/test-nodebridge.ts handler.name --data='{"key":"value","nested":{"foo":"bar"}}'
Available Handler Categories
| Category | Example Handlers |
|---|---|
| models | models.list, models.test |
| config | config.list |
| providers | providers.list |
| mcp | mcp.list, mcp.getStatus |
| outputStyles | outputStyles.list |
| project | project.getRepoInfo, project.workspaces.list |
| projects | projects.list |
| sessions | sessions.list |
| skills | skills.list, skills.get, skills.add, skills.remove, skills.preview, skills.install |
| slashCommand | slashCommand.list |
| git | git.status, git.detectGitHub |
| utils | utils.getPaths, utils.detectApps, utils.playSound |
Examples
Test Model
bun scripts/test-nodebridge.ts models.test --model=anthropic/claude-sonnet-4-20250514
bun scripts/test-nodebridge.ts models.test --model=openai/gpt-4o --prompt="Say hello" --timeout=5000
List Models
bun scripts/test-nodebridge.ts models.list
Get File Paths
bun scripts/test-nodebridge.ts utils.getPaths --cwd=/path/to/dir --maxFiles=100
List Projects
bun scripts/test-nodebridge.ts projects.list --includeSessionDetails=true
Get Skill Details
bun scripts/test-nodebridge.ts skills.get --name=my-skill
Git Status
bun scripts/test-nodebridge.ts git.status --cwd=/path/to/repo
Output Format
The script outputs:
- Request - JSON of the data sent to the handler
- Response - JSON of the handler's return value with timing
Success response structure:
{
"success": true,
"data": { ... }
}
Error response structure:
{
"success": false,
"error": "Error message"
}
Notes
- The script has a 30-second timeout for all requests
- Exit code 0 on success, 1 on error
- Use
-hor--helpfor help message
When not to use it
- →Production handler execution
- →Non-NodeBridge testing
Prerequisites
Limitations
- →30-second request timeout
- →Requires handler availability
How it compares
It provides a standardized CLI interface for testing backend handlers, bypassing the need for full application integration.
Compared to similar skills
test-nodebridge-handler side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| test-nodebridge-handler (this skill) | 1 | 6mo | Review | Intermediate |
| nestjs-expert | 37 | 6mo | Review | Advanced |
| openevidence-local-dev-loop | 1 | 25d | Caution | Beginner |
| ideogram-local-dev-loop | 0 | 25d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by neovateai
View all by neovateai →You might also like
nestjs-expert
davila7
Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.
openevidence-local-dev-loop
jeremylongshore
Set up local development environment for OpenEvidence integration. Use when configuring development workflow, setting up testing environment, or creating a rapid iteration loop for clinical AI development. Trigger with phrases like "openevidence dev setup", "openevidence local", "openevidence development", "openevidence testing environment".
ideogram-local-dev-loop
jeremylongshore
Configure Ideogram local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Ideogram. Trigger with phrases like "ideogram dev setup", "ideogram local development", "ideogram dev environment", "develop with ideogram".
node
dannybrown37
Invoke when the user is writing or debugging TypeScript or JavaScript code, working with Node.js tooling, or asking about ESLint/Prettier configuration.
supabase-developer
daffy0208
Build full-stack applications with Supabase (PostgreSQL, Auth, Storage, Real-time, Edge Functions). Use when implementing authentication, database design with RLS, file storage, real-time features, or serverless functions.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.