[{"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",1566,"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",483,"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-13 02:16:32",{"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,85,92,99,126,151],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":84},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":84},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":40},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":40},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[133,134,135,121,136,137,138,139,140,141,142,143,144,145,111,146,147,148,149,150],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":168,"publishedAt":40},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[157,162,165],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":163,"categoryName":164,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":166,"categoryName":167,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000010","后端与接口",[153,27,169,170,171,172,173,147,174,112,175,176,177,178,117,179,180,181,182,183],"Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]