Index of every page on this site: llms.txt
All skills
block avatar

/berdctl-new-command

@77422a9
by Block Open Sourceblock/berd1.1k stars
137
Run it yourself

Use when adding, extending, modifying, or removing berdctl commands, verbs, nouns, schemas, help text, or any of the berdctl surface.

  • 1 file
  • 2.2 KB
  • Updated 3 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/block/berd/berdctl-new-command

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈39 tokens for metadata: the name and description. ≈528 when used: this file.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈155 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

berdctl command changes

One command is one renderer module. Descriptors are the source for zod validation, TS input types, CLI help, and generated contract JSON. Background: docs/berdctl-architecture.md.

Rules

  • Verbs must be UI-visible. Prefer reversible mutations, but one-way visible product actions like creating a session or sending a prompt are allowed. Delete, bulk, silent, invisible, or broadly destructive work requires auth/confirmation design review.
  • Put bounds in zod; clap mirrors them.
  • Keep descriptors import-pure. Import stores, Tauri APIs, navigation, providers, and caches only inside execute/precheck.
  • Do not hand-edit generated contract JSON.
  • Keep the broker command-agnostic; normal command changes do not touch src-tauri/plugins/berdctl/.
  • Breaking wire reshapes bump both discovery.rs constants and the contract mirror. New commands and optional fields are not reshapes.

Workflow

  • Add commands with just new-command <noun> <verb>.
  • Implement src/features/berdctl/commands/impl/<verbNoun>.ts with: .strict() schema, .describe() on every field, summary, description, helpFooter, safety metadata, optional precheck, and execute.
  • Update inventories only when needed: registry.ts group cli.about, top-level help pins in tree.rs, and distro/skills/berdctl/SKILL.md for overview changes.
  • Run pnpm generate:berdctl-contract, pnpm vitest run src/features/berdctl, and cargo test -p berdctl from src-tauri/.
  • Before review, confirm the verb is UI-visible and either reversible or a direct visible product action, help is complete, error messages name the fixing command, artifacts are regenerated, and tests cover the behavior.

Keep CLI shapes expressible by the generated field walker. If a requested operation needs an explicit null or another shape that generic flags cannot represent safely, model it as a separate command action instead of adding command-specific Rust mapping. Example: use session move --project-id <id> for moving into a project and session clear-project for moving out.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 77422a9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 months ago

README badge

README badge for block/berd/berdctl-new-command