[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76ZGRK1XAAVCJC5DEPX4RD5":3,"skill-same:01M76ZGRK1XAAVCJC5DEPX4RD5":57},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M76ZGRK1XAAVCJC5DEPX4RD5","piv",null,"PIV workflow orchestrator - Plan, Implement, Validate loop for systematic multi-phase software development. Use when building features phase-by-phase with PRPs, automated validation loops, or multi-agent orchestration. Supports PRD creation, PRP generation, codebase analysis, and iterative execution with validation.","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\u002Fsmokealot420\u002Fftw\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: piv\ndescription: \"PIV workflow orchestrator - Plan, Implement, Validate loop for systematic multi-phase software development. Use when building features phase-by-phase with PRPs, automated validation loops, or multi-agent orchestration. Supports PRD creation, PRP generation, codebase analysis, and iterative execution with validation.\"\nuser-invocable: true\ndisable-model-invocation: true\nmetadata: {\"openclaw\":{\"emoji\":\"gear\",\"homepage\":\"https:\u002F\u002Fgithub.com\u002FSmokeAlot420\u002Fftw\",\"requires\":{\"bins\":[\"git\"]},\"os\":[\"darwin\",\"linux\"]}}\n---\n\n# PIV Ralph Orchestrator\n\n## Arguments: $ARGUMENTS\n\nParse arguments using this logic:\n\n### PRD Path Mode (first argument ends with `.md`)\n\nIf the first argument ends with `.md`, it's a direct path to a PRD file:\n- `PRD_PATH` - Direct path to the PRD file\n- `PROJECT_PATH` - Derived by going up from PRDs\u002F folder\n- `START_PHASE` - Second argument (default: 1)\n- `END_PHASE` - Third argument (default: auto-detect from PRD)\n\n### Project Path Mode\n\nIf the first argument does NOT end with `.md`:\n- `PROJECT_PATH` - Absolute path to project (default: current working directory)\n- `START_PHASE` - Second argument (default: 1)\n- `END_PHASE` - Third argument (default: 4)\n- `PRD_PATH` - Auto-discover from `PROJECT_PATH\u002FPRDs\u002F` folder\n\n### Detection Logic\n\n```\nIf $ARGUMENTS[0] ends with \".md\":\n  PRD_PATH = $ARGUMENTS[0]\n  PROJECT_PATH = dirname(dirname(PRD_PATH))\n  START_PHASE = $ARGUMENTS[1] or 1\n  END_PHASE = $ARGUMENTS[2] or auto-detect from PRD\n  PRD_NAME = basename without extension\nElse:\n  PROJECT_PATH = $ARGUMENTS[0] or current working directory\n  START_PHASE = $ARGUMENTS[1] or 1\n  END_PHASE = $ARGUMENTS[2] or 4\n  PRD_PATH = auto-discover from PROJECT_PATH\u002FPRDs\u002F\n  PRD_NAME = discovered PRD basename\n```\n\n### Mode Detection\n\nAfter parsing arguments:\n- If PRD_PATH was provided or auto-discovered → **MODE = \"execute\"** (normal flow)\n- If no PRD found and no PRD_PATH provided → **MODE = \"discovery\"**\n\n---\n\n## Required Reading by Role\n\n**CRITICAL: Each role MUST read their instruction files before acting.**\n\n| Role | Instructions |\n|------|-------------|\n| Discovery (no PRD) | Read {baseDir}\u002Freferences\u002Fpiv-discovery.md |\n| PRD Creation | Read {baseDir}\u002Freferences\u002Fcreate-prd.md |\n| PRP Generation | Read {baseDir}\u002Freferences\u002Fgenerate-prp.md |\n| Codebase Analysis | Read {baseDir}\u002Freferences\u002Fcodebase-analysis.md |\n| Executor | Read {baseDir}\u002Freferences\u002Fpiv-executor.md + {baseDir}\u002Freferences\u002Fexecute-prp.md |\n| Validator | Read {baseDir}\u002Freferences\u002Fpiv-validator.md |\n| Debugger | Read {baseDir}\u002Freferences\u002Fpiv-debugger.md |\n\n**Prerequisite:** A PRD must exist before entering the Phase Workflow. If no PRD exists, the orchestrator enters Discovery Mode (see below).\n\n---\n\n## Discovery Mode (No PRD Found)\n\nWhen MODE = \"discovery\":\n\n1. Read {baseDir}\u002Freferences\u002Fpiv-discovery.md for the discovery process\n2. Present discovery questions to the user in a friendly, conversational tone (single message)\n   - Target audience is vibe coders, not senior engineers — keep it approachable\n   - Skip questions the user already answered in their initial message\n3. Wait for user answers\n4. Fill gaps with your own expertise:\n   - If user doesn't know tech stack → research (web search, codebase scan) and PROPOSE one\n   - If user can't define phases → propose 3-4 phases based on scope\n   - Always propose-and-confirm: \"Here's what I'd suggest — does this sound right?\"\n5. Run project setup (create PRDs\u002F, PRPs\u002Ftemplates\u002F, PRPs\u002Fplanning\u002F)\n6. Generate PRD: Read {baseDir}\u002Freferences\u002Fcreate-prd.md, use discovery answers + your proposals to write PRD to PROJECT_PATH\u002FPRDs\u002FPRD-{project-name}.md\n7. Set PRD_PATH to the generated PRD, auto-detect phases → continue to Phase Workflow\n\nThe orchestrator handles discovery and PRD generation directly (no sub-agent needed — interactive Q&A requires staying in the same session, and answers are already in context for PRD generation).\n\n---\n\n## Orchestrator Philosophy\n\n> \"Context budget: ~15% orchestrator, 100% fresh per subagent\"\n\nYou are the **orchestrator**. You stay lean and manage workflow. You DO NOT execute PRPs yourself - you spawn specialized sub-agents with fresh context for each task.\n\n**Sub-agent spawning:** Use the `sessions_spawn` tool to create fresh sub-agent sessions. Each spawn is non-blocking — you'll receive results via an announce step. Wait for each agent's results before proceeding to the next step.\n\n---\n\n## Project Setup (piv-init)\n\nIf the project doesn't have PIV directories, create them:\n```bash\nmkdir -p PROJECT_PATH\u002FPRDs PROJECT_PATH\u002FPRPs\u002Ftemplates PROJECT_PATH\u002FPRPs\u002Fplanning\n```\nCopy `{baseDir}\u002Fassets\u002Fprp_base.md` to `PROJECT_PATH\u002FPRPs\u002Ftemplates\u002Fprp_base.md` if it doesn't exist.\nCreate `PROJECT_PATH\u002FWORKFLOW.md` from `{baseDir}\u002Fassets\u002Fworkflow-template.md` if it doesn't exist.\n\n---\n\n## Phase Workflow\n\nFor each phase from START_PHASE to END_PHASE:\n\n### Step 1: Check\u002FGenerate PRP\n\nCheck for existing PRP:\n```bash\nls -la PROJECT_PATH\u002FPRPs\u002F 2>\u002Fdev\u002Fnull | grep -i \"phase.*N\\|pN\\|p-N\"\n```\n\nIf no PRP exists, spawn a **fresh sub-agent** using `sessions_spawn` to do both codebase analysis and PRP generation in sequence:\n\n```\nRESEARCH & PRP GENERATION MISSION - Phase {N}\n==============================================\n\nProject root: {PROJECT_PATH}\nPRD Path: {PRD_PATH}\n\n## Phase {N} Scope (from PRD)\n{paste phase scope}\n\n## Step 1: Codebase Analysis\nRead {baseDir}\u002Freferences\u002Fcodebase-analysis.md for the process.\nSave to: {PROJECT_PATH}\u002FPRPs\u002Fplanning\u002F{PRD_NAME}-phase-{N}-analysis.md\n\n## Step 2: Generate PRP (analysis context still loaded)\nRead {baseDir}\u002Freferences\u002Fgenerate-prp.md for the process.\nUse template: PRPs\u002Ftemplates\u002Fprp_base.md\nOutput to: {PROJECT_PATH}\u002FPRPs\u002FPRP-{PRD_NAME}-phase-{N}.md\n\nDo BOTH steps yourself. DO NOT spawn sub-agents.\n```\n\n### Step 2: Spawn EXECUTOR\n\nSpawn a fresh sub-agent using `sessions_spawn`:\n\n```\nEXECUTOR MISSION - Phase {N}\n============================\n\nRead {baseDir}\u002Freferences\u002Fpiv-executor.md for your role definition.\nRead {baseDir}\u002Freferences\u002Fexecute-prp.md for the execution process.\n\nPRP Path: {PRP_PATH}\nProject: {PROJECT_PATH}\n\nFollow: Load PRP → Plan Thoroughly → Execute → Validate → Verify\nOutput EXECUTION SUMMARY with Status, Files, Tests, Issues.\n```\n\n### Step 3: Spawn VALIDATOR\n\nSpawn a fresh sub-agent using `sessions_spawn`:\n\n```\nVALIDATOR MISSION - Phase {N}\n=============================\n\nRead {baseDir}\u002Freferences\u002Fpiv-validator.md for your validation process.\n\nPRP Path: {PRP_PATH}\nProject: {PROJECT_PATH}\nExecutor Summary: {SUMMARY}\n\nVerify ALL requirements independently.\nOutput VERIFICATION REPORT with Grade, Checks, Gaps.\n```\n\n**Process result:** PASS → commit | GAPS_FOUND → debugger | HUMAN_NEEDED → ask user\n\n### Step 4: Debug Loop (Max 3 iterations)\n\nSpawn a fresh sub-agent using `sessions_spawn`:\n\n```\nDEBUGGER MISSION - Phase {N} - Iteration {I}\n============================================\n\nRead {baseDir}\u002Freferences\u002Fpiv-debugger.md for your debugging methodology.\n\nProject: {PROJECT_PATH}\nPRP Path: {PRP_PATH}\nGaps: {GAPS}\nErrors: {ERRORS}\n\nFix root causes, not symptoms. Run tests after each fix.\nOutput FIX REPORT with Status, Fixes Applied, Test Results.\n```\n\nAfter debugger: re-validate → PASS (commit) or loop (max 3) or escalate.\n\n### Step 5: Smart Commit\n\n```bash\ncd PROJECT_PATH && git status && git diff --stat\n```\n\nCreate semantic commit with `Built with FTW (First Try Works) - https:\u002F\u002Fgithub.com\u002FSmokeAlot420\u002Fftw`.\n\n### Step 6: Update WORKFLOW.md\n\nMark phase complete, note validation results.\n\n### Step 7: Next Phase\n\nLoop back to Step 1 for next phase.\n\n---\n\n## Error Handling\n\n- **No PRD**: Enter Discovery Mode (see Discovery Mode section above)\n- **Executor BLOCKED**: Ask user for guidance\n- **Validator HUMAN_NEEDED**: Ask user for guidance\n- **3 debug cycles exhausted**: Escalate to user\n\n### Sub-Agent Timeout\u002FFailure\nWhen a sub-agent times out or fails:\n1. Check for partial work (files created, tests written)\n2. Retry once with a simplified, shorter prompt\n3. If retry fails, escalate to user with what was accomplished\n\n---\n\n## Completion\n\n```\n## PIV RALPH COMPLETE\n\nPhases Completed: START to END\nTotal Commits: N\nValidation Cycles: M\n\n### Phase Summary:\n- Phase 1: [feature] - validated in N cycles\n...\n\nAll phases successfully implemented and validated.\n```\n","# PIV Ralph Orchestrator\n\n## Arguments: $ARGUMENTS\n\nParse arguments using this logic:\n\n### PRD Path Mode (first argument ends with `.md`)\n\nIf the first argument ends with `.md`, it's a direct path to a PRD file:\n- `PRD_PATH` - Direct path to the PRD file\n- `PROJECT_PATH` - Derived by going up from PRDs\u002F folder\n- `START_PHASE` - Second argument (default: 1)\n- `END_PHASE` - Third argument (default: auto-detect from PRD)\n\n### Project Path Mode\n\nIf the first argument does NOT end with `.md`:\n- `PROJECT_PATH` - Absolute path to project (default: current working directory)\n- `START_PHASE` - Second argument (default: 1)\n- `END_PHASE` - Third argument (default: 4)\n- `PRD_PATH` - Auto-discover from `PROJECT_PATH\u002FPRDs\u002F` folder\n\n### Detection Logic\n\n```\nIf $ARGUMENTS[0] ends with \".md\":\n  PRD_PATH = $ARGUMENTS[0]\n  PROJECT_PATH = dirname(dirname(PRD_PATH))\n  START_PHASE = $ARGUMENTS[1] or 1\n  END_PHASE = $ARGUMENTS[2] or auto-detect from PRD\n  PRD_NAME = basename without extension\nElse:\n  PROJECT_PATH = $ARGUMENTS[0] or current working directory\n  START_PHASE = $ARGUMENTS[1] or 1\n  END_PHASE = $ARGUMENTS[2] or 4\n  PRD_PATH = auto-discover from PROJECT_PATH\u002FPRDs\u002F\n  PRD_NAME = discovered PRD basename\n```\n\n### Mode Detection\n\nAfter parsing arguments:\n- If PRD_PATH was provided or auto-discovered → **MODE = \"execute\"** (normal flow)\n- If no PRD found and no PRD_PATH provided → **MODE = \"discovery\"**\n\n---\n\n## Required Reading by Role\n\n**CRITICAL: Each role MUST read their instruction files before acting.**\n\n| Role | Instructions |\n|------|-------------|\n| Discovery (no PRD) | Read {baseDir}\u002Freferences\u002Fpiv-discovery.md |\n| PRD Creation | Read {baseDir}\u002Freferences\u002Fcreate-prd.md |\n| PRP Generation | Read {baseDir}\u002Freferences\u002Fgenerate-prp.md |\n| Codebase Analysis | Read {baseDir}\u002Freferences\u002Fcodebase-analysis.md |\n| Executor | Read {baseDir}\u002Freferences\u002Fpiv-executor.md + {baseDir}\u002Freferences\u002Fexecute-prp.md |\n| Validator | Read {baseDir}\u002Freferences\u002Fpiv-validator.md |\n| Debugger | Read {baseDir}\u002Freferences\u002Fpiv-debugger.md |\n\n**Prerequisite:** A PRD must exist before entering the Phase Workflow. If no PRD exists, the orchestrator enters Discovery Mode (see below).\n\n---\n\n## Discovery Mode (No PRD Found)\n\nWhen MODE = \"discovery\":\n\n1. Read {baseDir}\u002Freferences\u002Fpiv-discovery.md for the discovery process\n2. Present discovery questions to the user in a friendly, conversational tone (single message)\n   - Target audience is vibe coders, not senior engineers — keep it approachable\n   - Skip questions the user already answered in their initial message\n3. Wait for user answers\n4. Fill gaps with your own expertise:\n   - If user doesn't know tech stack → research (web search, codebase scan) and PROPOSE one\n   - If user can't define phases → propose 3-4 phases based on scope\n   - Always propose-and-confirm: \"Here's what I'd suggest — does this sound right?\"\n5. Run project setup (create PRDs\u002F, PRPs\u002Ftemplates\u002F, PRPs\u002Fplanning\u002F)\n6. Generate PRD: Read {baseDir}\u002Freferences\u002Fcreate-prd.md, use discovery answers + your proposals to write PRD to PROJECT_PATH\u002FPRDs\u002FPRD-{project-name}.md\n7. Set PRD_PATH to the generated PRD, auto-detect phases → continue to Phase Workflow\n\nThe orchestrator handles discovery and PRD generation directly (no sub-agent needed — interactive Q&A requires staying in the same session, and answers are already in context for PRD generation).\n\n---\n\n## Orchestrator Philosophy\n\n> \"Context budget: ~15% orchestrator, 100% fresh per subagent\"\n\nYou are the **orchestrator**. You stay lean and manage workflow. You DO NOT execute PRPs yourself - you spawn specialized sub-agents with fresh context for each task.\n\n**Sub-agent spawning:** Use the `sessions_spawn` tool to create fresh sub-agent sessions. Each spawn is non-blocking — you'll receive results via an announce step. Wait for each agent's results before proceeding to the next step.\n\n---\n\n## Project Setup (piv-init)\n\nIf the project doesn't have PIV directories, create them:\n```bash\nmkdir -p PROJECT_PATH\u002FPRDs PROJECT_PATH\u002FPRPs\u002Ftemplates PROJECT_PATH\u002FPRPs\u002Fplanning\n```\nCopy `{baseDir}\u002Fassets\u002Fprp_base.md` to `PROJECT_PATH\u002FPRPs\u002Ftemplates\u002Fprp_base.md` if it doesn't exist.\nCreate `PROJECT_PATH\u002FWORKFLOW.md` from `{baseDir}\u002Fassets\u002Fworkflow-template.md` if it doesn't exist.\n\n---\n\n## Phase Workflow\n\nFor each phase from START_PHASE to END_PHASE:\n\n### Step 1: Check\u002FGenerate PRP\n\nCheck for existing PRP:\n```bash\nls -la PROJECT_PATH\u002FPRPs\u002F 2>\u002Fdev\u002Fnull | grep -i \"phase.*N\\|pN\\|p-N\"\n```\n\nIf no PRP exists, spawn a **fresh sub-agent** using `sessions_spawn` to do both codebase analysis and PRP generation in sequence:\n\n```\nRESEARCH & PRP GENERATION MISSION - Phase {N}\n==============================================\n\nProject root: {PROJECT_PATH}\nPRD Path: {PRD_PATH}\n\n## Phase {N} Scope (from PRD)\n{paste phase scope}\n\n## Step 1: Codebase Analysis\nRead {baseDir}\u002Freferences\u002Fcodebase-analysis.md for the process.\nSave to: {PROJECT_PATH}\u002FPRPs\u002Fplanning\u002F{PRD_NAME}-phase-{N}-analysis.md\n\n## Step 2: Generate PRP (analysis context still loaded)\nRead {baseDir}\u002Freferences\u002Fgenerate-prp.md for the process.\nUse template: PRPs\u002Ftemplates\u002Fprp_base.md\nOutput to: {PROJECT_PATH}\u002FPRPs\u002FPRP-{PRD_NAME}-phase-{N}.md\n\nDo BOTH steps yourself. DO NOT spawn sub-agents.\n```\n\n### Step 2: Spawn EXECUTOR\n\nSpawn a fresh sub-agent using `sessions_spawn`:\n\n```\nEXECUTOR MISSION - Phase {N}\n============================\n\nRead {baseDir}\u002Freferences\u002Fpiv-executor.md for your role definition.\nRead {baseDir}\u002Freferences\u002Fexecute-prp.md for the execution process.\n\nPRP Path: {PRP_PATH}\nProject: {PROJECT_PATH}\n\nFollow: Load PRP → Plan Thoroughly → Execute → Validate → Verify\nOutput EXECUTION SUMMARY with Status, Files, Tests, Issues.\n```\n\n### Step 3: Spawn VALIDATOR\n\nSpawn a fresh sub-agent using `sessions_spawn`:\n\n```\nVALIDATOR MISSION - Phase {N}\n=============================\n\nRead {baseDir}\u002Freferences\u002Fpiv-validator.md for your validation process.\n\nPRP Path: {PRP_PATH}\nProject: {PROJECT_PATH}\nExecutor Summary: {SUMMARY}\n\nVerify ALL requirements independently.\nOutput VERIFICATION REPORT with Grade, Checks, Gaps.\n```\n\n**Process result:** PASS → commit | GAPS_FOUND → debugger | HUMAN_NEEDED → ask user\n\n### Step 4: Debug Loop (Max 3 iterations)\n\nSpawn a fresh sub-agent using `sessions_spawn`:\n\n```\nDEBUGGER MISSION - Phase {N} - Iteration {I}\n============================================\n\nRead {baseDir}\u002Freferences\u002Fpiv-debugger.md for your debugging methodology.\n\nProject: {PROJECT_PATH}\nPRP Path: {PRP_PATH}\nGaps: {GAPS}\nErrors: {ERRORS}\n\nFix root causes, not symptoms. Run tests after each fix.\nOutput FIX REPORT with Status, Fixes Applied, Test Results.\n```\n\nAfter debugger: re-validate → PASS (commit) or loop (max 3) or escalate.\n\n### Step 5: Smart Commit\n\n```bash\ncd PROJECT_PATH && git status && git diff --stat\n```\n\nCreate semantic commit with `Built with FTW (First Try Works) - https:\u002F\u002Fgithub.com\u002FSmokeAlot420\u002Fftw`.\n\n### Step 6: Update WORKFLOW.md\n\nMark phase complete, note validation results.\n\n### Step 7: Next Phase\n\nLoop back to Step 1 for next phase.\n\n---\n\n## Error Handling\n\n- **No PRD**: Enter Discovery Mode (see Discovery Mode section above)\n- **Executor BLOCKED**: Ask user for guidance\n- **Validator HUMAN_NEEDED**: Ask user for guidance\n- **3 debug cycles exhausted**: Escalate to user\n\n### Sub-Agent Timeout\u002FFailure\nWhen a sub-agent times out or fails:\n1. Check for partial work (files created, tests written)\n2. Retry once with a simplified, shorter prompt\n3. If retry fails, escalate to user with what was accomplished\n\n---\n\n## Completion\n\n```\n## PIV RALPH COMPLETE\n\nPhases Completed: START to END\nTotal Commits: N\nValidation Cycles: M\n\n### Phase Summary:\n- Phase 1: [feature] - validated in N cycles\n...\n\nAll phases successfully implemented and validated.\n```\n",{"name":5,"metadata":24,"description":7,"user-invocable":34,"disable-model-invocation":34},{"openclaw":25},{"os":26,"emoji":29,"homepage":30,"requires":31},[27,28],"darwin","linux","gear","https:\u002F\u002Fgithub.com\u002FSmokeAlot420\u002Fftw",{"bins":32},[33],"git",true,"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fsmokealot420\u002Fftw",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":45,"prompt":55,"zipAvailable":34},[46,49,52],{"tool":47,"command":48},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill piv",{"tool":50,"command":51},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill piv",{"tool":53,"command":54},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill piv","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsmokealot420\u002Fftw\u002FSKILL.md",[],[58,66,73,80,87,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":65},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":65},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":65},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":65},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":65},"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",[],[]]