SkillAgentSearch skills...

nb-complete

AI coding assistant for Apache NetBeans. Connect Claude, OpenCode, Codex, Gemini and other coding agents through ACP, with IDE-aware tools via MCP.

Install / Use

npx skills add anandb/nb-complete

Installs into whichever agent you are using.

About this skill
📦

Other

Other agent config

Quality Score

84/100

Supported Platforms

Claude Code
Gemini CLI
OpenAI Codex

Tags

Our assessment of nb-complete

nb-complete scores 84/100 on our quality scale, 2780th of 4,705 Development & Engineering skills we index.

Its Other is 22 KB long, well organised into 22 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

It has 28 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
18/20
Description
15/15
Adoption
6/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated yesterday, so nb-complete is actively maintained.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-21. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nb-complete compared with similar skills

All 4 of these similar skills score higher than nb-complete; compare them before choosing.

SkillScoreStarsUpdatedFormat
nb-complete (this skill)by anandb84281d agoOther
taste-skillby Leonxlnx100120.0ktodayCLAUDE.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md

Frequently asked questions

How do I install nb-complete?
Run npx skills add anandb/nb-complete. The install tabs above show the steps for each supported agent.
Which AI agents does nb-complete work with?
It is written for Claude Code, Gemini CLI and OpenAI Codex, as a Other file. Other agents that read the same format can often use it too.
Is nb-complete safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is Apache-2.0-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is nb-complete still maintained?
The repository was last updated yesterday, so nb-complete is actively maintained.

BeanBot

Version Build Status Maven Central NetBeans License Buy Me A Coffee

An AI pair programmer that lives inside your NetBeans editor — ask, explain, generate, and refactor code without leaving the IDE.

BeanBot is a NetBeans IDE plugin designed to provide integrated AI capabilities through the Agent Client Protocol (ACP). It offers a structured chat interface for technical assistance, including code generation, project analysis, and automated task execution.

| | | | | :---: | :---: | :---: | | UI Screenshot 1 | UI Screenshot 2 | UI Screenshot 3 |


Getting Started

Supported coding harnesses: Oh My Pi, OpenCode, Codex, OpenClaw, Pi, Goose, Cursor, Copilot, Claude, Hermes, Gemini, Devin, Kilo Code, Cline, Jcode, Qwen Code, Kimi Code, Grok, OpenHands — pick one during onboarding or later from the help menu.

Token and cost statistics are captured from the ACP traffic itself, not from an external process: the usage updates and per-turn token figures a harness already sends are recorded into an embedded H2 database under the NetBeans user directory (beanbot/usage-stats.mv.db), so they survive restarts and are readable without a harness running. The currency button in the toolbar opens the panel, which breaks the figures down by model and by agent; they are approximate for harnesses that report incomplete usage. Not all harnesses report usage as a monetary value.

Project working directory (experimental): by default the ACP server keeps the working directory it started with, exactly as in 1.27.0 — switching to a session in another project never restarts it. Enabling Options > BeanBot > Actions → Enable ACP server restart on project switch binds the server to the session's project and restarts it on a switch; a restart terminates every session the running server serves. The option is read at startup, so changing it requires an IDE restart. This could be useful if you are running a containerized harness, and changing the project requires the workspace to be remounted.

Installation from Source

  1. Clone the repository:
    git clone https://github.com/anandb/nb-complete.git
    cd nb-complete
    
  2. Build the package:
    ./mvnw package -DskipTests
    
  3. Compiling the user guide needs tweego on the path.
  4. The generated NBM will be located in the ./target/nbm/ directory.
  5. Install the plugin through the Tools -> Plugins -> Downloaded tab.

Dependency Security Scan

The check-cvss profile runs OWASP Dependency-Check against the resolved dependencies:

export NVD_API_KEY=<your key>    # free from https://nvd.nist.gov/developers/request-an-api-key
./mvnw verify -Pcheck-cvss

The key is read from the NVD_API_KEY environment variable (or pass -Dnvd.api.key=...). Without a key the NVD feed is rate-limited heavily, so the first run is slow either way — it downloads the NVD dataset into the local Maven repository and caches it for later runs. Reports land in target/dependency-check-report.html and .json; accepted false positives belong in scripts/dependency-check-suppressions.xml.


Architecture

The project follows a hexagonal (ports & adapters) architecture integrated into the NetBeans Platform:

  • model/: ACP-compliant data records (sessions, messages, updates, config options). Zero dependencies on upper layers.
  • contract/: Service interfaces that define ports for session control, process management, and UI callbacks. manager/ implements; ui/ consumes.
  • manager/: Core orchestration — protocol client (JSON-RPC over stdin/stdout), session state machine, process lifecycle, and SSE strategy dispatch.
  • mcp/: MCP server integration — hosts a local server that registers the IDE tool set (editor context and navigation, filesystem, git/hg, tasks, projects, stash diff) so that the AI client can inspect open tabs and control editor navigation.
  • project/: NetBeans lifecycle hooks (@OnStart/@OnStop), the open-project manager, and the markdown project type.
  • tasks/: todo.txt task repository integration — bugtracking providers, issue cache, task editors.
  • support/: Pure utilities — logging, JSON mapping, text scanning, constants, browser helpers. Zero dependencies on upper layers.
  • db/: H2 persistence layer — usage-stats store, session store, pinned-message and model-list caches, SQL loader, preference migration. Depends on model/, support/, contract/.
  • pattern/: Compiled regex patterns as pure constants with no dependencies; consumed by all layers (ui, support, mcp, tasks, project, manager, db).
  • ui/: All Swing components — chat window, message bubbles, streaming animation, theming, options panel, stash diff viewer. Depends on contract/ interfaces, plus model/ data records, support/ utilities, and — through the ui/platform/ bridge only — the project/ layer. Never imports manager/ or mcp/.

