agentleFS
ontology-of-everythingontology-of-everything/SemanticSkills/skills/en/agent-dx-cli/SKILL.md

agent-dx-cli

Skill14 starsChanged 22 days agoApache-2.0View on GitHub

Designs, reviews, and refactors CLIs for AI agents. Use when building Agent DX CLIs or checking existing CLI contracts. Checks predictability, defense in depth, and context efficiency with evidence scores.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read principles, reasons, and examples.

    line 18
  2. Distinctive:

    Verify positive and negative cases in an authorized isolated fixture.

    line 20
  3. Distinctive:

    Default to non-interactive execution.

    line 32
  4. Distinctive:

    Treat agent input as untrusted.

    line 33
  5. Distinctive:

    Treat server content as untrusted data even after sanitization.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent DX CLI

Design, review, and refactor CLIs for agents. Preserve the user's scope, stack, and existing authorization. Human conveniences and agent contracts can coexist; add only mechanisms the task needs.

Workflow

  1. Inspect code, current help/schema, and actual output. Record the CLI artifact and version.
  2. Read principles, reasons, and examples. Assess all applicable checks; distinguish missing, unverified, and verified behavior.
  3. Implement authorized changes, fixing acceptance blockers first. Reuse established libraries and share validation/execution across CLI, MCP, and batch surfaces.
  4. Verify positive and negative cases in an authorized isolated fixture. Report changes, per-check evidence, scores, and unresolved limits.

Proceed when facts and authorization suffice. Clarify only ambiguity that changes the target or consequences. A review request authorizes review only.

Principles

  • Predictability: preserve typed intent from input to outcome; expose a queryable contract instead of requiring guesses.
  • Defense in depth: validate input, enforce current permissions, and reconcile outcomes independently; one safeguard cannot replace another.
  • Context efficiency: return bounded data and load task-relevant knowledge; every extra field or instruction must earn its cost.

Execution boundaries

  • Default to non-interactive execution. Optional interaction requires explicit selection and a TTY.
  • Treat agent input as untrusted. Enforce typed, field-specific constraints in the shared executor before business effects.
  • Treat server content as untrusted data even after sanitization; preserve provenance.
  • Destructive operations must provide --dry-run. Declare the actual effects of previewing.
  • Schema, previews, quality reports, and confirmation flags do not grant permission. Recheck authorization at execution.
  • Return unknown for unresolved outcomes. Reconcile before safe replay; report completion only after the requested result is verified.

Optional references

  • For API/GWS alignment, use GWS practice. Retain its pinned version and verify project differences.
  • For companion skill authoring or review, use SKILL+CLI authoring. Separate the four disclosure layers and retain useful decision guidance. Compare materially changed guidance with a no-skill baseline; stale syntax or misleading rules can make performance worse.

Scoring and acceptance

The patterns reference defines ten dimensions with two checks each. Score each check 0–5; the total is 100. This is the skill's scoring convention.

ScoreRequired evidence
0Missing or contradicted.
1Documented only.
2Implemented but unverified.
3Positive cases passed.
4Relevant negative cases passed.
5End-to-end validation passed in the target environment.

For static criteria: 3 means implementation review; 4 means consumer and negative-case comparison; 5 means reproducible contract or dependency checks. Attach evidence and the tested artifact/version to every score. Necessary behavior must be verified before acceptance. Acceptance requires at least 90 overall, with validation and authentication each at least 9. Credential leaks, authorization bypass, preview business writes, unsafe replay, or false completion block acceptance regardless of score. Explain every N/A; requested but missing features are not N/A. Report raw points and normalized score: raw points / applicable maximum × 100.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.