Skip to content
VEKTIS

Claude Code skills overview

VEKTIS ships a set of Claude Code skills that automate the customer side of impact tracking — installing the SDK, finding features in your codebase, inserting tracking calls, and diagnosing problems. Each skill is invoked from your project root with claude /<skill-name>.

This page is the routing layer: pick the skill that matches your situation. If you’re new to VEKTIS, start with vektis-bootstrap.

Pick by situation

Section titled “Pick by situation”

Just install the SDK

Add @vektis-io/tracker to your app, write env vars, insert init code. vektis-install →

Find existing analytics calls

Sweep your codebase for Mixpanel, Segment, Amplitude, PostHog, or GA4 calls and turn them into tracked features. vektis-discover →

Bulk-create dev items + write tracking calls

Take an approved candidate list and instrument the codebase in one diff. vektis-instrument →

Re-scan after shipping new features

Catch features added since your last instrumentation pass — already-tracked features are filtered out. vektis-update →

SDK isn't behaving

Diagnose error codes or symptoms and get ranked hypotheses with concrete next steps. vektis-troubleshoot →

How they fit together

Section titled “How they fit together”

The skills compose into a single end-to-end flow. vektis-bootstrap runs three of them in sequence as a meta-skill; the rest are usable on their own when you only need part of the flow.

StageSkillWhat it produces
1. Install SDKvektis-install@vektis-io/tracker added, env vars written, init code inserted
2. Find features in codevektis-discover.vektis/discover-output.json — an approved list of candidates
3. Create dev items + insert trackingvektis-instrumentDev Items in your VEKTIS organization + vektis.track() calls in source
Periodicvektis-updateSame output as discover, but only NEW features since last pass
Anytimevektis-troubleshootRanked hypotheses for an SDK error or symptom
First time, all-in-onevektis-bootstrapWraps install → discover → instrument with two confirmation prompts

Installing the skills

Section titled “Installing the skills”

Run this once, from your project root, after installing the tracker:

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

This copies the skill directories into .claude/skills/. Re-running is safe — your local edits are preserved. Full guide: Installing the Claude Code skills.

Common patterns

Section titled “Common patterns”
  • You inherited a codebase that already calls vektis.track() — vektis-bootstrap exits cleanly and points you at vektis-update. No re-bootstrapping; you’re already set up.
  • You only want to install the SDK without instrumenting yet — run vektis-install directly. You can run vektis-discover and vektis-instrument later when you’re ready.
  • You don’t have any existing analytics SDK calls — vektis-discover will exit cleanly with an empty-state message. Add Dev Items manually in your VEKTIS dashboard, or call vektis.track() directly in your code and run vektis-update afterwards.
  • Your codebase grew a lot since last pass — run vektis-update, not vektis-discover. Update filters out already-tracked features so you only see the new surface.

Authentication

Section titled “Authentication”

Every skill that talks to VEKTIS authenticates the same way: an OAuth browser flow on first use, then cached credentials for subsequent runs. If you can’t open a browser, every skill accepts a --paste-token flag for the manual fallback. Full reference: Installing the Claude Code skills — Authenticate the skills.

Section titled “Related”