The library contains ten common skill workflows for coding agents. Every workflow is implemented in TypeScript, Python, Go, and Rust, so the first choice is your repository's language—not which example happens to exist.
| Skill workflow | Control flow moved into code |
|---|---|
| Review a branch | checks, review, zero-critical gate |
| Investigate a failure | evidence, diagnosis, supported cause |
| QA a web change | build, changed-route QA, no-blocker gate |
| Release a package | tests, review, approval, publish, verify |
| Triage an issue | read, classify, one next action |
| Repair CI | failed log, supported repair, rerun |
| Upgrade a dependency | baseline, compatibility review, approval, update, tests |
| Run a database migration | dry-run, risk review, approval, apply, verify |
| Audit security | mechanical scans, trust-boundary review, zero-critical gate |
| Publish an iOS build | archive, metadata review, approval, upload, processing check |
Change the language segment in any link to python, go, or rust. Source files are grouped separately for fast browsing:
Run all forty fixtures:
go build -o /tmp/yskill ./cmd/yskill
YSKILL=/tmp/yskill bash ./examples/library/test-all.sh
The included commands produce harmless evidence so the examples run in this repository. Replace them with project commands before adopting a skill workflow.
These examples show longer programs with a thin SKILL.md and scripted
responses under fixtures/responses.json.
| Example | Language | Pattern |
|---|---|---|
release-checklist |
TypeScript | approval, build, model-authored notes, publish, verify |
env-doctor |
Python | probe, diagnose, wait for a person, recheck |
investigate |
Go | structured hypotheses, real probes, bounded attempts |
data-migration |
Rust | dry-run, approval, apply, verify |
convert-skill |
Go | extract a prose workflow, generate code, execute its fixtures |
From the repository root:
go build -o /tmp/yskill ./cmd/yskill
/tmp/yskill test examples/release-checklist
/tmp/yskill test examples/env-doctor
/tmp/yskill test examples/investigate
/tmp/yskill test examples/data-migration
YSKILL=/tmp/yskill /tmp/yskill test examples/convert-skillWhen adapting an example, change the repository-specific commands and model instructions. Keep stable operation IDs for existing steps so saved runs can replay them.
The first-party evaluation suite runs every example-library pattern through TypeScript, Python, Go, and Rust. It also checks resume, replay, changed behavior, blocking, and changed source.
These results show that the tested Yield version runs the skill workflow steps in code. They do not compare Yield with prose or test whether an agent's judgment is correct.