You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instructions — Step-by-step actionable workflow (not prose), each step tells the agent what to DO
Examples — At least 2 concrete input/output examples with realistic data (no lorem ipsum / foo / bar)
Guidelines — Best practices, edge cases, error handling
Quality
Under 300 lines total (159 lines)
Instructions are specific enough that an AI agent can follow them without guessing
Works cross-platform (no vendor lock-in or proprietary APIs without a free tier) — the CLI is open source (MIT, npm @yylo/cli)
Solves a real, recurring problem a developer would encounter at least weekly
Files
skills/your-skill-name/SKILL.md added
Use-case article added in use-cases/ (optional but recommended)
Which use case does this skill serve?
The new use-case article use-cases/run-kanban-tasks-for-coding-agents.md (included in this PR): keeping AI coding-agent task state durable and dependency-aware across sessions instead of chat scrollback — agents pick only unblocked work, execute one task at a time, and close tasks with tested responses plus commit hashes.
Example usage
yy ledger ready --tag backend --limit 5
yy ledger mark in_progress --id T-141 --response "Starting: porting upload client to shared retry helper"
yy ledger mark done --id T-141 --response "Completed: swapped fetch loop for retry helper, 12 unit tests green" --commit 9f31c0a
Category
development — coding-agent task lifecycle and dependency-aware work, sibling to agent-workflow-packager.
Additional context
Disclosure: I'm on the team that builds YYLO. This skill is adapted (with provenance cited in the Overview) from the canonical ledger-tasks-yylo SKILL.md in yylo-dev/yylo-skills (MIT) — trimmed to house format, host-specific frontmatter removed, prerequisites added. The license field is MIT (the source skill's license) rather than the repo default; happy to adjust if a uniform Apache-2.0 declaration is preferred for the catalog. The PR was prepared with an AI agent's help and reviewed by me. README gains one catalog row and one use-case bullet, both bottom-appended per the freshest merged adds (#530/#531). Glad to revise or trim anything.
Thanks for the PR and for the upfront disclosure — it made this easy to review. I'm going to close it rather than merge, for two reasons:
The prerequisites don't work as written. The skill installs only @yylo/cli and then runs yy ledger --version, but YYLO's own README says yy ledger delegates to a separately installed Ledger CLI — yylo-ledger, a Python package (pip install yylo-ledger), which isn't on npm. An agent following the skill fails at step one, and compatibility would also need to list Python.
Scope. The catalog aims for skills that are useful to a broad set of agent users. This one exists solely to operate a single, very new tool (YYLO Ledger was created last month), so for now it serves people who have already adopted YYLO — who can get the canonical skill from yylo-dev/yylo-skills directly.
You're welcome to resubmit once Ledger has wider adoption and the install path is fixed. If you do, please also use license: Apache-2.0 to match the catalog, and base the use case on a real workflow rather than an illustrative one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Skill:
ledger-tasks-yyloChecklist
Before submitting, ensure your skill meets these requirements:
Frontmatter (SKILL.md YAML header)
name— Lowercase kebab-case only (a-z,0-9,-), max 64 charsdescription— States WHAT it does and WHEN to use it, includes trigger words, max 1024 chars, third person (no "I"/"you"/"we")license— Present (e.g.,Apache-2.0) — declaredMIT, matching the upstream sourcecompatibility— Concrete system requirements (e.g., "Requires Python 3.9+") or "No special requirements"metadata.author— Your GitHub usernamemetadata.version— Semantic version ("1.0.0")metadata.category— One of:documents,development,data-ai,devops,business,design,automation,research,productivity,contentmetadata.tags— Array of 3–5 relevant tagsBody Sections
Quality
@yylo/cli)Files
skills/your-skill-name/SKILL.mdaddeduse-cases/(optional but recommended)Which use case does this skill serve?
The new use-case article
use-cases/run-kanban-tasks-for-coding-agents.md(included in this PR): keeping AI coding-agent task state durable and dependency-aware across sessions instead of chat scrollback — agents pick only unblocked work, execute one task at a time, and close tasks with tested responses plus commit hashes.Example usage
Category
development— coding-agent task lifecycle and dependency-aware work, sibling toagent-workflow-packager.Additional context
Disclosure: I'm on the team that builds YYLO. This skill is adapted (with provenance cited in the Overview) from the canonical
ledger-tasks-yyloSKILL.md in yylo-dev/yylo-skills (MIT) — trimmed to house format, host-specific frontmatter removed, prerequisites added. Thelicensefield isMIT(the source skill's license) rather than the repo default; happy to adjust if a uniform Apache-2.0 declaration is preferred for the catalog. The PR was prepared with an AI agent's help and reviewed by me. README gains one catalog row and one use-case bullet, both bottom-appended per the freshest merged adds (#530/#531). Glad to revise or trim anything.