{"id":"07cf3f34-2164-4274-81a4-255ad6a2055a","entityType":"agent","slug":"clawhub-paudyyin-writing-plans-enhanced","name":"Writing Plans Enhanced","canonicalUrl":"https://www.xpersona.co/agent/clawhub-paudyyin-writing-plans-enhanced","canonicalPath":"/agent/clawhub-paudyyin-writing-plans-enhanced","generatedAt":"2026-10-11T20:59:29.971Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T16:51:09.973Z","emptyReason":null},"description":"Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that... Skill: Writing Plans Enhanced Owner: paudyyin Summary: Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that... Tags: latest:1.0.2 Version history: v1.0.2 | 2026-07-17T00:29:29.392Z | user Optimize description: English verb-first + Use when format, No-Op Test cleanup (-14% lines) v1.0.1 | 2026-06-19T00:08:00.078Z |","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s172x1s50dh0bgmm3yc9516nr586kk4b:writing-plans-enhanced","sourceUrl":"https://clawhub.ai/paudyyin/writing-plans-enhanced","homepage":"https://clawhub.ai/paudyyin/skills/writing-plans-enhanced","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/paudyyin/writing-plans-enhanced","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/paudyyin/skills/writing-plans-enhanced","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that... "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:51:09.973Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:51:09.973Z","emptyReason":null},"stars":null,"forks":null,"downloads":1024,"packageName":null,"latestVersion":"1.0.2","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:51:09.898Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T16:51:09.973Z","lastCrawledAt":"2026-10-11T16:51:09.898Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T16:51:09.898Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.2","createdAt":"2026-07-17T00:29:29.392Z","changelog":"Optimize description: English verb-first + Use when format, No-Op Test cleanup (-14% lines)","fileCount":4,"zipByteSize":4304},{"version":"1.0.1","createdAt":"2026-06-19T00:08:00.078Z","changelog":"2026-06-19 批量更新","fileCount":4,"zipByteSize":4258},{"version":"1.0.0","createdAt":"2026-05-14T10:56:06.673Z","changelog":"多步任务计划写作，支持里程碑/数据流/风险表/交互式HTML","fileCount":3,"zipByteSize":3968}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s172x1s50dh0bgmm3yc9516nr586kk4b:writing-plans-enhanced","setupComplexity":"low","setupSteps":["Node.js workspace detected. Install dependencies securely: run `npm ci --ignore-scripts` to prevent post-install lifecycle triggers from running arbitrary code, then selectively audit the dependency tree.","Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T20:59:29.971Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-paudyyin-writing-plans-enhanced/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T16:51:09.973Z","emptyReason":null},"readme":"Skill: Writing Plans Enhanced\n\nOwner: paudyyin\n\nSummary: Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that...\n\nTags: latest:1.0.2\n\nVersion history:\n\nv1.0.2 | 2026-07-17T00:29:29.392Z | user\n\nOptimize description: English verb-first + Use when format, No-Op Test cleanup (-14% lines)\n\nv1.0.1 | 2026-06-19T00:08:00.078Z | user\n\n2026-06-19 批量更新\n\nv1.0.0 | 2026-05-14T10:56:06.673Z | user\n\n多步任务计划写作，支持里程碑/数据流/风险表/交互式HTML\n\nArchive index:\n\nArchive v1.0.2: 4 files, 4304 bytes\n\nFiles: _meta.json (141b), package.json (268b), skill-card.md (1973b), SKILL.md (6358b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: writing-plans-enhanced\nversion: 1.0.0\ndescription: \"Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that need visual planning artifacts.\"\ndependencies: []\n---\n\n# Writing Plans �?Enhanced\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase. Document everything they need to know: which files to touch, data flow, mockups, risks. Give them the whole plan as bite-sized tasks.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n**Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md`\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies/libraries]\n\n**Effort:** ~N weeks | **Surfaces touched:** N packages | **New tables:** N | **Feature flag:** name\n```\n\n## Milestone Timeline\n\nShip in slices, each independently reviewable and each behind the flag. Nothing is user-visible until the last slice.\n\n```markdown\n### Milestone 1: Schema & API Contract (Week 1 · Mon–Tue)\n\nNew tables, migrations, and API stubs. No UI. Contract reviewed before anything else lands.\n\n- `packages/db` �?new migrations\n- `packages/api` �?tRPC router stubs\n\n### Milestone 2: Core Component (Week 1 · Wed–Fri)\n\nStatic component rendered from fixtures. Optimistic insert on submit, rollback on failure.\n\n- `apps/web` �?new component\n- `apps/storybook` �?fixture stories\n\n### Milestone 3: Realtime Integration (Week 2 · Mon–Wed)\n\nSubscribe to changes. Track state for sidebar digest.\n\n### Milestone 4: Notifications & Ramp (Week 2 · Thu–Fri)\n\nMention detection �?notification row, email digest fallback, ramp feature flag.\n```\n\n## Data Flow\n\nDescribe the data flow from client to persistence. Use ASCII diagrams with solid = request/response, dashed = realtime/async.\n\n```markdown\n### Data Flow: Optimistic Write Path\n\nClient                    API Server              Database\n  �?                         �?                      �?  ├─�?POST /tasks (optimistic)                       �?  �? ├─�?update local cache immediately              �?  �? └─�?send mutation ─────►┤                       �?  �?                          ├─�?validate ─────────►┤\n  �?                          �?                      �?  �?                          │◄─ 200 OK ─────────────�?  │◄─ cache update ──────────�?                      �?  �?                         �?                      �?\n### Realtime Fan-Out (dashed path)\n\nDatabase ─ ─ ─�?WebSocket ─ ─ ─�?Other clients\n  �?             �?                 �?  └─�?trigger ──►┤                  └─�?re-render\n                 └─�?push notification\n```\n\n## Mockups\n\nNot pixel-final �?just enough that the reviewer and implementer agree on layout and placement.\n\n```markdown\n### A · Thread Inside an Open Task Card\n\n┌──────────────────────────────────────�?�? Ship onboarding empty-state rewrite  �?�? BIR-1142 · Assigned to Priya · Due  �?├──────────────────────────────────────�?�? Priya: Should we add an illustration?�?�? You: Yes, let me mock it up          �?�?                                      �?�? ┌─────────────────────────────────�?�?�? �?Add a comment...          Post �?�?�? └─────────────────────────────────�?�?└──────────────────────────────────────�?\n### B · Sidebar Unread Digest\n\n┌──────────────────────────────────────�?�?🔴 Jonah commented on BIR-1142       �?�?   \"Should the illustration swap...\"  �?�?🔵 Aiko mentioned you on BIR-1098    �?�?   \"@priya can you confirm...\"        �?└──────────────────────────────────────�?```\n\n## Risk Table\n\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| Migration locks table during deploy | Medium | High | Run with `CONCURRENTLY`; schedule off-peak |\n| Realtime subscription leaks memory | Low | Medium | Add max-subscription cap; monitor heap |\n| Feature flag not ramped correctly | Medium | Medium | Auto-alert if flag stuck > 3 days |\n\n## Bite-Sized Task Granularity\n\n**Each step is one action (2-5 minutes):**\n\n- \"Write the failing test\" �?step\n- \"Run it to make sure it fails\" �?step\n- \"Implement the minimal code to make the test pass\" �?step\n- \"Run the tests and make sure they pass\" �?step\n- \"Commit\" �?step\n\n## Task Structure\n\n```markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact/path/to/file.py`\n- Modify: `exact/path/to/existing.py:123-145`\n- Test: `tests/exact/path/to/test.py`\n\n**Step 1: Write the failing test**\n[code block]\n\n**Step 2: Run test to verify it fails**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n**Step 3: Write minimal implementation**\n[code block]\n\n**Step 4: Run test to verify it passes**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: PASS\n\n**Step 5: Commit**\n```bash\ngit add tests/path/test.py src/path/file.py\ngit commit -m \"feat: add specific feature\"\n```\n\n## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `docs/plans/<filename>.md`. Two execution options:**\n\n1. **Subagent-Driven (this session)** �?I dispatch fresh subagent per task, review between tasks\n2. **Parallel Session (separate)** �?Open new session with executing-plans, batch execution with checkpoints\n\nWhich approach?\"\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn73z7zhz92tv6skpnmpy5pdfh86j68x\",\n  \"slug\": \"writing-plans-enhanced\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1784248169392\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:\n\nCreate enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[paudyyin](https://clawhub.ai/user/paudyyin)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineering teams use this skill before complex multi-step implementation work to create repository-aware plans with milestones, data flow, mockups, risks, and bite-sized execution tasks.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Generated plans may contain incorrect or misleading implementation guidance.\n\nMitigation: Review each plan before execution and confirm that proposed files, data flows, risks, and tasks match the repository.\n\nRisk: Plans may propose subagent handoff, git add, or git commit commands.\n\nMitigation: Require explicit approval before executing subagent handoffs or any git staging and commit commands.\n\nRisk: The skill creates persistent planning markdown files in the repository.\n\nMitigation: Inspect generated docs/plans files before keeping or committing them.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/paudyyin/skills/writing-plans-enhanced)\n\n## Skill Output:\n\n**Output Type(s):** [Markdown, Code, Shell commands, Guidance]\n\n**Output Format:** [Markdown implementation plan with headings, diagrams, mockups, risk tables, task steps, code blocks, and command blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Plans are intended to be saved as persistent markdown files under docs/plans and reviewed before execution.]\n\n## Skill Version(s):\n\n1.0.2 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v1.0.2:package.json\n\n{\r\n    \"name\":  \"writing-plans-enhanced\",\r\n    \"version\":  \"1.0.0\",\r\n    \"description\":  \"Use when you have a spec or requirements for a multi-step task, before touching code. Enhanced version with milestone timelines, data flow diagrams, mockups, and risk tables.\"\r\n}\n\nArchive v1.0.1: 4 files, 4258 bytes\n\nFiles: _meta.json (141b), package.json (268b), skill-card.md (1789b), SKILL.md (6388b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: writing-plans-enhanced\ndescription: Use when you have a spec or requirements for a multi-step task, before touching code. Enhanced version with milestone timelines, data flow diagrams, mockups, and risk tables.\n---\n\n# Writing Plans — Enhanced\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase. Document everything they need to know: which files to touch, data flow, mockups, risks. Give them the whole plan as bite-sized tasks.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n**Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md`\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies/libraries]\n\n**Effort:** ~N weeks | **Surfaces touched:** N packages | **New tables:** N | **Feature flag:** name\n```\n\n## Milestone Timeline\n\nShip in slices, each independently reviewable and each behind the flag. Nothing is user-visible until the last slice.\n\n```markdown\n### Milestone 1: Schema & API Contract (Week 1 · Mon–Tue)\n\nNew tables, migrations, and API stubs. No UI. Contract reviewed before anything else lands.\n\n- `packages/db` — new migrations\n- `packages/api` — tRPC router stubs\n\n### Milestone 2: Core Component (Week 1 · Wed–Fri)\n\nStatic component rendered from fixtures. Optimistic insert on submit, rollback on failure.\n\n- `apps/web` — new component\n- `apps/storybook` — fixture stories\n\n### Milestone 3: Realtime Integration (Week 2 · Mon–Wed)\n\nSubscribe to changes. Track state for sidebar digest.\n\n### Milestone 4: Notifications & Ramp (Week 2 · Thu–Fri)\n\nMention detection → notification row, email digest fallback, ramp feature flag.\n```\n\n## Data Flow\n\nDescribe the data flow from client to persistence. Use ASCII diagrams with solid = request/response, dashed = realtime/async.\n\n```markdown\n### Data Flow: Optimistic Write Path\n\nClient                    API Server              Database\n  │                          │                       │\n  ├─► POST /tasks (optimistic)                       │\n  │  ├─► update local cache immediately              │\n  │  └─► send mutation ─────►┤                       │\n  │                           ├─► validate ─────────►┤\n  │                           │                       │\n  │                           │◄─ 200 OK ─────────────┤\n  │◄─ cache update ──────────┤                       │\n  │                          │                       │\n\n### Realtime Fan-Out (dashed path)\n\nDatabase ─ ─ ─► WebSocket ─ ─ ─► Other clients\n  │              │                  │\n  └─► trigger ──►┤                  └─► re-render\n                 └─► push notification\n```\n\n## Mockups\n\nNot pixel-final — just enough that the reviewer and implementer agree on layout and placement.\n\n```markdown\n### A · Thread Inside an Open Task Card\n\n┌──────────────────────────────────────┐\n│  Ship onboarding empty-state rewrite  │\n│  BIR-1142 · Assigned to Priya · Due  │\n├──────────────────────────────────────┤\n│  Priya: Should we add an illustration?│\n│  You: Yes, let me mock it up          │\n│                                       │\n│  ┌─────────────────────────────────┐ │\n│  │ Add a comment...          Post │ │\n│  └─────────────────────────────────┘ │\n└──────────────────────────────────────┘\n\n### B · Sidebar Unread Digest\n\n┌──────────────────────────────────────┐\n│ 🔴 Jonah commented on BIR-1142       │\n│    \"Should the illustration swap...\"  │\n│ 🔵 Aiko mentioned you on BIR-1098    │\n│    \"@priya can you confirm...\"        │\n└──────────────────────────────────────┘\n```\n\n## Risk Table\n\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| Migration locks table during deploy | Medium | High | Run with `CONCURRENTLY`; schedule off-peak |\n| Realtime subscription leaks memory | Low | Medium | Add max-subscription cap; monitor heap |\n| Feature flag not ramped correctly | Medium | Medium | Auto-alert if flag stuck > 3 days |\n\n## Bite-Sized Task Granularity\n\n**Each step is one action (2-5 minutes):**\n\n- \"Write the failing test\" — step\n- \"Run it to make sure it fails\" — step\n- \"Implement the minimal code to make the test pass\" — step\n- \"Run the tests and make sure they pass\" — step\n- \"Commit\" — step\n\n## Task Structure\n\n```markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact/path/to/file.py`\n- Modify: `exact/path/to/existing.py:123-145`\n- Test: `tests/exact/path/to/test.py`\n\n**Step 1: Write the failing test**\n[code block]\n\n**Step 2: Run test to verify it fails**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n**Step 3: Write minimal implementation**\n[code block]\n\n**Step 4: Run test to verify it passes**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: PASS\n\n**Step 5: Commit**\n```bash\ngit add tests/path/test.py src/path/file.py\ngit commit -m \"feat: add specific feature\"\n```\n\n## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `docs/plans/<filename>.md`. Two execution options:**\n\n1. **Subagent-Driven (this session)** — I dispatch fresh subagent per task, review between tasks\n2. **Parallel Session (separate)** — Open new session with executing-plans, batch execution with checkpoints\n\nWhich approach?\"\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn73z7zhz92tv6skpnmpy5pdfh86j68x\",\n  \"slug\": \"writing-plans-enhanced\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1781827680078\n}\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nUse when you have a spec or requirements for a multi-step task, before touching code. Enhanced version with milestone timelines, data flow diagrams, mockups, and risk tables. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[paudyyin](https://clawhub.ai/user/paudyyin) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to create detailed implementation plans before code changes, including timelines, data flow, mockups, risks, and task-by-task execution handoff. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Generated plans can influence future code changes through task steps, commit guidance, and execution handoff instructions. <br>\nMitigation: Review generated plans before using them to drive implementation, especially suggested tasks, commits, and subagent workflow. <br>\n\n\n## Reference(s): <br>\n- [Writing Plans Enhanced on ClawHub](https://clawhub.ai/paudyyin/writing-plans-enhanced) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Markdown, Files, Guidance, Shell commands] <br>\n**Output Format:** [Markdown implementation plan with code blocks, ASCII diagrams, tables, and execution choices] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Plans are intended to be saved under docs/plans/YYYY-MM-DD-<feature-name>.md.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v1.0.1:package.json\n\n{\r\n    \"name\":  \"writing-plans-enhanced\",\r\n    \"version\":  \"1.0.0\",\r\n    \"description\":  \"Use when you have a spec or requirements for a multi-step task, before touching code. Enhanced version with milestone timelines, data flow diagrams, mockups, and risk tables.\"\r\n}\n\nArchive v1.0.0: 3 files, 3968 bytes\n\nFiles: skill-card.md (1782b), SKILL.md (6388b), _meta.json (141b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: writing-plans-enhanced\ndescription: Use when you have a spec or requirements for a multi-step task, before touching code. Enhanced version with milestone timelines, data flow diagrams, mockups, and risk tables.\n---\n\n# Writing Plans — Enhanced\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase. Document everything they need to know: which files to touch, data flow, mockups, risks. Give them the whole plan as bite-sized tasks.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n**Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md`\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies/libraries]\n\n**Effort:** ~N weeks | **Surfaces touched:** N packages | **New tables:** N | **Feature flag:** name\n```\n\n## Milestone Timeline\n\nShip in slices, each independently reviewable and each behind the flag. Nothing is user-visible until the last slice.\n\n```markdown\n### Milestone 1: Schema & API Contract (Week 1 · Mon–Tue)\n\nNew tables, migrations, and API stubs. No UI. Contract reviewed before anything else lands.\n\n- `packages/db` — new migrations\n- `packages/api` — tRPC router stubs\n\n### Milestone 2: Core Component (Week 1 · Wed–Fri)\n\nStatic component rendered from fixtures. Optimistic insert on submit, rollback on failure.\n\n- `apps/web` — new component\n- `apps/storybook` — fixture stories\n\n### Milestone 3: Realtime Integration (Week 2 · Mon–Wed)\n\nSubscribe to changes. Track state for sidebar digest.\n\n### Milestone 4: Notifications & Ramp (Week 2 · Thu–Fri)\n\nMention detection → notification row, email digest fallback, ramp feature flag.\n```\n\n## Data Flow\n\nDescribe the data flow from client to persistence. Use ASCII diagrams with solid = request/response, dashed = realtime/async.\n\n```markdown\n### Data Flow: Optimistic Write Path\n\nClient                    API Server              Database\n  │                          │                       │\n  ├─► POST /tasks (optimistic)                       │\n  │  ├─► update local cache immediately              │\n  │  └─► send mutation ─────►┤                       │\n  │                           ├─► validate ─────────►┤\n  │                           │                       │\n  │                           │◄─ 200 OK ─────────────┤\n  │◄─ cache update ──────────┤                       │\n  │                          │                       │\n\n### Realtime Fan-Out (dashed path)\n\nDatabase ─ ─ ─► WebSocket ─ ─ ─► Other clients\n  │              │                  │\n  └─► trigger ──►┤                  └─► re-render\n                 └─► push notification\n```\n\n## Mockups\n\nNot pixel-final — just enough that the reviewer and implementer agree on layout and placement.\n\n```markdown\n### A · Thread Inside an Open Task Card\n\n┌──────────────────────────────────────┐\n│  Ship onboarding empty-state rewrite  │\n│  BIR-1142 · Assigned to Priya · Due  │\n├──────────────────────────────────────┤\n│  Priya: Should we add an illustration?│\n│  You: Yes, let me mock it up          │\n│                                       │\n│  ┌─────────────────────────────────┐ │\n│  │ Add a comment...          Post │ │\n│  └─────────────────────────────────┘ │\n└──────────────────────────────────────┘\n\n### B · Sidebar Unread Digest\n\n┌──────────────────────────────────────┐\n│ 🔴 Jonah commented on BIR-1142       │\n│    \"Should the illustration swap...\"  │\n│ 🔵 Aiko mentioned you on BIR-1098    │\n│    \"@priya can you confirm...\"        │\n└──────────────────────────────────────┘\n```\n\n## Risk Table\n\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| Migration locks table during deploy | Medium | High | Run with `CONCURRENTLY`; schedule off-peak |\n| Realtime subscription leaks memory | Low | Medium | Add max-subscription cap; monitor heap |\n| Feature flag not ramped correctly | Medium | Medium | Auto-alert if flag stuck > 3 days |\n\n## Bite-Sized Task Granularity\n\n**Each step is one action (2-5 minutes):**\n\n- \"Write the failing test\" — step\n- \"Run it to make sure it fails\" — step\n- \"Implement the minimal code to make the test pass\" — step\n- \"Run the tests and make sure they pass\" — step\n- \"Commit\" — step\n\n## Task Structure\n\n```markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact/path/to/file.py`\n- Modify: `exact/path/to/existing.py:123-145`\n- Test: `tests/exact/path/to/test.py`\n\n**Step 1: Write the failing test**\n[code block]\n\n**Step 2: Run test to verify it fails**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n**Step 3: Write minimal implementation**\n[code block]\n\n**Step 4: Run test to verify it passes**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: PASS\n\n**Step 5: Commit**\n```bash\ngit add tests/path/test.py src/path/file.py\ngit commit -m \"feat: add specific feature\"\n```\n\n## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `docs/plans/<filename>.md`. Two execution options:**\n\n1. **Subagent-Driven (this session)** — I dispatch fresh subagent per task, review between tasks\n2. **Parallel Session (separate)** — Open new session with executing-plans, batch execution with checkpoints\n\nWhich approach?\"\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn73z7zhz92tv6skpnmpy5pdfh86j68x\",\n  \"slug\": \"writing-plans-enhanced\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1778756166673\n}\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nUse when you have a spec or requirements for a multi-step task, before touching code. Enhanced version with milestone timelines, data flow diagrams, mockups, and risk tables. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[paudyyin](https://clawhub.ai/user/paudyyin) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineering teams use this skill to create comprehensive implementation plans for multi-step tasks before changing code. The plans cover files to touch, data flow, mockups, risks, milestones, tests, and handoff options. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Generated plans include visible instructions for later agent execution, which could lead to unintended task execution if accepted without review. <br>\nMitigation: Review the generated plan header, task scope, and checkpoints before using any subagent execution workflow. <br>\n\n\n## Reference(s): <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown implementation plan with structured sections, tables, ASCII diagrams, and shell command examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Plans are intended to be reviewed before execution and may be saved under docs/plans/YYYY-MM-DD-<feature-name>.md.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Writing Plans Enhanced Owner: paudyyin Summary: Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that... Tags: latest:1.0.2 Version history: v1.0.2 | 2026-07-17T00:29:29.392Z | user Optimize description: English verb-first + Use when format, No-Op Test cleanup (-14% lines) v1.0.1 | 2026-06-19T00:08:00.078Z | ","codeSnippets":[],"executableExamples":[{"language":"markdown","snippet":"# [Feature Name] Implementation Plan\n\n> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies/libraries]\n\n**Effort:** ~N weeks | **Surfaces touched:** N packages | **New tables:** N | **Feature flag:** name"},{"language":"markdown","snippet":"### Milestone 1: Schema & API Contract (Week 1 · Mon–Tue)\n\nNew tables, migrations, and API stubs. No UI. Contract reviewed before anything else lands.\n\n- `packages/db` �?new migrations\n- `packages/api` �?tRPC router stubs\n\n### Milestone 2: Core Component (Week 1 · Wed–Fri)\n\nStatic component rendered from fixtures. Optimistic insert on submit, rollback on failure.\n\n- `apps/web` �?new component\n- `apps/storybook` �?fixture stories\n\n### Milestone 3: Realtime Integration (Week 2 · Mon–Wed)\n\nSubscribe to changes. Track state for sidebar digest.\n\n### Milestone 4: Notifications & Ramp (Week 2 · Thu–Fri)\n\nMention detection �?notification row, email digest fallback, ramp feature flag."},{"language":"markdown","snippet":"### Data Flow: Optimistic Write Path\n\nClient                    API Server              Database\n  �?                         �?                      �?  ├─�?POST /tasks (optimistic)                       �?  �? ├─�?update local cache immediately              �?  �? └─�?send mutation ─────►┤                       �?  �?                          ├─�?validate ─────────►┤\n  �?                          �?                      �?  �?                          │◄─ 200 OK ─────────────�?  │◄─ cache update ──────────�?                      �?  �?                         �?                      �?\n### Realtime Fan-Out (dashed path)\n\nDatabase ─ ─ ─�?WebSocket ─ ─ ─�?Other clients\n  �?             �?                 �?  └─�?trigger ──►┤                  └─�?re-render\n                 └─�?push notification"},{"language":"markdown","snippet":"### A · Thread Inside an Open Task Card\n\n┌──────────────────────────────────────�?�? Ship onboarding empty-state rewrite  �?�? BIR-1142 · Assigned to Priya · Due  �?├──────────────────────────────────────�?�? Priya: Should we add an illustration?�?�? You: Yes, let me mock it up          �?�?                                      �?�? ┌─────────────────────────────────�?�?�? �?Add a comment...          Post �?�?�? └─────────────────────────────────�?�?└──────────────────────────────────────�?\n### B · Sidebar Unread Digest\n\n┌──────────────────────────────────────�?�?🔴 Jonah commented on BIR-1142       �?�?   \"Should the illustration swap...\"  �?�?🔵 Aiko mentioned you on BIR-1098    �?�?   \"@priya can you confirm...\"        �?└──────────────────────────────────────�?"},{"language":"markdown","snippet":"### Task N: [Component Name]\n\n**Files:**\n- Create: `exact/path/to/file.py`\n- Modify: `exact/path/to/existing.py:123-145`\n- Test: `tests/exact/path/to/test.py`\n\n**Step 1: Write the failing test**\n[code block]\n\n**Step 2: Run test to verify it fails**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n**Step 3: Write minimal implementation**\n[code block]\n\n**Step 4: Run test to verify it passes**\nRun: `pytest tests/path/test.py::test_name -v`\nExpected: PASS\n\n**Step 5: Commit**"},{"language":"text","snippet":"## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `docs/plans/<filename>.md`. Two execution options:**\n\n1. **Subagent-Driven (this session)** �?I dispatch fresh subagent per task, review between tasks\n2. **Parallel Session (separate)** �?Open new session with executing-plans, batch execution with checkpoints\n\nWhich approach?\"\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn73z7zhz92tv6skpnmpy5pdfh86j68x\",\n  \"slug\": \"writing-plans-enhanced\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1784248169392\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:\n\nCreate enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[paudyyin](https://clawhub.ai/user/paudyyin)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineering teams use this skill before complex multi-step implementation work to create repository-aware plans with milestones, data flow, mockups, risks, and bite-sized execution tasks.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Generated plans may contain incorrect or misleading implementation guidance.\n\nMitigation: Review each plan before execution and confirm that proposed files, data flows, risks, and tasks match the repository.\n\nRisk: Plans may propose subagent handoff, git add, or git commit commands.\n\nMitigation: Require explicit approval before executing subagent handoffs or any git staging and commit commands.\n\nRisk: The skill creates persistent planning markdown files in the repository.\n\nMitigation: Inspect generated docs/plans files before keeping or committing them.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/paudyyin/skills/writing-plans-enhanced)\n\n## Skill Output:\n\n**Output Type(s):** [Markdown, Code, Shell commands, Guidance]\n\n**Output Format:** [Markdown implementation plan with headings, diagrams, mockups, risk tables, task step"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: writing-plans-enhanced\nversion: 1.0.0\ndescription: \"Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that need visual planning artifacts.\"\ndependencies: []\n---\n\n# Writing Plans �?Enhanced\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase. Document everything they need to know: which files to touch, data flow, mockups, risks. Give them the whole plan as bite-sized tasks.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n**Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md`\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies/libraries]\n\n**Effort:** ~N weeks | **Surfaces touched:** N packages | **New tables:** N | **Feature flag:** name\n```\n\n## Milestone Timeline\n\nShip in slices, each independently reviewable and each behind the flag. Nothing is user-visible until the last slice.\n\n```markdown\n### Milestone 1: Schema & API Contract (Week 1 · Mon–Tue)\n\nNew tables, migrations, and API stubs. No UI. Contract reviewed before anything else lands.\n\n- `packages/db` �?new migrations\n- `packages/api` �?tRPC router stubs\n\n### Milestone 2: Core Component (Week 1 · Wed–Fri)\n\nStatic component rendered from fixtures. Optimistic insert on submit, rollback on failure.\n\n- `apps/web` �?new component\n- `apps/storybook` �?fixture stories\n\n### Milestone 3: Realtime Integration (Week 2 · Mon–Wed)\n\nSubscribe to changes. Track state for sidebar digest.\n\n### Milestone 4: Notifications & Ramp (Week 2 · Thu–Fri)\n\nMention detection �?notification row, email digest fallback, ramp feature flag.\n```\n\n## Data Flow\n\nDescribe the data flow from client to persistence. Use ASCII diagrams with solid = request/response, dashed = realtime/async.\n\n```markdown\n### Data Flow: Optimistic Write Path\n\nClient                    API Server              Database\n  �?                         �?                      �?  ├─�?POST /tasks (optimistic)                       �?  �? ├─�?update local cache immediately              �?  �? └─�?send mutation ─────►┤                       �?  �?                          ├─�?validate ─────────►┤\n  �?                          �?                      �?  �?                          │◄─ 200 OK ─────────────�?  │◄─ cache update ──────────�?                      �?  �?                         �?                      �?\n### Realtime Fan-Out (dashed path)\n\nDatabase ─ ─ ─�?WebSocket ─ ─ ─�?Other clients\n  �?             �?                 �?  └─�?trigger ──►┤                  └─�?re-render\n                 └─�?push notification\n```\n\n## M"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn73z7zhz92tv6skpnmpy5pdfh86j68x\",\n  \"slug\": \"writing-plans-enhanced\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1784248169392\n}"},{"path":"skill-card.md","content":"## Description:\n\nCreate enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[paudyyin](https://clawhub.ai/user/paudyyin)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineering teams use this skill before complex multi-step implementation work to create repository-aware plans with milestones, data flow, mockups, risks, and bite-sized execution tasks.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Generated plans may contain incorrect or misleading implementation guidance.\n\nMitigation: Review each plan before execution and confirm that proposed files, data flows, risks, and tasks match the repository.\n\nRisk: Plans may propose subagent handoff, git add, or git commit commands.\n\nMitigation: Require explicit approval before executing subagent handoffs or any git staging and commit commands.\n\nRisk: The skill creates persistent planning markdown files in the repository.\n\nMitigation: Inspect generated docs/plans files before keeping or committing them.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/paudyyin/skills/writing-plans-enhanced)\n\n## Skill Output:\n\n**Output Type(s):** [Markdown, Code, Shell commands, Guidance]\n\n**Output Format:** [Markdown implementation plan with headings, diagrams, mockups, risk tables, task steps, code blocks, and command blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Plans are intended to be saved as persistent markdown files under docs/plans and reviewed before execution.]\n\n## Skill Version(s):\n\n1.0.2 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."},{"path":"package.json","content":"{\r\n    \"name\":  \"writing-plans-enhanced\",\r\n    \"version\":  \"1.0.0\",\r\n    \"description\":  \"Use when you have a spec or requirements for a multi-step task, before touching code. Enhanced version with milestone timelines, data flow diagrams, mockups, and risk tables.\"\r\n}"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that... Skill: Writing Plans Enhanced Owner: paudyyin Summary: Create enhanced implementation plans with milestone timelines, data flow diagrams, mockups, and risk tables. Use when planning complex multi-step tasks that... Tags: latest:1.0.2 Version history: v1.0.2 | 2026-07-17T00:29:29.392Z | user Optimize description: English verb-first + Use when format, No-Op Test cleanup (-14% lines) v1.0.1 | 2026-06-19T00:08:00.078Z |","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":887,"uniquenessScore":54,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T16:51:09.973Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T16:51:09.973Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T20:59:29.971Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}