Skip to content
Skills Library
Programming · Review & audit

command-surface-audit

/command-surface-audit

Audit, classify and run the real ableton-mind command surface. Use whenever package scripts, CI commands, docs commands, bins, "run all commands", stale scripts, broken commands or command coverage are mentioned.

Licence
MIT
Last repository change
23.06.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Audit, classify and run the real ableton-mind command surface. Use whenever package scripts, CI commands, docs commands, bins, "run all commands", stale scripts, broken commands or command coverage are mentioned.

Triggers from the description

run all commands
Original author description

Audit, classify and run the real ableton-mind command surface. Use whenever package scripts, CI commands, docs commands, bins, "run all commands", stale scripts, broken commands or command coverage are mentioned.

How it works

  1. Workflow
  2. Report Format
  3. Local Execution
Original SKILL.md headings · 31 lines, 175 words
SKILL.md preview
---
name: command-surface-audit
description: Audit, classify and run the real ableton-mind command surface. Use whenever package scripts, CI commands, docs commands, bins, "run all commands", stale scripts, broken commands or command coverage are mentioned.
---

# Command Surface Audit

Use this skill to build an evidence-backed command matrix from the current checkout.

## Workflow

1. Inventory commands from package.json scripts, bin entries, .github/workflows, docs snippets and scripts/.
2. Classify each command as safe read/check, local mutating, external read, publish/write or hardware/live.
3. Run safe commands. Use dry-run or check mode for packaging and release paths.
4. Do not run publish/write commands without explicit user confirmation.
5. Record exact failures with the command, output signature, source file and likely owner.
6. Flag commands that exist in docs but not package.json, or package scripts that no workflow/docs can reach.

## Report Format

Write _workspace/quality-audit/command-surface-{N}.md:

| Command | Source | Class | Status | Evidence | Notes |
|---|---|---|---|---|---|

End with:
- Broken commands.
- Stale or undocumented commands.
- Commands blocked by missing Live, hardware, credentials or external services.
- Suggested tests or docs changes.

## Local Execution

When running locally from Codex, use `rtk proxy <command>` for raw commands. Keep raw command names in the report so CI/users can copy them.

Versions

The database has no other skills named command-surface-audit.

Database snapshot: 13.11.2026 · package version 9d4018280a09 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90test-coverage-expansion
    Add or plan missing tests for ableton-mind. Use for untested code, regression tests, coverage gaps, commands without tests, TS tools, Python bridge handlers, CLI scripts, recipes, knowledge, distribution checks and audit-driven fixes.
  • 100ableton-mind-quality-audit
    Orchestrates the ableton-mind quality audit team whenever the user asks for full repo audit, quality hardening, run/test all commands, security/usability/flow review, refactor audit, coverage expansion, launch readiness, release readiness, regression hunt, or to…
  • 100cli-commands
    Use when adding or modifying CLI command (`but` commands) under `crates/but/src`.
  • 95webiny-cli-extensions
    Adding custom commands to the Webiny CLI using CliCommandFactory. Use this skill when the developer wants to create a custom CLI command, add a data migration script, build a code generator, create deployment scripts, export CMS content, or add health check commands. Covers…
  • 91manifest-surface
    Use when a manifest declares tools, hooks or commands a document also lists.
  • 100add-fallback-commands
    Add fallback commands to your Command Palette extension for catch-all search behavior. Use when asked to add search functionality, query matching, direct input handling, calculator-style evaluation, URL opening, command execution, or results that appear when no other extension…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.