Agent skill

Ledger Tasks Yylo

by sickn33 in sickn33/agentic-awesome-skills

Use YYLO Ledger task management: create, list, search, get, mark, update, archive, deps, ready, order and merge with dependencies.

MITAuto-check passedProductivity & Automation

Install Ledger Tasks Yylo

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills ledger-tasks-yylo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ledger-tasks-yylo .claude/skills/ledger-tasks-yylo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ledger-tasks-yylo" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ledger-tasks-yylo into .claude/skills/ledger-tasks-yylo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ledger-tasks-yylo", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ledger-tasks-yylo

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills ledger-tasks-yylo --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ledger-tasks-yylo .agents/skills/ledger-tasks-yylo && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ledger-tasks-yylo" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ledger-tasks-yylo into .agents/skills/ledger-tasks-yylo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ledger-tasks-yylo", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills ledger-tasks-yylo --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ledger-tasks-yylo .cursor/skills/ledger-tasks-yylo && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ledger-tasks-yylo" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ledger-tasks-yylo into .cursor/skills/ledger-tasks-yylo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ledger-tasks-yylo", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/ledger-tasks-yylo

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills ledger-tasks-yylo --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ledger-tasks-yylo .gemini/skills/ledger-tasks-yylo && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ledger-tasks-yylo" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ledger-tasks-yylo into .gemini/skills/ledger-tasks-yylo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ledger-tasks-yylo", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills ledger-tasks-yylo

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ledger-tasks-yylo .github/skills/ledger-tasks-yylo && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ledger-tasks-yylo" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ledger-tasks-yylo into .github/skills/ledger-tasks-yylo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ledger-tasks-yylo", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills ledger-tasks-yylo --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ledger-tasks-yylo .opencode/skills/ledger-tasks-yylo && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ledger-tasks-yylo" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/ledger-tasks-yylo into .opencode/skills/ledger-tasks-yylo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ledger-tasks-yylo", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ledger-tasks-yylo
GitHub stars: 47k
Used in: 1 other repo
Token cost: ~2.8k tokens
SKILL.md length: 1,005 words
Files: 1
Skills in repo: 1,497
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Use YYLO Ledger task management: create, list, search, get, mark, update, archive, deps, ready, order and merge with dependencies.

Works in 10 steps: Task sizing: Create tasks small enough… → Status flow: backlog → todo →… → Always include --response when using… → …
Tasks that involve Task management
SKILL.md covers YYLO Ledger CLI Reference, When to Use and Limitations
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ledger Tasks Yylo is an agent skill from sickn33/agentic-awesome-skills. Use YYLO Ledger task management: create, list, search, get, mark, update, archive, deps, ready, order and merge with dependencies.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires the yy CLI (YYLO Ledger 0.3.x+) installed and a routed Ledger controller; git and bash for worktree tasks. Command help (yy ledger --help) is…

It sits in Productivity & Automation, covering Task management. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

Tasks that involve Task management

Example prompts

“/ledger-tasks-yylo”

Requirements

Compatibility (from SKILL.md): Requires the `yy` CLI (YYLO Ledger 0.3.x+) installed and a routed Ledger controller; git and bash for worktree tasks. Command help (`yy ledger --help`) is authoritative for the installed runtime.

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

Task sizing: Create tasks small enough to complete in one iteration without filling the context window
Status flow: backlog → todo → in_progress → done (or archive for abandoned tasks)
Always include --response when using mark — document what you did and how you tested it
Attach commits: Use --commit HASH when marking done, then update TASK_ID --commit HASH to link the git history
Use ready before starting work to find unblocked tasks
Use order --scores to plan parallel execution pipelines
Use [blocked_by] markup in task body when creating tasks that depend on others
Use [task_id] markup in task body to cross-reference related tasks
Use get TASK_ID to see full task details including resolved dependency and related task info
Concurrent features are supported — start each selected task with yy task start TASK_ID; each gets a dedicated product worktree, while yy…

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires the `yy` CLI (YYLO Ledger 0.3.x+) installed and a routed Ledger controller; git and bash for worktree tasks. Command help (`yy ledger --help`) is authoritative for the installed runtime.
From compatibility in the SKILL.md frontmatter.

