git clone --depth 1 https://github.com/Prism-Shadow/penguin-harness /tmp/0.2.6 && cp -r /tmp/0.2.6/changelog/0.2.6/2026-08-25-penguin-orchestration- ~/.claude/skills/0.2.62026-08-25-penguin-orchestration-skill.md
# New built-in skill: penguin-orchestration - **Date:** 2026-08-25 - **Type:** feature - **Scope:** `skills`, `docs` - **PR:** [#463](https://github.com/Prism-Shadow/penguin-harness/pull/463) [中文版](2026-08-25-penguin-orchestration-skill.zh.md) Added `penguin-orchestration` (v1) to the skill library's AI App Development group, right after `penguin-cli`. It teaches an agent running inside PenguinHarness to drive the harness itself over the `penguin` CLI against its own local server: list and create agents, start sessions and steer them mid-flight, read transcripts, and query costs and scheduled tasks. The skill documents the server-backed CLI surface [the CLI-on-server rework](2026-08-25-cli-on-server.md) introduced — the injected `PENGUIN_API_URL` / `PENGUIN_API_TOKEN` / project, agent and session id environment variables inside agent sessions, and the lock-file attach or auto-start path outside. ## Details - Recipes: summarize yesterday's conversations (session ids embed their creation timestamp, `session-YYYY-MM-DD-HH-mm-ss-<8hex>`), query the last 7 days of cost (`penguin cost --days 7 --by agent` and variants), create an agent and talk to it (`penguin agent create` then `penguin run --agent-id`), inspect scheduled tasks (`penguin schedule ls`) and create one by writing a schedule TOML with file tools, and run a CLI-driven conversation in the background — `exec_command` with `run_in_background` for a completion report, or `penguin run --background` for a server-side run that survives the caller — steering it mid-flight with `penguin input <session_id> -m ... --timeout 0`. - Cautions cover the one-active-task-per-session rule, approval modes for unattended sessions (`allow-all` / `read-only`; `always-ask` hangs), runaway self-messaging loops, project-level cost attribution, and the standing ban on hand-editing `.project_config.toml` / `.vault.toml`. - Registered in `SKILL_GROUPS`, the package README table and the bilingual docs skill tables; hand-drawn `icon.svg` (a conductor node fanning out to two nodes). No `preinstall` marker, so new `default_agent`s get it like the rest of the library.
Use when developing PenguinHarness itself — changing packages/{core,server,web,cli,desktop,landing,docs,skills}, the built-in model catalog, the installers or the release workflow; writing or auditing changelog entries; writing a blog post or capturing release screenshots; deciding what to do about data already on disk; or auditing prose that reads like a leaked authoring session. Covers the two-repo symlink layout, the CI-parity verification chain, the record-and-ship contract, where blog media is hosted, and the seams that are intentional.
Use when changing the PenguinHarness Web App (`packages/web`) — adding or restyling any UI, picking a status colour, adding an icon, laying out a row or a form field, writing user-facing copy, or building a popup. Covers the semantic tone tokens, the icon size/stroke/gap scale, the semantic-versus-formatting rule for explanatory text, the two-dictionary i18n contract, and the portal-panel pattern with its Esc and scroll caveats.
Run one specified Test Agent on one specified Benchmark Case exactly once, privately score that execution, and return one protocol result.
Initialize an Agent's settings from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.
Improve an Agent State through versioned scores and score-linked Traces from a frozen Benchmark.