[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JTANE4XT8JRNHJ7TFHD2B1":3,"skill-same:01M6JTANE4XT8JRNHJ7TFHD2B1":84},{"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":26,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6JTANE4XT8JRNHJ7TFHD2B1","run-work",null,"Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as \u002Fagiflow:run-work \u003Cwork-unit>. Uses get_work_unit, list_tasks, update_task, get_work_unit_progress.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FAgiFlow\u002Fai-plugin\u002Fskills\u002Frun-work\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"run","run work","work","get","deliver","track","sequence","unit","complete","progress","as","end","feature","MCP","dependency","session","list","api","execution","update","tasks","commit","2026-11-10 10:12:30",false,"---\nname: run-work\ndescription: \"Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as \u002Fagiflow:run-work \u003Cwork-unit>. Uses get_work_unit, list_tasks, update_task, get_work_unit_progress.\"\ntags:\n  - agiflow\n  - mcp\n  - execution\n  - work-unit\nmetadata:\n  mirrors: backend\u002Fapis\u002Fagiflow-api ...\u002Fprompts\u002Fwork.md\n---\n\n> Invoked as `\u002Fagiflow:run-work`. In hosts without slash-prompts, this skill is triggered by matching intent and drives AgiFlow via its MCP tools.\n\n**Usage**:\n\n- `\u002Fagiflow:run-work \u003Cwork-unit-slug-or-id>` - Execute specific work unit\n- `\u002Fagiflow:run-work` - List and select from available work units\n\n**Examples**:\n\n- `\u002Fagiflow:run-work DXX-WU-1` (using slug)\n- `\u002Fagiflow:run-work 01K8FABMNEJG1XTA9JGHSNFV40` (using ID)\n- `\u002Fagiflow:run-work` (interactive selection)\n\n---\n\n**Guardrails**\n\n- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.\n- Keep changes tightly scoped to the requested outcome within the work unit scope.\n- A work unit represents a cohesive feature\u002Fepic that can be completed in one Claude Code session.\n\nIf a work unit slug\u002Fid is provided, load it with `get_work_unit`; otherwise list available work units with `list_work_units` for selection.\n\n---\n\n## AgiFlow Project Management Guidelines\n\nFollow the shared AgiFlow project-management guidelines in [`references\u002Fagiflow-agents.md`](..\u002F..\u002Freferences\u002Fagiflow-agents.md) — agent assignment, the task status workflow and transitions, work-unit best practices, and the tags strategy apply to this workflow.\n\n\n---\n\n**Task Status Workflow (per task)**\nEach task moves individually through: `Todo → In Progress → Testing → Review`\nThe work unit stays `in_progress` until all tasks reach `Review` or `Done`.\nIf any task hits `Blocked`, consider setting the work unit to `blocked` too.\n\n**IMPORTANT: Planning Status Guard**\nThis skill ONLY executes tasks in \"Todo\" or later status. Tasks in \"Planning\" have NOT been groomed and are NOT ready for execution. Use `backlog-grooming` to promote Planning tasks to Todo first.\n\n**Steps**\nTrack these steps as TODOs and complete them one by one.\n\n## 1. Work Unit Selection & Loading\n\n**If work unit slug\u002Fid NOT provided:**\n\n1. Use `list_work_units` MCP tool to show available work units:\n   - Filter by `status: \"in_progress\"` for active work, or work units with tasks in \"Todo\"\n   - Do NOT pick up work units where all tasks are still in \"Planning\" status\n   - Display: slug, title, type, priority, task count, status\n2. Ask user to select which work unit to work on.\n3. Once user selects, proceed with the selected work unit slug\u002Fid.\n\n**If work unit slug\u002Fid IS provided:** 4. Use `get_work_unit` MCP tool with the provided slug\u002Fid to retrieve:\n\n- Work unit: title, description, goals, type, priority, status, dates, devInfo\n- Tasks: All tasks associated with this work unit (already included in response)\n- Note: `get_work_unit` returns tasks automatically - no separate `list_tasks` call needed\n\n5. Review the work unit and all its tasks to understand:\n   - Complete feature scope and deliverables\n   - Task dependencies and execution order\n   - Acceptance criteria across all tasks\n\n**5b. PLANNING STATUS GUARD (MANDATORY):**\n\n- Check all tasks in the work unit\n- If ANY task has status \"Planning\": **REFUSE to execute**\n- Report: \"Cannot execute: N task(s) are still in Planning status. Use **backlog-grooming** to promote them to Todo first.\"\n- List the Planning tasks by title\n- **STOP execution** — do not proceed\n\n## 2. Start Work Unit Execution\n\n6. If work unit status is \"planning\":\n   - First verify ALL tasks are in \"Todo\" or later status (not \"Planning\")\n   - If verified, use `update_work_unit` MCP tool to set status to \"in_progress\"\n   - If any tasks are in \"Planning\", REFUSE and suggest `backlog-grooming`\n7. Create a TODO list of all tasks in execution order (use TodoWrite tool).\n8. Document execution plan in work unit via `update_work_unit` devInfo:\n   ```typescript\n   devInfo: {\n     executionPlan: \"Backend API → Frontend UI → Tests → Documentation\",\n     sessionId: \"\u003Ccurrent-session-id>\",\n     startedAt: \"\u003Ctimestamp>\"\n   }\n   ```\n\n## 3. Execute Tasks Sequentially\n\n9. For each task in the work unit (in dependency order from the tasks array):\n   - Review task details: title, description, acceptance criteria, assignee\n   - Use `update_task` MCP tool to set status to \"In Progress\"\n   - **BEFORE editing any code**: Use `architect` MCP `get_file_design_pattern` (MANDATORY)\n   - Implement the task following acceptance criteria\n   - **AFTER editing code**: Use `architect` MCP `review_code_change` (MANDATORY)\n   - Update task `devInfo` with implementation notes:\n     ```typescript\n     devInfo: {\n       filesChanged: [\"path\u002Fto\u002Ffile.ts:42\"],\n       testResults: { passed: true, coverage: \"85%\" },\n       notes: \"Implementation notes here\"\n     }\n     ```\n   - Mark acceptance criteria as checked via `update_task`\n\n   **Testing phase for each task:**\n   - Use `update_task` to move status to \"Testing\"\n   - Run unit tests, integration tests, type check and lint for affected code\n   - **If tests PASS**: proceed to move task to \"Review\"\n   - **If tests FAIL**:\n     - Increment `retryCount` in devInfo\n     - If `retryCount >= maxRetries` (default: 2): move task to \"Blocked\", set work unit to \"blocked\", stop\n     - If `retryCount \u003C maxRetries`: move task back to \"Todo\", document failure, continue to next task or stop session\n   - Use `update_task` to set status to \"Review\" when tests pass\n\n   - Update your TODO list (mark task as completed)\n\n10. Between tasks:\n    - Commit changes with meaningful commit messages\n    - Run tests to ensure no regressions\n    - Update work unit progress in devInfo\n\n## 4. Work Unit Progress Tracking\n\n11. The work unit tasks array automatically updates as tasks are completed.\n    - Use `get_work_unit` to check current state and task statuses\n    - Track: How many tasks in Review or Done vs. total?\n    - Monitor: Are we on track for target date?\n    - Work unit stays `in_progress` until all tasks reach `Review` or `Done`\n\n12. Update work unit `devInfo` as you progress via `update_work_unit`:\n    ```typescript\n    devInfo: {\n      executionPlan: \"...\",\n      sessionId: \"\u003Csession-id>\",\n      startedAt: \"\u003Ctimestamp>\",\n      progress: {\n        completedTasks: 3,\n        totalTasks: 8,\n        lastTaskCompleted: \"Implement cart API\",\n        currentTask: \"Add cart UI component\"\n      },\n      testResults: {\n        unitTests: \"passing\",\n        integrationTests: \"passing\",\n        coverage: \"85%\"\n      },\n      blockers: [] \u002F\u002F or list any blockers encountered\n    }\n    ```\n\n## 5. Work Unit Completion\n\n13. When ALL tasks in work unit are in \"Review\" or \"Done\":\n    - Verify all tasks have status \"Review\" or \"Done\"\n    - Verify all acceptance criteria across all tasks are met\n    - Run full test suite for the feature\n    - Review all files changed (use git diff)\n\n14. Draft a PR description for the work unit (DO NOT create the PR yet - just draft the text):\n    - Title format: `[WORK-UNIT-SLUG] Work unit title` (e.g., `[DXX-WU-1] Shopping cart feature`)\n    - Body should include:\n      - Work unit reference and summary\n      - List of tasks completed\n      - Summary of all changes across tasks\n      - Files modified (use `file.ts:42` format)\n      - Test results\n\n15. Use `update_work_unit` to set status to \"completed\" and save draft PR text and commit message:\n\n    ```typescript\n    {\n      status: \"completed\",\n      completedAt: new Date(),\n      devInfo: {\n        ...existing,\n        draftCommitMessage: \"feat(cart): implement shopping cart feature\\n\\n- Add cart API endpoints\\n- Add cart UI components\\n- Add integration tests\\n\\nCloses: DXX-WU-1\",\n        draftPr: {\n          title: \"[DXX-WU-1] Shopping cart feature\",\n          body: \"## Summary\\n\\nImplemented shopping cart feature.\\n\\n## Tasks Completed\\n\\n- [DXX-1] Add cart API\\n- [DXX-2] Add cart UI\\n- [DXX-3] Add cart tests\\n\\n## Changes\\n\\n- Added cart endpoints\\n- Added cart components\\n- Added integration tests\\n\\n## Files Modified\\n\\n- src\u002Fapi\u002Fcart.ts:42\\n- src\u002Fcomponents\u002FCart.tsx:15\\n- tests\u002Fcart.test.ts:1\\n\\n## Test Results\\n\\nAll tests passing. Coverage: 85%\"\n        },\n        finalNotes: \"All tasks completed. Files changed: [...]. Tests passing.\",\n        completedBy: \"\u003Cmember-id>\",\n        totalDuration: \"3.5 hours\"\n      }\n    }\n    ```\n\n    **Note on draftCommitMessage**: Write a conventional commit message that will be used for the final git commit. Format: `type(scope): description` with optional body listing changes.\n\n16. Create final summary comment documenting:\n    - Work unit scope and goals achieved\n    - All files created\u002Fmodified (use `file.ts:42` format)\n    - Test coverage and results\n    - Any follow-up work needed\n    - Performance or architectural notes\n\n## 6. Handle Blockers or Scope Changes\n\n17. If blocked on a task:\n    - Use `update_task` to set task status to \"Blocked\"\n    - Use `update_work_unit` to set status to \"blocked\"\n    - Document blocker in work unit devInfo\n    - Use `create_task_comment` on blocked task with details explaining what human intervention is needed\n    - Consider creating follow-up tasks for blockers\n\n18. If scope changes during execution:\n    - Use `create_task` to add new tasks to work unit\n    - Update work unit description\u002Fgoals if needed\n    - Communicate scope change in work unit comments\n\n**Common Mistakes to Avoid**\n\n- ❌ Starting without reviewing all tasks in work unit (lack of context)\n- ❌ Working on tasks in wrong order (missing dependencies)\n- ❌ Skipping vibe-lint MCP validation (MANDATORY for every file)\n- ❌ Not tracking work unit-level progress in devInfo\n- ❌ Completing tasks in isolation without considering work unit goals\n- ❌ Not running integration tests between tasks\n- ❌ Moving task to \"Review\" without first going through \"Testing\"\n- ❌ Marking work unit complete when tasks are still in \"In Progress\" or \"Testing\"\n- ❌ Not documenting scope changes or blockers\n- ❌ Forgetting to commit between tasks (losing incremental progress)\n- ❌ Not updating work unit status when blocked\n- ❌ Setting work unit to \"completed\" before all tasks reach \"Review\" or \"Done\"\n- ❌ Executing tasks that are still in \"Planning\" status (must be promoted to \"Todo\" via `backlog-grooming` first)\n","> Invoked as `\u002Fagiflow:run-work`. In hosts without slash-prompts, this skill is triggered by matching intent and drives AgiFlow via its MCP tools.\n\n**Usage**:\n\n- `\u002Fagiflow:run-work \u003Cwork-unit-slug-or-id>` - Execute specific work unit\n- `\u002Fagiflow:run-work` - List and select from available work units\n\n**Examples**:\n\n- `\u002Fagiflow:run-work DXX-WU-1` (using slug)\n- `\u002Fagiflow:run-work 01K8FABMNEJG1XTA9JGHSNFV40` (using ID)\n- `\u002Fagiflow:run-work` (interactive selection)\n\n---\n\n**Guardrails**\n\n- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.\n- Keep changes tightly scoped to the requested outcome within the work unit scope.\n- A work unit represents a cohesive feature\u002Fepic that can be completed in one Claude Code session.\n\nIf a work unit slug\u002Fid is provided, load it with `get_work_unit`; otherwise list available work units with `list_work_units` for selection.\n\n---\n\n## AgiFlow Project Management Guidelines\n\nFollow the shared AgiFlow project-management guidelines in [`references\u002Fagiflow-agents.md`](..\u002F..\u002Freferences\u002Fagiflow-agents.md) — agent assignment, the task status workflow and transitions, work-unit best practices, and the tags strategy apply to this workflow.\n\n\n---\n\n**Task Status Workflow (per task)**\nEach task moves individually through: `Todo → In Progress → Testing → Review`\nThe work unit stays `in_progress` until all tasks reach `Review` or `Done`.\nIf any task hits `Blocked`, consider setting the work unit to `blocked` too.\n\n**IMPORTANT: Planning Status Guard**\nThis skill ONLY executes tasks in \"Todo\" or later status. Tasks in \"Planning\" have NOT been groomed and are NOT ready for execution. Use `backlog-grooming` to promote Planning tasks to Todo first.\n\n**Steps**\nTrack these steps as TODOs and complete them one by one.\n\n## 1. Work Unit Selection & Loading\n\n**If work unit slug\u002Fid NOT provided:**\n\n1. Use `list_work_units` MCP tool to show available work units:\n   - Filter by `status: \"in_progress\"` for active work, or work units with tasks in \"Todo\"\n   - Do NOT pick up work units where all tasks are still in \"Planning\" status\n   - Display: slug, title, type, priority, task count, status\n2. Ask user to select which work unit to work on.\n3. Once user selects, proceed with the selected work unit slug\u002Fid.\n\n**If work unit slug\u002Fid IS provided:** 4. Use `get_work_unit` MCP tool with the provided slug\u002Fid to retrieve:\n\n- Work unit: title, description, goals, type, priority, status, dates, devInfo\n- Tasks: All tasks associated with this work unit (already included in response)\n- Note: `get_work_unit` returns tasks automatically - no separate `list_tasks` call needed\n\n5. Review the work unit and all its tasks to understand:\n   - Complete feature scope and deliverables\n   - Task dependencies and execution order\n   - Acceptance criteria across all tasks\n\n**5b. PLANNING STATUS GUARD (MANDATORY):**\n\n- Check all tasks in the work unit\n- If ANY task has status \"Planning\": **REFUSE to execute**\n- Report: \"Cannot execute: N task(s) are still in Planning status. Use **backlog-grooming** to promote them to Todo first.\"\n- List the Planning tasks by title\n- **STOP execution** — do not proceed\n\n## 2. Start Work Unit Execution\n\n6. If work unit status is \"planning\":\n   - First verify ALL tasks are in \"Todo\" or later status (not \"Planning\")\n   - If verified, use `update_work_unit` MCP tool to set status to \"in_progress\"\n   - If any tasks are in \"Planning\", REFUSE and suggest `backlog-grooming`\n7. Create a TODO list of all tasks in execution order (use TodoWrite tool).\n8. Document execution plan in work unit via `update_work_unit` devInfo:\n   ```typescript\n   devInfo: {\n     executionPlan: \"Backend API → Frontend UI → Tests → Documentation\",\n     sessionId: \"\u003Ccurrent-session-id>\",\n     startedAt: \"\u003Ctimestamp>\"\n   }\n   ```\n\n## 3. Execute Tasks Sequentially\n\n9. For each task in the work unit (in dependency order from the tasks array):\n   - Review task details: title, description, acceptance criteria, assignee\n   - Use `update_task` MCP tool to set status to \"In Progress\"\n   - **BEFORE editing any code**: Use `architect` MCP `get_file_design_pattern` (MANDATORY)\n   - Implement the task following acceptance criteria\n   - **AFTER editing code**: Use `architect` MCP `review_code_change` (MANDATORY)\n   - Update task `devInfo` with implementation notes:\n     ```typescript\n     devInfo: {\n       filesChanged: [\"path\u002Fto\u002Ffile.ts:42\"],\n       testResults: { passed: true, coverage: \"85%\" },\n       notes: \"Implementation notes here\"\n     }\n     ```\n   - Mark acceptance criteria as checked via `update_task`\n\n   **Testing phase for each task:**\n   - Use `update_task` to move status to \"Testing\"\n   - Run unit tests, integration tests, type check and lint for affected code\n   - **If tests PASS**: proceed to move task to \"Review\"\n   - **If tests FAIL**:\n     - Increment `retryCount` in devInfo\n     - If `retryCount >= maxRetries` (default: 2): move task to \"Blocked\", set work unit to \"blocked\", stop\n     - If `retryCount \u003C maxRetries`: move task back to \"Todo\", document failure, continue to next task or stop session\n   - Use `update_task` to set status to \"Review\" when tests pass\n\n   - Update your TODO list (mark task as completed)\n\n10. Between tasks:\n    - Commit changes with meaningful commit messages\n    - Run tests to ensure no regressions\n    - Update work unit progress in devInfo\n\n## 4. Work Unit Progress Tracking\n\n11. The work unit tasks array automatically updates as tasks are completed.\n    - Use `get_work_unit` to check current state and task statuses\n    - Track: How many tasks in Review or Done vs. total?\n    - Monitor: Are we on track for target date?\n    - Work unit stays `in_progress` until all tasks reach `Review` or `Done`\n\n12. Update work unit `devInfo` as you progress via `update_work_unit`:\n    ```typescript\n    devInfo: {\n      executionPlan: \"...\",\n      sessionId: \"\u003Csession-id>\",\n      startedAt: \"\u003Ctimestamp>\",\n      progress: {\n        completedTasks: 3,\n        totalTasks: 8,\n        lastTaskCompleted: \"Implement cart API\",\n        currentTask: \"Add cart UI component\"\n      },\n      testResults: {\n        unitTests: \"passing\",\n        integrationTests: \"passing\",\n        coverage: \"85%\"\n      },\n      blockers: [] \u002F\u002F or list any blockers encountered\n    }\n    ```\n\n## 5. Work Unit Completion\n\n13. When ALL tasks in work unit are in \"Review\" or \"Done\":\n    - Verify all tasks have status \"Review\" or \"Done\"\n    - Verify all acceptance criteria across all tasks are met\n    - Run full test suite for the feature\n    - Review all files changed (use git diff)\n\n14. Draft a PR description for the work unit (DO NOT create the PR yet - just draft the text):\n    - Title format: `[WORK-UNIT-SLUG] Work unit title` (e.g., `[DXX-WU-1] Shopping cart feature`)\n    - Body should include:\n      - Work unit reference and summary\n      - List of tasks completed\n      - Summary of all changes across tasks\n      - Files modified (use `file.ts:42` format)\n      - Test results\n\n15. Use `update_work_unit` to set status to \"completed\" and save draft PR text and commit message:\n\n    ```typescript\n    {\n      status: \"completed\",\n      completedAt: new Date(),\n      devInfo: {\n        ...existing,\n        draftCommitMessage: \"feat(cart): implement shopping cart feature\\n\\n- Add cart API endpoints\\n- Add cart UI components\\n- Add integration tests\\n\\nCloses: DXX-WU-1\",\n        draftPr: {\n          title: \"[DXX-WU-1] Shopping cart feature\",\n          body: \"## Summary\\n\\nImplemented shopping cart feature.\\n\\n## Tasks Completed\\n\\n- [DXX-1] Add cart API\\n- [DXX-2] Add cart UI\\n- [DXX-3] Add cart tests\\n\\n## Changes\\n\\n- Added cart endpoints\\n- Added cart components\\n- Added integration tests\\n\\n## Files Modified\\n\\n- src\u002Fapi\u002Fcart.ts:42\\n- src\u002Fcomponents\u002FCart.tsx:15\\n- tests\u002Fcart.test.ts:1\\n\\n## Test Results\\n\\nAll tests passing. Coverage: 85%\"\n        },\n        finalNotes: \"All tasks completed. Files changed: [...]. Tests passing.\",\n        completedBy: \"\u003Cmember-id>\",\n        totalDuration: \"3.5 hours\"\n      }\n    }\n    ```\n\n    **Note on draftCommitMessage**: Write a conventional commit message that will be used for the final git commit. Format: `type(scope): description` with optional body listing changes.\n\n16. Create final summary comment documenting:\n    - Work unit scope and goals achieved\n    - All files created\u002Fmodified (use `file.ts:42` format)\n    - Test coverage and results\n    - Any follow-up work needed\n    - Performance or architectural notes\n\n## 6. Handle Blockers or Scope Changes\n\n17. If blocked on a task:\n    - Use `update_task` to set task status to \"Blocked\"\n    - Use `update_work_unit` to set status to \"blocked\"\n    - Document blocker in work unit devInfo\n    - Use `create_task_comment` on blocked task with details explaining what human intervention is needed\n    - Consider creating follow-up tasks for blockers\n\n18. If scope changes during execution:\n    - Use `create_task` to add new tasks to work unit\n    - Update work unit description\u002Fgoals if needed\n    - Communicate scope change in work unit comments\n\n**Common Mistakes to Avoid**\n\n- ❌ Starting without reviewing all tasks in work unit (lack of context)\n- ❌ Working on tasks in wrong order (missing dependencies)\n- ❌ Skipping vibe-lint MCP validation (MANDATORY for every file)\n- ❌ Not tracking work unit-level progress in devInfo\n- ❌ Completing tasks in isolation without considering work unit goals\n- ❌ Not running integration tests between tasks\n- ❌ Moving task to \"Review\" without first going through \"Testing\"\n- ❌ Marking work unit complete when tasks are still in \"In Progress\" or \"Testing\"\n- ❌ Not documenting scope changes or blockers\n- ❌ Forgetting to commit between tasks (losing incremental progress)\n- ❌ Not updating work unit status when blocked\n- ❌ Setting work unit to \"completed\" before all tasks reach \"Review\" or \"Done\"\n- ❌ Executing tasks that are still in \"Planning\" status (must be promoted to \"Todo\" via `backlog-grooming` first)\n",{"name":5,"tags":54,"metadata":58,"description":7},[55,56,45,57],"agiflow","mcp","work-unit",{"mirrors":59},"backend\u002Fapis\u002Fagiflow-api ...\u002Fprompts\u002Fwork.md","main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FAgiFlow\u002Fai-plugin\u002Fskills\u002Frun-work",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill run-work",{"tool":76,"command":77},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill run-work",{"tool":79,"command":80},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill run-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FAgiFlow\u002Fai-plugin\u002Fskills\u002Frun-work\u002FSKILL.md",true,[],[85,95,103,111,119,127],{"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":89,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":94},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":94},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":94},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":94},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":94},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]