Support
We’re here to help you get the most out of Skills Trace. Find the right support channel for your needs.
Frequently Asked Questions
How do I get started with Skills Trace?
Install the appropriate gateway adapter (@skills-trace/express, @skills-trace/vercel, or @skills-trace/cloudflare), configure a fingerprint registry, and choose an emitter for telemetry output. See our Getting Started guide for step-by-step instructions.
Does Skills Trace modify my prompts or LLM requests?
No. Skills Trace operates in read-only mode. It inspects request payloads to detect skill fingerprints but never modifies, blocks, or alters any prompts or API calls.
What data does Skills Trace collect?
Skills Trace emits only skill identity metadata — skill ID, version, detection method, and confidence score. It never logs prompt content, user data, or LLM responses.
What is the performance impact?
Minimal. Watermark detection runs in under 5ms (p99), and the full detection pipeline completes in under 20ms. Detection is asynchronous and does not block request processing.
Can I use Skills Trace with my existing observability stack?
Yes. Skills Trace supports multiple emitters including ClickHouse, HTTP webhooks, JSONL files, SQLite, and PostgreSQL. You can fan out to multiple destinations using the multi-emitter.
Is Skills Trace open source?
The core detection engine and all gateway adapters are open source. The web dashboard and enterprise features are available as a managed service.