[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJQZSVJ93CFV0W1G9C9KF4":3,"skill-same:01M6MJQZSVJ93CFV0W1G9C9KF4":83},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6MJQZSVJ93CFV0W1G9C9KF4","analytics-dashboard-integrity",null,"Use when designing, reviewing, or fixing dashboards or analytical reports with cohorts, activation, retention, payments, revenue, forecasts, valuation metrics, denominators, privacy-sensitive rows, or source disagreements.","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\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fanalytics-dashboard-integrity\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"analytics","analytics dashboard","analytics dashboard integrity","integrity","dashboard","use","when","source","with","retention","revenue","analytical","activation","reports","dashboards","privacy","payments","metrics","valuation","2026-11-10 10:12:30",false,"---\nname: analytics-dashboard-integrity\ndescription: Use when designing, reviewing, or fixing dashboards or analytical reports with cohorts, activation, retention, payments, revenue, forecasts, valuation metrics, denominators, privacy-sensitive rows, or source disagreements.\n---\n\n# Analytics Dashboard Integrity\n\nUse this skill when a dashboard or analytical report can drive business decisions and the risk is metric trust, not visual layout alone.\n\n## Metric Trust Gate\n\nBefore approving dashboard metrics, define:\n\n1. source of truth;\n2. grain;\n3. denominator;\n4. eligibility filter;\n5. event or payment filter;\n6. date anchor or `asOf` date;\n7. freshness;\n8. known disagreement with other sources.\n\nKeep cohort membership filters separate from event and payment filters. A filter that silently changes the denominator must be explicit.\n\nPayment currencies, credits, balances, bonus units, and revenue must stay separate unless a documented conversion rule exists.\n\nWhen a dashboard or management summary combines several live sources, pin a single canonical snapshot boundary before writing the final numbers. Record the source-specific snapshot times and the report `asOf`; do not silently mix a later API\u002Fsource refresh into a table or narrative already bound to an earlier sheet\u002Fexport fact. If a later source disagrees, show it as a separate reconciliation note or refresh the whole dependent metric set together.\n\nFor monetary summaries, independently recompute every derived value from the exact source amounts, including currency conversion, rounding, cost per action, subtotals, and totals. After correcting a formula or conversion, recheck the changed formula and the nearest dependent totals before release.\n\nKeep rates at full computational precision until their final display, or format them directly from the retained numerator and denominator. Do not round a fraction and then round its percentage again: for example, 384\u002F542 displays as 70.8% to one decimal, while prematurely storing 0.7085 can incorrectly display 70.9%. Check displayed percentages against the original counts when a value lies near a rounding boundary.\n\nWhen session recordings, Webvisor\u002Fvideo review, browser screenshots, or other visual behavior evidence suggest a funnel or product defect, size that defect against a source-of-truth denominator before naming it as the main cause or highest-priority opportunity. Record how many users, sessions, accounts, revenue, or eligible events use the observed path, and compare it with competing paths. A vivid replay of a minority path is evidence for a hypothesis, not proof that the defect explains overall conversion, activation, retention, or revenue.\n\n## Attribution And Event Evidence\n\nBefore joining page traffic with CRM\u002FRoistat landing-page metrics, compare actual URL variants across both sources. A trailing slash can split one canonical page into separate traffic and revenue rows. Confirm redirects\u002Fcanonical URLs for the affected paths, preserve query strings and fragments, and require zero collisions within site and channel before normalizing. Do not sum unique visitors across merged URL variants; use an exact combined source query if more than one traffic row maps to a canonical key.\n\nBefore calculating advertising cost per lead or return, verify the linkage\nbetween visits, lead events and attributed sources, including telephone-source\nassignments when calls contribute. A source label or UTM value on a CRM card does\nnot itself prove that link. Keep unlinked leads in an explicit unknown bucket;\nzero linked leads with unverified tracking is not proof of zero advertising\nleads. Expense detail must not be used to invent matching lead attribution.\n\nWhen CRM UTM sources differ from the advertising-source registry, inspect both\nlive values before repairing joins. An alternate source match must require the\npaid medium and an exact, unambiguous campaign match; never assign all traffic\nfrom a search engine to its advertising account. Verify organic, missing-tag,\nunknown-campaign and test-record cases as well as real paid leads. In Trino,\nrepeated CTE joins can exceed the query-stage limit: reduce redundant joins and\ncompare old\u002Fnew totals in separate equivalent queries instead of combining\nboth full graphs or changing server limits.\n\nFor appointment funnels, distinguish booking, actual attendance, an indication\nfor treatment and performed treatment. Define the evidence source and event date\nfor each before calculating attendance or treatment conversion. Inspect existing\nfields, activities and history before proposing new stages. If the attendance\nevent is not established, mark attendance metrics unavailable rather than infer\nattendance from a treatment-indication status.\n\nWhen grouped analytics rows do not sum to the total, obtain a comparable\nungrouped control with the same filters, period and attribution. Check a named\nsegment and its complement using comparable controls. An unsampled response does\nnot prove that every grouped row was disclosed. Preserve unexplained residuals;\ndo not distribute them across visible rows or name privacy suppression as the\ncause without evidence.\n\nWhen extending a report with recovered URL rows, recompute every residual from\nthe current detail and the pinned ungrouped control before generating totals.\nNever append recovered rows while retaining the original residual as another\nadditive row: that double-counts the recovered visits or pageviews. Keep initial\ndisclosure counts as historical evidence separately, and require the current\ndetail plus current residual to equal the control for every site and channel.\n\nAfter excluding robot, test, or out-of-scope records, recheck membership of the\nfinal detail list. Keep groups with zero in-scope activity and no in-scope\ncommercial events in the raw audit, but exclude them from a list presented as\n\"visited pages\" or another list of observed in-scope entities.\n\n## Lost Advertising Identifier Recovery\n\nWhen a CRM lead has a paid campaign but an empty ad identifier, inspect the\nactual capture and serialization functions as well as the reporting join. Test\nreal-length identifiers through the full metadata chain: a phone privacy regex\ncan match a substring of a long ad number. Use a field-specific numeric policy\nfor ad identifiers; preserve contact filtering in other fields. Recover past\nidentifiers only from an exact click marker and matching campaign\u002Fsource\u002Fmedium\nin retained access logs. Save the original CRM fields, update existing records\nonly, read them back, and verify the rendered report. Check every paid form\naffected by the same cause, not only the screenshot example.\n\n## Cohorts And Forecasts\n\nFor activation, retention, payment, revenue, or funnel cohorts:\n\n- mark immature horizons from the `asOf` date;\n- handle right-censoring and partial periods;\n- avoid presenting immature periods as stable facts;\n- record sample size and denominator for every rate.\n\nForecasts must be deterministic enough that two implementers compute the same point estimate, interval boundaries, status, and warning order. Negative clipping, interval composition, status precedence, and validation-error signs must be specified before coding.\n\nSmall-sample forecasts need uncertainty, backtesting or a reliability status. A single forward trend without reliability is not a management metric.\n\n## Privacy And Live Data\n\nWhen editing SQL in an Ace editor, do not assume textbox `fill` replaces the\nwhole document: its textarea can represent only the current line. Select the\nwhole editor document, paste the replacement, then select\u002Fcopy it back and\ncompare the complete text before running or saving. Preserve the full preimage. If the copied text differs, stop before save confirmation; inspect the editor lock and unlock it before replacing the document again. Gate the save action on exact equality, rather than merely printing the comparison.\n\nFor pivot tables with CSS-generated header labels, check that every rendered metric has a visible header whenever the metric list changes; updating grid width alone is insufficient. Verify saved CSS after reopening the real report. In Superset, wait for the CSS preview to reflect the edit, close its dialog, save the dashboard, and require the save confirmation before reloading.\n\nDashboards that expose live user, generation, payment, or revenue aggregates need explicit auth, cache, and privacy review. Do not include direct personal, payment, account, credential, or raw operational rows unless the delivery surface and audience require them and the values are minimized.\n","# Analytics Dashboard Integrity\n\nUse this skill when a dashboard or analytical report can drive business decisions and the risk is metric trust, not visual layout alone.\n\n## Metric Trust Gate\n\nBefore approving dashboard metrics, define:\n\n1. source of truth;\n2. grain;\n3. denominator;\n4. eligibility filter;\n5. event or payment filter;\n6. date anchor or `asOf` date;\n7. freshness;\n8. known disagreement with other sources.\n\nKeep cohort membership filters separate from event and payment filters. A filter that silently changes the denominator must be explicit.\n\nPayment currencies, credits, balances, bonus units, and revenue must stay separate unless a documented conversion rule exists.\n\nWhen a dashboard or management summary combines several live sources, pin a single canonical snapshot boundary before writing the final numbers. Record the source-specific snapshot times and the report `asOf`; do not silently mix a later API\u002Fsource refresh into a table or narrative already bound to an earlier sheet\u002Fexport fact. If a later source disagrees, show it as a separate reconciliation note or refresh the whole dependent metric set together.\n\nFor monetary summaries, independently recompute every derived value from the exact source amounts, including currency conversion, rounding, cost per action, subtotals, and totals. After correcting a formula or conversion, recheck the changed formula and the nearest dependent totals before release.\n\nKeep rates at full computational precision until their final display, or format them directly from the retained numerator and denominator. Do not round a fraction and then round its percentage again: for example, 384\u002F542 displays as 70.8% to one decimal, while prematurely storing 0.7085 can incorrectly display 70.9%. Check displayed percentages against the original counts when a value lies near a rounding boundary.\n\nWhen session recordings, Webvisor\u002Fvideo review, browser screenshots, or other visual behavior evidence suggest a funnel or product defect, size that defect against a source-of-truth denominator before naming it as the main cause or highest-priority opportunity. Record how many users, sessions, accounts, revenue, or eligible events use the observed path, and compare it with competing paths. A vivid replay of a minority path is evidence for a hypothesis, not proof that the defect explains overall conversion, activation, retention, or revenue.\n\n## Attribution And Event Evidence\n\nBefore joining page traffic with CRM\u002FRoistat landing-page metrics, compare actual URL variants across both sources. A trailing slash can split one canonical page into separate traffic and revenue rows. Confirm redirects\u002Fcanonical URLs for the affected paths, preserve query strings and fragments, and require zero collisions within site and channel before normalizing. Do not sum unique visitors across merged URL variants; use an exact combined source query if more than one traffic row maps to a canonical key.\n\nBefore calculating advertising cost per lead or return, verify the linkage\nbetween visits, lead events and attributed sources, including telephone-source\nassignments when calls contribute. A source label or UTM value on a CRM card does\nnot itself prove that link. Keep unlinked leads in an explicit unknown bucket;\nzero linked leads with unverified tracking is not proof of zero advertising\nleads. Expense detail must not be used to invent matching lead attribution.\n\nWhen CRM UTM sources differ from the advertising-source registry, inspect both\nlive values before repairing joins. An alternate source match must require the\npaid medium and an exact, unambiguous campaign match; never assign all traffic\nfrom a search engine to its advertising account. Verify organic, missing-tag,\nunknown-campaign and test-record cases as well as real paid leads. In Trino,\nrepeated CTE joins can exceed the query-stage limit: reduce redundant joins and\ncompare old\u002Fnew totals in separate equivalent queries instead of combining\nboth full graphs or changing server limits.\n\nFor appointment funnels, distinguish booking, actual attendance, an indication\nfor treatment and performed treatment. Define the evidence source and event date\nfor each before calculating attendance or treatment conversion. Inspect existing\nfields, activities and history before proposing new stages. If the attendance\nevent is not established, mark attendance metrics unavailable rather than infer\nattendance from a treatment-indication status.\n\nWhen grouped analytics rows do not sum to the total, obtain a comparable\nungrouped control with the same filters, period and attribution. Check a named\nsegment and its complement using comparable controls. An unsampled response does\nnot prove that every grouped row was disclosed. Preserve unexplained residuals;\ndo not distribute them across visible rows or name privacy suppression as the\ncause without evidence.\n\nWhen extending a report with recovered URL rows, recompute every residual from\nthe current detail and the pinned ungrouped control before generating totals.\nNever append recovered rows while retaining the original residual as another\nadditive row: that double-counts the recovered visits or pageviews. Keep initial\ndisclosure counts as historical evidence separately, and require the current\ndetail plus current residual to equal the control for every site and channel.\n\nAfter excluding robot, test, or out-of-scope records, recheck membership of the\nfinal detail list. Keep groups with zero in-scope activity and no in-scope\ncommercial events in the raw audit, but exclude them from a list presented as\n\"visited pages\" or another list of observed in-scope entities.\n\n## Lost Advertising Identifier Recovery\n\nWhen a CRM lead has a paid campaign but an empty ad identifier, inspect the\nactual capture and serialization functions as well as the reporting join. Test\nreal-length identifiers through the full metadata chain: a phone privacy regex\ncan match a substring of a long ad number. Use a field-specific numeric policy\nfor ad identifiers; preserve contact filtering in other fields. Recover past\nidentifiers only from an exact click marker and matching campaign\u002Fsource\u002Fmedium\nin retained access logs. Save the original CRM fields, update existing records\nonly, read them back, and verify the rendered report. Check every paid form\naffected by the same cause, not only the screenshot example.\n\n## Cohorts And Forecasts\n\nFor activation, retention, payment, revenue, or funnel cohorts:\n\n- mark immature horizons from the `asOf` date;\n- handle right-censoring and partial periods;\n- avoid presenting immature periods as stable facts;\n- record sample size and denominator for every rate.\n\nForecasts must be deterministic enough that two implementers compute the same point estimate, interval boundaries, status, and warning order. Negative clipping, interval composition, status precedence, and validation-error signs must be specified before coding.\n\nSmall-sample forecasts need uncertainty, backtesting or a reliability status. A single forward trend without reliability is not a management metric.\n\n## Privacy And Live Data\n\nWhen editing SQL in an Ace editor, do not assume textbox `fill` replaces the\nwhole document: its textarea can represent only the current line. Select the\nwhole editor document, paste the replacement, then select\u002Fcopy it back and\ncompare the complete text before running or saving. Preserve the full preimage. If the copied text differs, stop before save confirmation; inspect the editor lock and unlock it before replacing the document again. Gate the save action on exact equality, rather than merely printing the comparison.\n\nFor pivot tables with CSS-generated header labels, check that every rendered metric has a visible header whenever the metric list changes; updating grid width alone is insufficient. Verify saved CSS after reopening the real report. In Superset, wait for the CSS preview to reflect the edit, close its dialog, save the dashboard, and require the save confirmation before reloading.\n\nDashboards that expose live user, generation, payment, or revenue aggregates need explicit auth, cache, and privacy review. Do not include direct personal, payment, account, credential, or raw operational rows unless the delivery surface and audience require them and the values are minimized.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fanalytics-dashboard-integrity",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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill analytics-dashboard-integrity",{"tool":69,"command":70},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill analytics-dashboard-integrity",{"tool":72,"command":73},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill analytics-dashboard-integrity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fanalytics-dashboard-integrity\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"agents\u002Fopenai.yaml","REFERENCE","参考文档",309,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fanalytics-dashboard-integrity\u002Fagents\u002Fopenai.yaml",[84,94,102,110,118,126],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":93},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":93},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":93},"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":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":93},"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":93},"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",[],[]]