Repository navigation
feat: add ledger-tasks-yylo skill - #55
Closed
InsightFactoryAPP wants to merge 2 commits into
Closed
InsightFactoryAPP wants to merge 2 commits into
InsightFactoryAPP wants to merge 2 commits into
Conversation
|
|
||
| <div align="center"> | ||
| <img src="https://readme-typing-svg.demolab.com?font=Fira+Code&size=20&duration=3000&pause=800&color=58A6FF¢er=true&vCenter=true&width=620&height=50&lines=64+Agent+Skills;Works+with+Claude%2C+Codex%2C+Gemini+CLI%2C+Manus+AI;Agent+Skills+for+Founders+Who+Hate+Marketing;Install+in+seconds.+No+setup+required." alt="Typing SVG" /> | ||
| <img src="https://readme-typing-svg.demolab.com?font=Fira+Code&size=20&duration=3000&pause=800&color=58A6FF¢er=true&vCenter=true&width=620&height=50&lines=65+Agent+Skills;Works+with+Claude%2C+Codex%2C+Gemini+CLI%2C+Manus+AI;Agent+Skills+for+Founders+Who+Hate+Marketing;Install+in+seconds.+No+setup+required." alt="Typing SVG" /> |
Contributor
There was a problem hiding this comment.
Regenerate plugin skill counts
The root catalog and CLI registry now list 65 skills, but both Claude plugin discovery manifests still advertise 64. Plugin and marketplace users will receive stale catalog metadata; regenerate and commit both manifests so their published count matches the catalog. This is a non-blocking metadata concern.
Knowledge Base Used: Registry generation and release artifacts
Artifacts
- The authored Node script parses all relevant metadata counts and invokes the compiled CLI registry loader, showing whether catalog discovery metadata agrees.
- The verifier was executed against a clean archive of `HEAD^`; all catalog and manifest counts are 64, showing the prior state was consistent.
- The verifier was executed in the candidate checkout; runtime CLI discovery finds all 65 skills while plugin and marketplace descriptions remain 64, confirming stale discovery metadata.
This comment has been minimized.
This comment has been minimized.
Contributor
|
Thank you for your submission. We are closing this PR for the following reasons:
We appreciate your interest in OpenDirectory! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds the
ledger-tasks-yyloskill. It gives a coding agent a durable Kanban board the agent operates itself through theyyCLI — tasks, dependencies, readiness, and receipts that survive across sessions.Solo founders shipping with Claude, Codex, or Gemini agents lose task state the moment a session ends. This skill makes the agent plan, track, and close its own work: implementation-sized tasks,
mark donewith a response and commit hash, dependency graphs with cycle detection,ready/orderfor safe parallel execution, and receipt-preserving closes. One prerequisite (@yylo/cli), no API keys, works on any Git repository.What this skill does
You ask your agent to manage its own work ("create a task for the OAuth refactor", "what's ready to work on?", "mark TASK-42 done - implemented and tested") and it drives the YYLO Ledger board:
deps add/remove, cycle detection,[blocked_by]inline markupFiles
skills/ledger-tasks-yylo/SKILL.md— frontmatter + the full agent contractskills/ledger-tasks-yylo/README.md— pitch, prerequisites, usage (install block added byscripts/update_skill_readmes.py)skills/ledger-tasks-yylo/package.json— categoryDeveloper ToolsREADME.md,packages/cli/registry.json— regenerated with the repo's own scripts (pnpm exec tsx scripts/update-readme.ts+scripts/build-registry.ts), counts 64 → 65Validation
pnpm exec tsx scripts/validate-pr.ts— all 65 skills valid, descriptions populatedscripts/build-registry.tsregenerated; registry is in sync withskills/(CI check will confirm)scripts/update_skill_readmes.pyran; only pre-existing template drift in another skill's README was reverted to keep this PR additive-onlyDisclosure
I'm a contributor on the YYLO project (yylo-dev), submitting our own MIT-licensed skill. This PR was prepared with AI assistance and follows the CONTRIBUTING guide: skill folder + package.json + regenerated registry/README via the repo's own scripts. YYLO's CLI is already listed in 70+ community awesome lists (see the yylo-dev/yylo README badges), and yylo-skills is installable via
npx skills add yylo-dev/yylo-skills— so theskills.shinstall path works today.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Safe to merge.
Findings
Summary
Adds the
ledger-tasks-yyloskill and synchronizes its catalog and distribution metadata.Reviews (2) · Last reviewed commit: "fix: address review - ledger namespace c..."