Update to Qodo

{
  "description": "Set up Qodo in a coding agent — install the CLI, sign in, and verify tools. Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 344
    },
    {
      "relative_path": "references/authentication.md",
      "size_in_bytes": 3062
    },
    {
      "relative_path": "references/host-recovery.md",
      "size_in_bytes": 1059
    },
    {
      "relative_path": "references/runtime.md",
      "size_in_bytes": 6950
    },
    {
      "relative_path": "references/skill-updates.md",
      "size_in_bytes": 1663
    }
  ],
  "name": "qodo-setup",
  "skill_md_contents": "---\nname: qodo-setup\ndescription: Set up Qodo in a coding agent — install the CLI, sign in, and verify tools. Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login.\nowner: Qodo\nmetadata:\n  vendor: qodo\n  version: \"1.0.12\"\n  recommended: \"true\"\n  package: \"qodo\"\n  distribution: \"marketplace\"\n  instruction_mode: \"embedded\"\n---\n\n# Set up Qodo\n\n## Description\n\nVerify the available Qodo path. Skill installation does not prove account or tool access.\n\n## Prerequisites\n\nA shell for CLI setup or a host-connected QAR MCP server. Never handle credentials.\n\n## Instructions\n\n### Connected MCP path\n\nInspect connected QAR tool schemas and annotations. With harmless input, call one\nread-only tool; catalog visibility does not prove read access. Check `isError` before\n`structuredContent`; an execution error is not readiness. A read cannot prove write\nauthorization: report writes as unverified until a user-authorized action. Never make\na test write. The host and QAR own MCP auth. Report missing tools, `MT-AUTH-FORBIDDEN`,\nand connection errors as MCP access issues; never ask for an API key. For MCP-only setup,\nreport the verified scope and hand off here. Skip every CLI step below. Continue only if CLI access was\nrequested or is needed for local collection, using the same deployment.\n\nResolve `references/...` links relative to this installed `SKILL.md` directory.\nRuntime/login setup does not authorize enterprise installation or maintenance.\nFor requested enterprise installs, disclose packages and maintenance before approval;\npreserve opt-outs, edits, owners and optional-package choices.\n\n### 1. Find or install the runtime\n\nIn PowerShell, resolve the verified native/Node invocation in [runtime.md](references/runtime.md)\nfirst; `qodo` below represents that invocation. On POSIX, probe PATH directly:\n\n```sh\nqodo --version\n```\n\nIf missing on POSIX, try `\"${QODO_HOME:-$HOME/.qodo}/bin/qodo\" --version`.\nFor a missing, old or unparseable runtime, follow the reference. Setup requests cover installation subject\nto host approvals; plugin installation alone does not. Retain the selected deployment.\n\nKeep the executable as `<qodo>`. Require Qodo CLI **2.0.0 or newer** before authentication.\n\n### 2. Connect\n\nRun:\n\n```sh\n<qodo> read whoami --json --skill qodo-setup --skill-version 1.0.12 --distribution marketplace --host codex\n```\n\nReuse a successful identity check. On failure, read\n[authentication.md](references/authentication.md) before choosing login.\n\nFor Cloud, run `<qodo> login` when signed out. For customer deployments, preserve the\ndocumented login endpoint; never fall back to Cloud. Wait for login, then recheck identity.\n\nReuse the successful execution context, requesting each required host approval. A diagnostic\napproval is not blanket permission. Stop on cancellation or denied permission.\n\n### 3. Verify tools\n\nOnly after identity succeeds, run:\n\n```sh\n<qodo> tools --refresh --json --skill qodo-setup --skill-version 1.0.12 --distribution marketplace --host codex\n```\n\nRequire a usable catalog and the task's capability; unrelated tools do not establish access.\nIf refresh fails, report that sign-in succeeded but tools are unavailable, with the exact error\nand `<qodo> tools --refresh` as the retry. Do not log in again for a catalog failure.\n\n## Configuration\n\nThe CLI owns credentials, transport and runtime updates; the package's\nlifecycle owner updates skills. For `QODO_NOTICE` updates or repeated Kiro read approvals,\nread [host-recovery.md](references/host-recovery.md) only when encountered.\n\n## Error Handling\n\nGive the actual error and one next action. Never report readiness after a failed\nidentity, canceled login or unavailable catalog. Never disable the keychain, copy credentials,\nchange host permission files, or offer unrestricted command approvals to make setup pass.\n\n## 4. Hand off\n\nConfirm Qodo connection and relevant tool readiness, then return to the authorized task.\nReadiness does not prove a later tool call succeeds. Do not install optional Standards.\n"
}