[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M746FG08EVBKY20G82GN3B41":3,"skill-same:01M746FG08EVBKY20G82GN3B41":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M746FG08EVBKY20G82GN3B41","options-strategy",null,"Build and compare multi-leg option structures from a chain: iron condors, iron butterflies, call butterflies, vertical spreads both debit and credit including bull put and bear call spreads, straddles, strangles, covered calls, cash-secured puts, protective puts, and the two-expiry family of calendars, diagonals and ratio diagonals. Produces legs, breakevens, maximum gain and loss, reward to risk, model probability of profit, net position Greeks and an estimate of what the round trip costs at quoted spreads, then ranks every structure side by side. Use when the user asks what structure fits a view, what an iron condor would pay, which spread is better, what the breakevens are, how much a trade can lose, what a calendar or a diagonal or a ratio diagonal would do, or asks to compare strategies. Not for order placement and not for recommendations.","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\u002FIman\u002Fagent-driven-options-desk-and-skills\u002Fskills\u002Foptions-strategy\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: options-strategy\ndescription: \"Build and compare multi-leg option structures from a chain: iron condors, iron butterflies, call butterflies, vertical spreads both debit and credit including bull put and bear call spreads, straddles, strangles, covered calls, cash-secured puts, protective puts, and the two-expiry family of calendars, diagonals and ratio diagonals. Produces legs, breakevens, maximum gain and loss, reward to risk, model probability of profit, net position Greeks and an estimate of what the round trip costs at quoted spreads, then ranks every structure side by side. Use when the user asks what structure fits a view, what an iron condor would pay, which spread is better, what the breakevens are, how much a trade can lose, what a calendar or a diagonal or a ratio diagonal would do, or asks to compare strategies. Not for order placement and not for recommendations.\"\n---\n\n# Option strategies\n\nThree commands. Build one structure, list what exists, or compare them all.\n\n## Execution route\n\nPrefer `option_strategy_build` to list or build structures and\n`option_strategy_compare` to compare them. Use `option_chain_snapshot` first\nwhen a fresh chain is needed. If the user has attached a CSV or JSON chain,\npass its path as `source_path` for a local file. For remote chat, pass its\ncontent as `source_data` or `source_text`. Do not ask the user for it again.\nIf a matching MCP tool is not available, use\nthe `optiondesk` commands below. If neither MCP nor the CLI is available,\nsay that no fresh structure analysis can be produced; do not invent figures\nor present example or remembered values as current.\n\n## User-supplied data\n\nBefore you send data to the tool, ask the user to state that private analysis\nis permitted. Then set `rights_confirmed` to true and name `data_source`.\nThe local desk does not gate on that name: any `data_source` is accepted,\nso whether that provider's terms allow the analysis is the user's\nresponsibility (only the hosted service refuses Yahoo, yfinance and\npersonal Alpha Vantage data).\n\nIf the attachment fields are unclear, call `option_snapshot_schema`. Normalize\nknown column aliases, call or put notation, numeric commas, and clear percentage\nunits. Report the repairs from `normalization`. Never invent a missing spot,\nexpiry, strike, option type, quote, timestamp, or source. If a required value\nis missing, ask only for that value.\n\nThe imported chain becomes a normal Option Desk artifact. Use its path for the\nstrategy, comparison, plots, positioning, Greeks, and the local dashboard.\n\n## Data boundary\n\nUse fresh provider data only when the tool reports that access is allowed.\nA local Yahoo adapter also requires the personal-use acknowledgement. A\nhosted tool must use a provider that is approved for public display, derived\noutputs, storage, and MCP delivery. Never bypass a provider refusal. When no\napproved tool is available, analyse a snapshot that the user supplied and\nhad the right to share. Otherwise, state that current figures are unavailable.\n\n## Run it\n\n```\noptiondesk strategy --list                    # the playbook, as data\noptiondesk chain SPY --from-file chain.csv --data-source \"broker export\" --accept-data-rights\noptiondesk strategy iron_condor               # build one from the latest chain\noptiondesk strategy --recommend 1 --vol-view crush\noptiondesk compare                            # every structure, ranked\n```\n\n`strategy` takes `--snapshot PATH` to pick a chain, `--size` for contracts\nper leg, and `--underlying-entry` for structures that hold the underlying.\n`--recommend N` takes an outlook from -2 (strong bearish) through 0\n(neutral) to +2 (strong bullish), with `--vol-view crush|expand|neutral`,\n`--owns-underlying` and `--direction-unknown`.\n\n`compare` builds every buildable structure from one snapshot and ranks\nthem. Add `--include-underlying` for covered calls and the like.\n\n## The five-direction framework\n\nStructures are organised by which of five outcomes they need, anchored on\nthe one standard deviation expected move: strong bearish, mild bearish,\nneutral, mild bullish, strong bullish. Three of the five sit inside the\nnormal expected range and two are extreme. That is why a vertical spread\nbeats a naked long option for most views: it reaches maximum profit on a\nnormal move rather than needing an extreme one.\n\n## Reporting rules you must follow\n\nThe ranking is by model expected profit per unit of capital at risk. Quote\nthe caveat with it, every time: expectations come from a lognormal model at\na single at-the-money volatility while the market prices each strike\ndifferently, so a positive expectation largely measures that disagreement\nrather than an edge.\n\nA structure whose friction verdict is untradeable is excluded from the\nranking. Say so rather than presenting it as a candidate.\n\nPremiums are mid quotes. They are not fills, and a real entry crosses the\nspread on every leg. Maximum gain or loss may come back as the string\n\"unlimited\", which is a fact about the structure and must never be\nrendered as a number.\n\nNothing here is advice. Present structures as analysis of what a shape\nwould pay under stated assumptions, never as what the user should do, and\nnever recommend an entry, an exit or a size.\nThe full terms are in DISCLAIMER.md, which ships beside this skill when it\nis installed from a package and sits at the repository root otherwise. The\nsubstance is already above: research software, not advice, modelled numbers\nthat are not fills.\n\nCite the artifact path when reporting from it. The artifact is the record;\nprose is a summary of it, and a number quoted without its source cannot be\nchecked later.\n\nRead `degraded` before quoting anything. When it is true, give\n`degraded_reason` first, in the same breath as the number rather than as a\nfootnote. Both fields are in the summary the command prints, not only in\nthe artifact.\n\n\n## What an audit found in these numbers, and what to say about it\n\n**A two-expiry maximum can be a property of the scan, not the structure.**\nCalendars, diagonals and ratio diagonals have no closed-form maximum, so\nthe analysis scans a window around spot. When the payoff is monotone in the\ntrade's own direction the maximum lands on the window edge, and the figure\ngrows as the window widens: one live ratio diagonal reads 1.47 reward to\nrisk at a tenth of the width, 4.90 at the shipped width and 12.02 at two\nand a half times it. Every plan now carries\n`reward_risk_bounded_by_scan`, `max_gain_on_boundary` and `scan_range_sd`.\nWhen the flag is true, say where the maximum sits: on the live pair the\nedges are about ten standard deviations out, which is arithmetic rather\nthan a scenario.\n\n**`delta_ratio` is a bound on the entry split, not a guarantee.** It was\ndocumented for a while as the thing that keeps a large move uncapped. It is\nnot: one long against two short satisfies it at 0.76 and is a net short\ncall with unbounded loss. What keeps the move uncapped is holding more\nback-month contracts than front-month ones, which the builder checks first.\nDo not repeat the older claim.\n\n**Every figure names the carry it used.** Plans carry `risk_free_rate` and\n`dividend_yield` read from the chain rather than assumed. They matter: at\nthe module defaults instead of the measured values, three of the four legs\nof a ratio diagonal land on different strikes.\n\n## Going deeper\n\n- `reference.md`: all twenty-three structures in a table with what each needs and when it pays, the five direction framework, the friction verdicts, and the fields that are not numbers.\n- `workflows\u002Fchoose-a-structure.md`: turning a view into a structure, and the rules for reporting one.\n","# Option strategies\n\nThree commands. Build one structure, list what exists, or compare them all.\n\n## Execution route\n\nPrefer `option_strategy_build` to list or build structures and\n`option_strategy_compare` to compare them. Use `option_chain_snapshot` first\nwhen a fresh chain is needed. If the user has attached a CSV or JSON chain,\npass its path as `source_path` for a local file. For remote chat, pass its\ncontent as `source_data` or `source_text`. Do not ask the user for it again.\nIf a matching MCP tool is not available, use\nthe `optiondesk` commands below. If neither MCP nor the CLI is available,\nsay that no fresh structure analysis can be produced; do not invent figures\nor present example or remembered values as current.\n\n## User-supplied data\n\nBefore you send data to the tool, ask the user to state that private analysis\nis permitted. Then set `rights_confirmed` to true and name `data_source`.\nThe local desk does not gate on that name: any `data_source` is accepted,\nso whether that provider's terms allow the analysis is the user's\nresponsibility (only the hosted service refuses Yahoo, yfinance and\npersonal Alpha Vantage data).\n\nIf the attachment fields are unclear, call `option_snapshot_schema`. Normalize\nknown column aliases, call or put notation, numeric commas, and clear percentage\nunits. Report the repairs from `normalization`. Never invent a missing spot,\nexpiry, strike, option type, quote, timestamp, or source. If a required value\nis missing, ask only for that value.\n\nThe imported chain becomes a normal Option Desk artifact. Use its path for the\nstrategy, comparison, plots, positioning, Greeks, and the local dashboard.\n\n## Data boundary\n\nUse fresh provider data only when the tool reports that access is allowed.\nA local Yahoo adapter also requires the personal-use acknowledgement. A\nhosted tool must use a provider that is approved for public display, derived\noutputs, storage, and MCP delivery. Never bypass a provider refusal. When no\napproved tool is available, analyse a snapshot that the user supplied and\nhad the right to share. Otherwise, state that current figures are unavailable.\n\n## Run it\n\n```\noptiondesk strategy --list                    # the playbook, as data\noptiondesk chain SPY --from-file chain.csv --data-source \"broker export\" --accept-data-rights\noptiondesk strategy iron_condor               # build one from the latest chain\noptiondesk strategy --recommend 1 --vol-view crush\noptiondesk compare                            # every structure, ranked\n```\n\n`strategy` takes `--snapshot PATH` to pick a chain, `--size` for contracts\nper leg, and `--underlying-entry` for structures that hold the underlying.\n`--recommend N` takes an outlook from -2 (strong bearish) through 0\n(neutral) to +2 (strong bullish), with `--vol-view crush|expand|neutral`,\n`--owns-underlying` and `--direction-unknown`.\n\n`compare` builds every buildable structure from one snapshot and ranks\nthem. Add `--include-underlying` for covered calls and the like.\n\n## The five-direction framework\n\nStructures are organised by which of five outcomes they need, anchored on\nthe one standard deviation expected move: strong bearish, mild bearish,\nneutral, mild bullish, strong bullish. Three of the five sit inside the\nnormal expected range and two are extreme. That is why a vertical spread\nbeats a naked long option for most views: it reaches maximum profit on a\nnormal move rather than needing an extreme one.\n\n## Reporting rules you must follow\n\nThe ranking is by model expected profit per unit of capital at risk. Quote\nthe caveat with it, every time: expectations come from a lognormal model at\na single at-the-money volatility while the market prices each strike\ndifferently, so a positive expectation largely measures that disagreement\nrather than an edge.\n\nA structure whose friction verdict is untradeable is excluded from the\nranking. Say so rather than presenting it as a candidate.\n\nPremiums are mid quotes. They are not fills, and a real entry crosses the\nspread on every leg. Maximum gain or loss may come back as the string\n\"unlimited\", which is a fact about the structure and must never be\nrendered as a number.\n\nNothing here is advice. Present structures as analysis of what a shape\nwould pay under stated assumptions, never as what the user should do, and\nnever recommend an entry, an exit or a size.\nThe full terms are in DISCLAIMER.md, which ships beside this skill when it\nis installed from a package and sits at the repository root otherwise. The\nsubstance is already above: research software, not advice, modelled numbers\nthat are not fills.\n\nCite the artifact path when reporting from it. The artifact is the record;\nprose is a summary of it, and a number quoted without its source cannot be\nchecked later.\n\nRead `degraded` before quoting anything. When it is true, give\n`degraded_reason` first, in the same breath as the number rather than as a\nfootnote. Both fields are in the summary the command prints, not only in\nthe artifact.\n\n\n## What an audit found in these numbers, and what to say about it\n\n**A two-expiry maximum can be a property of the scan, not the structure.**\nCalendars, diagonals and ratio diagonals have no closed-form maximum, so\nthe analysis scans a window around spot. When the payoff is monotone in the\ntrade's own direction the maximum lands on the window edge, and the figure\ngrows as the window widens: one live ratio diagonal reads 1.47 reward to\nrisk at a tenth of the width, 4.90 at the shipped width and 12.02 at two\nand a half times it. Every plan now carries\n`reward_risk_bounded_by_scan`, `max_gain_on_boundary` and `scan_range_sd`.\nWhen the flag is true, say where the maximum sits: on the live pair the\nedges are about ten standard deviations out, which is arithmetic rather\nthan a scenario.\n\n**`delta_ratio` is a bound on the entry split, not a guarantee.** It was\ndocumented for a while as the thing that keeps a large move uncapped. It is\nnot: one long against two short satisfies it at 0.76 and is a net short\ncall with unbounded loss. What keeps the move uncapped is holding more\nback-month contracts than front-month ones, which the builder checks first.\nDo not repeat the older claim.\n\n**Every figure names the carry it used.** Plans carry `risk_free_rate` and\n`dividend_yield` read from the chain rather than assumed. They matter: at\nthe module defaults instead of the measured values, three of the four legs\nof a ratio diagonal land on different strikes.\n\n## Going deeper\n\n- `reference.md`: all twenty-three structures in a table with what each needs and when it pays, the five direction framework, the friction verdicts, and the fields that are not numbers.\n- `workflows\u002Fchoose-a-structure.md`: turning a view into a structure, and the rules for reporting one.\n",{"name":5,"description":7},"main","347aedf8480cd92b21f761e97b7343a45898f5fa","plugins\u002FIman\u002Fagent-driven-options-desk-and-skills\u002Fskills\u002Foptions-strategy",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill options-strategy",{"tool":40,"command":41},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill options-strategy",{"tool":43,"command":44},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill options-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FIman\u002Fagent-driven-options-desk-and-skills\u002Fskills\u002Foptions-strategy\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"reference.md","REFERENCE","参考文档",4847,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FIman\u002Fagent-driven-options-desk-and-skills\u002Fskills\u002Foptions-strategy\u002Freference.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"workflows\u002Fchoose-a-structure.md",1132,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FIman\u002Fagent-driven-options-desk-and-skills\u002Fskills\u002Foptions-strategy\u002Fworkflows\u002Fchoose-a-structure.md",[59,69,77,85,93,101],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":68},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":68},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":68},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":68},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":68},"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",[],[]]