[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGWJC9430RXZVFEXFR9ZMV":3,"skill-same:01M6MGWJC9430RXZVFEXFR9ZMV":74},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6MGWJC9430RXZVFEXFR9ZMV","attribute-creation",null,"Guides you step-by-step through defining a calculated attribute (dimension) on a Honeydew entity. Covers SQL expression building and pushes to Honeydew via the MCP tools.","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\u002Fhoneydew-ai\u002Fhoneydew-ai-coding-agents-plugins\u002Fskills\u002Fattribute-creation\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],"creation","attribute creation","MCP","sql","mcp tools","Tools","expression","via","guides","you","entity","2026-11-10 10:12:30",false,"---\nname: attribute-creation\ndescription: Guides you step-by-step through defining a calculated attribute (dimension) on a Honeydew entity. Covers SQL expression building and pushes to Honeydew via the MCP tools.\n---\n\n## Prerequisites\n\nBefore creating attributes, ensure you are on the correct workspace and branch. Use `get_session_workspace_and_branch` to check the current session context. For development work, create a branch with `create_workspace_branch` (the session switches automatically). See the `model-exploration` skill for the full workspace\u002Fbranch tool reference.\n\n---\n\n## Overview\n\nA Honeydew **calculated attribute** is a virtual, per-row column defined on an entity — analogous to an expression in a SQL `SELECT` clause.\nIt is evaluated once per row, not aggregated. In BI tools it surfaces as a **dimension** users can group, filter, and slice by.\n\nUse a calculated attribute when:\n\n- You need a reusable, governed column that doesn't exist verbatim in the source table (e.g. `net_price`, `customer_tier`, `order_month`)\n- The value should be consistent everywhere it's consumed, not recalculated ad-hoc in each dashboard\n- You want to expose a clean, business-friendly label for a raw or encoded column\n\nDo **not** use a calculated attribute for aggregations across rows — use a metric instead.\n\n---\n\n## Building the SQL Expression\n\n### Core Rules\n\n- **Use simple expressions** — easy to understand\n- **Use the SQL dialect of the connected data warehouse** (Snowflake, Databricks, or BigQuery)\n- **Use `entity.field` format** for all attribute\u002Fmetric references\n- **No joins or subqueries** — simple expressions only (window functions allowed)\n- **Use fully qualified column names** — `orders.amount`, not just `amount`\n- **Prefer ILIKE over LIKE** for case-insensitive matching\n\nSee [reference.md](reference.md) for: SQL functions, JSON\u002Fsemi-structured data, geography, data types, full YAML schema, attribute types, time grain, and format strings.\n\n---\n\n## Creation Methods\n\n### Primary: create_object with YAML\n\nCall `create_object` with `yaml_text`:\n\n```yaml\ntype: calculated_attribute\nentity: \u003Centity_name>\nname: \u003Csnake_case_name>\ndisplay_name: \u003CHuman Readable Name>\ndescription: |-\n  \u003Cbusiness description>\nowner: \u003Cowner_email_or_team>\ndatatype: string|number|float|bool|date|timestamp|time\nsql: |-\n  \u003CSQL expression>\nfolder: \u003Coptional folder path>\n```\n\n**Required fields:**\n\n- `type: calculated_attribute`\n- `entity` — the entity this attribute belongs to\n- `name` — snake_case identifier\n- `owner` — **CRITICAL: always set** (email or team name)\n- `datatype` — **CRITICAL: always set explicitly**\n- `sql` — the expression\n\n### Update: update_object\n\n1. Use `get_entity` or `search_model` (with `search_mode: EXACT`) to find the attribute's `object_key`.\n2. Call `update_object` with the full updated YAML (`yaml_text`) and the `object_key`.\n\n> **Minimal diff rule:** When updating, preserve the existing field order and formatting from the current YAML. Only change the fields you need to modify. Objects are versioned in git, so unnecessary reordering or reformatting creates noisy diffs.\n\n### After Creation\u002FUpdate: Display the UI Link\n\nAfter a successful `create_object` or `update_object` call, the response includes a `ui_url` field. **Always display this URL to the user** so they can quickly open the object in the Honeydew application.\n\n### Delete: delete_object\n\n1. Use `search_model` (with `search_mode: EXACT`) to find the attribute's `object_key`.\n2. Call `delete_object` with that `object_key`.\n\n---\n\n## Examples\n\nSee [examples.md](examples.md) for full worked examples covering: basic, boolean flag, grouping\u002Fbinning, multi-entity, date truncation, window function, running total, semi-structured JSON, safe division, update, and delete.\n\n---\n\n## Discovery Helpers\n\nUse these MCP tools to explore existing attributes:\n\n- `get_entity` — Get entity details including all attributes (filter by `__typename` for `CalcAttribute` or `DataSetAttribute`)\n- `get_field` — Get detailed info about a specific attribute by entity and field name\n- `search_model` — Search for attributes across the model by name (use `search_mode: EXACT` for known names, `OR` for broad discovery)\n- `list_entities` — List entities to identify where to anchor new attributes\n\n---\n\n## Documentation Lookup\n\nUse the `honeydew-docs` MCP tools to search the Honeydew documentation when:\n\n- You need warehouse-specific SQL function details not covered in `reference.md` (Snowflake, Databricks, BigQuery differences)\n- The user asks about advanced attribute types (multi-entity, aggregation) or when to use each\n- You need guidance on time grain configuration, format strings, or data type nuances\n- The user needs advanced modeling patterns for calculated attributes (e.g., complex bucketing, conditional logic, semi-structured data extraction)\n\nSearch for topics like: \"calculated attributes\", \"attribute types\", \"multi-entity attribute\", \"aggregation attribute\", \"time grain\", \"format strings\", \"advanced modeling\".\n\n---\n\n## Best Practices\n\n- **Reuse existing attributes — don't repeat logic.**\n  If a calculated attribute already exists on the entity (or you just created one), reference it by name\n  (`entity.attribute_name`) rather than inlining its SQL expression. This keeps definitions DRY and ensures changes propagate.\n- **Qualify every column reference** with the entity name: `orders.amount`, not `amount`.\n- **Set timegrain** on every date\u002Ftimestamp attribute.\n- **Hide raw \u002F intermediate columns** so they don't clutter BI tool field pickers.\n- **Use folder** to group related attributes.\n- **Prefer Multi-Entity over duplicating columns.** Reference related entities rather than copying definitions.\n- **Use DIV0 for division** to avoid divide-by-zero errors.\n- **Use ILIKE over LIKE** for case-insensitive string matching.\n\n---\n\n## MANDATORY: Validate After Creating\n\n**After creating ANY attribute, you MUST invoke the `validation` skill to test and validate results.**\n\nSee `validation` skill for:\n\n- How to execute attributes via `get_data_from_fields` (attributes go in the attributes parameter)\n- Type-specific sanity checks (booleans, dates, buckets, etc.)\n- When to alert the user about suspicious results\n\n**Quick validation — check distinct values:**\n\nCall `get_data_from_fields` with:\n\n- `attributes`: `[\"\u003Centity>.\u003Cattribute_name>\"]`\n- `metrics`: `[\"COUNT(\u003Centity>.\u003Cattribute_name>)\"]` — forces aggregation, returning one row per distinct value\n\nThis lets you quickly inspect all distinct output values and their frequencies to confirm the attribute logic is correct (see the **query** skill's \"Getting Distinct Values\" tip for more details).\n\n---\n\n## Common Pitfalls to Avoid\n\n- **Unqualified column references.** `amount` will fail — write `orders.amount`.\n- **Using Aggregation attribute when a metric is better.** If it's a reusable KPI, use a metric.\n- **Aggregating from same-grain or higher-grain entity.** Only aggregate from higher-granularity (many-side) entities.\n","## Prerequisites\n\nBefore creating attributes, ensure you are on the correct workspace and branch. Use `get_session_workspace_and_branch` to check the current session context. For development work, create a branch with `create_workspace_branch` (the session switches automatically). See the `model-exploration` skill for the full workspace\u002Fbranch tool reference.\n\n---\n\n## Overview\n\nA Honeydew **calculated attribute** is a virtual, per-row column defined on an entity — analogous to an expression in a SQL `SELECT` clause.\nIt is evaluated once per row, not aggregated. In BI tools it surfaces as a **dimension** users can group, filter, and slice by.\n\nUse a calculated attribute when:\n\n- You need a reusable, governed column that doesn't exist verbatim in the source table (e.g. `net_price`, `customer_tier`, `order_month`)\n- The value should be consistent everywhere it's consumed, not recalculated ad-hoc in each dashboard\n- You want to expose a clean, business-friendly label for a raw or encoded column\n\nDo **not** use a calculated attribute for aggregations across rows — use a metric instead.\n\n---\n\n## Building the SQL Expression\n\n### Core Rules\n\n- **Use simple expressions** — easy to understand\n- **Use the SQL dialect of the connected data warehouse** (Snowflake, Databricks, or BigQuery)\n- **Use `entity.field` format** for all attribute\u002Fmetric references\n- **No joins or subqueries** — simple expressions only (window functions allowed)\n- **Use fully qualified column names** — `orders.amount`, not just `amount`\n- **Prefer ILIKE over LIKE** for case-insensitive matching\n\nSee [reference.md](reference.md) for: SQL functions, JSON\u002Fsemi-structured data, geography, data types, full YAML schema, attribute types, time grain, and format strings.\n\n---\n\n## Creation Methods\n\n### Primary: create_object with YAML\n\nCall `create_object` with `yaml_text`:\n\n```yaml\ntype: calculated_attribute\nentity: \u003Centity_name>\nname: \u003Csnake_case_name>\ndisplay_name: \u003CHuman Readable Name>\ndescription: |-\n  \u003Cbusiness description>\nowner: \u003Cowner_email_or_team>\ndatatype: string|number|float|bool|date|timestamp|time\nsql: |-\n  \u003CSQL expression>\nfolder: \u003Coptional folder path>\n```\n\n**Required fields:**\n\n- `type: calculated_attribute`\n- `entity` — the entity this attribute belongs to\n- `name` — snake_case identifier\n- `owner` — **CRITICAL: always set** (email or team name)\n- `datatype` — **CRITICAL: always set explicitly**\n- `sql` — the expression\n\n### Update: update_object\n\n1. Use `get_entity` or `search_model` (with `search_mode: EXACT`) to find the attribute's `object_key`.\n2. Call `update_object` with the full updated YAML (`yaml_text`) and the `object_key`.\n\n> **Minimal diff rule:** When updating, preserve the existing field order and formatting from the current YAML. Only change the fields you need to modify. Objects are versioned in git, so unnecessary reordering or reformatting creates noisy diffs.\n\n### After Creation\u002FUpdate: Display the UI Link\n\nAfter a successful `create_object` or `update_object` call, the response includes a `ui_url` field. **Always display this URL to the user** so they can quickly open the object in the Honeydew application.\n\n### Delete: delete_object\n\n1. Use `search_model` (with `search_mode: EXACT`) to find the attribute's `object_key`.\n2. Call `delete_object` with that `object_key`.\n\n---\n\n## Examples\n\nSee [examples.md](examples.md) for full worked examples covering: basic, boolean flag, grouping\u002Fbinning, multi-entity, date truncation, window function, running total, semi-structured JSON, safe division, update, and delete.\n\n---\n\n## Discovery Helpers\n\nUse these MCP tools to explore existing attributes:\n\n- `get_entity` — Get entity details including all attributes (filter by `__typename` for `CalcAttribute` or `DataSetAttribute`)\n- `get_field` — Get detailed info about a specific attribute by entity and field name\n- `search_model` — Search for attributes across the model by name (use `search_mode: EXACT` for known names, `OR` for broad discovery)\n- `list_entities` — List entities to identify where to anchor new attributes\n\n---\n\n## Documentation Lookup\n\nUse the `honeydew-docs` MCP tools to search the Honeydew documentation when:\n\n- You need warehouse-specific SQL function details not covered in `reference.md` (Snowflake, Databricks, BigQuery differences)\n- The user asks about advanced attribute types (multi-entity, aggregation) or when to use each\n- You need guidance on time grain configuration, format strings, or data type nuances\n- The user needs advanced modeling patterns for calculated attributes (e.g., complex bucketing, conditional logic, semi-structured data extraction)\n\nSearch for topics like: \"calculated attributes\", \"attribute types\", \"multi-entity attribute\", \"aggregation attribute\", \"time grain\", \"format strings\", \"advanced modeling\".\n\n---\n\n## Best Practices\n\n- **Reuse existing attributes — don't repeat logic.**\n  If a calculated attribute already exists on the entity (or you just created one), reference it by name\n  (`entity.attribute_name`) rather than inlining its SQL expression. This keeps definitions DRY and ensures changes propagate.\n- **Qualify every column reference** with the entity name: `orders.amount`, not `amount`.\n- **Set timegrain** on every date\u002Ftimestamp attribute.\n- **Hide raw \u002F intermediate columns** so they don't clutter BI tool field pickers.\n- **Use folder** to group related attributes.\n- **Prefer Multi-Entity over duplicating columns.** Reference related entities rather than copying definitions.\n- **Use DIV0 for division** to avoid divide-by-zero errors.\n- **Use ILIKE over LIKE** for case-insensitive string matching.\n\n---\n\n## MANDATORY: Validate After Creating\n\n**After creating ANY attribute, you MUST invoke the `validation` skill to test and validate results.**\n\nSee `validation` skill for:\n\n- How to execute attributes via `get_data_from_fields` (attributes go in the attributes parameter)\n- Type-specific sanity checks (booleans, dates, buckets, etc.)\n- When to alert the user about suspicious results\n\n**Quick validation — check distinct values:**\n\nCall `get_data_from_fields` with:\n\n- `attributes`: `[\"\u003Centity>.\u003Cattribute_name>\"]`\n- `metrics`: `[\"COUNT(\u003Centity>.\u003Cattribute_name>)\"]` — forces aggregation, returning one row per distinct value\n\nThis lets you quickly inspect all distinct output values and their frequencies to confirm the attribute logic is correct (see the **query** skill's \"Getting Distinct Values\" tip for more details).\n\n---\n\n## Common Pitfalls to Avoid\n\n- **Unqualified column references.** `amount` will fail — write `orders.amount`.\n- **Using Aggregation attribute when a metric is better.** If it's a reusable KPI, use a metric.\n- **Aggregating from same-grain or higher-grain entity.** Only aggregate from higher-granularity (many-side) entities.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fhoneydew-ai\u002Fhoneydew-ai-coding-agents-plugins\u002Fskills\u002Fattribute-creation",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill attribute-creation",{"tool":56,"command":57},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill attribute-creation",{"tool":59,"command":60},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill attribute-creation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fhoneydew-ai\u002Fhoneydew-ai-coding-agents-plugins\u002Fskills\u002Fattribute-creation\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"examples.md","REFERENCE","参考文档",3703,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fhoneydew-ai\u002Fhoneydew-ai-coding-agents-plugins\u002Fskills\u002Fattribute-creation\u002Fexamples.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"reference.md",6920,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fhoneydew-ai\u002Fhoneydew-ai-coding-agents-plugins\u002Fskills\u002Fattribute-creation\u002Freference.md",[75,85,93,101,109,117],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":84},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":84},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":84},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":84},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":84},"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",[],[]]