← Back to Skills Marketplace
blueworldmarketing

Nerve Kanban Bwm

by blueworldmarketing · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
62
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install nerve-kanban-bwm
Description
Interact with the Nerve Kanban board API. CRUD tasks, manage workflow (execute, approve, reject, abort), handle proposals, configure the board. All endpoints...
Usage Guidance
This skill appears to be a straightforward API reference for a Nerve Kanban server and is instruction-only (no install). Before installing: 1) Confirm where the agent will point the skill (what base URL) and whether that server requires authentication — the SKILL.md does not explain auth or how credentials are provided. 2) If the server is not local/dev-only, require secure transport and credentials (API token, OAuth, etc.) and ensure the skill is configured to use them. 3) Note that the API can spawn subagent sessions via the execute endpoint — if you allow autonomous model invocation, the agent could start background runs; consider disabling autonomous invocation or restricting the skill to trusted agents. 4) Test the skill in an isolated/dev environment first and review the actual Nerve server's auth and access controls before giving it network access to production systems.
Capability Analysis
Type: OpenClaw Skill Name: nerve-kanban-bwm Version: 1.0.0 The skill bundle provides a standard API interface for managing a Kanban board (Nerve). It includes comprehensive documentation for CRUD operations on tasks and proposals, workflow management (execute, approve, reject), and board configuration. The logic is consistent with its stated purpose, and there are no indicators of data exfiltration, malicious execution, or prompt injection. All endpoints are documented under /api/kanban in SKILL.md and references/api.md.
Capability Assessment
Purpose & Capability
The name, description, and listed endpoints align: all declared endpoints and actions (CRUD, proposals, workflow, config) match a Kanban management skill. However, the SKILL.md does not declare how the agent learns the server origin (it only gives an example http://localhost:3000) nor does it mention any authentication requirements—this omission is notable because a production Kanban API would typically require auth. The lack of required env/config for the base URL or credentials is an unexplained choice.
Instruction Scope
The instructions are narrowly scoped to calling the documented REST endpoints and handling CAS/version conflicts; there are no directives to read local files or unrelated system state. One important capability described is POST /api/kanban/tasks/:id/execute which 'spawns a gateway subagent session' and relies on background pollers — that means using the skill can cause agent sessions to be created and run autonomously via the Nerve server. That behavior is within the skill's stated purpose (execute tasks), but it increases the operational blast radius and should be explicit in policy/authorization controls.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk from an install perspective — nothing is downloaded or written to disk by the skill package itself.
Credentials
The skill declares no required environment variables or primary credential. This can be fine for a local/dev-only Kanban server, but it's unexpected for a networked production API. If the Nerve server requires authentication, the skill provides no mechanism for supplying or restricting credentials. Absence of any auth/config guidance is a proportionality gap worth clarifying.
Persistence & Privilege
always:false and default autonomous invocation are appropriate. However, because the API includes an endpoint that spawns agent sub-sessions, allowing the model to autonomously invoke this skill (disable-model-invocation=false) could let the agent create background runs. This is not inherently incorrect but increases risk; consider gating autonomous calls or limiting which models/commands are allowed to trigger /execute.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install nerve-kanban-bwm
  3. After installation, invoke the skill by name or use /nerve-kanban-bwm
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the nerve-kanban skill. - Provides REST API access to Nerve Kanban board for full task and workflow management. - Supports creating, updating, deleting, reordering, and executing tasks through standard endpoints. - Integrates proposals for agent-suggested task changes, with operator approval workflows. - Enforces CAS versioning for concurrency control on updates and moves. - Includes configuration endpoints and clear status transition rules for tasks.
Metadata
Slug nerve-kanban-bwm
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Nerve Kanban Bwm?

Interact with the Nerve Kanban board API. CRUD tasks, manage workflow (execute, approve, reject, abort), handle proposals, configure the board. All endpoints... It is an AI Agent Skill for Claude Code / OpenClaw, with 62 downloads so far.

How do I install Nerve Kanban Bwm?

Run "/install nerve-kanban-bwm" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Nerve Kanban Bwm free?

Yes, Nerve Kanban Bwm is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Nerve Kanban Bwm support?

Nerve Kanban Bwm is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Nerve Kanban Bwm?

It is built and maintained by blueworldmarketing (@blueworldmarketing); the current version is v1.0.0.

💬 Comments