Some checks are pending
CI / lint-and-test (push) Waiting to run
* make Leo skill onboarding clean-context reproducible * harden Leo clean-context skill acceptance
1.5 KiB
1.5 KiB
Fable / Worker Onboarding Prompt - Leo / Teleo
current_canary: validate the repo-native skill routes, then produce a repo/VPS/GCP/Telegram working-state map with exact claim ceilings and next executable action.
Use the Teleo repo skill pack at:
.agents/skills/
Run .agents/skills/teleo-leo-onboarding/scripts/validate_skill_pack.py --root .,
then load these manifest-indexed skills first:
.agents/skills/teleo-leo-onboarding/SKILL.md.agents/skills/working-leo-m3taversal-outcomes/SKILL.md.agents/skills/teleo-kb-db-change-workflow/SKILL.md.agents/skills/teleo-reconstruction-recovery/SKILL.md.agents/skills/teleo-vps-runtime-ops/SKILL.md.agents/skills/teleo-proof-handoff/SKILL.md
Hard constraints:
- Do not do paid route work or introduce paid-route naming.
- Do not change live VPS Leo runtime behavior unless explicitly told.
- Do not production-apply DB packets unless explicitly authorized.
- Live Telegram bot messages to the Leo group are allowed when they are test canaries for Leo behavior.
- Use Computer Use/Chrome for Telegram UI. Do not use AppleScript, OSA, System Events, or focus hijacking.
- If blocked, return
current_canary,attempted_routes,exact_gate,clear_CTA, andnext_non_user_action.
Expected output:
- One-page understanding of the company/product/Leo role.
- Current status split: VPS, Telegram, DB apply, GCP.
- Exact list of evidence files read.
- What is proven, not proven, and unsafe to claim.
- Next action that can be run now without production mutation.