What problem does it solve? Adding custom commands to a NocoBase application's nocobase CLI requires understanding how plugins expose a ./cli entry, how topics are registered, and how oclif commands are assembled into one command tree. This Skill provides the reference implementation and rules for doing that correctly. ## Core Features & Use Cases - Command authoring: Write oclif Command subclasses with args, flags, examples, and --json output conventions. - CLI plugin entry: Use defineCliPlugin to declare a topic and map sub-command names (including colon-nested names like artifact:build) to command classes. - Manifest setup: Configure package.json exports for ./cli and declare @oclif/core as a peer dependency so the plugin and application share one copy. - Use Case: You are building a NocoBase plugin that needs a nocobase demo greet command. Follow this Skill to create the command class, wire it into cli/index.ts, register the plugin in the application's cli/plugins.ts, and verify it with pnpm nocobase demo --help. ## Quick Start Ask the assistant to scaffold a new oclif command for your NocoBase plugin and register it under a topic in the application's nocobase CLI.