using-markitlisted

# Using Markit Use this skill to run `markit` reliably in terminal-based agent workflows. ## Scope - Convert known files and known URLs to markdown. - Use deterministic output modes for downstream automation. - Troubleshoot common failures. Do not cover plugin authoring, provider authoring, or onboarding context files unless the user explicitly asks. ## Non-goals - Open-web discovery, ranking, or source-finding. - Recency-filtered/domain-filtered research workflows. - Interactive browser automation workflows (click/fill/login/stateful navigation). - DOM action tasks that depend on browser node IDs. ## Defaults 1. Prefer the global `markit` command. 2. If `markit` is missing, install globally with `npm install -g markit-ai`. 3. Use `--json` when the result will be parsed or used for branching decisions. 4. Use `-q` when raw markdown should be piped/copied as-is. 5. Do not mutate config/provider settings unless the user asks. 6. Do not run `markit onboard`. ## Workflow 1. **Validate source and intent** - Identify source type: local file, URL, or stdin. - For binary formats (PDF, DOCX, images, audio), prefer file paths over stdin. - Confirm whether output should be parsed (`--json`) or emitted as markdown (`-q`). - If the user needs source discovery first (not conversion of known sources), stop and request specific URLs or files. 2. **Preflight command availability** - Check tool presence: - `markit --version` - If missing: - `npm install