[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M93PK71657W013F5TYF40G":3,"skill-same:01M6M93PK71657W013F5TYF40G":119},{"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":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6M93PK71657W013F5TYF40G","suede-agent-teams",null,"Suede AI Agent Teams Skills. Use when asked to \"split this work across agents\" or run coordinated shared changes in lanes with exclusive file ownership, collision checks, worktrees, rollback plans and evidence handoffs; also supports bounded contribution programs. NOT FOR: one bundled code DAG (suede-graph-flo-xr), diff review (suede-code), CI wiring (suede-ci-gate), or choosing one skill (suede-workflow-skills).","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\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"suede agent teams","teams","agent teams","evidence","when","wiring","bounded","changes","for","split","ownership","contribution","shared","across","worktrees","review","diff","use","work","rollback","ci","file","graph","code","run","workflow","dag","ai agent","2026-11-10 10:12:30",false,"---\nname: suede-agent-teams\ndescription: \"Suede AI Agent Teams Skills. Use when asked to \\\"split this work across agents\\\" or run coordinated shared changes in lanes with exclusive file ownership, collision checks, worktrees, rollback plans and evidence handoffs; also supports bounded contribution programs. NOT FOR: one bundled code DAG (suede-graph-flo-xr), diff review (suede-code), CI wiring (suede-ci-gate), or choosing one skill (suede-workflow-skills).\"\nmetadata:\n  display-name: \"Suede AI Agent Teams Skills\"\n---\n\n# Suede AI Agent Teams Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nRequires a host with agent delegation for parallel execution and repo\u002Ffile access; Git for worktrees and contribution ledgers. Without delegation, serialize the same lane plan and report the execution mode.\n\n## Model selection: Fable capped at 4 without asking\n\nSubagents inherit the session model unless the spawning call names one. Nothing in\nthis skill picks a model, so every agent it fans out lands on whatever the session\nhappens to be set to. That is how a run sized against one allocation gets billed to\nanother without anyone choosing it.\n\n**Up to 4 concurrent Fable subagents are allowed without an explicit Fable\ninstruction. Beyond that, Fable must be specified**: any roster past a scout, a\nbuilder, and a handoff writer passes 4, so this skill's fan-out does not run on Fable\nunless the user named Fable for this run. An inherited session model is not a\nspecification: \"the session was already on it\" is not the user asking. Absent an\nexplicit Fable instruction, do one of two things before launching: name a different\nmodel on the agent calls, or state plainly that the run will bill to the Fable\nallocation and get an answer. Silence is not consent to spend it.\n\n## Gate policy: advisory, not blocking\n\nEvery claim-verification step, check, quality gate, and ship verdict in this\nskill is a **recommendation to the user, not a control on the agent**. This\npolicy governs every gate, check, verdict, and \"do not ship \u002F publish \u002F\nproceed\" line elsewhere in this skill:\n\n- Run every check and report the results honestly. Verdicts (`ship`,\n  `ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are\n  advice attached to the work, not orders that change it.\n- Never block, delay, skip, rewrite, or refuse the action the user asked for\n  because a check failed or a gate said hold. Complete the requested action\n  as asked, and deliver the gate output alongside it as a clearly labeled\n  recommendation.\n- A failed gate changes what you report, never what you do.\n- Single exception: if a finding is extremely risky (data loss, security or\n  credential exposure, legal or rights violations, payment mistakes, or\n  irreversible public damage), pause, tell the user exactly what the risk is\n  and what the options are, and let them pick. Their choice is final.\n\n\nThe orchestrator assigns lanes, not conversations. Output is a delivery artifact, not a status update.\n\n## Team Contract\n\nBefore spawning or simulating lanes, define:\n\n- objective: user-visible outcome;\n- exact target: repo\u002Ffolder, branch, route, PR, live URL, API, simulator, or\n  release artifact;\n- constraints: WIP to preserve, files\u002Froutes not to touch, launch boundaries,\n  account boundaries, claims not approved, and secrets rules;\n- done signal: tests, build, screenshots, simulator, deploy readback, live\u002FAPI\n  readback, PR review, or handoff;\n- lane map: each lane, owner role, input, allowed files, output artifact, and\n  dependency order.\n\n## Team Ledger\n\nThe contract above, every lane status, and every gate result otherwise live only in\nthe orchestrator's context, and a multi-lane run routinely outlives a context window.\nPut them on disk. Default path: `.suede-team\u002F\u003Cslug>\u002Fledger.md` in the target repo,\nholding the resolved lane map, each lane's current state from the Status Vocabulary,\nand the evidence as it accumulates. Write it before the first builder opens a file and\nupdate it at every gate; the evidence handoff reads from it rather than from memory.\nIf the user keeps durable repo-local state somewhere else, use their path and say\nwhich one you used.\n\n## WIP Collision Detection\n\nBefore opening any parallel lanes:\n\n1. Run `git -C \u003Crepo> diff --name-only HEAD` and collect all dirty files.\n2. Run `git -C \u003Crepo> status --short` and collect all untracked new files.\n3. List every file each lane's scope would touch, based on the lane map.\n4. Flag a collision if the same file path appears in two or more lane scopes OR in the dirty file list plus any lane scope.\n\nCollision resolution rules:\n- Same file, independent changes: sequence the lanes; the second lane rebases on the first lane's commit before opening.\n- Same file, overlapping changes: merge the two lanes into one lane with one owner. Do not split responsibility for a single file across two concurrent builders.\n- Dirty file in a lane scope: the orchestrator decides. Either stash and restore, or make that lane the only lane allowed to touch the file.\n\nThe orchestrator writes the resolved lane map to the team ledger (`.suede-team\u002F\u003Cslug>\u002Fledger.md`, see Team Ledger) before any builder starts. No builder opens a file not in its assigned lane map.\n\n## Default Roster\n\nStart with Scout + Builder + Handoff Writer. Add roles only when a gate is needed: design changes add Design Reviewer, code risk adds Code Grader + Code Reviewer (both run suede-code, in `--grade-only` and `--findings-only` modes), public release adds Release Verifier.\n\n- **Scout:** finds repo, docs, current state, dirty files, live routes, and\n  likely blast radius.\n- **Planner:** turns requirements into verifiable tasks with acceptance\n  criteria and dependencies.\n- **Builder:** makes narrow code or content changes inside the existing system.\n- **Design reviewer:** checks rendered visual quality, responsive behavior,\n  accessibility, copy, and state coverage.\n- **Code grader:** assigns an A-F ship-risk grade across correctness, security,\n  data\u002Fstate, Suede truth, UX\u002Frelease behavior, tests, and deploy readiness.\n- **Code reviewer:** runs full-context review and turns findings into fix briefs.\n- **Visibility grader:** grades public pages, GitHub Pages sites, docs, and\n  launch surfaces for findability, first-screen clarity, CTA pull, proof, AI\n  readability, and design signal.\n- **Release verifier:** checks build, deploy, live\u002FAPI behavior, App Store\u002FiOS\n  truth, secrets, and published statements.\n- **Handoff writer:** produces a signed delivery record. If the handoff omits any required field (see Handoff Quality Checklist), the work is not done; it is held.\n\nFor high-risk work, keep builder and reviewer separate.\n\n## RFC Mode\n\nFor major architectural decisions, new feature designs, or changes with broad blast radius, run an RFC (Request for Comments) before spawning builders.\n\nAn RFC forces alignment on WHAT and WHY before committing to HOW.\n\nRFC status vocabulary: `draft | accepted | superseded | withdrawn`.\n\nBefore authoring one, read\n[`references\u002Fincident-and-rfc-templates.md`](references\u002Fincident-and-rfc-templates.md)\nand fill every section it lists: problem statement, proposed solution, alternatives\nconsidered, risks, success criteria, decision record.\n\nRequire an RFC for: shared interface changes, schema migrations, auth flow rewrites, payment path changes, public API contract changes, or any approach that's been discussed twice without resolution. No builder lane opens until RFC status is `accepted`.\n\nWhen to skip: clear, contained changes where the approach is obvious and the blast radius is narrow.\n\n## Feature Flag Strategy\n\nNot every change should ship as a hard deploy. Feature flags allow gradual rollout, A\u002FB testing, and instant rollback without a redeploy.\n\n**When to flag:**\n- New user-facing features in production traffic paths\n- Changes to auth, payment, or data migration paths\n- Any change that cannot be instantly rolled back by revert (e.g., a schema migration)\n- A\u002FB tests\n\nOnce a lane is flagged, read the lifecycle, the when-NOT-to-flag list, and the hygiene\nrules in\nthe Feature Flag Strategy section of [`references\u002Fscenario-templates.md`](references\u002Fscenario-templates.md)\nbefore the ramp starts. Every flag gets a removal date at creation; a stale flag is a\nP3 code review finding.\n\n## Rollback Decision Tree\n\nWhen something goes wrong after a deploy, the team needs a pre-agreed decision framework to avoid paralysis.\n\n```\nIs there active data loss or corruption? → ROLLBACK IMMEDIATELY. Don't investigate first.\nIs there a security exposure (PII, auth bypass, payment data)? → ROLLBACK IMMEDIATELY. Notify security.\nIs a primary user path broken (login, checkout, core workflow)? → ROLLBACK unless fix is \u003C15 minutes away.\nIs performance degraded but functional? → Hold and investigate. Set a 30-minute timer.\nIs it a cosmetic issue? → Hot-fix forward. No rollback.\n```\n\nAfter rollback:\n1. Write an immediate summary: what rolled back, what was affected, who was notified.\n2. Leave rollback notes in the PR and open a follow-up issue.\n3. Run a lightweight post-mortem (see below) before re-shipping.\n\n## Post-Mortem\n\nFor any production incident, failed release, or significant rollback, run a post-mortem. Keep it blameless: focus on systems, not individuals.\n\nSeverity: P0 (total outage) \u002F P1 (primary path broken) \u002F P2 (degraded) \u002F P3 (cosmetic).\n\nPost-mortems are required for P0 and P1 incidents. Optional but encouraged for P2. Skip for P3.\nWhen one is required, write it from\n[`references\u002Fincident-and-rfc-templates.md`](references\u002Fincident-and-rfc-templates.md)\nand fill every section: timeline, impact, root cause, contributing factors, what went\nwell, and action items with owners and due dates.\n\n## Phase Loop\n\nThe Phase Loop is the Continuous Team Loop run at minimal scale. Use it when a full 10-gate roster is overkill but you still need scout, plan, build, verify, and ship stages.\n\nFor high-risk changes, consult the Rollback Decision Tree before shipping. For gradual rollouts, use the Feature Flag Strategy. For shared interface changes, require RFC Mode before the plan stage opens.\n\n## Public Contribution Program\n\nWhen the objective is recurring work across owned or external public\nrepositories, read\n[`references\u002Fpublic-contribution-program.md`](references\u002Fpublic-contribution-program.md)\ncompletely before opening lanes. Use its deterministic ledger to score tasks,\nlease each repo\u002Fissue pair to one worker, and prevent duplicate work. Start in\n`local_only` authority with publication disabled. Keep external targets at a\nreviewed contribution packet unless the user separately approves a draft PR.\n\nThe outward artifact gate applies to branch names, commit messages, and PR\ncopy. Use conventional project language and omit voluntary tool-origin\nbranding or trailers. Never forge authorship or deny tool use; an upstream\ndisclosure requirement overrides neutral packaging and moves the lane to owner\nreview.\n\n## Model Tiering\n\nAllow up to three genuinely different fixes, each changing the diagnosis or strategy. Stop early when the same root cause repeats; escalate with the evidence instead of re-dispatching unchanged work.\n\nRead [the execution-loop protocol](references\u002Fexecution-loop.md) before assigning a model or dispatching a builder. It preserves model tiers, builder response handling and the gated continuous roster.\n\n## Inter-Lane Communication\n\nWhen a builder lane completes its output and a reviewer lane depends on it, the signal is explicit, not assumed.\n\nThe completing lane writes a Lane Ready notice:\n\n```\nLane: [name]\nStatus: output ready for review\nArtifact: [file path, URL, or PR link]\nReviewer: [lane name that receives this output]\nUnresolved: [any known issue the reviewer should know before starting]\n```\n\nThe reviewer lane does not start until it has received a Lane Ready notice from every upstream dependency in its lane map.\n\nThe orchestrator routes Lane Ready notices. In a sequential thread, the orchestrator posts the Lane Ready notice on behalf of each completing lane before invoking the next.\n\nLanes may not self-declare readiness if their output has not been verified against the acceptance criteria from the Team Contract.\n\n## Planning Quality Gate\n\nA plan is not ready until:\n\n- each task has one concern;\n- dependencies are ordered;\n- acceptance criteria are observable, not subjective;\n- required files or surfaces are named;\n- must-have requirements are covered;\n- tests, screenshots, builds, or API checks map to the risky behavior;\n- release and account boundaries are explicit.\n\nIf major uncertainty remains, run a short spike first and keep implementation\nout of scope until the spike reports back.\n\n## Review Convergence\n\nFor important merges, run at least two independent review lenses:\n\n- one asks whether the implementation works as intended;\n- one asks how it can fail in production, review, release, or public use.\n\nMerge the findings into:\n\n- consensus blockers;\n- plausible divergent risks;\n- accepted caveats;\n- fixes to execute now;\n- follow-ups that should not block.\n\nRepeat fix and review cycles until no blocker remains or the work is held.\n\n## Status Vocabulary\n\nValid states in order: `scoped` → `planned` → `executing` → `changed locally` → `verified locally` → `reviewed` → `committed` → `pushed` → `deployed` → `verified live` → `released`\n\nInterrupt states: `blocked` (needs external action) | `held` (needs named fix before continuing)\n\nDo not skip. `changed locally` is not `verified locally`. `deployed` is not `verified live`. Do not mark `released` until the done signal from the Team Contract passes.\n\n## Scenario Templates\n\nSix pre-built configurations exist for common high-risk deployments: (a) Auth Rewrite,\n(b) Payment Integration, (c) Public Launch Review, (d) Data Migration, (e) Performance\nAudit, (f) Recovery \u002F Incident Response. When the objective matches one, read\n[`references\u002Fscenario-templates.md`](references\u002Fscenario-templates.md) completely\nbefore opening lanes and adjust only the named target: each template carries its own\nroster, lane map, RFC and flag requirements, grader tolerances, and done signal.\n\n## Escalation Protocol\n\nStop the loop, surface the condition, and wait for human sign-off before continuing.\n\n| Condition | Threshold | Action |\n|---|---|---|\n| Repeated fix cycles | > 3 fix-rerun cycles on the same failing check | Stop. Write a diagnosis summary. Ask: is the acceptance criterion correct, or is the fix strategy wrong? |\n| Security finding of unknown severity | Any finding touching auth, session, PII, payment data, or access control that cannot be confidently classified as low risk | Stop. Do not attempt a fix. Surface the exact finding and uncertain blast radius. Human decides next step. |\n| Production incident with data exposure | Any indication of PII, payment data, or auth token exposure in production logs, error reports, or user reports | Stop all lanes. Trigger rollback decision tree. Notify human immediately. Do not investigate further before rollback. |\n| Cost spike | > 20 tool calls without a verified output, or estimated API\u002Finfra cost > $50 in a single loop | Stop. Summarize progress and remaining scope. Ask human to authorize continuation. |\n| Contradictory constraints | Two constraints in the Team Contract are mutually exclusive | Stop planning. Surface the conflict with a specific example. Do not proceed until human resolves. |\n\nNo agent may override an escalation threshold by re-scoping the task or declaring the condition resolved without human confirmation.\n\n## Red Flags: Stop\n\n- \"The lanes probably won't touch the same files\": probably is not a lane map. Run WIP collision detection first.\n- \"The approach is obvious, skip the RFC\": if it has been discussed twice without resolution, it is not obvious.\n- \"Mark it done, the code is written\": `changed locally` is not `verified locally`; the status vocabulary has no shortcuts.\n- \"Leave that caveat out so the handoff looks clean\": a handoff missing a field is status `held`, not done.\n- \"One more fix cycle will crack it\": past 3 cycles on the same failing check, stop and run the loop stall protocol.\n- \"The builder can review its own lane\": for high-risk work, builder and reviewer stay separate.\n\n## Handoff Quality Checklist\n\nA handoff is not complete until every field below is present and truthful. The handoff writer signs off by confirming each item.\n\nRequired fields:\n- [ ] Target: exact repo, branch, route, or URL (not \"the main app\")\n- [ ] Changed: every file path that was modified, created, or deleted (not \"various files\")\n- [ ] Commands: every bash command run, in order, with the actual output or exit code\n- [ ] Verification: observable evidence (screenshot URL, test output, curl response, build log), not \"it works\"\n- [ ] Status: one of the vocabulary states, not \"done\" unless the done signal from the Team Contract is satisfied\n- [ ] Next: the single most important unresolved step (not \"see above\")\n- [ ] Caveats: every known limitation, assumption, or deferred item; none omitted to make the handoff look cleaner\n\nIf any field is missing, the handoff writer must fill it before marking status `released` or `verified live`. A handoff with a missing field is status `held`.\n\n## Output Shape\n\nFor a team plan:\n\n```text\nObjective:\nTarget:\nConstraints:\nLane Map:\nDependency Order:\nDone Signal:\nShip Gate:\n```\n\nFor execution updates:\n\n```text\nLane:\nStatus:\nEvidence:\nNext:\nRisk:\n```\n\nFor final handoff:\n\n```text\nSimple explanation:\nUsual breakdown:\nTarget:\nChanged:\nVerification:\nCaveats:\nStatus:\nNext:\nCue Suede:\n```\n\n## Routing\n\n- The work is one repo's change and a bundled DAG can run it end to end →\n  **suede-graph-flo-xr**. Precedence: one repo, one change, research-through-release in a\n  single scripted run goes there; orchestration that is manual, ongoing, cross-repo,\n  or a public-contribution program stays here. A single lane inside a program here\n  that needs the full research-and-refute treatment can be handed to **suede-graph-flo-xr**\n  for that lane alone.\n- A recurring owned\u002Fpublic-repository contribution program needs issue leases,\n  isolated worktrees, review, and an authority-gated packet → read\n  `references\u002Fpublic-contribution-program.md` and keep this skill as controller\n- A code lane needs review or a ship grade → **suede-code** (full, `--findings-only`, or `--grade-only`)\n- The repo's merge gate is weak or missing → **suede-ci-gate**\n- A lane ships AI behavior → **suede-ai-eval** before that lane's quality gate closes\n- The public launch lane needs a page verdict → **suede-visibility-grader**, then **suede-launch-packaging**\n","# Suede AI Agent Teams Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nRequires a host with agent delegation for parallel execution and repo\u002Ffile access; Git for worktrees and contribution ledgers. Without delegation, serialize the same lane plan and report the execution mode.\n\n## Model selection: Fable capped at 4 without asking\n\nSubagents inherit the session model unless the spawning call names one. Nothing in\nthis skill picks a model, so every agent it fans out lands on whatever the session\nhappens to be set to. That is how a run sized against one allocation gets billed to\nanother without anyone choosing it.\n\n**Up to 4 concurrent Fable subagents are allowed without an explicit Fable\ninstruction. Beyond that, Fable must be specified**: any roster past a scout, a\nbuilder, and a handoff writer passes 4, so this skill's fan-out does not run on Fable\nunless the user named Fable for this run. An inherited session model is not a\nspecification: \"the session was already on it\" is not the user asking. Absent an\nexplicit Fable instruction, do one of two things before launching: name a different\nmodel on the agent calls, or state plainly that the run will bill to the Fable\nallocation and get an answer. Silence is not consent to spend it.\n\n## Gate policy: advisory, not blocking\n\nEvery claim-verification step, check, quality gate, and ship verdict in this\nskill is a **recommendation to the user, not a control on the agent**. This\npolicy governs every gate, check, verdict, and \"do not ship \u002F publish \u002F\nproceed\" line elsewhere in this skill:\n\n- Run every check and report the results honestly. Verdicts (`ship`,\n  `ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are\n  advice attached to the work, not orders that change it.\n- Never block, delay, skip, rewrite, or refuse the action the user asked for\n  because a check failed or a gate said hold. Complete the requested action\n  as asked, and deliver the gate output alongside it as a clearly labeled\n  recommendation.\n- A failed gate changes what you report, never what you do.\n- Single exception: if a finding is extremely risky (data loss, security or\n  credential exposure, legal or rights violations, payment mistakes, or\n  irreversible public damage), pause, tell the user exactly what the risk is\n  and what the options are, and let them pick. Their choice is final.\n\n\nThe orchestrator assigns lanes, not conversations. Output is a delivery artifact, not a status update.\n\n## Team Contract\n\nBefore spawning or simulating lanes, define:\n\n- objective: user-visible outcome;\n- exact target: repo\u002Ffolder, branch, route, PR, live URL, API, simulator, or\n  release artifact;\n- constraints: WIP to preserve, files\u002Froutes not to touch, launch boundaries,\n  account boundaries, claims not approved, and secrets rules;\n- done signal: tests, build, screenshots, simulator, deploy readback, live\u002FAPI\n  readback, PR review, or handoff;\n- lane map: each lane, owner role, input, allowed files, output artifact, and\n  dependency order.\n\n## Team Ledger\n\nThe contract above, every lane status, and every gate result otherwise live only in\nthe orchestrator's context, and a multi-lane run routinely outlives a context window.\nPut them on disk. Default path: `.suede-team\u002F\u003Cslug>\u002Fledger.md` in the target repo,\nholding the resolved lane map, each lane's current state from the Status Vocabulary,\nand the evidence as it accumulates. Write it before the first builder opens a file and\nupdate it at every gate; the evidence handoff reads from it rather than from memory.\nIf the user keeps durable repo-local state somewhere else, use their path and say\nwhich one you used.\n\n## WIP Collision Detection\n\nBefore opening any parallel lanes:\n\n1. Run `git -C \u003Crepo> diff --name-only HEAD` and collect all dirty files.\n2. Run `git -C \u003Crepo> status --short` and collect all untracked new files.\n3. List every file each lane's scope would touch, based on the lane map.\n4. Flag a collision if the same file path appears in two or more lane scopes OR in the dirty file list plus any lane scope.\n\nCollision resolution rules:\n- Same file, independent changes: sequence the lanes; the second lane rebases on the first lane's commit before opening.\n- Same file, overlapping changes: merge the two lanes into one lane with one owner. Do not split responsibility for a single file across two concurrent builders.\n- Dirty file in a lane scope: the orchestrator decides. Either stash and restore, or make that lane the only lane allowed to touch the file.\n\nThe orchestrator writes the resolved lane map to the team ledger (`.suede-team\u002F\u003Cslug>\u002Fledger.md`, see Team Ledger) before any builder starts. No builder opens a file not in its assigned lane map.\n\n## Default Roster\n\nStart with Scout + Builder + Handoff Writer. Add roles only when a gate is needed: design changes add Design Reviewer, code risk adds Code Grader + Code Reviewer (both run suede-code, in `--grade-only` and `--findings-only` modes), public release adds Release Verifier.\n\n- **Scout:** finds repo, docs, current state, dirty files, live routes, and\n  likely blast radius.\n- **Planner:** turns requirements into verifiable tasks with acceptance\n  criteria and dependencies.\n- **Builder:** makes narrow code or content changes inside the existing system.\n- **Design reviewer:** checks rendered visual quality, responsive behavior,\n  accessibility, copy, and state coverage.\n- **Code grader:** assigns an A-F ship-risk grade across correctness, security,\n  data\u002Fstate, Suede truth, UX\u002Frelease behavior, tests, and deploy readiness.\n- **Code reviewer:** runs full-context review and turns findings into fix briefs.\n- **Visibility grader:** grades public pages, GitHub Pages sites, docs, and\n  launch surfaces for findability, first-screen clarity, CTA pull, proof, AI\n  readability, and design signal.\n- **Release verifier:** checks build, deploy, live\u002FAPI behavior, App Store\u002FiOS\n  truth, secrets, and published statements.\n- **Handoff writer:** produces a signed delivery record. If the handoff omits any required field (see Handoff Quality Checklist), the work is not done; it is held.\n\nFor high-risk work, keep builder and reviewer separate.\n\n## RFC Mode\n\nFor major architectural decisions, new feature designs, or changes with broad blast radius, run an RFC (Request for Comments) before spawning builders.\n\nAn RFC forces alignment on WHAT and WHY before committing to HOW.\n\nRFC status vocabulary: `draft | accepted | superseded | withdrawn`.\n\nBefore authoring one, read\n[`references\u002Fincident-and-rfc-templates.md`](references\u002Fincident-and-rfc-templates.md)\nand fill every section it lists: problem statement, proposed solution, alternatives\nconsidered, risks, success criteria, decision record.\n\nRequire an RFC for: shared interface changes, schema migrations, auth flow rewrites, payment path changes, public API contract changes, or any approach that's been discussed twice without resolution. No builder lane opens until RFC status is `accepted`.\n\nWhen to skip: clear, contained changes where the approach is obvious and the blast radius is narrow.\n\n## Feature Flag Strategy\n\nNot every change should ship as a hard deploy. Feature flags allow gradual rollout, A\u002FB testing, and instant rollback without a redeploy.\n\n**When to flag:**\n- New user-facing features in production traffic paths\n- Changes to auth, payment, or data migration paths\n- Any change that cannot be instantly rolled back by revert (e.g., a schema migration)\n- A\u002FB tests\n\nOnce a lane is flagged, read the lifecycle, the when-NOT-to-flag list, and the hygiene\nrules in\nthe Feature Flag Strategy section of [`references\u002Fscenario-templates.md`](references\u002Fscenario-templates.md)\nbefore the ramp starts. Every flag gets a removal date at creation; a stale flag is a\nP3 code review finding.\n\n## Rollback Decision Tree\n\nWhen something goes wrong after a deploy, the team needs a pre-agreed decision framework to avoid paralysis.\n\n```\nIs there active data loss or corruption? → ROLLBACK IMMEDIATELY. Don't investigate first.\nIs there a security exposure (PII, auth bypass, payment data)? → ROLLBACK IMMEDIATELY. Notify security.\nIs a primary user path broken (login, checkout, core workflow)? → ROLLBACK unless fix is \u003C15 minutes away.\nIs performance degraded but functional? → Hold and investigate. Set a 30-minute timer.\nIs it a cosmetic issue? → Hot-fix forward. No rollback.\n```\n\nAfter rollback:\n1. Write an immediate summary: what rolled back, what was affected, who was notified.\n2. Leave rollback notes in the PR and open a follow-up issue.\n3. Run a lightweight post-mortem (see below) before re-shipping.\n\n## Post-Mortem\n\nFor any production incident, failed release, or significant rollback, run a post-mortem. Keep it blameless: focus on systems, not individuals.\n\nSeverity: P0 (total outage) \u002F P1 (primary path broken) \u002F P2 (degraded) \u002F P3 (cosmetic).\n\nPost-mortems are required for P0 and P1 incidents. Optional but encouraged for P2. Skip for P3.\nWhen one is required, write it from\n[`references\u002Fincident-and-rfc-templates.md`](references\u002Fincident-and-rfc-templates.md)\nand fill every section: timeline, impact, root cause, contributing factors, what went\nwell, and action items with owners and due dates.\n\n## Phase Loop\n\nThe Phase Loop is the Continuous Team Loop run at minimal scale. Use it when a full 10-gate roster is overkill but you still need scout, plan, build, verify, and ship stages.\n\nFor high-risk changes, consult the Rollback Decision Tree before shipping. For gradual rollouts, use the Feature Flag Strategy. For shared interface changes, require RFC Mode before the plan stage opens.\n\n## Public Contribution Program\n\nWhen the objective is recurring work across owned or external public\nrepositories, read\n[`references\u002Fpublic-contribution-program.md`](references\u002Fpublic-contribution-program.md)\ncompletely before opening lanes. Use its deterministic ledger to score tasks,\nlease each repo\u002Fissue pair to one worker, and prevent duplicate work. Start in\n`local_only` authority with publication disabled. Keep external targets at a\nreviewed contribution packet unless the user separately approves a draft PR.\n\nThe outward artifact gate applies to branch names, commit messages, and PR\ncopy. Use conventional project language and omit voluntary tool-origin\nbranding or trailers. Never forge authorship or deny tool use; an upstream\ndisclosure requirement overrides neutral packaging and moves the lane to owner\nreview.\n\n## Model Tiering\n\nAllow up to three genuinely different fixes, each changing the diagnosis or strategy. Stop early when the same root cause repeats; escalate with the evidence instead of re-dispatching unchanged work.\n\nRead [the execution-loop protocol](references\u002Fexecution-loop.md) before assigning a model or dispatching a builder. It preserves model tiers, builder response handling and the gated continuous roster.\n\n## Inter-Lane Communication\n\nWhen a builder lane completes its output and a reviewer lane depends on it, the signal is explicit, not assumed.\n\nThe completing lane writes a Lane Ready notice:\n\n```\nLane: [name]\nStatus: output ready for review\nArtifact: [file path, URL, or PR link]\nReviewer: [lane name that receives this output]\nUnresolved: [any known issue the reviewer should know before starting]\n```\n\nThe reviewer lane does not start until it has received a Lane Ready notice from every upstream dependency in its lane map.\n\nThe orchestrator routes Lane Ready notices. In a sequential thread, the orchestrator posts the Lane Ready notice on behalf of each completing lane before invoking the next.\n\nLanes may not self-declare readiness if their output has not been verified against the acceptance criteria from the Team Contract.\n\n## Planning Quality Gate\n\nA plan is not ready until:\n\n- each task has one concern;\n- dependencies are ordered;\n- acceptance criteria are observable, not subjective;\n- required files or surfaces are named;\n- must-have requirements are covered;\n- tests, screenshots, builds, or API checks map to the risky behavior;\n- release and account boundaries are explicit.\n\nIf major uncertainty remains, run a short spike first and keep implementation\nout of scope until the spike reports back.\n\n## Review Convergence\n\nFor important merges, run at least two independent review lenses:\n\n- one asks whether the implementation works as intended;\n- one asks how it can fail in production, review, release, or public use.\n\nMerge the findings into:\n\n- consensus blockers;\n- plausible divergent risks;\n- accepted caveats;\n- fixes to execute now;\n- follow-ups that should not block.\n\nRepeat fix and review cycles until no blocker remains or the work is held.\n\n## Status Vocabulary\n\nValid states in order: `scoped` → `planned` → `executing` → `changed locally` → `verified locally` → `reviewed` → `committed` → `pushed` → `deployed` → `verified live` → `released`\n\nInterrupt states: `blocked` (needs external action) | `held` (needs named fix before continuing)\n\nDo not skip. `changed locally` is not `verified locally`. `deployed` is not `verified live`. Do not mark `released` until the done signal from the Team Contract passes.\n\n## Scenario Templates\n\nSix pre-built configurations exist for common high-risk deployments: (a) Auth Rewrite,\n(b) Payment Integration, (c) Public Launch Review, (d) Data Migration, (e) Performance\nAudit, (f) Recovery \u002F Incident Response. When the objective matches one, read\n[`references\u002Fscenario-templates.md`](references\u002Fscenario-templates.md) completely\nbefore opening lanes and adjust only the named target: each template carries its own\nroster, lane map, RFC and flag requirements, grader tolerances, and done signal.\n\n## Escalation Protocol\n\nStop the loop, surface the condition, and wait for human sign-off before continuing.\n\n| Condition | Threshold | Action |\n|---|---|---|\n| Repeated fix cycles | > 3 fix-rerun cycles on the same failing check | Stop. Write a diagnosis summary. Ask: is the acceptance criterion correct, or is the fix strategy wrong? |\n| Security finding of unknown severity | Any finding touching auth, session, PII, payment data, or access control that cannot be confidently classified as low risk | Stop. Do not attempt a fix. Surface the exact finding and uncertain blast radius. Human decides next step. |\n| Production incident with data exposure | Any indication of PII, payment data, or auth token exposure in production logs, error reports, or user reports | Stop all lanes. Trigger rollback decision tree. Notify human immediately. Do not investigate further before rollback. |\n| Cost spike | > 20 tool calls without a verified output, or estimated API\u002Finfra cost > $50 in a single loop | Stop. Summarize progress and remaining scope. Ask human to authorize continuation. |\n| Contradictory constraints | Two constraints in the Team Contract are mutually exclusive | Stop planning. Surface the conflict with a specific example. Do not proceed until human resolves. |\n\nNo agent may override an escalation threshold by re-scoping the task or declaring the condition resolved without human confirmation.\n\n## Red Flags: Stop\n\n- \"The lanes probably won't touch the same files\": probably is not a lane map. Run WIP collision detection first.\n- \"The approach is obvious, skip the RFC\": if it has been discussed twice without resolution, it is not obvious.\n- \"Mark it done, the code is written\": `changed locally` is not `verified locally`; the status vocabulary has no shortcuts.\n- \"Leave that caveat out so the handoff looks clean\": a handoff missing a field is status `held`, not done.\n- \"One more fix cycle will crack it\": past 3 cycles on the same failing check, stop and run the loop stall protocol.\n- \"The builder can review its own lane\": for high-risk work, builder and reviewer stay separate.\n\n## Handoff Quality Checklist\n\nA handoff is not complete until every field below is present and truthful. The handoff writer signs off by confirming each item.\n\nRequired fields:\n- [ ] Target: exact repo, branch, route, or URL (not \"the main app\")\n- [ ] Changed: every file path that was modified, created, or deleted (not \"various files\")\n- [ ] Commands: every bash command run, in order, with the actual output or exit code\n- [ ] Verification: observable evidence (screenshot URL, test output, curl response, build log), not \"it works\"\n- [ ] Status: one of the vocabulary states, not \"done\" unless the done signal from the Team Contract is satisfied\n- [ ] Next: the single most important unresolved step (not \"see above\")\n- [ ] Caveats: every known limitation, assumption, or deferred item; none omitted to make the handoff look cleaner\n\nIf any field is missing, the handoff writer must fill it before marking status `released` or `verified live`. A handoff with a missing field is status `held`.\n\n## Output Shape\n\nFor a team plan:\n\n```text\nObjective:\nTarget:\nConstraints:\nLane Map:\nDependency Order:\nDone Signal:\nShip Gate:\n```\n\nFor execution updates:\n\n```text\nLane:\nStatus:\nEvidence:\nNext:\nRisk:\n```\n\nFor final handoff:\n\n```text\nSimple explanation:\nUsual breakdown:\nTarget:\nChanged:\nVerification:\nCaveats:\nStatus:\nNext:\nCue Suede:\n```\n\n## Routing\n\n- The work is one repo's change and a bundled DAG can run it end to end →\n  **suede-graph-flo-xr**. Precedence: one repo, one change, research-through-release in a\n  single scripted run goes there; orchestration that is manual, ongoing, cross-repo,\n  or a public-contribution program stays here. A single lane inside a program here\n  that needs the full research-and-refute treatment can be handed to **suede-graph-flo-xr**\n  for that lane alone.\n- A recurring owned\u002Fpublic-repository contribution program needs issue leases,\n  isolated worktrees, review, and an authority-gated packet → read\n  `references\u002Fpublic-contribution-program.md` and keep this skill as controller\n- A code lane needs review or a ship grade → **suede-code** (full, `--findings-only`, or `--grade-only`)\n- The repo's merge gate is weak or missing → **suede-ci-gate**\n- A lane ships AI behavior → **suede-ai-eval** before that lane's quality gate closes\n- The public launch lane needs a page verdict → **suede-visibility-grader**, then **suede-launch-packaging**\n",{"name":5,"metadata":57,"description":7},{"display-name":58},"Suede AI Agent Teams Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams",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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-agent-teams",{"tool":75,"command":76},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-agent-teams",{"tool":78,"command":79},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-agent-teams","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002FSKILL.md",true,[83,89,93,97,101,105,109,113],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"agents\u002Fopenai.yaml","REFERENCE","参考文档",738,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002Fagents\u002Fopenai.yaml",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"CARD.md",4656,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002FCARD.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fexecution-loop.md",4793,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002Freferences\u002Fexecution-loop.md",{"path":98,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fincident-and-rfc-templates.md",1960,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002Freferences\u002Fincident-and-rfc-templates.md",{"path":102,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fpublic-contribution-program.md",13974,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002Freferences\u002Fpublic-contribution-program.md",{"path":106,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fscenario-templates.md",8276,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002Freferences\u002Fscenario-templates.md",{"path":110,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fworked-contract.md",2089,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002Freferences\u002Fworked-contract.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fcontribution-ledger.mjs","SCRIPT","脚本",52312,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-agent-teams\u002Fscripts\u002Fcontribution-ledger.mjs",[120,130,138,146,154,162],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":129},"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":129},"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":129},"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":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":129},"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":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":129},"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":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":129},"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",[],[]]