aops-cli-sugar-authoring

Guides authoring of sugar CLI subcommands over hosted aops-cli and eops-cli domain operations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eeemzs/aops --skill aops-cli-sugar-authoring-eeemzs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aops-cli-sugar-authoring
Source: https://github.com/eeemzs/aops/tree/main/assets/skills/aops-cli-sugar-authoring
Command: npx skills add https://github.com/eeemzs/aops --skill aops-cli-sugar-authoring-eeemzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adding a new CLI subcommand over an existing hosted domain operation is error-prone: developers guess payload fields, bypass the agent gateway, or forget write guards. This Skill provides a thin authoring playbook that keeps every new sugar command wired to the canonical agent schema discovery contract. ## Core Features & Use Cases - Authoring Patterns for Both CLIs: Step-by-step patterns for commander-based aops-cli commands and the manual argv plus topic registry approach in eops-cli. - Pre-Authoring Discovery Workflow: Commands to confirm operation registration, pull live input contracts via agent schema --tool, and search architecture guides before writing code. - Guard and Safety Conventions: Enforces --apply/--confirm guards for hosted writes, idempotency keys, and mandatory schema-discovery pointers in help text. - Use Case: You need to add aops-cli docman publish over an existing hosted operation. Follow the playbook to confirm the operation exists, fetch its input schema, implement the subcommand with shared helpers, and verify with --help and a preview invoke. ## Quick Start Ask the agent to author a new aops-cli sugar subcommand for a specific hosted domain operation, following the aops-cli-sugar-authoring skill and verifying it with agent schema discovery.

Frequently Asked Questions about aops-cli-sugar-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new aops-cli subcommand over a hosted operation?▼

Open the domain commander file in apps/aops/apps/aops-cli/src/commands, append a subcommand inside the make<Domain>Command() factory using .command/.description/.option, and implement a run function reusing requireApiState and invokeHostedToolWithApiState. Verify with --help and agent schema.

How do I author an eops-cli sugar command with the topic registry?▼

Append a topic entry with route, summary, usage, options, notes, and examples in the domain registry file, then add a builder function returning action, operationId, and input. Wire the builder into the dispatch chain and verify with a build plus --help.

When should I create a sugar command instead of using agent invoke?▼

Create a sugar only when it adds composite behavior across multiple operations, better naming, or improved operator ergonomics. If a plain agent invoke --tool <id> call suffices, authoring a sugar is an anti-pattern.

Does every write-shaped CLI command need --apply and --confirm flags?▼

Yes, hosted write sugars must require --apply and --confirm together, with an optional --idempotency-key. Help text must also point operators to agent schema --tool <toolId> so they fetch the live input contract instead of guessing payload fields.

What is out of scope for CLI sugar authoring?▼

Authoring new operations inside a domain kit, exposing them through the host plugin, or changing the federated catalog is out of scope. Those follow the kit and host-plugin authoring flow documented in the tooling-cli-host-plugin-system guide.