Context cost

Ledger Tasks Yylo loads about 2.8k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 1,005 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~37
When it runs · the whole SKILL.md, loaded when a task matches: ~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,005 words, ~2,848 tokens.

Download SKILL.mdSave it as .claude/skills/ledger-tasks-yylo/SKILL.md (or your agent's skills folder).

name: ledger-tasks-yylo
description: Use YYLO Ledger task management: create, list, search, get, mark, update, archive, deps, ready, order and merge with dependencies.
compatibility: Requires the `yy` CLI (YYLO Ledger 0.3.x+) installed and a routed Ledger controller; git and bash for worktree tasks. Command help (`yy ledger --help`) is authoritative for the installed runtime.
category: project-management
risk: safe
source: https://github.com/yylo-dev/yylo-skills
source_repo: yylo-dev/yylo-skills
source_type: community
date_added: 2026-09-19
license: MIT
license_source: https://github.com/yylo-dev/yylo-skills/blob/main/LICENSE
argument-hint: [command or workflow question]
enable-shell-directives: true

YYLO Ledger CLI Reference

Use yy ledger for all commands. 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

Cross-project access is disabled by default. The source .juno_task/config.json must set kanbanRegistry.enabled: true and explicitly list allowedProjects; environment overrides are YYLO_LEDGER_REGISTRY_ENABLED and YYLO_LEDGER_REGISTRY_ALLOWED_PROJECTS. Register with yy ledger project add ALIAS --path /absolute/project, then route any command with --project ALIAS. The destination wrapper/runtime remains authoritative, and routing failures never fall back to the source board.

Legacy Task compatibility commands

CREATE — Add a new task

bash

yy ledger create "Task description here" --status backlog --tags feature,backend

Options: --status (backlog|todo|in_progress|done), --tags (comma/space-separated), --blocked-by (task IDs), --related-tasks (task IDs)

LIST — Browse tasks with summary stats

bash

yy ledger list --limit 5 --sort asc
yy ledger list --status todo --sort asc
yy ledger list --status todo,in_progress --limit 10

SEARCH — Find tasks by criteria

bash

yy ledger search --status todo --tag backend --limit 10
yy ledger search --body "OAuth" --open
yy ledger search --commit abc123

Filters: --status, --tag, --body, --response, --commit, --open (no agent_response), --recent, --exclude (exclude tags)

GET — Full task details (including dependency info and related task details)

bash

yy ledger get TASK_ID

MARK — Update status with required response message

bash

yy ledger mark in_progress --id TASK_ID --response "Starting work on this"
yy ledger mark done --id TASK_ID --response "Completed: implemented X, tested Y" --commit abc123def
yy ledger mark todo --id TASK_ID --response "Reopening: found regression"

Required: --id and --response. Optional: --commit (recommended for done).

UPDATE — Modify task fields

bash

yy ledger update TASK_ID --status todo --tags backend,urgent
yy ledger update TASK_ID --commit abc123def
yy ledger update TASK_ID --response "Additional context"

ARCHIVE — Soft delete (preserves data, sets status to archive)

bash

yy ledger archive TASK_ID

Immutable cold archive packs

Normal list, search, ready, and order are deliberately hot-only. Exact get TASK_ID transparently resolves a hot task or a read-only archived task; use history TASK_ID explicitly for its ledger. Discover cold tasks only with bounded, projected archive-search output:

bash

yy ledger archive-search --tag backend --before 2026-01-01 --limit 20 --projection metadata

Before archive maintenance, preflight the installed version/help and obtain explicit owner authorization. The repository and index must be clean, and reports must be durable new paths outside the repository:

bash

yy ledger --version
yy ledger archive-pack plan --status done,archive --older-than 90d --max-tasks 1000 --target-bytes 26214400 --hard-max-bytes 47185920 --report /external/receipts/archive-plan.json
# Independently inspect selected IDs, revisions, source HEAD, policy, and plan hash.
yy ledger archive-pack create --plan /external/receipts/archive-plan.json --report /external/receipts/archive-create.json
yy ledger archive-pack doctor
yy ledger doctor

A stale plan or selected-task/worktree conflict must fail closed: discard the plan, resolve the conflict, and plan again. Never automate archival, edit/append packs or manifests, restore/reopen an archived ID, use force/lossy controls, or enumerate archive files directly. Create follow-up work as a new hot task related to the archived ID. Production archival, push/deploy, and post-deploy E2E each require separate authorization; agents must not infer it from implementation approval.

Dependency Management

DEPS — View, add, or remove task dependencies

bash

# View dependency info (blockers, dependents, priority score)
yy ledger deps TASK_ID

# Add blockers (TASK_ID cannot start until BLOCKER1 and BLOCKER2 are done)
yy ledger deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2

# Remove a blocker
yy ledger deps remove --id TASK_ID --blocked-by BLOCKER1

Cycle detection prevents circular dependencies automatically.

READY — Tasks with all blockers satisfied (safe to work on)

bash

yy ledger ready
yy ledger ready --tag backend --limit 5

Returns tasks where status is backlog/todo/in_progress AND all blocked_by tasks are done/archive.

ORDER — Topological sort of open tasks respecting dependencies

bash

yy ledger order
yy ledger order --scores

Use for determining safe parallel execution order.

Body Markup for Inline Dependencies

Declare dependencies and relations directly in task body text:

[blocked_by]TASK_ID[/blocked_by]          — This task is blocked by TASK_ID
[blocked_by]ID1, ID2[/blocked_by]         — Blocked by multiple tasks
[task_id]RELATED_ID[/task_id]             — Reference a related task
[task_id]ID1 ID2[/task_id]                — Multiple related tasks

These are parsed automatically when the task is created/updated.

Merge (Multi-Directory Consolidation)

When tasks get scattered across subdirectories:

bash

# First produce and review a deterministic plan
yy ledger merge ./sub1/.juno_task ./sub2/.juno_task --into ./.juno_task \
  --dry-run --plan-file /external/ledger-merge-plan.json

# Apply only that reviewed plan and retain its receipt
yy ledger merge ./sub1/.juno_task ./sub2/.juno_task --into ./.juno_task \
  --apply-plan /external/ledger-merge-plan.json \
  --receipt-file /external/ledger-merge-receipt.json

Output Formats

All commands support: -f json, -f ndjson (default), -f xml, -f table Add --raw for compact output. Add -p for pretty print.

Show full SKILL.md (451 more words)Show less

Best Practices

Task sizing: Create tasks small enough to complete in one iteration without filling the context window
Status flow: backlog → todo → in_progress → done (or archive for abandoned tasks)
Always include --response when using mark — document what you did and how you tested it
Attach commits: Use --commit HASH when marking done, then update TASK_ID --commit HASH to link the git history
Use ready before starting work to find unblocked tasks
Use order --scores to plan parallel execution pipelines
Use [blocked_by] markup in task body when creating tasks that depend on others
Use [task_id] markup in task body to cross-reference related tasks
Use get TASK_ID to see full task details including resolved dependency and related task info
Concurrent features are supported — start each selected task with yy task start TASK_ID; each gets a dedicated product worktree, while yy merge serializes only target updates

Canonical Controller Routing

YYLO Ledger mutation resolves the controller in this order: explicit JUNO_TASK_ROOT, repository-local registration, then the current project root. Diagnose before orchestration with .juno_task/scripts/controller_resolver.py --cwd "$PWD" --operation kanban. The resolver may bootstrap or idempotently confirm a registration, but changing an existing controller requires yy migrate registration plan followed by a separately authorized apply. Explicit/registered path or branch errors fail closed—YYLO Ledger never switches Git branches or falls back silently.

Run YYLO Ledger and workflows from the controller. A task checkout may implement/test but routes task/session writes to that controller. An integration-owner checkout stays clean and refuses Kanban/orchestration/session writes in strict mode; launch from the controller and pass the product checkout separately as TASK_ROOT.

Environment Variables

JUNO_TASK_ROOT — Explicit canonical controller/task-storage root (not the product TASK_ROOT)
JUNO_CONTROLLER_BRANCH — Expected controller branch for environment-based routing
JUNO_WORKSPACE_ROLE — controller, task, or integration-owner
JUNO_WORKSPACE_ENFORCEMENT — off, warn, or strict
JUNO_DEBUG=true — Show diagnostic messages
JUNO_VERBOSE=true — Show informational messages
JUNO_KANBAN_LIST_BODY_TRUNCATE_CHARS=N — Override list body truncation (default: 1200)

$ARGUMENTS

When to Use

You need to interact with the YYLO Ledger task board (create, list, search, get, mark, update, archive, deps, ready, order, merge).
You need dependency-aware scheduling (deps, ready, order) or multi-directory consolidation (merge).
Use the dedicated wiki-yylo, workflow-yylo and artifact-yylo skills for native wiki/workflow/artifact Records instead of guessing their arguments.

Limitations

Requires YYLO Ledger 0.3.x+ with the needed command groups; if a group is absent, fail closed and request a Ledger upgrade - never edit store files by hand.
Discovery (list, search, ready, order) is hot-only; cold tasks need explicit archive-search.
archive-pack and merge need explicit owner authorization, a clean tree, and external plan/receipt paths; never automate archival or force past conflicts.
Does not grant push, deploy, release, or production-mutation authority.

Example

bash

yy ledger --version && yy ledger --help
yy ledger ready --limit 5
yy ledger get TASK_ID

Adapted from yylo-dev/yylo-skills (MIT) - v2.0.1; frontmatter, When to Use/Limitations, and safety boundaries added for upstream compliance.

Files

Just SKILL.md in skills/ledger-tasks-yylo of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

lingxling/awesome-skills-cnantigravity-awesome-skills/skills/ledger-tasks-yylo antigravity-awesome-skills/plugins/agentic-awesome-skills/skills/ledger-tasks-yylo+1 more

Compare with similar skills

Ledger Tasks Yylo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ledger Tasks Yylo compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ledger Tasks Yylo this skillsickn33/agentic-awesome-skills	47k	1 repos	~2.8k	Automated safety check: Pass	MIT	2 days ago
Superset Agent Standupsuperset-sh/superset	15k	—	~712	Automated safety check: Pass	Custom licence	today
AgentRQ Workspace Agentagentrq/agentrq	1.1k	—	~1.9k	Automated safety check: Pass	AGPL-3.0	today
Markdown Task Managerioniks/MarkdownTaskManager	535	—	~2.2k	Automated safety check: Pass	MPL-2.0	3 mo ago
Pi Messenger Crewnicobailon/pi-messenger	719	—	~3.7k	Automated safety check: Pass	None	1 mo ago
Codekanban CLIfy0/CodeKanban	226	—	~2.7k	Automated safety check: Pass	Apache-2.0	7 days ago

Similar skills

Superset Agent Standup
superset-sh/superset
Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.
15k GitHub stars~712 tokensUpdated today
Productivity & AutomationAuto-check passed
AgentRQ Workspace Agent
agentrq/agentrq
Guides a workspace agent through executing assigned tasks, replying to a remote human operator, and creating sub-tasks, memory and events inside an AgentRQ workspace.
1.1k GitHub stars~1.9k tokensUpdated today
Productivity & AutomationAuto-check passed
Markdown Task Manager
ioniks/MarkdownTaskManager
A skill your agent uses when managing tasks, the system is a Kanban task manager based on local Markdown files (kanban.md and archive.md).
535 GitHub stars~2.2k tokensUpdated 3 mo ago
Productivity & AutomationAuto-check passed
Pi Messenger Crew
nicobailon/pi-messenger
Orchestrator reference for pi-messenger Crew planning, task management, configuration, and agent coordination.
719 GitHub stars~3.7k tokensUpdated 1 mo ago
Productivity & AutomationAuto-check passed
Codekanban CLI
fy0/CodeKanban
Operate CodeKanban workflows, terminal sessions, and web sessions through the installable codekanban-cli command.
226 GitHub stars~2.7k tokensUpdated 7 days ago
Productivity & AutomationAuto-check passed
Kanban Video Orchestrator
Luciole-Studio/Misaka-Agent
Plan and run multi-agent video production pipelines. An agent skill from Luciole-Studio/Misaka-Agent.
171 GitHub starsUsed in 2 repos~2.4k tokens
Productivity & AutomationAuto-check: notes

Questions about Ledger Tasks Yylo

What does Ledger Tasks Yylo do?

Use YYLO Ledger task management: create, list, search, get, mark, update, archive, deps, ready, order and merge with dependencies. Ledger Tasks Yylo is an agent skill from sickn33/agentic-awesome-skills. Use YYLO Ledger task management: create, list, search, get, mark, update, archive, deps, ready, order and merge with dependencies.

When should I use Ledger Tasks Yylo?

Ledger Tasks Yylo fits situations like: tasks that involve Task management.

How do I install Ledger Tasks Yylo in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a claude-code`. Or copy the skill folder (skills/ledger-tasks-yylo in sickn33/agentic-awesome-skills) into .claude/skills/ledger-tasks-yylo in your project. Claude Code loads it when a task matches its description.

How do I install Ledger Tasks Yylo in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a codex`. Or copy the skill folder (skills/ledger-tasks-yylo in sickn33/agentic-awesome-skills) into .agents/skills/ledger-tasks-yylo in your project. Codex loads it when a task matches its description.

Can I use Ledger Tasks Yylo in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill ledger-tasks-yylo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ledger-tasks-yylo, .gemini/skills/ledger-tasks-yylo, .github/skills/ledger-tasks-yylo and .opencode/skills/ledger-tasks-yylo in your project.

What does Ledger Tasks Yylo need to run?

SKILL.md names no scripts, command-line tools or credentials: Ledger Tasks Yylo is instructions for the agent only. Compatibility (from SKILL.md): Requires the `yy` CLI (YYLO Ledger 0.3.x+) installed and a routed Ledger controller; git and bash for worktree tasks. Command help (`yy ledger --help`) is authoritative for the installed runtime..

Does Ledger Tasks Yylo access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Ledger Tasks Yylo safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ledger Tasks Yylo use?

Ledger Tasks Yylo is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ledger Tasks Yylo use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ledger Tasks Yylo?

Skills that share tags, products or a category with Ledger Tasks Yylo: Superset Agent Standup (superset-sh/superset, 15k stars), AgentRQ Workspace Agent (agentrq/agentrq, 1.1k stars), Markdown Task Manager (ioniks/MarkdownTaskManager, 535 stars) and Pi Messenger Crew (nicobailon/pi-messenger, 719 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ledger Tasks Yylo?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ledger Tasks Yylo

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

YYLO Ledger CLI Reference

Supported task contract

Opt-in cross-project routing

Legacy Task compatibility commands

Immutable cold archive packs

Dependency Management

Body Markup for Inline Dependencies

Merge (Multi-Directory Consolidation)

Output Formats

Best Practices

Canonical Controller Routing

Environment Variables

When to Use

Limitations

Example

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from sickn33/agentic-awesome-skills

Related

Questions about Ledger Tasks Yylo