ableton-mind-build-168d01 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ableton-mind-build-168d01 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill whenever the user asks to execute, implement, continue, scaffold, redo, synchronize, evaluate or gate concrete work for ableton-mind. Conceptual questions about PLAN.md can be answered directly without launching a full cycle.
For broad repo quality audits, command sweeps, security/usability/refactor review, missing-test coverage or release-readiness hardening, hand off to ableton-mind-quality-audit. That sibling harness uses a different team and report structure while preserving this build harness for PLAN.md phase execution.
| Track | Agent | Domain |
|---|---|---|
| Lead | architect | plan, ADRs, integration, phase gates |
| A — Server | ts-server-engineer | TS/Node MCP server, tools, resources, prompts |
| A — Bridge | python-bridge-engineer | Python Remote Script, LiveAPI, TCP JSON-RPC |
| B — Knowledge | knowledge-curator | device schemas, packs, scales, MIDI data |
| C — Recipes | recipe-designer | JSON music recipes |
| D — Distribution | distribution-docs-engineer | MCPB/DXT, npm, Docker, docs, CI, CLI |
| E — QA | qa-integration | parity, contract drift, recipe lint, smoke, gate |
| F — Local Copilot | local-copilot-engineer | local LLM, chat, ask, tool tiers, safety policy |
| Mode | When | Action |
|---|---|---|
| Initial | PROGRESS.md does not exist | Create workspace state and plan Phase 0 spike |
| Continue | PROGRESS.md points to ongoing work | Write the next cycle briefing and continue |
| Redo phase | User requests a redo | Archive current workspace and recreate the requested scope |
| Phase gate | QA exists but PROGRESS is stale | Read verdict, update PROGRESS and decide next cycle |
| Sync only | User asks status | Report state without dispatching tracks |
The architect writes _workspace/cycle-briefing-{N}.md with: PLAN phase, one-sentence goal, assignments per track, changed contracts, dependencies and gate criteria. Keep tasks concrete and file-scoped.
Run tracks in parallel only when their write scopes do not conflict and the current tooling/user permission allows sub-agents. Phase 0 spike is sequential: contract, bridge, server, integration. Later phases can run server, bridge, knowledge, recipes, distribution, local-copilot and QA in parallel as dependencies allow. Local-copilot work owns src/llm/ and src/cli/chat.ts; coordinate with distribution for public docs and with QA for safety-tier tests.
When work returns, read each _workspace/*_summary.md and the QA report. Compare delivered work with the briefing, write or update ADRs for contract changes, update PROGRESS.md and report the outcome in under 200 words.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.