What problem does it solve? Talent authors need to prove a Talent actually behaves correctly on Oteny, not just that it passes linting, before tagging a release. This Skill provides the test/ship rung of the authoring workflow: running a Talent on a disposable neutralized clone, reading debug traces, and gating commit, staging, and green/red status before release. ## Core Features & Use Cases - Clone-based testing: Run a Talent on a disposable, neutralized clone to verify real behavior without touching production data. - Oteny dev CLI reference: Covers the verbs lint-talent, clone, reload, test, traces, logs, selfcheck, migrate-talent, reinit, and reap, plus the CI request-staging-run and staging-run-status path. - Release gating: Enforces a commit to staging to green/red gate before tagging a Talent release. - Use Case: After editing a Talent's persona and skills, use this Skill to clone the bot, run behavioral tests, inspect traces for failures, fix issues, and only tag the release once staging reports green. ## Quick Start Use the oteny-talent-dev-loop skill to clone my Talent, run its tests, and show me the debug traces before I tag a release.