Skip to content
VEKTIS

Installing the Claude Code skills

VEKTIS ships a set of Claude Code skills — vektis-install, vektis-troubleshoot, vektis-discover, vektis-instrument, vektis-update, and vektis-bootstrap — that automate end-to-end SDK setup, debug failed events, and instrument analytics calls in your codebase. This page covers two things:

  1. How the skill files get into your project — where npx @vektis-io/tracker install-skills puts them and how to handle re-installs.
  2. How those skills authenticate with VEKTIS — the OAuth browser flow they use the first time you run one, and the paste-token fallback if your environment can’t open a browser.

Section 1 — Get the skills into your project

Section titled “Section 1 — Get the skills into your project”

After you’ve installed @vektis-io/tracker (any framework — see the per-framework guides), run:

Terminal window
npx @vektis-io/tracker install-skills

This copies the vektis-* skill directories plus the shared helper directory into <your-project>/.claude/skills/. Once they’re there, run claude /vektis-install (or any other /vektis-* skill) from your project root.

Flags

Section titled “Flags”
  • --create — create .claude/skills/ if it doesn’t exist. Without this flag, install-skills skips with a one-line hint when there’s no .claude/ directory.
  • --force — overwrite skill files you’ve edited locally. By default the script preserves any skill file you’ve modified and logs which ones were skipped.

Re-running is safe

Section titled “Re-running is safe”

The script tracks which files came from this package via a .vektis-managed marker and only updates them when this package ships new content. If you’ve customized a skill, your changes are preserved — pass --force if you want to discard them.

The _shared/ directory under .claude/skills/ is vendor-controlled — install-skills always overwrites it. Don’t edit those files; they’ll be replaced on the next run.

Package managers

Section titled “Package managers”

Works under npm, pnpm, yarn, and bun. The script reads INIT_CWD (set by all four) to find your project root.

Failure modes — no .claude/ directory, permission denied, no project root found — exit zero with a one-line hint, so they don’t break a CI install step.

Section 2 — Authenticate the skills

Section titled “Section 2 — Authenticate the skills”

The first time you run a /vektis-* skill that talks to VEKTIS, it needs an authenticated session against your VEKTIS account. Two paths.

OAuth browser flow (default)

Section titled “OAuth browser flow (default)”

Run any skill — claude /vektis-install, claude /vektis-discover, etc. The skill opens your default browser to a VEKTIS authorization page. You sign in (or are already signed in), click Authorize, and the skill receives a token automatically. No copying API keys, no pasting.

This is the recommended path for any environment with a working default browser.

Paste-token fallback

Section titled “Paste-token fallback”

If your environment can’t open a browser — headless server, SSH session, restrictive corporate firewall — the OAuth flow won’t complete. Re-run the skill with --paste-token:

Terminal window
claude /vektis-install --paste-token

The skill will:

  1. Print a sign-in URL you can open on a different machine
  2. Walk you to the CLI tokens page in your VEKTIS settings
  3. Ask you to paste the generated token back into the terminal

You only do this once per machine — the token is cached locally and re-used for subsequent skill runs.

Verifying

Section titled “Verifying”

After running install-skills and signing in once:

  1. ls .claude/skills/ should list vektis-install/, vektis-troubleshoot/, vektis-discover/, vektis-instrument/, plus any other vektis-* skills shipped in your version of the SDK, plus a _shared/ directory.
  2. From your project root, claude /vektis-install should launch the install skill — the first run prompts you to authorize.
  3. If a skill says it can’t find your project, or doesn’t appear at all, see the troubleshooting page.
Section titled “Related”