onboard
Skill5 starsChanged 5 months agoApache-2.0View on GitHub
Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 149 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Phase 1 — service repo: create sentry-options/schemas/{namespace}/schema.json, add the validate-schema CI workflow and (for Python) the …
- Very specific: line 23
Phase 3 — ops: add the injector annotations (options.sentry.io/inject, options.sentry.io/namespace) to the deployment.
- Distinctive: line 27
After each phase, surface the checkpoint from the guide (e.g.
“Common” is measured: kept by at least 6 in 10 of the 149 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
sentry-options Onboarding
Guide the user through integrating a service with sentry-options. The authoritative, step-by-step instructions live in the setup guide — follow it rather than reproducing details here. This skill intentionally defers specifics (version pins, exact file contents, schema rules) to the docs so it can't drift out of sync.
Setup guide: https://github.com/getsentry/sentry-options/blob/main/docs/setup.md Options/schema reference: https://github.com/getsentry/sentry-options/blob/main/docs/options.md
How to run this
- Gather inputs from the user:
- Repository name (e.g.
seer,snuba). - Namespace(s) — must be the repo name or prefixed with
{repo}-(e.g.seer,seer-autofix). - Any initial options or feature flags (name, type, default, description).
- Repository name (e.g.
- Walk the three phases from the setup guide, in order, using the exact file contents, version pins, and commands it specifies (do not write versions or schema rules from memory — they change):
- Phase 1 — service repo: create
sentry-options/schemas/{namespace}/schema.json, add thevalidate-schemaCI workflow and (for Python) thesentry-options-gen-stubspre-commit hook, add the client dependency, callinit()at startup, and copy schemas into the image withSENTRY_OPTIONS_DIR. - Phase 2 — sentry-options-automator: register the repo in
repos.jsonand addoption-values/{namespace}/{target}/values.yaml(the mandatorydefaulttarget plus a folder per region you want to deploy to). - Phase 3 — ops: add the injector annotations (
options.sentry.io/inject,options.sentry.io/namespace) to the deployment.
- Phase 1 — service repo: create
- For schema/type details (primitives, arrays, structs, dicts, optional fields, feature flags) consult the options/schema reference.
- After each phase, surface the checkpoint from the guide (e.g. merge the PR) before moving on.
Other versions161 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 161
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- nateherkai/AIS-OS★ 1.4ksame name
- poshan0126/dotclaude★ 871same name
- talesofai/cohub★ 571same name
- me2resh/apexyard★ 532same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 421same name
151 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use soak-test, team-live-ops and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
HK-hubSkillteach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Also in 18 projects that use this
CoralGameSkillproject-stage-detect
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.
Also in 15 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 11 projects that use this
- +6 more from lilangMax
- +1 more from CoralGame
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-optionSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

