[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMDA5MGQFV4XQ778DM26WF":3,"skill-same:01M6MMDA5MGQFV4XQ778DM26WF":76},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":69},"01M6MMDA5MGQFV4XQ778DM26WF","runtype-templates",null,"Create, validate, or share distributable Runtype Full Product Object (FPO) templates with import-time variables and pending secrets, or install a product from a runtype.com example, a use.runtype.com\u002Fnow link, or a template URL.","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\u002Fruntypelabs\u002Fskills\u002Fskills\u002Fruntype-templates\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"runtype","runtype templates","templates","time","pending","object","true","Variables","URL","now","import","full","create","task","example","use","install","template","secrets","product","share","2026-11-10 10:12:30",false,"---\nname: runtype-templates\ndescription: 'Create, validate, or share distributable Runtype Full Product Object (FPO) templates with import-time variables and pending secrets, or install a product from a runtype.com example, a use.runtype.com\u002Fnow link, or a template URL.'\nuser-invocable: true\nargument-hint: '[FPO or template task]'\n---\n\n# Runtype Templates\n\nUse this skill when a Runtype product should become a portable Full Product Object (FPO)\ntemplate that another workspace, team, customer, or marketplace user can import. It also\ncovers installing a product from a shared example or template link.\n\n## Source of truth\n\nWhen the Runtype MCP server is available, read the schema docs before you write or\nvalidate a template.\n\nAlways read:\n\n- `get_platform_documentation(topic=\"types-fpo-template\")` for the template wrapper.\n- `get_platform_documentation(topic=\"types-fpo\")` for the wrapped `productObject`. Use\n  FPO version `2.0` for new templates.\n- `get_platform_documentation(topic=\"product-schema\")` for the JSON Schema of the\n  product object.\n\nRead these when the template contains that part:\n\n- Surfaces: `surface-types` and `types-surface-configs`.\n- Flows: `flow-step-types`.\n- Tools: `builtin-tools`, `orthogonal-tools`, and `external-tools`.\n\nFor prose guidance, call `search_documentation` for \"FPO templates\" or read the public\nguides: [FPO templates](https:\u002F\u002Fdocs.runtype.com\u002Fdeveloper-guides\u002Fguides\u002Ffpo-templates) and\n[Importing products](https:\u002F\u002Fdocs.runtype.com\u002Fdeveloper-guides\u002Fguides\u002Fimporting-products).\n\n## Template shape\n\nAn FPO template has three top-level keys:\n\n- `version`: the template format version, `\"1.0\"` or `\"1.1\"`. This is separate from\n  `productObject.version`, which is `\"2.0\"` for new templates.\n- `productObject`: the full product definition.\n- `template.variables`: the non-secret values the importer supplies.\n\nA template must declare at least one variable or at least one pending secret: a tool with\n`auth.setupRequired: true` and a non-empty `auth.secrets` array, a top-level\n`productObject.secrets[]` entry, or a `{{secret:KEY}}` reference anywhere in the product.\n\nUse variables for names, public URLs, recipient lists, selected models, and other\nnon-secret configuration. Every credential uses the pending-secret pattern.\n\n### Variables\n\nEach variable needs `key`, `label`, `inputType`, and `required`:\n\n```json\n{\n  \"key\": \"companyName\",\n  \"label\": \"Company name\",\n  \"inputType\": \"text\",\n  \"required\": true,\n  \"defaultValue\": \"Acme\"\n}\n```\n\n- `inputType` is one of `text`, `textarea`, `url`, `secret`, `select`, `number`, or\n  `boolean`.\n- A `select` variable needs a non-empty `options` array of `{ \"label\", \"value\" }`. Only\n  `select` variables can have `options`.\n- A template can declare up to 50 variables.\n- Set defaults with `defaultValue`. Inline `{{key|default}}` syntax is rejected.\n- When a string field is exactly `{{key}}` and the variable is `number` or `boolean`, the\n  field keeps that type. Every other substitution produces a string.\n- A typed field (a URL such as `externalConfig.endpoint`, a number such as\n  `config.loopConfig.maxTurns`, an enum, or a datetime such as a schedule's `runAt`) can\n  hold a variable. Validation checks such fields after substitution, so a bad default or\n  import value fails there instead.\n\n### Runtime tokens and template variables\n\nImport treats every bare `{{name}}` in `productObject` as a template variable. That\nincludes runtime tokens such as a step output in a prompt. Only these references pass\nthrough to run time without a declaration:\n\n- `{{secret:KEY}}`\n- `{{flow:name}}`, which resolves to the flow variable `name` at run time\n- System and message variables, such as `{{_record.metadata.field}}`, `{{_now}}`,\n  `{{userMessage}}`, and `{{messages}}`\n- Host-resolved variables: `{{_identity.token}}` in a tool or MCP header, and\n  `{{_agent.*}}` \u002F `{{_organization.id}}` in a memory `profileTemplate`, including a\n  fallback such as `{{_agent.alias || \"live\"}}`\n\nWhen you turn a working product into a template, rewrite runtime flow tokens with the\n`flow:` prefix. For example, change `Summarize {{research}}` to\n`Summarize {{flow:research}}`. Do not declare a runtime token as a template variable,\nbecause import replaces it with a fixed value.\n\nIf a field cannot take the `flow:` prefix, such as a Liquid template body, declare a\ntemplate variable whose `defaultValue` is the runtime text, and reference that variable in\nthe field.\n\n### Optional bundled resources\n\nA template can also ship these `productObject` arrays. Import creates each resource:\n\n- `schedules[]`: cron or one-time runs that target a capability through `capabilityId`.\n  A scheduled capability does not need a `type: \"schedule\"` surface.\n- `evals[]`: eval suites with their cases.\n- `skills[]`: agent skills, bound to agent capabilities through `bindTo`.\n\nFor the field tables, see the FPO templates guide.\n\n## Pending secrets\n\nUse this pattern for every credential:\n\n1. Declare the key on the target tool's `auth.secrets` array.\n2. Set `auth.setupRequired: true`, plus `auth.type` and `auth.setupInstructions`.\n3. Reference the key in the tool config as `{{secret:KEY}}`.\n4. Leave the value out of the template. Import creates the secret as unconfigured, and the\n   importer fills it in after import.\n\n```json\n{\n  \"config\": {\n    \"headers\": { \"Authorization\": \"Bearer {{secret:ACME_API_KEY}}\" }\n  },\n  \"auth\": {\n    \"type\": \"api_key\",\n    \"setupRequired\": true,\n    \"secrets\": [{ \"key\": \"ACME_API_KEY\", \"required\": true }],\n    \"setupInstructions\": {\n      \"summary\": \"Add your Acme API key.\",\n      \"steps\": [\"Create an API key in Acme.\", \"Add it as a secret after import.\"]\n    }\n  }\n}\n```\n\nEach `auth.secrets` entry is an object with `key` and `required`, not a bare string.\n\nWhen the credential belongs to the product rather than one tool (an MCP server header, an\nexternal agent's auth, a model key), declare it in top-level `productObject.secrets[]`\n(`{ \"id\", \"key\", \"description\"?, \"required\"? }`) and reference it as `{{secret:KEY}}`\nwherever it is used. Import lists it with the other pending secrets.\n\nDo not use a variable with `inputType: \"secret\"` for credentials. Import writes that value\ninto the product object as plain text. A `secret` variable cannot have a `defaultValue`.\n\n## Validation workflow\n\n1. Validate the template document with `runtype validate-product .\u002Ftemplate.json --template`\n   or `POST https:\u002F\u002Fapi.runtype.com\u002Fv1\u002Fpublic\u002Fproducts\u002Fvalidate-template`. Fix every error,\n   such as `UNDECLARED_TEMPLATE_VARIABLE`, `INLINE_TEMPLATE_DEFAULT_NOT_ALLOWED`, and\n   `DUPLICATE_TEMPLATE_VARIABLE`. Review warnings such as `UNUSED_TEMPLATE_VARIABLE` and\n   `TEMPLATE_VARIABLE_SECRET_IS_UNSAFE`.\n2. Resolve template defaults, or supply test values for required variables.\n3. Run `validate_product` on the resolved product object.\n4. Run the focused validators for changed parts: `validate_product_tool`,\n   `validate_product_flow`, `validate_product_agent`, and `validate_product_surface`.\n5. Confirm that every route references a real capability id.\n6. Confirm that every secret reference has a matching pending-secret declaration.\n7. Confirm that importer-visible variables are few and meaningful.\n\n## Share a template\n\n1. Host the template JSON at a public HTTPS URL, such as a raw GitHub file URL.\n2. URL-encode that URL and share `https:\u002F\u002Fuse.runtype.com\u002Fnow?from=ENCODED_TEMPLATE_URL`.\n3. Optional: Prefill a variable with `&templateParam%3AVARIABLE_KEY=VALUE`. The import page\n   ignores prefilled values for secret variables.\n4. Optional: Add a button to a repository `README`:\n\n   ```md\n   [Deploy to Runtype](https:\u002F\u002Fuse.runtype.com\u002Fnow?from=https%3A%2F%2Fexample.com%2FYOUR_TEMPLATE.json)\n   ```\n\n5. Test the link: pass it to `create_product_from_example` as `url` and confirm the product\n   is created.\n\n## Set up a product from a link\n\nWhen a user provides a `use.runtype.com\u002Fnow?...` link, a `runtype.com\u002Fexamples\u002F\u003Cslug>` page,\nor a direct FPO or template JSON URL, do not open the dashboard page, which requires\nsign-in. Pass the original link to `create_product_from_example` as `url`, or pass a known\n`slug` from `list_example_templates`.\n\n1. Supply import-time values in the tool's `variables` argument. Omitted keys fall back to\n   `templateParam` values in the link, then to template defaults. If a required variable\n   still has no value, the tool returns the variable specs and creates nothing. Ask the\n   user for those values, then call the tool again with them in `variables`.\n2. Draft examples require `allow_draft: true`. Use it only when the user intends to install\n   that draft.\n3. Call `get_product_setup` with the created product id. Complete the steps you can\n   automate, and give the user the remaining secret, OAuth, or surface-install links. Never\n   ask the user to paste secret values in chat. Give them the dashboard link from\n   `get_product_setup` or `get_secret_intake_manifest`, then confirm with `check_secrets`.\n4. Test the product at its user-facing layer. For an agent, call `execute_agent` with a\n   `messages` array of `{ \"role\": \"user\", \"content\": \"...\" }` turns.\n\nThe tool rejects some links:\n\n- A link with `?import=` or `?sessionId=` points to a temporary import preview. Ask for the\n  original source: an example slug, a `?session=` link, or the document URL.\n- A link with `?template=` points to a built-in dashboard template. Open it in the\n  dashboard, or build the product with `create_product`.\n- A `\u002Fnow` link with none of `example`, `session`, `templateUrl`, or `from` has nothing to\n  import. Ask the user for the full link.\n\n## Anti-patterns\n\n- Hardcoded API keys, tokens, client secrets, or bearer values.\n- Too many variables. Every variable adds setup work for the importer.\n- Workspace ids, runtime ids, or surface keys as template variables.\n- Bare runtime tokens such as `{{research}}` left in the product object.\n- Partial product schemas with a note that validation still needs work.\n- Templates for one-off private account updates. Use the `runtype-admin` skill instead.\n\nFor platform scoping and account setup, use the `runtype` skill.\n","# Runtype Templates\n\nUse this skill when a Runtype product should become a portable Full Product Object (FPO)\ntemplate that another workspace, team, customer, or marketplace user can import. It also\ncovers installing a product from a shared example or template link.\n\n## Source of truth\n\nWhen the Runtype MCP server is available, read the schema docs before you write or\nvalidate a template.\n\nAlways read:\n\n- `get_platform_documentation(topic=\"types-fpo-template\")` for the template wrapper.\n- `get_platform_documentation(topic=\"types-fpo\")` for the wrapped `productObject`. Use\n  FPO version `2.0` for new templates.\n- `get_platform_documentation(topic=\"product-schema\")` for the JSON Schema of the\n  product object.\n\nRead these when the template contains that part:\n\n- Surfaces: `surface-types` and `types-surface-configs`.\n- Flows: `flow-step-types`.\n- Tools: `builtin-tools`, `orthogonal-tools`, and `external-tools`.\n\nFor prose guidance, call `search_documentation` for \"FPO templates\" or read the public\nguides: [FPO templates](https:\u002F\u002Fdocs.runtype.com\u002Fdeveloper-guides\u002Fguides\u002Ffpo-templates) and\n[Importing products](https:\u002F\u002Fdocs.runtype.com\u002Fdeveloper-guides\u002Fguides\u002Fimporting-products).\n\n## Template shape\n\nAn FPO template has three top-level keys:\n\n- `version`: the template format version, `\"1.0\"` or `\"1.1\"`. This is separate from\n  `productObject.version`, which is `\"2.0\"` for new templates.\n- `productObject`: the full product definition.\n- `template.variables`: the non-secret values the importer supplies.\n\nA template must declare at least one variable or at least one pending secret: a tool with\n`auth.setupRequired: true` and a non-empty `auth.secrets` array, a top-level\n`productObject.secrets[]` entry, or a `{{secret:KEY}}` reference anywhere in the product.\n\nUse variables for names, public URLs, recipient lists, selected models, and other\nnon-secret configuration. Every credential uses the pending-secret pattern.\n\n### Variables\n\nEach variable needs `key`, `label`, `inputType`, and `required`:\n\n```json\n{\n  \"key\": \"companyName\",\n  \"label\": \"Company name\",\n  \"inputType\": \"text\",\n  \"required\": true,\n  \"defaultValue\": \"Acme\"\n}\n```\n\n- `inputType` is one of `text`, `textarea`, `url`, `secret`, `select`, `number`, or\n  `boolean`.\n- A `select` variable needs a non-empty `options` array of `{ \"label\", \"value\" }`. Only\n  `select` variables can have `options`.\n- A template can declare up to 50 variables.\n- Set defaults with `defaultValue`. Inline `{{key|default}}` syntax is rejected.\n- When a string field is exactly `{{key}}` and the variable is `number` or `boolean`, the\n  field keeps that type. Every other substitution produces a string.\n- A typed field (a URL such as `externalConfig.endpoint`, a number such as\n  `config.loopConfig.maxTurns`, an enum, or a datetime such as a schedule's `runAt`) can\n  hold a variable. Validation checks such fields after substitution, so a bad default or\n  import value fails there instead.\n\n### Runtime tokens and template variables\n\nImport treats every bare `{{name}}` in `productObject` as a template variable. That\nincludes runtime tokens such as a step output in a prompt. Only these references pass\nthrough to run time without a declaration:\n\n- `{{secret:KEY}}`\n- `{{flow:name}}`, which resolves to the flow variable `name` at run time\n- System and message variables, such as `{{_record.metadata.field}}`, `{{_now}}`,\n  `{{userMessage}}`, and `{{messages}}`\n- Host-resolved variables: `{{_identity.token}}` in a tool or MCP header, and\n  `{{_agent.*}}` \u002F `{{_organization.id}}` in a memory `profileTemplate`, including a\n  fallback such as `{{_agent.alias || \"live\"}}`\n\nWhen you turn a working product into a template, rewrite runtime flow tokens with the\n`flow:` prefix. For example, change `Summarize {{research}}` to\n`Summarize {{flow:research}}`. Do not declare a runtime token as a template variable,\nbecause import replaces it with a fixed value.\n\nIf a field cannot take the `flow:` prefix, such as a Liquid template body, declare a\ntemplate variable whose `defaultValue` is the runtime text, and reference that variable in\nthe field.\n\n### Optional bundled resources\n\nA template can also ship these `productObject` arrays. Import creates each resource:\n\n- `schedules[]`: cron or one-time runs that target a capability through `capabilityId`.\n  A scheduled capability does not need a `type: \"schedule\"` surface.\n- `evals[]`: eval suites with their cases.\n- `skills[]`: agent skills, bound to agent capabilities through `bindTo`.\n\nFor the field tables, see the FPO templates guide.\n\n## Pending secrets\n\nUse this pattern for every credential:\n\n1. Declare the key on the target tool's `auth.secrets` array.\n2. Set `auth.setupRequired: true`, plus `auth.type` and `auth.setupInstructions`.\n3. Reference the key in the tool config as `{{secret:KEY}}`.\n4. Leave the value out of the template. Import creates the secret as unconfigured, and the\n   importer fills it in after import.\n\n```json\n{\n  \"config\": {\n    \"headers\": { \"Authorization\": \"Bearer {{secret:ACME_API_KEY}}\" }\n  },\n  \"auth\": {\n    \"type\": \"api_key\",\n    \"setupRequired\": true,\n    \"secrets\": [{ \"key\": \"ACME_API_KEY\", \"required\": true }],\n    \"setupInstructions\": {\n      \"summary\": \"Add your Acme API key.\",\n      \"steps\": [\"Create an API key in Acme.\", \"Add it as a secret after import.\"]\n    }\n  }\n}\n```\n\nEach `auth.secrets` entry is an object with `key` and `required`, not a bare string.\n\nWhen the credential belongs to the product rather than one tool (an MCP server header, an\nexternal agent's auth, a model key), declare it in top-level `productObject.secrets[]`\n(`{ \"id\", \"key\", \"description\"?, \"required\"? }`) and reference it as `{{secret:KEY}}`\nwherever it is used. Import lists it with the other pending secrets.\n\nDo not use a variable with `inputType: \"secret\"` for credentials. Import writes that value\ninto the product object as plain text. A `secret` variable cannot have a `defaultValue`.\n\n## Validation workflow\n\n1. Validate the template document with `runtype validate-product .\u002Ftemplate.json --template`\n   or `POST https:\u002F\u002Fapi.runtype.com\u002Fv1\u002Fpublic\u002Fproducts\u002Fvalidate-template`. Fix every error,\n   such as `UNDECLARED_TEMPLATE_VARIABLE`, `INLINE_TEMPLATE_DEFAULT_NOT_ALLOWED`, and\n   `DUPLICATE_TEMPLATE_VARIABLE`. Review warnings such as `UNUSED_TEMPLATE_VARIABLE` and\n   `TEMPLATE_VARIABLE_SECRET_IS_UNSAFE`.\n2. Resolve template defaults, or supply test values for required variables.\n3. Run `validate_product` on the resolved product object.\n4. Run the focused validators for changed parts: `validate_product_tool`,\n   `validate_product_flow`, `validate_product_agent`, and `validate_product_surface`.\n5. Confirm that every route references a real capability id.\n6. Confirm that every secret reference has a matching pending-secret declaration.\n7. Confirm that importer-visible variables are few and meaningful.\n\n## Share a template\n\n1. Host the template JSON at a public HTTPS URL, such as a raw GitHub file URL.\n2. URL-encode that URL and share `https:\u002F\u002Fuse.runtype.com\u002Fnow?from=ENCODED_TEMPLATE_URL`.\n3. Optional: Prefill a variable with `&templateParam%3AVARIABLE_KEY=VALUE`. The import page\n   ignores prefilled values for secret variables.\n4. Optional: Add a button to a repository `README`:\n\n   ```md\n   [Deploy to Runtype](https:\u002F\u002Fuse.runtype.com\u002Fnow?from=https%3A%2F%2Fexample.com%2FYOUR_TEMPLATE.json)\n   ```\n\n5. Test the link: pass it to `create_product_from_example` as `url` and confirm the product\n   is created.\n\n## Set up a product from a link\n\nWhen a user provides a `use.runtype.com\u002Fnow?...` link, a `runtype.com\u002Fexamples\u002F\u003Cslug>` page,\nor a direct FPO or template JSON URL, do not open the dashboard page, which requires\nsign-in. Pass the original link to `create_product_from_example` as `url`, or pass a known\n`slug` from `list_example_templates`.\n\n1. Supply import-time values in the tool's `variables` argument. Omitted keys fall back to\n   `templateParam` values in the link, then to template defaults. If a required variable\n   still has no value, the tool returns the variable specs and creates nothing. Ask the\n   user for those values, then call the tool again with them in `variables`.\n2. Draft examples require `allow_draft: true`. Use it only when the user intends to install\n   that draft.\n3. Call `get_product_setup` with the created product id. Complete the steps you can\n   automate, and give the user the remaining secret, OAuth, or surface-install links. Never\n   ask the user to paste secret values in chat. Give them the dashboard link from\n   `get_product_setup` or `get_secret_intake_manifest`, then confirm with `check_secrets`.\n4. Test the product at its user-facing layer. For an agent, call `execute_agent` with a\n   `messages` array of `{ \"role\": \"user\", \"content\": \"...\" }` turns.\n\nThe tool rejects some links:\n\n- A link with `?import=` or `?sessionId=` points to a temporary import preview. Ask for the\n  original source: an example slug, a `?session=` link, or the document URL.\n- A link with `?template=` points to a built-in dashboard template. Open it in the\n  dashboard, or build the product with `create_product`.\n- A `\u002Fnow` link with none of `example`, `session`, `templateUrl`, or `from` has nothing to\n  import. Ask the user for the full link.\n\n## Anti-patterns\n\n- Hardcoded API keys, tokens, client secrets, or bearer values.\n- Too many variables. Every variable adds setup work for the importer.\n- Workspace ids, runtime ids, or surface keys as template variables.\n- Bare runtime tokens such as `{{research}}` left in the product object.\n- Partial product schemas with a note that validation still needs work.\n- Templates for one-off private account updates. Use the `runtype-admin` skill instead.\n\nFor platform scoping and account setup, use the `runtype` skill.\n",{"name":5,"description":7,"argument-hint":45,"user-invocable":46},"[FPO or template task]",true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fruntypelabs\u002Fskills\u002Fskills\u002Fruntype-templates",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":58,"prompt":68,"zipAvailable":46},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill runtype-templates",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill runtype-templates",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill runtype-templates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fruntypelabs\u002Fskills\u002Fskills\u002Fruntype-templates\u002FSKILL.md",[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",539,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fruntypelabs\u002Fskills\u002Fskills\u002Fruntype-templates\u002Fagents\u002Fopenai.yaml",[77,87,95,103,111,119],{"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":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":86},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":86},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":86},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":86},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":86},"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",[],[]]