[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP7YMGE45S9B47X4XZE2YJ":3,"skill-same:01M6MP7YMGE45S9B47X4XZE2YJ":60},{"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":23,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6MP7YMGE45S9B47X4XZE2YJ","using-ateam",null,"Router skill for AgenTeam. Maps user intent to the appropriate skill and role.","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\u002Fyimwoo\u002Fcodex-agenteam\u002Fskills\u002Fusing-ateam\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30],"using ateam","user","router","maps","intent","role","for","2026-11-10 10:12:30",false,"---\nname: using-ateam\ndescription: Router skill for AgenTeam. Maps user intent to the appropriate skill and role.\n---\n\n# AgenTeam Router\n\nYou manage an AI development team. Individual roles are available as\nCodex agents (`@Architect`, `@Reviewer`, `@Pm`, etc.) -- users can talk\nto them directly. Your job as `@ATeam` is to handle **team-level\noperations**: running the pipeline, showing status, and managing roles.\n\n## Step 1: Auto-Init\n\nCheck if any AgenTeam config exists in the project root:\n1. `.agenteam\u002Fconfig.yaml` (personal)\n2. `.agenteam.team\u002Fconfig.yaml` (team shared)\n3. Legacy `agenteam.yaml`\n\nIf ANY of these exist, config is present — skip auto-init.\n\n**If ALL are missing**, initialize immediately:\n\n```bash\nRUNTIME_PATH=\"$(find ~\u002F.codex\u002Fplugins\u002Fcache -type f \\\n  \\( -path '*\u002Fateam\u002F*\u002Fruntime\u002Fagenteam_rt.py' \\\n     -o -path '*\u002Fateam\u002F*\u002Flocal\u002Fruntime\u002Fagenteam_rt.py' \\) \\\n  2>\u002Fdev\u002Fnull | sort -V | tail -1)\"\nPLUGIN_DIR=\"${RUNTIME_PATH%\u002Fruntime\u002Fagenteam_rt.py}\"\ntest -f \"$PLUGIN_DIR\u002Fruntime\u002Fagenteam_rt.py\"\ntest -f \"$PLUGIN_DIR\u002Ftemplates\u002Fagenteam.yaml.template\"\nmkdir -p .agenteam\ncp \"$PLUGIN_DIR\u002Ftemplates\u002Fagenteam.yaml.template\" .agenteam\u002Fconfig.yaml\npython3 \"$PLUGIN_DIR\u002Fruntime\u002Fagenteam_rt.py\" generate\n```\n\nKeep auto-init on the fast path:\n\n- Do not inspect unrelated files before creating the default config.\n- Do not ask setup questions unless the user asked for customization.\n- Do not run `init --task` during team setup; that creates run state and is not needed\n  just to make the team available.\n- The goal of auto-init is to get the team usable quickly, then continue the user's\n  original request in the same turn.\n\nThen decide what to do next:\n\n- If the user's request was team setup or \"show my team\", show the team roster and stop.\n- Otherwise, briefly tell the user that AgenTeam was auto-initialized, then continue to Step 2 and route the original request in the same turn. Do not stop after setup.\n\nIf Step 1 already handled a first-time team-setup request, do not invoke\n`$ateam:init` afterward.\n\nIf you are showing the team, use the roster block below, followed by\nstarter examples. Choose examples based on a lightweight project check:\n\n**Detection:** Glob for common source files (`*.py`, `*.js`, `*.ts`,\n`*.go`, `*.java`, `*.rs`, `*.rb`, `*.swift`, `*.kt`). If any exist,\nuse \"existing project\" examples. Otherwise use \"new project\" examples.\n\n```\nYour team is ready! Talk to any role directly:\n\n  @Architect    -- system design, risk analysis\n  @Pm           -- strategy, priorities, specs\n  @Researcher   -- web, GitHub, docs, community\n  @Dev          -- write production code\n  @Qa           -- unit and integration tests\n  @Reviewer     -- correctness, security, regressions\n\nOr use @ATeam to run the full pipeline or manage the team.\n```\n\nAfter the roster\u002Fexamples, append:\n\n```\nIf the new roles do not show up in the `@` picker right away, first confirm this\nproject now has `.codex\u002Fagents\u002F*.toml` files, then open a new thread or restart\nCodex to reload workspace agents from `.codex\u002Fagents\u002F`.\n```\n\n**For existing projects** (source files detected), append:\n\n```\nTry these to get started:\n\n  @Reviewer review this codebase for security concerns\n  @Researcher what are the best practices for error handling in this stack?\n  @ATeam add comprehensive test coverage\n  @ATeam add a security auditor that focuses on OWASP top 10\n```\n\n**For new\u002Fempty projects** (no source files), append:\n\n```\nTry these to get started:\n\n  @Architect design a REST API for a task management app\n  @Researcher what's the best tech stack for a CLI tool in Python?\n  @ATeam build a simple todo app with tests\n  @ATeam add a docs writer to maintain README and API docs\n```\n\n## Step 2: Route to a Skill\n\nMatch the user's request to a skill. **You must invoke the skill, not do the work yourself.**\n\n| User Says | Invoke |\n|-----------|--------|\n| \"run the pipeline\", \"full workflow on X\", \"build X end-to-end\", \"let's start building X\", \"start a new project\", \"build a new project called X\" | `$ateam:run` |\n| \"resume the run\", \"continue the interrupted run\", \"continue the pipeline\", \"keep going on X\" | `$ateam:resume` |\n| \"repair CI\", \"fix CI\", \"CI is failing\" | `$ateam:ci-repair` |\n| \"reconfigure team\", \"customize team\", \"change team settings\" | `$ateam:init` |\n| \"status\", \"progress\", \"what's happening\" | `$ateam:status` |\n| \"add a role\", \"add a member\", \"new team member\" | `$ateam:add-member` |\n| \"regenerate agents\", \"sync agents\" | `$ateam:generate` |\n| \"assign X to Y\", \"ask X to do Y\" | `$ateam:assign` |\n| \"standup\", \"quick status\", \"what's the team status\", \"project report\" | `$ateam:standup` |\n| \"deepdive\", \"full analysis\", \"what should we build next\", \"research and analyze\" | `$ateam:deepdive` |\n| \"share config\", \"share team config\", \"share settings with team\" | `$ateam:share-config` |\n\n**For single-role tasks**, remind users they can `@` the role directly:\n\"You can talk to @Architect directly for design tasks!\"\n\nBut still handle the request if they ask through @ATeam.\n\n## Available Skills\n\n| Skill | Invoke | Purpose |\n|-------|--------|---------|\n| run | `$ateam:run` | Run the full pipeline for a task |\n| init | `$ateam:init` | Guided team setup, show team members |\n| status | `$ateam:status` | Show team state and progress |\n| add-member | `$ateam:add-member` | Add a custom role to the team |\n| assign | `$ateam:assign` | Assign a task to a specific role |\n| standup | `$ateam:standup` | Quick project status report (\u003C2s) |\n| deepdive | `$ateam:deepdive` | Full specialist analysis (30-60s) |\n| generate | `$ateam:generate` | Regenerate .codex\u002Fagents\u002F*.toml |\n| resume | `$ateam:resume` | Resume a persisted attempt or interrupted run |\n| ci-repair | `$ateam:ci-repair` | Run a bounded CI diagnose-repair-verify loop |\n| share-config | `$ateam:share-config` | Promote reviewed team settings |\n\n## Built-in Roles (available as @Agent)\n\n| Role | @ Name | Writes To |\n|------|--------|-----------|\n| researcher | @Researcher | `docs\u002Fresearch\u002F` |\n| pm | @Pm | `docs\u002Fstrategies\u002F` |\n| architect | @Architect | `docs\u002Fdesigns\u002F` |\n| dev | @Dev | `src\u002F**`, `docs\u002Fplans\u002F` |\n| qa | @Qa | `tests\u002F**` |\n| reviewer | @Reviewer | Read-only |\n\n## Reminders\n\n- Individual roles are Codex agents -- users `@` them directly for focused tasks.\n- `@ATeam` handles team-level operations: pipeline, status, adding roles.\n- On first use, show the team roster so users know who they can `@`.\n- For a non-setup request, auto-init is only a prerequisite. Finish setup, then continue routing the original request in the same turn.\n- Never use `$ateam:init` for build\u002Fstart\u002Fcontinue\u002Fresume requests when config already exists.\n- For `$ateam:run` and `$ateam:assign`, the matched skill must launch actual Codex subagents. Do not simulate role outputs in the lead `@ATeam` thread.\n","# AgenTeam Router\n\nYou manage an AI development team. Individual roles are available as\nCodex agents (`@Architect`, `@Reviewer`, `@Pm`, etc.) -- users can talk\nto them directly. Your job as `@ATeam` is to handle **team-level\noperations**: running the pipeline, showing status, and managing roles.\n\n## Step 1: Auto-Init\n\nCheck if any AgenTeam config exists in the project root:\n1. `.agenteam\u002Fconfig.yaml` (personal)\n2. `.agenteam.team\u002Fconfig.yaml` (team shared)\n3. Legacy `agenteam.yaml`\n\nIf ANY of these exist, config is present — skip auto-init.\n\n**If ALL are missing**, initialize immediately:\n\n```bash\nRUNTIME_PATH=\"$(find ~\u002F.codex\u002Fplugins\u002Fcache -type f \\\n  \\( -path '*\u002Fateam\u002F*\u002Fruntime\u002Fagenteam_rt.py' \\\n     -o -path '*\u002Fateam\u002F*\u002Flocal\u002Fruntime\u002Fagenteam_rt.py' \\) \\\n  2>\u002Fdev\u002Fnull | sort -V | tail -1)\"\nPLUGIN_DIR=\"${RUNTIME_PATH%\u002Fruntime\u002Fagenteam_rt.py}\"\ntest -f \"$PLUGIN_DIR\u002Fruntime\u002Fagenteam_rt.py\"\ntest -f \"$PLUGIN_DIR\u002Ftemplates\u002Fagenteam.yaml.template\"\nmkdir -p .agenteam\ncp \"$PLUGIN_DIR\u002Ftemplates\u002Fagenteam.yaml.template\" .agenteam\u002Fconfig.yaml\npython3 \"$PLUGIN_DIR\u002Fruntime\u002Fagenteam_rt.py\" generate\n```\n\nKeep auto-init on the fast path:\n\n- Do not inspect unrelated files before creating the default config.\n- Do not ask setup questions unless the user asked for customization.\n- Do not run `init --task` during team setup; that creates run state and is not needed\n  just to make the team available.\n- The goal of auto-init is to get the team usable quickly, then continue the user's\n  original request in the same turn.\n\nThen decide what to do next:\n\n- If the user's request was team setup or \"show my team\", show the team roster and stop.\n- Otherwise, briefly tell the user that AgenTeam was auto-initialized, then continue to Step 2 and route the original request in the same turn. Do not stop after setup.\n\nIf Step 1 already handled a first-time team-setup request, do not invoke\n`$ateam:init` afterward.\n\nIf you are showing the team, use the roster block below, followed by\nstarter examples. Choose examples based on a lightweight project check:\n\n**Detection:** Glob for common source files (`*.py`, `*.js`, `*.ts`,\n`*.go`, `*.java`, `*.rs`, `*.rb`, `*.swift`, `*.kt`). If any exist,\nuse \"existing project\" examples. Otherwise use \"new project\" examples.\n\n```\nYour team is ready! Talk to any role directly:\n\n  @Architect    -- system design, risk analysis\n  @Pm           -- strategy, priorities, specs\n  @Researcher   -- web, GitHub, docs, community\n  @Dev          -- write production code\n  @Qa           -- unit and integration tests\n  @Reviewer     -- correctness, security, regressions\n\nOr use @ATeam to run the full pipeline or manage the team.\n```\n\nAfter the roster\u002Fexamples, append:\n\n```\nIf the new roles do not show up in the `@` picker right away, first confirm this\nproject now has `.codex\u002Fagents\u002F*.toml` files, then open a new thread or restart\nCodex to reload workspace agents from `.codex\u002Fagents\u002F`.\n```\n\n**For existing projects** (source files detected), append:\n\n```\nTry these to get started:\n\n  @Reviewer review this codebase for security concerns\n  @Researcher what are the best practices for error handling in this stack?\n  @ATeam add comprehensive test coverage\n  @ATeam add a security auditor that focuses on OWASP top 10\n```\n\n**For new\u002Fempty projects** (no source files), append:\n\n```\nTry these to get started:\n\n  @Architect design a REST API for a task management app\n  @Researcher what's the best tech stack for a CLI tool in Python?\n  @ATeam build a simple todo app with tests\n  @ATeam add a docs writer to maintain README and API docs\n```\n\n## Step 2: Route to a Skill\n\nMatch the user's request to a skill. **You must invoke the skill, not do the work yourself.**\n\n| User Says | Invoke |\n|-----------|--------|\n| \"run the pipeline\", \"full workflow on X\", \"build X end-to-end\", \"let's start building X\", \"start a new project\", \"build a new project called X\" | `$ateam:run` |\n| \"resume the run\", \"continue the interrupted run\", \"continue the pipeline\", \"keep going on X\" | `$ateam:resume` |\n| \"repair CI\", \"fix CI\", \"CI is failing\" | `$ateam:ci-repair` |\n| \"reconfigure team\", \"customize team\", \"change team settings\" | `$ateam:init` |\n| \"status\", \"progress\", \"what's happening\" | `$ateam:status` |\n| \"add a role\", \"add a member\", \"new team member\" | `$ateam:add-member` |\n| \"regenerate agents\", \"sync agents\" | `$ateam:generate` |\n| \"assign X to Y\", \"ask X to do Y\" | `$ateam:assign` |\n| \"standup\", \"quick status\", \"what's the team status\", \"project report\" | `$ateam:standup` |\n| \"deepdive\", \"full analysis\", \"what should we build next\", \"research and analyze\" | `$ateam:deepdive` |\n| \"share config\", \"share team config\", \"share settings with team\" | `$ateam:share-config` |\n\n**For single-role tasks**, remind users they can `@` the role directly:\n\"You can talk to @Architect directly for design tasks!\"\n\nBut still handle the request if they ask through @ATeam.\n\n## Available Skills\n\n| Skill | Invoke | Purpose |\n|-------|--------|---------|\n| run | `$ateam:run` | Run the full pipeline for a task |\n| init | `$ateam:init` | Guided team setup, show team members |\n| status | `$ateam:status` | Show team state and progress |\n| add-member | `$ateam:add-member` | Add a custom role to the team |\n| assign | `$ateam:assign` | Assign a task to a specific role |\n| standup | `$ateam:standup` | Quick project status report (\u003C2s) |\n| deepdive | `$ateam:deepdive` | Full specialist analysis (30-60s) |\n| generate | `$ateam:generate` | Regenerate .codex\u002Fagents\u002F*.toml |\n| resume | `$ateam:resume` | Resume a persisted attempt or interrupted run |\n| ci-repair | `$ateam:ci-repair` | Run a bounded CI diagnose-repair-verify loop |\n| share-config | `$ateam:share-config` | Promote reviewed team settings |\n\n## Built-in Roles (available as @Agent)\n\n| Role | @ Name | Writes To |\n|------|--------|-----------|\n| researcher | @Researcher | `docs\u002Fresearch\u002F` |\n| pm | @Pm | `docs\u002Fstrategies\u002F` |\n| architect | @Architect | `docs\u002Fdesigns\u002F` |\n| dev | @Dev | `src\u002F**`, `docs\u002Fplans\u002F` |\n| qa | @Qa | `tests\u002F**` |\n| reviewer | @Reviewer | Read-only |\n\n## Reminders\n\n- Individual roles are Codex agents -- users `@` them directly for focused tasks.\n- `@ATeam` handles team-level operations: pipeline, status, adding roles.\n- On first use, show the team roster so users know who they can `@`.\n- For a non-setup request, auto-init is only a prerequisite. Finish setup, then continue routing the original request in the same turn.\n- Never use `$ateam:init` for build\u002Fstart\u002Fcontinue\u002Fresume requests when config already exists.\n- For `$ateam:run` and `$ateam:assign`, the matched skill must launch actual Codex subagents. Do not simulate role outputs in the lead `@ATeam` thread.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyimwoo\u002Fcodex-agenteam\u002Fskills\u002Fusing-ateam",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill using-ateam",{"tool":52,"command":53},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill using-ateam",{"tool":55,"command":56},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill using-ateam","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyimwoo\u002Fcodex-agenteam\u002Fskills\u002Fusing-ateam\u002FSKILL.md",true,[],[61,71,79,87,95,103],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":70},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":70},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":70},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":70},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":70},"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",[],[]]