How do I install the CLI Agent Surface Work skill?

Run npx skillmds@latest add clawic/cli-agent-surface-work-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CLI Agent Surface Work safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CLI Agent Surface Work?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CLI Agent Surface Work free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CLI Agent Surface Work?

clawic (@clawic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CLI Agent Surface Work by clawic — Agent Skill

Name: CLI Agent Surface Work
Author: clawic

File contents

cli-agent-surface-work

Work on the public claw CLI as an agent-facing contract.

Procedure

Use claw search, claw commands resolve, and claw inspect commands|command-intents|why|schemas|storage|codebase --json when available. For governance-heavy CLI/doc work, start with claw governance doctor --json to collect the current reads, skills, closing checks, external-pending lanes, and stale-doc risks.
Read the CLI ADR, decision map, naming guide, and the tests for the affected command.
Keep stable JSON output in the accepted envelope shape unless the command is explicitly in migration debt.
Add registry entries, generated/help docs, aliases, negative legacy tests, and smoke coverage with the behavior.
For new CLI words or aliases, classify the phrase as covered, candidate_alias, gap, future, blocked, or external_pending; record explicit demand through claw commands record instead of activating semantic routing by guess.
If the change adds durable docs, ADRs, guardrails, or harnesses, register the discovery route in docs/discoverability.registry.json per docs/adr/0017-discoverability-and-meta-code-routing.md.
Treat aliases as thin portals; avoid semantic routers that guess intent.
Update docs and examples in the same change when public usage changes.
Before closure for canon, route, storage, permission, ADR, skill, or Clawix/ClawJS integration changes, run node scripts/discoverability-check.mjs closure --changed-file <path> --json. The closing report must cite the real claw search ... --json and claw inspect ... --json evidence plus the discovered artifact, or mark the work PARTIAL/BLOCKED.

Constraints

claw is the public CLI. Do not add new public clawjs, clawix, or framework-domain CLIs.
Do not expose secret-bearing, destructive, cost-bearing, or native permission actions without host approval boundaries.
Do not make source files the primary map when the CLI registry can answer.
Do not report public CLI surface closure as complete when the affected artifact cannot be found by claw search and inspected through claw inspect.

---name: cli-agent-surface-work-2description: Change the public agent-facing CLI surface while preserving registry-backed discovery, JSON envelopes, aliases, docs, and tests.---# cli-agent-surface-workWork on the public `claw` CLI as an agent-facing contract.## Procedure1. Use `claw search`, `claw commands resolve`, and `claw inspect commands|command-intents|why|schemas|storage|codebase --json` when available. For governance-heavy CLI/doc work, start with `claw governance doctor --json` to collect the current reads, skills, closing checks, external-pending lanes, and stale-doc risks.2. Read the CLI ADR, decision map, naming guide, and the tests for the affected command.3. Keep stable JSON output in the accepted envelope shape unless the command is explicitly in migration debt.4. Add registry entries, generated/help docs, aliases, negative legacy tests, and smoke coverage with the behavior.5. For new CLI words or aliases, classify the phrase as `covered`, `candidate_alias`, `gap`, `future`, `blocked`, or `external_pending`; record explicit demand through `claw commands record` instead of activating semantic routing by guess.6. If the change adds durable docs, ADRs, guardrails, or harnesses, register the discovery route in `docs/discoverability.registry.json` per `docs/adr/0017-discoverability-and-meta-code-routing.md`.7. Treat aliases as thin portals; avoid semantic routers that guess intent.8. Update docs and examples in the same change when public usage changes.9. Before closure for canon, route, storage, permission, ADR, skill, or Clawix/ClawJS integration changes, run `node scripts/discoverability-check.mjs closure --changed-file <path> --json`. The closing report must cite the real `claw search ... --json` and `claw inspect ... --json` evidence plus the discovered artifact, or mark the work `PARTIAL/BLOCKED`.## Constraints- `claw` is the public CLI. Do not add new public `clawjs`, `clawix`, or framework-domain CLIs.- Do not expose secret-bearing, destructive, cost-bearing, or native permission actions without host approval boundaries.- Do not make source files the primary map when the CLI registry can answer.- Do not report public CLI surface closure as complete when the affected artifact cannot be found by `claw search` and inspected through `claw inspect`.

Frequently asked questions

CLI Agent Surface Work