oteny-talent-dev-loop

Runs the Oteny Talent test, clone, and staging dev loop via the Oteny dev CLI.

2|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/otenycom/talents --skill oteny-talent-dev-loop-otenycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oteny-talent-dev-loop
Source: https://github.com/otenycom/talents/tree/main/.claude/skills/oteny-talent-dev-loop
Command: npx skills add https://github.com/otenycom/talents --skill oteny-talent-dev-loop-otenycom

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about oteny-talent-dev-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test an Oteny Talent before releasing it?▼

Test an Oteny Talent by running it on a disposable, neutralized clone using the Oteny dev CLI clone and test verbs. Read the debug traces to diagnose failures, fix issues, and only tag a release after staging reports green.

What commands does the Oteny dev CLI provide for Talent development?▼

The Oteny dev CLI provides lint-talent, clone, reload, test, traces, logs, selfcheck, migrate-talent, reinit, and reap. It also supports the CI path with request-staging-run and staging-run-status for gating releases.

Why test a Talent on a clone instead of the live bot?▼

A clone is disposable and neutralized, so testing cannot damage real user data or production state. It proves the Talent behaves correctly, not just that it lints, before commit, staging, and release tagging.

How do I read debug traces for a failing Oteny Talent?▼

Use the traces and logs verbs of the Oteny dev CLI after running tests on the clone. The traces show where behavior diverged from expectations so you can fix the Talent and rerun until staging is green.

When should I run lint-talent versus the full clone test loop?▼

Run lint-talent for quick static checks during editing. Use the full clone, test, and staging loop when you need behavioral proof before gating a commit to staging and tagging a release.