[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75F22FV58PA02MT82T2CGC4":3,"skill-same:01M75F22FV58PA02MT82T2CGC4":55},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M75F22FV58PA02MT82T2CGC4","codifica",null,"Keep context when work moves between agents or between you and a human. Uses the Codifica protocol to give every agent a shared, persistent memory of tasks, decisions, and handoffs — stored as plain text in Git.","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\u002Fdavidedicillo\u002Fcodifica\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: codifica\ndescription: Keep context when work moves between agents or between you and a human. Uses the Codifica protocol to give every agent a shared, persistent memory of tasks, decisions, and handoffs — stored as plain text in Git.\nversion: 1.0.0\nhomepage: https:\u002F\u002Fgithub.com\u002Fdavidedicillo\u002Fcodifica\nmetadata: {\"openclaw\":{\"emoji\":\"📋\",\"requires\":{\"anyBins\":[\"git\"]}}}\n---\n\n# Codifica Protocol Agent\n\nYou are operating in a repository that uses the **Codifica protocol (v0.2)** — a file-based protocol for coordinating work between humans and AI agents.\n\nCodifica uses plain text files committed with the code. There is no external service, no API, no database. Git is the audit log.\n\n## Before doing any work\n\n1. Read `codifica.json` at the repo root\n2. Read the spec file it references (the `spec` field — typically `codifica-spec.md`)\n3. Read ALL state files matching the `state` field (may be a string, glob, or array)\n\n**Do not proceed without reading the spec.**\n\nIf `codifica.json` does not exist in the repo, this protocol does not apply — work normally.\n\n## Understanding codifica.json\n\n```json\n{\n  \"protocol\": \"codifica\",\n  \"version\": \"0.2\",\n  \"spec\": \"codifica-spec.md\",\n  \"state\": \"work.md\",\n  \"assets\": \"assets\u002F\",\n  \"rules\": \"strict\"\n}\n```\n\nKey fields:\n- `state` — path to the state file(s). May be `\"work.md\"`, `\"work\u002F*.md\"`, or an array like `[\"work\u002Factive.md\", \"work\u002Fdone.md\"]`\n- `rules` — may be a string (`\"strict\"`) or an object with `allowed_agents`, `file_scope`, `max_concurrent_tasks_per_agent`, `stale_claim_hours`, and `custom_types`\n\nIf `rules` is an object, check:\n- `allowed_agents` — if non-empty and your agent name is not listed, stop and ask a human\n- `file_scope.include` \u002F `file_scope.exclude` — do not modify files outside the allowed scope\n- `max_concurrent_tasks_per_agent` — do not claim more tasks than this limit\n\n## Finding work\n\nScan all state files for tasks where:\n- `state` is `todo`\n- `owner` matches your agent name (`agent:\u003Cyour-name>`) or is `unassigned`\n- All `depends_on` tasks have `state: done`\n\nPick by priority: `critical` > `high` > `normal` > `low`.\n\nAmong equal priority, prefer tasks with no `depends_on` (leaf tasks first).\n\n## Claiming a task\n\nBefore starting work, you MUST claim the task in a single atomic commit:\n1. Set `state: in_progress`\n2. Set `owner: agent:\u003Cyour-name>`\n3. Set `claimed_at: \u003CISO-8601 timestamp>`\n4. Add a `state_transitions` entry recording the claim\n\nCommit all these changes together. If you are working with a remote, push immediately. If the push fails (another agent claimed first), do NOT start work — pull, re-evaluate, and pick a different task.\n\nAn `unassigned` task in `in_progress` is a protocol violation.\n\n## Reading context before starting\n\nBefore starting a task, read its `context` field:\n- `context.files` — read these files for background\n- `context.references` — read `execution_notes` from these prior task IDs\n- `context.constraints` — hard rules beyond acceptance criteria\n- `context.notes` — free-form guidance from the human\n\nIf the task has `depends_on`, also read the dependency tasks' `execution_notes` (especially the `summary`) and `artifacts` for handoff context.\n\n## Doing the work\n\nFollow the task's `acceptance` criteria. Respect any `context.constraints`. Work within the `file_scope` defined in `codifica.json`.\n\n## Recording completion\n\nWhen you complete work, update the task in the state file:\n\n1. Add an `execution_notes` entry:\n   ```yaml\n   execution_notes:\n     - by: agent:\u003Cyour-name>\n       note: |\n         Description of what you did.\n       summary: \"Single line, max 120 chars, scannable answer\"\n       timestamp: \u003CISO-8601>\n       provenance:\n         session_id: \u003Cyour-session-id-if-available>\n   ```\n\n2. Record any files you produced in `artifacts`:\n   ```yaml\n   artifacts:\n     - path: src\u002Ffeature\u002Fnew-file.ts\n       type: code\n     - path: assets\u002FTASK-ID\u002Foutput.csv\n       type: csv\n   ```\n\n3. Move the task to the appropriate next state:\n   - For `build` tasks: `in_progress` → `to_be_tested`\n   - For other types (`test`, `investigate`, `followup`): `in_progress` → `done` (may skip `to_be_tested`)\n   - Set `completed_at: \u003CISO-8601>` when moving to `done`\n\n4. Add a `state_transitions` entry:\n   ```yaml\n   state_transitions:\n     - from: in_progress\n       to: to_be_tested\n       by: agent:\u003Cyour-name>\n       reason: \"Work completed, ready for testing\"\n       timestamp: \u003CISO-8601>\n   ```\n\n5. Commit with a message referencing the task ID: `FEAT-101: implement login flow`\n\n## Rules you MUST follow\n\n- Pull before reading state files. Pull before writing changes.\n- Claim tasks with a single commit before starting work.\n- If your claim push fails, do not start — pick a different task.\n- Never edit `human_review` sections.\n- Never delete or modify files in `assets\u002F`.\n- Only the task owner may move a task from `to_be_tested` to `done`.\n- Never move tasks to `blocked` or `rejected` — only humans may do this.\n- Never reclaim stale tasks from other agents — only humans may reclaim.\n- Do not start tasks with unmet `depends_on`.\n- Include a `summary` (single line, max 120 chars) on your closing execution note.\n- Record artifacts produced by your work.\n- Set `completed_at` when moving a task to `done`.\n\n## Requesting a block\n\nIf you discover a genuine blocker (missing dependency, failing test, ambiguous requirement):\n- Add a note to `execution_notes` explaining the blocker and recommending the task be blocked\n- Do NOT move the task to `blocked` yourself — only humans may do this\n\n## Answering questions about work\n\nWhen asked about what work has been done (by you or other agents):\n- Scan state files for tasks matching the query (by `owner`, `state`, `labels`, `completed_at`)\n- Read the `summary` field on closing `execution_notes` for quick answers\n- Drill into full `note` text and `artifacts` when more detail is needed\n- Use `completed_at` and `labels` to filter by time and domain\n\nThis is the structured alternative to reading chat transcripts.\n\n## Conflicts\n\nIf your push fails due to a Git conflict:\n1. Pull the latest state\n2. Re-evaluate whether your changes still apply\n3. Retry or yield to human resolution\n\nConflicts on the same task should be escalated to a human.\n\n## Task states reference\n\n```\ntodo → in_progress → to_be_tested → done\n         ↓                            ↑\n       blocked ──→ todo ──────────────┘\n         ↓\n       rejected ──→ todo (human-only reopen)\n```\n\nOnly humans may move tasks to `blocked` or `rejected`.\nOnly humans may reopen tasks from `rejected`.\n","# Codifica Protocol Agent\n\nYou are operating in a repository that uses the **Codifica protocol (v0.2)** — a file-based protocol for coordinating work between humans and AI agents.\n\nCodifica uses plain text files committed with the code. There is no external service, no API, no database. Git is the audit log.\n\n## Before doing any work\n\n1. Read `codifica.json` at the repo root\n2. Read the spec file it references (the `spec` field — typically `codifica-spec.md`)\n3. Read ALL state files matching the `state` field (may be a string, glob, or array)\n\n**Do not proceed without reading the spec.**\n\nIf `codifica.json` does not exist in the repo, this protocol does not apply — work normally.\n\n## Understanding codifica.json\n\n```json\n{\n  \"protocol\": \"codifica\",\n  \"version\": \"0.2\",\n  \"spec\": \"codifica-spec.md\",\n  \"state\": \"work.md\",\n  \"assets\": \"assets\u002F\",\n  \"rules\": \"strict\"\n}\n```\n\nKey fields:\n- `state` — path to the state file(s). May be `\"work.md\"`, `\"work\u002F*.md\"`, or an array like `[\"work\u002Factive.md\", \"work\u002Fdone.md\"]`\n- `rules` — may be a string (`\"strict\"`) or an object with `allowed_agents`, `file_scope`, `max_concurrent_tasks_per_agent`, `stale_claim_hours`, and `custom_types`\n\nIf `rules` is an object, check:\n- `allowed_agents` — if non-empty and your agent name is not listed, stop and ask a human\n- `file_scope.include` \u002F `file_scope.exclude` — do not modify files outside the allowed scope\n- `max_concurrent_tasks_per_agent` — do not claim more tasks than this limit\n\n## Finding work\n\nScan all state files for tasks where:\n- `state` is `todo`\n- `owner` matches your agent name (`agent:\u003Cyour-name>`) or is `unassigned`\n- All `depends_on` tasks have `state: done`\n\nPick by priority: `critical` > `high` > `normal` > `low`.\n\nAmong equal priority, prefer tasks with no `depends_on` (leaf tasks first).\n\n## Claiming a task\n\nBefore starting work, you MUST claim the task in a single atomic commit:\n1. Set `state: in_progress`\n2. Set `owner: agent:\u003Cyour-name>`\n3. Set `claimed_at: \u003CISO-8601 timestamp>`\n4. Add a `state_transitions` entry recording the claim\n\nCommit all these changes together. If you are working with a remote, push immediately. If the push fails (another agent claimed first), do NOT start work — pull, re-evaluate, and pick a different task.\n\nAn `unassigned` task in `in_progress` is a protocol violation.\n\n## Reading context before starting\n\nBefore starting a task, read its `context` field:\n- `context.files` — read these files for background\n- `context.references` — read `execution_notes` from these prior task IDs\n- `context.constraints` — hard rules beyond acceptance criteria\n- `context.notes` — free-form guidance from the human\n\nIf the task has `depends_on`, also read the dependency tasks' `execution_notes` (especially the `summary`) and `artifacts` for handoff context.\n\n## Doing the work\n\nFollow the task's `acceptance` criteria. Respect any `context.constraints`. Work within the `file_scope` defined in `codifica.json`.\n\n## Recording completion\n\nWhen you complete work, update the task in the state file:\n\n1. Add an `execution_notes` entry:\n   ```yaml\n   execution_notes:\n     - by: agent:\u003Cyour-name>\n       note: |\n         Description of what you did.\n       summary: \"Single line, max 120 chars, scannable answer\"\n       timestamp: \u003CISO-8601>\n       provenance:\n         session_id: \u003Cyour-session-id-if-available>\n   ```\n\n2. Record any files you produced in `artifacts`:\n   ```yaml\n   artifacts:\n     - path: src\u002Ffeature\u002Fnew-file.ts\n       type: code\n     - path: assets\u002FTASK-ID\u002Foutput.csv\n       type: csv\n   ```\n\n3. Move the task to the appropriate next state:\n   - For `build` tasks: `in_progress` → `to_be_tested`\n   - For other types (`test`, `investigate`, `followup`): `in_progress` → `done` (may skip `to_be_tested`)\n   - Set `completed_at: \u003CISO-8601>` when moving to `done`\n\n4. Add a `state_transitions` entry:\n   ```yaml\n   state_transitions:\n     - from: in_progress\n       to: to_be_tested\n       by: agent:\u003Cyour-name>\n       reason: \"Work completed, ready for testing\"\n       timestamp: \u003CISO-8601>\n   ```\n\n5. Commit with a message referencing the task ID: `FEAT-101: implement login flow`\n\n## Rules you MUST follow\n\n- Pull before reading state files. Pull before writing changes.\n- Claim tasks with a single commit before starting work.\n- If your claim push fails, do not start — pick a different task.\n- Never edit `human_review` sections.\n- Never delete or modify files in `assets\u002F`.\n- Only the task owner may move a task from `to_be_tested` to `done`.\n- Never move tasks to `blocked` or `rejected` — only humans may do this.\n- Never reclaim stale tasks from other agents — only humans may reclaim.\n- Do not start tasks with unmet `depends_on`.\n- Include a `summary` (single line, max 120 chars) on your closing execution note.\n- Record artifacts produced by your work.\n- Set `completed_at` when moving a task to `done`.\n\n## Requesting a block\n\nIf you discover a genuine blocker (missing dependency, failing test, ambiguous requirement):\n- Add a note to `execution_notes` explaining the blocker and recommending the task be blocked\n- Do NOT move the task to `blocked` yourself — only humans may do this\n\n## Answering questions about work\n\nWhen asked about what work has been done (by you or other agents):\n- Scan state files for tasks matching the query (by `owner`, `state`, `labels`, `completed_at`)\n- Read the `summary` field on closing `execution_notes` for quick answers\n- Drill into full `note` text and `artifacts` when more detail is needed\n- Use `completed_at` and `labels` to filter by time and domain\n\nThis is the structured alternative to reading chat transcripts.\n\n## Conflicts\n\nIf your push fails due to a Git conflict:\n1. Pull the latest state\n2. Re-evaluate whether your changes still apply\n3. Retry or yield to human resolution\n\nConflicts on the same task should be escalated to a human.\n\n## Task states reference\n\n```\ntodo → in_progress → to_be_tested → done\n         ↓                            ↑\n       blocked ──→ todo ──────────────┘\n         ↓\n       rejected ──→ todo (human-only reopen)\n```\n\nOnly humans may move tasks to `blocked` or `rejected`.\nOnly humans may reopen tasks from `rejected`.\n",{"name":5,"version":24,"homepage":25,"metadata":26,"description":7},"1.0.0","https:\u002F\u002Fgithub.com\u002Fdavidedicillo\u002Fcodifica",{"openclaw":27},{"emoji":28,"requires":29},"📋",{"anyBins":30},[31],"git","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fdavidedicillo\u002Fcodifica",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill codifica",{"tool":47,"command":48},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill codifica",{"tool":50,"command":51},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill codifica","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdavidedicillo\u002Fcodifica\u002FSKILL.md",true,[],[56,64,71,78,85,92],{"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":63},"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":63},"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":63},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":63},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":63},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":63},"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",[],[]]