Skip to main content
Orwel ships an agent skill — a set of instructions your AI assistant (Claude Code) loads to install and wire the SDK correctly into any project: env-based key, a wrapper module, init once, and the full API.

Install

Add the skill once; your assistant picks it up automatically.
npx skills add hyperlabs-ai/hyper-skills/orwel
The skill is open source in hyperlabs-ai/hyper-skills. Once installed it lives in your skills directory and triggers automatically on Orwel-related requests.

Use it

Just ask. The skill handles the whole install — package, env var, wrapper, and the init call:
Prompt
"Add Orwel tracking to this project. Key: orwel_pk_xxxxxxxxxxxxxxxx"

What it guarantees

1

Detects your framework

Identifies the stack and installs the orwel package.
2

Creates a wrapper module

A small module that reads the key from the environment and re-exports the SDK.
3

Initializes once

Client-side, before any tracking call — never twice.
4

Knows the full API

Methods and validation rules, so calls are correct from the start.

Rule 0 — key in env, never hardcoded

The skill always reads the key from an environment variable (it never pastes a literal key into code), using the right name per framework:
FrameworkEnv variable
Vite (React / Vue / Svelte)VITE_ORWEL_KEY
Next.jsNEXT_PUBLIC_ORWEL_KEY
SvelteKit / AstroPUBLIC_ORWEL_KEY
Nuxt 3NUXT_PUBLIC_ORWEL_KEY
Create React AppREACT_APP_ORWEL_KEY
The SDK key is an ingest-only public key (it can write events, not read data), so it’s safe in the browser bundle. Still, read it from an environment variable so you can rotate it per environment without changing code.