skills/doctor/SKILL.md
Check whether TARS is installed correctly and the local helper can read and write the workspace
npx skillsauth add ajayjohn/tars-work-assistant doctorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when setup fails, TARS cannot write to the workspace, or the user asks whether their install is healthy.
Call mcp__tars_vault__runtime_info with the active workspace path if known.
If it returns:
required_runtime: "ok": tell the user the local TARS helper is connected.required_runtime: "error": show the recovery block in Step 3.optional_search: "degraded": mention that semantic search enhancements are unavailable, but setup and keyword search still work.Do not treat missing fastembed or sqlite-vec as setup blockers.
If the helper is connected and a workspace path is known, summarize:
_system/install.yaml existsKeep the first answer short. Put technical details under Details only if needed.
If mcp__tars_vault__runtime_info is unavailable, do not mention raw MCP tool names in the user-facing response. Say:
I can't safely finish TARS setup because the local TARS helper is not connected.
This helper creates and checks the workspace in the background. This is not an Obsidian, calendar, task, email, or Slack issue. Those integrations are optional.
Try this:
1. Make sure the TARS plugin is enabled in Claude.
2. Restart Claude so the local helper starts.
3. Run `/doctor` again, or ask "check my TARS install."
4. When the check passes, run `/welcome`.
Details: TARS needs Python 3.10+ and the bundled `tars-vault` helper. It does not require the Python `mcp` package for first setup. Semantic search packages are optional and can be added later.
If the user is in a code checkout and asks for technical help, suggest:
python3 scripts/doctor.py --workspace "<path to your TARS workspace>"
If the check passes, end with:
TARS is ready. If this is your first run, use `/welcome`, or just say "set up TARS."
If there are warnings only, say setup can continue and name the feature that will be degraded.
tools
Open Collider semantic collision engine for non-obvious idea generation
content-media
Zero-setup quick demo. Accept pasted content or a natural request and produce a useful structured artifact in under 5 minutes.
development
Vault hygiene — broken links, orphans, schema violations, staleness, contradictions, sparse notes, framework state drift
tools
Deterministic first-run setup contract for the TARS Markdown workspace, with optional Obsidian mode and deferred setup continuation