# Ledger Tasks Yylo

Comprehensive guide for using YYLO Ledger task management without bypassing controller...

- Repository: https://github.com/iflytek/skillhub (5351 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add iflytek/skillhub --skill ledger-tasks-yylo -g -a claude-code -y`
Codex: `npx skills add iflytek/skillhub --skill ledger-tasks-yylo -g -a codex -y`
Cursor: `npx skills add iflytek/skillhub --skill ledger-tasks-yylo -g -a cursor -y`
Gemini CLI: `npx skills add iflytek/skillhub --skill ledger-tasks-yylo -g -a gemini-cli -y`

## Description

Comprehensive guide for using YYLO Ledger task management without bypassing controller routing, lifecycle state, or mutation receipts. Covers task commands, dependency management, best practices, and workflow patterns. Use when you need to interact with the YYLO Ledger board.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## YYLO Ledger CLI Reference

Use `yy ledger` for all commands. Before any operation, run `yy ledger --version` and `yy ledger --help`; the installed runtime's help is authoritative. Read the current task/board state before mutation, preserve the returned mutation receipt when offered, and never edit Markdown/store files directly to bypass controller routing or lifecycle state. If the required command group is absent, stop and request a Ledger upgrade rather than guessing or invoking mutable source code. Ledger 0.3.x exposes both the compatible flat task commands and the native ID-first `record|task|wiki|workflow|artifact` groups. `yy kanban` is a labelled compatibility alias for the same controller-routed task runtime.

### Supported task contract

- Preflight installed `yy ledger --version` and `yy ledger --help`; command help is authoritative for the selected runtime.
- Use the flat task surface for lifecycle task management. Use the dedicated native skills for wiki, workflow, and artifact Records rather than guessing their arguments.
- New operational PDRs, contracts, plans, reports, receipts, and evidence belong in typed Artifact Records, not product documentation, task bodies/responses, or new `.juno_task/specs` files.
- If a required native group is absent, fail closed and request a Ledger upgrade. Never invoke mutable source directly or write Ledger store files by hand.
- Read current task state before mutation, preserve mutation receipts where offered, and never bypass controller routing or lifecycle state with direct file edits.
- Normal discovery is hot-only unless an explicit cold-archive command is used.

### Opt-in cross-project routing

The rest: https://github.com/iflytek/skillhub/blob/HEAD/builtin-skills/skills/ledger-tasks-yylo/SKILL.md