3 ms·
The channels concept is visible via a conf file: # skill-scopes.conf -- GENERATED from extensions_scoped.toml. DO NOT EDIT. # # extensions_scoped.toml is the s
by RohanAdwankar 23d ago
The channels concept is visible via a conf file:
# skill-scopes.conf -- GENERATED from extensions_scoped.toml. DO NOT EDIT.
#
# extensions_scoped.toml is the single source of truth: each [[skills]] entry
# lists the skill's `scopes`, and this file is derived from them -- one
# `<scope> <directory> ...` line per scope, both sorted for a stable render.
#
# The tokens after the scope are skill DIRECTORY names, not SKILL.md names:
# launch-daemon.sh resolves each against /opt/hatch/skills-scoped/<directory>.
#
# launch-daemon.sh reads this at cell boot and reveals only the gated skills
# whose scope matches the VM's JARVIS_CD_CHANNEL. An unset/unknown channel or a
# missing line reveals nothing (fail-closed). Edit the manifest, not this file.
hatch-e2e ads_mcp health nutrition
hatch-evals ads_mcp health nutrition
internal-test ads_mcp audio_notes_read documents end-call health nutrition polymarket price-tracker
prod granola notion whatsapp