Layer Dependencies

Dependencies flow downward only — no upward imports between layers:

        ┌─────────┐
        │   ui/   │  ← presentation (highest)
        └────┬────┘
             │
        ┌────▼────┐
        │manager/ │  ← business logic
        └────┬────┘
             │
    ┌────────┼────────┐
    ▼        ▼        ▼
┌────────┐ ┌────────┐ ┌────────┐
│ model/ │ │contract│ │support/│  ← data, interfaces, utils (lowest)
└────────┘ └────────┘ └────────┘

Connection Flow

┌──────────┐    SSE / JSON-RPC    ┌───────────────────┐
│  Sidebar │ ◄──────────────────► │ AcpProtocolClient │
│ (client) │     stdin/stdout     │    (transport)    │
└──────────┘                      └────────┬──────────┘
                                           │
                                      ┌────▼──────┐
                                      │ ProcessMgr│
                                      │ (dispatch)│
                                      └────┬──────┘
                                           │
                                      ┌────▼──────┐
                                      │SessionMgr │
                                      │ (session) │
                                      └────┬──────┘
                                           │
                              ┌─────────────┼─────────────┐
                              ▼             ▼             ▼
                        ┌──────────┐  ┌──────────┐  ┌──────────┐
                        │ Strategy │  │ Lifecycle│  │   MCP    │
                        │ Registry │  │ Handler  │  │  Server  │
                        └──────────┘  └──────────┘  └──────────┘

project/, mcp/, tasks/, db/, and pattern/ sit outside this five-layer model: project/ is NetBeans lifecycle wiring, mcp/ is the tool-serving adapter surface, tasks/ is a self-contained bugtracking feature, db/ is the H2 persistence adapter, and pattern/ is a dependency-free regex-constant satellite imported by every layer. model/, contract/, and support/ import none of project/, mcp/, or tasks/; manager/ reaches mcp/ only from ProcessManager (via McpManager/McpToolAdapter).


Source Organization

All source lives under src/main/java/github/anandb/netbeans/:

| Package | Files | Role | | --- | --- | --- | | contract/ | 29 | Service interfaces (UI callbacks, session & process control, permission & request handlers, pinned message control) | | db/ | 8 | H2 persistence layer (usage-stats store, session store, pinned-message and model-list caches, SQL loader, preference migration) | | manager/ | 29 | Core orchestration, protocol clients, session management, process lifecycle (includes strategy/, file cache, VCS ignore) | | mcp/ | 44 | MCP server integration (editor, filesystem, VCS, task and project tool providers, tool input records, message servlet) | | model/ | 33 | ACP-compliant data models (session, messages, updates, config options, color tokens, usage records); harness-catalog.yaml holds the harness definitions | | pattern/ | 40 | Compiled regex patterns (pure constants, no dependencies; consumed by all layers) | | project/ | 12 | NetBeans lifecycle hooks, project manager (includes mdproject/, the markdown project type) | | support/ | 42 | Utilities (logging, JSON mapping, text scanning, constants, browser helpers, pinned message store, shortcut utils, binary resolution) | | tasks/ | 17 | todo.txt task repository integration (bugtracking providers, issue cache, task editors) | | ui/ | 137 | Swing components, platform integration, markdown project UI (chat, bubbles, theming, options, stash diff, file search, send-to-assistant actions) |


Code Reading Path

For a guided walkthrough mapped to the plugin's execution flow, read files in this order:

Phase 1: Entry & Lifecycle

  1. project/ACPStartup.java — NetBeans @OnStart hook
  2. project/ACPShutdown.java — @OnStop cleanup
  3. src/main/resources/github/anandb/netbeans/ui/layer.xml — NetBeans registration (window menu/shortcuts, editor popup, Git toolbar); the Options panel is registered by annotation in ui/options/ACPOptionsPanelController.java

Phase 2: Server Process

  1. manager/ProcessManager.java — Owns the ACP server subprocess and acts as the central request-dispatch hub; spawn itself is in manager/ServerProcessLifecycle.startServer(), launching the harness binary the user selected (15 supported)
  2. support/BinaryResolver.java — Locates the binary on PATH
  3. manager/AcpProtocolClient.java — JSON-RPC over stdin/stdout, SSE read loop, pending request tracking

Phase 3: Session Management

  1. manager/SessionManager.java — Session CRUD, state machine, SSE routing
  2. manager/SessionStateMachine.java — Finite-state machine for session lifecycle
  3. model/Session.java — Session data record
  4. model/SessionUpdate.java — SSE notification payload model
  5. model/Message.java — Message model (prompts, tool calls, results)
  6. manager/PreambleSender.java — Posts the startup preamble for a new session, one chunk at a time

Phase 4: Strategy Dispatch (SSE handler chain)

  1. contract/UIHandler.java — Callback interface for rendering
  2. [`manager/strategy/StrategyRegistry.ja

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars28
CategoryDevelopment
Updated1d ago
Forks3

Languages

Java

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info