[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KCVZCD2X1RASWPZ96FZ6R":3,"skill-same:01M75KCVZCD2X1RASWPZ96FZ6R":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75KCVZCD2X1RASWPZ96FZ6R","pi-workflow",null,"Workflow orchestration for Pi's task management, self-improvement, and code quality standards. Use when starting new projects, managing multi-step tasks (3+ steps or architectural decisions), capturing lessons from mistakes, writing verifiable code, or establishing quality gates before completion. Includes planning templates, progress tracking, bug fixing autonomy, and a lessons capture system to prevent repeated mistakes.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fkai-tw\u002Fpi-workflow\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: pi-workflow\ndescription: Workflow orchestration for Pi's task management, self-improvement, and code quality standards. Use when starting new projects, managing multi-step tasks (3+ steps or architectural decisions), capturing lessons from mistakes, writing verifiable code, or establishing quality gates before completion. Includes planning templates, progress tracking, bug fixing autonomy, and a lessons capture system to prevent repeated mistakes.\n---\n\n# Pi Workflow Orchestration\n\nThis skill provides Pi's structured approach to task management, quality assurance, and continuous self-improvement.\n\n## Core Workflows\n\n### 1. Plan Node Default\nEnter plan mode for ANY non-trivial task (3+ steps or architectural decisions):\n- Write detailed specs upfront to reduce ambiguity\n- If something goes sideways, STOP and re-plan immediately—don't keep pushing\n- Use plan mode for verification steps, not just building\n\n### 2. Subagent Strategy\n- Use subagents liberally to keep main context window clean\n- Offload research, exploration, and parallel analysis to subagents\n- For complex problems, throw more compute at it via subagents\n- One tack per subagent for focused execution\n\n### 3. Self-Improvement Loop\n- After ANY correction from the user: update `tasks\u002Flessons.md` with metadata (Priority, Status, Area, Pattern-Key)\n- Log command failures to `tasks\u002Ferrors.md` for diagnosis patterns\n- Log feature requests to `tasks\u002Ffeature_requests.md` for future work\n- Write rules for yourself that prevent the same mistake\n- Ruthlessly iterate on these lessons until mistake rate drops\n- Review lessons at session start for relevant projects\n- Track recurring patterns with Recurrence-Count (bump priority at ≥3 occurrences)\n\n### 4. Verification Before Done\n- Never mark a task complete without proving it works\n- Diff behavior between main and your changes when relevant\n- Ask yourself: \"Would a staff engineer approve this?\"\n- Run tests, check logs, demonstrate correctness\n\n### 5. Demand Elegance (Balanced)\n- For non-trivial changes: pause and ask \"is there a more elegant way?\"\n- If a fix feels hacky: \"Knowing everything I know now, implement the elegant solution\"\n- Skip this for simple, obvious fixes—don't over-engineer\n- Challenge your own work before presenting it\n\n### 6. Autonomous Bug Fixing\n- When given a bug report: just fix it. Don't ask for hand-holding\n- Point at logs, errors, failing tests—then resolve them\n- Zero context switching required from the user\n- Go fix failing CI tests without being told how\n\n## Task Management\n\n1. **Plan First**: Write plan to `tasks\u002Ftodo.md` with checkable items\n2. **Verify Plan**: Check in before starting implementation\n3. **Track Progress**: Mark items complete as you go\n4. **Explain Changes**: High-level summary at each step\n5. **Document Results**: Add review section to `tasks\u002Ftodo.md`\n6. **Capture Lessons**: Update `tasks\u002Flessons.md` after corrections\n\n## File Organization\n\n- `tasks\u002Ftodo.md` — active sprint (current project)\n- `tasks\u002Flessons.md` — corrections, insights, best practices (structured)\n- `tasks\u002Ferrors.md` — command failures, API errors, exceptions (NEW)\n- `tasks\u002Ffeature_requests.md` — missing capabilities, feature requests (NEW)\n- `memory\u002FYYYY-MM-DD.md` — session logs (daily)\n- `MEMORY.md` — your curated memories (maintained by user)\n\nSee [WORKFLOW_ORCHESTRATION.md](references\u002Fworkflow_orchestration.md) for detailed reference.\n\nSee [LESSONS.md](references\u002Flessons.md) for philosophy and framing.\n\nSee [PHASE1-PHASE2-ENHANCED-LESSONS.md](references\u002Fphase1-phase2-enhanced-lessons.md) for structured lesson format and file separation.\n\nSee [LESSONS_UPDATE_GUIDE.md](references\u002Flessons_update_guide.md) for syncing lessons from workspace to skill.\n\n## Capturing Lessons\n\n### Lessons Format (Phase 1+2 Enhanced)\n\nEach lesson gets structured metadata for filtering and recurring pattern detection:\n\n```markdown\n## [LRN-YYYYMMDD-XXX] rule_name (category)\n\n**Logged**: ISO-8601 timestamp\n**Priority**: low | medium | high | critical\n**Status**: pending | in_progress | resolved | promoted\n**Area**: backend | infra | tests | docs | config\n**Pattern-Key**: category.pattern_name (optional, for recurring detection)\n\n### Summary\nOne-line description\n\n### Details\nFull context and examples\n\n### Applied to\nProjects or files where this was used\n\n### Metadata\n- Source: correction | insight | user_feedback\n- Related Files: path\u002Fto\u002Ffile\n- Tags: tag1, tag2\n- See Also: LRN-20250225-001 (if related to existing entry)\n- Recurrence-Count: 1 (increment if you see it again)\n- First-Seen: 2025-02-23\n- Last-Seen: 2025-02-23\n```\n\n### Errors & Features (NEW)\n\nLog failures and feature gaps separately for better organization:\n\n**Errors** (`tasks\u002Ferrors.md`):\n- Command failures, API errors, exceptions\n- Include reproducibility, environment, suggested fix\n\n**Features** (`tasks\u002Ffeature_requests.md`):\n- Missing capabilities, things you wish existed\n- Include complexity estimate and suggested implementation\n\n### Syncing to Skill\n\nPeriodically merge workspace lessons into the published skill:\n\n```bash\n# From openclaw-workflow repo\npython3 scripts\u002Fsync_lessons.py --workspace ~\u002F.openclaw\u002Fworkspace\n\n# Dry run (preview changes)\npython3 scripts\u002Fsync_lessons.py --workspace ~\u002F.openclaw\u002Fworkspace --dry-run\n```\n\nThis merges workspace lessons into `references\u002Flessons.md` for version control and sharing.\n\n## Hooks (Optional)\n\nEnable automatic bootstrap reminders for self-improvement:\n\n```bash\nopenclaw hooks enable pi-workflow\n```\n\nThis injects a reminder at session start showing:\n- When to log lessons\u002Ferrors\u002Ffeatures\n- Format and metadata fields\n- Recurring pattern detection\n- Promotion paths\n\nSee `hooks\u002Fopenclaw\u002FHOOK.md` for details.\n\n---\n\n## Core Principles\n\n- **Simplicity First**: Make every change as simple as possible. Minimal code impact.\n- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.\n- **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.\n","# Pi Workflow Orchestration\n\nThis skill provides Pi's structured approach to task management, quality assurance, and continuous self-improvement.\n\n## Core Workflows\n\n### 1. Plan Node Default\nEnter plan mode for ANY non-trivial task (3+ steps or architectural decisions):\n- Write detailed specs upfront to reduce ambiguity\n- If something goes sideways, STOP and re-plan immediately—don't keep pushing\n- Use plan mode for verification steps, not just building\n\n### 2. Subagent Strategy\n- Use subagents liberally to keep main context window clean\n- Offload research, exploration, and parallel analysis to subagents\n- For complex problems, throw more compute at it via subagents\n- One tack per subagent for focused execution\n\n### 3. Self-Improvement Loop\n- After ANY correction from the user: update `tasks\u002Flessons.md` with metadata (Priority, Status, Area, Pattern-Key)\n- Log command failures to `tasks\u002Ferrors.md` for diagnosis patterns\n- Log feature requests to `tasks\u002Ffeature_requests.md` for future work\n- Write rules for yourself that prevent the same mistake\n- Ruthlessly iterate on these lessons until mistake rate drops\n- Review lessons at session start for relevant projects\n- Track recurring patterns with Recurrence-Count (bump priority at ≥3 occurrences)\n\n### 4. Verification Before Done\n- Never mark a task complete without proving it works\n- Diff behavior between main and your changes when relevant\n- Ask yourself: \"Would a staff engineer approve this?\"\n- Run tests, check logs, demonstrate correctness\n\n### 5. Demand Elegance (Balanced)\n- For non-trivial changes: pause and ask \"is there a more elegant way?\"\n- If a fix feels hacky: \"Knowing everything I know now, implement the elegant solution\"\n- Skip this for simple, obvious fixes—don't over-engineer\n- Challenge your own work before presenting it\n\n### 6. Autonomous Bug Fixing\n- When given a bug report: just fix it. Don't ask for hand-holding\n- Point at logs, errors, failing tests—then resolve them\n- Zero context switching required from the user\n- Go fix failing CI tests without being told how\n\n## Task Management\n\n1. **Plan First**: Write plan to `tasks\u002Ftodo.md` with checkable items\n2. **Verify Plan**: Check in before starting implementation\n3. **Track Progress**: Mark items complete as you go\n4. **Explain Changes**: High-level summary at each step\n5. **Document Results**: Add review section to `tasks\u002Ftodo.md`\n6. **Capture Lessons**: Update `tasks\u002Flessons.md` after corrections\n\n## File Organization\n\n- `tasks\u002Ftodo.md` — active sprint (current project)\n- `tasks\u002Flessons.md` — corrections, insights, best practices (structured)\n- `tasks\u002Ferrors.md` — command failures, API errors, exceptions (NEW)\n- `tasks\u002Ffeature_requests.md` — missing capabilities, feature requests (NEW)\n- `memory\u002FYYYY-MM-DD.md` — session logs (daily)\n- `MEMORY.md` — your curated memories (maintained by user)\n\nSee [WORKFLOW_ORCHESTRATION.md](references\u002Fworkflow_orchestration.md) for detailed reference.\n\nSee [LESSONS.md](references\u002Flessons.md) for philosophy and framing.\n\nSee [PHASE1-PHASE2-ENHANCED-LESSONS.md](references\u002Fphase1-phase2-enhanced-lessons.md) for structured lesson format and file separation.\n\nSee [LESSONS_UPDATE_GUIDE.md](references\u002Flessons_update_guide.md) for syncing lessons from workspace to skill.\n\n## Capturing Lessons\n\n### Lessons Format (Phase 1+2 Enhanced)\n\nEach lesson gets structured metadata for filtering and recurring pattern detection:\n\n```markdown\n## [LRN-YYYYMMDD-XXX] rule_name (category)\n\n**Logged**: ISO-8601 timestamp\n**Priority**: low | medium | high | critical\n**Status**: pending | in_progress | resolved | promoted\n**Area**: backend | infra | tests | docs | config\n**Pattern-Key**: category.pattern_name (optional, for recurring detection)\n\n### Summary\nOne-line description\n\n### Details\nFull context and examples\n\n### Applied to\nProjects or files where this was used\n\n### Metadata\n- Source: correction | insight | user_feedback\n- Related Files: path\u002Fto\u002Ffile\n- Tags: tag1, tag2\n- See Also: LRN-20250225-001 (if related to existing entry)\n- Recurrence-Count: 1 (increment if you see it again)\n- First-Seen: 2025-02-23\n- Last-Seen: 2025-02-23\n```\n\n### Errors & Features (NEW)\n\nLog failures and feature gaps separately for better organization:\n\n**Errors** (`tasks\u002Ferrors.md`):\n- Command failures, API errors, exceptions\n- Include reproducibility, environment, suggested fix\n\n**Features** (`tasks\u002Ffeature_requests.md`):\n- Missing capabilities, things you wish existed\n- Include complexity estimate and suggested implementation\n\n### Syncing to Skill\n\nPeriodically merge workspace lessons into the published skill:\n\n```bash\n# From openclaw-workflow repo\npython3 scripts\u002Fsync_lessons.py --workspace ~\u002F.openclaw\u002Fworkspace\n\n# Dry run (preview changes)\npython3 scripts\u002Fsync_lessons.py --workspace ~\u002F.openclaw\u002Fworkspace --dry-run\n```\n\nThis merges workspace lessons into `references\u002Flessons.md` for version control and sharing.\n\n## Hooks (Optional)\n\nEnable automatic bootstrap reminders for self-improvement:\n\n```bash\nopenclaw hooks enable pi-workflow\n```\n\nThis injects a reminder at session start showing:\n- When to log lessons\u002Ferrors\u002Ffeatures\n- Format and metadata fields\n- Recurring pattern detection\n- Promotion paths\n\nSee `hooks\u002Fopenclaw\u002FHOOK.md` for details.\n\n---\n\n## Core Principles\n\n- **Simplicity First**: Make every change as simple as possible. Minimal code impact.\n- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.\n- **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fkai-tw\u002Fpi-workflow",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill pi-workflow",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill pi-workflow",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill pi-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fkai-tw\u002Fpi-workflow\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]