- Step 1: When DB file not found at expected path, trace createDb() calls in server code to find the resolvedPath (defaults to ~/.mc/data/mission-control.db).
- Step 2: Verify DB existence with: ls -la ~/.mc/data/mission-control.db
- Step 3: Inspect schema with: sqlite3 ~/.mc/data/mission-control.db ".schema tasks"
- Step 4: Check actual column names (e.g., 'state' vs 'status'); adjust frontend types or backend schema accordingly.
- Step 5: Validate data inserted correctly: sqlite3 ~/.mc/data/mission-control.db "SELECT * FROM tasks ORDER BY timestamp DESC LIMIT 5;"
- Pitfall: The frontend Task interface may use 'status' while the DB uses 'state'; always verify before debugging application logic.
Mc Db Discovery
该 Skill 提供一套排查流程：在预期路径找不到 Mission Control SQLite 数据库时，从服务端代码追踪 createDb() 的解析路径，用 ls 确认文件是否存在，用 sqlite3 查看 tasks 表结构，核对实际列名（如 state 与 status 的差异）并调整前端类型或后端 schema，最后查询最新记录验证数据已写入。
安装技能
复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。
执行命令安装此 skill： npx secure-skills-cli add mc-db-discoveryMetadata
- name
- mc-db-discovery
- description
- Systematic workflow to locate and verify the Mission Control SQLite database when path assumptions fail, and reconcile frontend/backend schema mismatches.