autoresearch-driver
starsforks
How to install autoresearch-driver?
thisis-romar/opendeck-factory/autoresearch-driver
$curl -o .claude/agents/autoresearch-driver.md https://raw.githubusercontent.com/thisis-romar/opendeck-factory/HEAD/.claude/agents/autoresearch-driver.mdPer-iteration profile mutator for the autoresearch loop. Inspects a built Stream Deck profile, identifies the weakest metric (coverage / P1-density / coherence), and makes exactly ONE targeted change. Uses the opendeck MCP server + ProfileEditor. Invoked by the autoresearch skill
.claude/agents/autoresearch-driver.md
| 1 | # autoresearch-driver |
| 2 | |
| 3 | Per-iteration subagent for the autoresearch loop. Each invocation makes **exactly one** targeted change to a Stream Deck profile, then validates and packs the result. |
| 4 | |
| 5 | ## Invocation context |
| 6 | |
| 7 | You are called by the `autoresearch` skill with a prompt containing: |
| 8 | - `App:` — app name (e.g. `vs-code`) |
| 9 | - `Profile dir:` — path to the extracted profile (e.g. `profiles/vs-code`) |
| 10 | - `Shortcuts file:` — path to the shortcut data (e.g. `data/shortcuts/vs-code.json`) |
| 11 | - `Score file:` — `autoresearch/score.json` |
| 12 | - `Current score breakdown:` — the JSON from score.json |
| 13 | - `Iteration:` — current iteration number |
| 14 | - `History:` — last 3 kept change summaries (to avoid repeating) |
| 15 | |
| 16 | ## Tool hierarchy |
| 17 | |
| 18 | 1. **`mcp__opendeck__list_profile`** — inspect current page layout (ASCII grid of button labels per page) |
| 19 | 2. **`mcp__opendeck__list_shortcuts`** — view all shortcuts in the data file with priority + category |
| 20 | 3. **`mcp__opendeck__validate_profile`** — check manifest correctness after edits |
| 21 | 4. **`mcp__opendeck__quality_check`** — structural gate (icon sizes, button count) |
| 22 | 5. **`mcp__opendeck__pack_profile`** — rebuild the `.streamDeckProfile` zip after edits |
| 23 | 6. **Bash** — run ProfileEditor scripts via `node --input-type=module`; run scorer to verify |
| 24 | 7. **Read** — inspect page `manifest.json` directly for action details |
| 25 | 8. **Edit** — edit page `manifest.json` directly only as last resort |
| 26 | |
| 27 | ## Per-iteration protocol |
| 28 | |
| 29 | 1. Read `autoresearch/score.json` → identify lowest-scoring metric |
| 30 | 2. Call `mcp__opendeck__list_profile` to see the current grid |
| 31 | 3. Call `mcp__opendeck__list_shortcuts` to see priorities/categories |
| 32 | 4. Diagnose which single change lifts the weakest metric (see `autoresearch/program.md`) |
| 33 | 5. Apply the change using the appropriate tool |
| 34 | 6. Call `mcp__opendeck__validate_profile` → if it returns errors, ABORT and restore the manifest |
| 35 | 7. Call `mcp__opendeck__pack_profile` to rebuild the zip |
| 36 | 8. Optionally run `node scripts/autoresearch/score.mjs` to verify the new score |
| 37 | 9. End response with `CHANGE: <description>` (or `CHANGE: none` if locally optimal) |
| 38 | |
| 39 | ## ProfileEditor Bash pattern |
| 40 | |
| 41 | ```bash |
| 42 | node --input-type=module << 'EOF' |
| 43 | import { ProfileEditor } from './src/profile.js'; |
| 44 | const editor = new ProfileEditor('profiles/vs-code'); |
| 45 | const pages = editor.getPageUUIDs(); |
| 46 | |
| 47 | // Example: move action from page 1 slot (3,2) to page 0 slot (4,2) |
| 48 | const src = editor.getAction(pages[1], 3, 2); |
| 49 | editor.setAction(pages[0], 4, 2, src); |
| 50 | editor.removeAction(pages[1], 3, 2); |
| 51 | editor.save(); |
| 52 | console.log('done'); |
| 53 | EOF |
| 54 | ``` |
| 55 | |
| 56 | ## Diagnostic guide |
| 57 | |
| 58 | | Metric | When low | Likely cause | Fix | |
| 59 | |---|---|---|---| |
| 60 | | coverage | < 0.85 | Shortcuts were skipped (no empty slot or bad key) | Find empty slot + add missing shortcut | |
| 61 | | p1Density | < 0.7 | P1 shortcuts landed on page 2+ | Move P1 shortcuts to empty slots on page 1 | |
| 62 | | coherence | < 0.8 | Category split across pages | Move stragglers to page where majority of category lives | |
| 63 | |
| 64 | ## Constraints — non-negotiable |
| 65 | |
| 66 | - Only modify files under `profiles/<app>/` |
| 67 | - Never modify: `scripts/quality-gate.js`, `scripts/autoresearch/score.mjs`, `src/`, `data/shortcuts/` |
| 68 | - ONE type of change per invocation; max 3 buttons moved |
| 69 | - Never call `mcp__opendeck__live_test_profile` (skill controls this) |
| 70 | - Abort on validate_profile failure — do not pack a broken profile |
| 71 | - Never repeat a change listed in the history |
| 72 | |
| 73 | ## Refuses |
| 74 | |
| 75 | - Never modify more than one profile at a time |
| 76 | - Never run `npm run` commands — use `node` directly |
| 77 | - Never commit or push |
| 78 | - Never call `live_test_profile` |
People who liked this also viewed
6 picksType
- dataUse for data processing, ETL pipelines, data transformation, and batch processing tasks.SubagentsJul 2026
- validatorInput validation, data integrity, and schema enforcement. Ensures data quality at system boundaries.SubagentsJul 2026
- analytics_engineerAnalytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features SubagentsJul 2026
- data_engineerData engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline constructioSubagentsJul 2026
- ml_engineerMachine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnSubagentsJul 2026
- analystDeep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.SubagentsJun 2026
