Documentation Index
Fetch the complete documentation index at: https://docs.selftune.dev/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Contributor signals let skill creators see how their skills are being used in the wild without compromising user privacy. Users opt in to share anonymized signal data, which skill creators can review in the cloud dashboard.How it works
For users (contributing)
-
Opt in to contributions:
-
Or approve on a per-skill basis:
-
Signals are uploaded with:
For creators (receiving)
-
Enable contributions for your skill:
- View signals in the cloud dashboard under the Signals page
- Generate evolution proposals from aggregate contributor data in the Proposals page of the dashboard.
Privacy guarantees
- No raw user prompts are transmitted
- Only aggregate signal patterns: query categories, trigger/miss counts
- Source keys are deterministic SHA-256 hashes — the relay can deduplicate without identifying users
- PII patterns are stripped via regex before transmission
- Signals are stored in
contribution_signalstable, idempotent on(org_id, source_key)
Signal data
Each signal contains:| Field | Description |
|---|---|
| Skill name | Which skill the signal is about |
| Signal type | Category of the observation |
| Confidence | How certain the classification is |
| Source key | SHA-256 hash for deduplication (not identifiable) |
Contribution relay
Signals flow through the contribution relay endpoint:Community bundle submissions
Community bundles are a separate data source from relay signals. While relay signals capture lightweight, real-time event data (trigger counts, miss rates), community bundles contain richer anonymized export data submitted by contributors.Two distinct data sources
The cloud dashboard displays both data sources, labeled separately:| Source | Label | How it arrives |
|---|---|---|
| Relay signals | contribution_signal | selftune contributions upload |
| Community bundles | community_bundle | selftune contribute --submit |
How bundles arrive
Contributors use the CLI to build and submit an anonymized export bundle:POST /api/v1/community/bundles request with the sanitized bundle, the contributor’s hashed identity, and the creator_id from the skill’s selftune.contribute.json file. Authentication uses the contributor’s local API key.