[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DWSKJ5215FDYSZQK7M3T7S":3,"skill-same:01M6DWSKJ5215FDYSZQK7M3T7S":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6DWSKJ5215FDYSZQK7M3T7S","tap-capability-authoring",null,"Create Octomind capabilities: config.toml triggers, provider files, MCP server wiring, version pins, symlinks. Use when editing capabilities\u002F\u003Cname>\u002F files.","Muvon\u002Foctomind-tap","Muvon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25336907?v=4","01M6DWA4KTRX4J73CW5CECKAD0","01M6DWA4QSWFGYE6WDMAMFF1WE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-capability-authoring\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"tap capability authoring","authoring","tap","capability","create","wiring","when","triggers","toml","editing","provider","config","scripts","server","with scripts","capabilities","mcp server","MCP","files","checkout","2026-11-10 10:12:30",false,"---\nname: tap-capability-authoring\ntitle: \"Capability Authoring\"\ndescription: \"Create Octomind capabilities: config.toml triggers, provider files, MCP server wiring, version pins, symlinks. Use when editing capabilities\u002F\u003Cname>\u002F files.\"\nlicense: Apache-2.0\ncompatibility: \"Requires: an Octomind tap checkout with scripts\u002Flint-capabilities.sh and scripts\u002Fsetup-symlinks.sh.\"\ndomains: octomind\n---\n\n## Overview\n\nA capability is the layer between agents and MCP servers or toolchains: agents declare what they need (`capabilities = [\"websearch\"]`), the capability supplies the wiring. This skill covers the two files every capability needs, provider wiring, registration, and validation. Use it when an agent needs a tool no existing capability covers, or when adding a provider to an existing one.\n\n## Mental model\n\nOne capability, two kinds of file:\n\n- `config.toml` — routing metadata: required `triggers` (how users phrase the need) and an optional `domains` gate. It drives auto-activation, `capability discover`, and the tap's embedding model.\n- `\u003Cprovider>.toml` — how one tool fulfils the capability: `[deps]`, `[roles.mcp]`, `[[mcp.servers]]`. `default.toml` is a symlink to the active provider; users switch with `[capabilities] \u003Cname> = \"\u003Cprovider>\"` in their config.\n\nAgents never see providers, so implementations swap without touching agents.\n\n## Rules\n\n### Directory layout\n\n```\ncapabilities\u002F\u003Cname>\u002F\n  config.toml          triggers (+ optional domains)\n  \u003Cprovider-a>.toml    provider wiring\n  \u003Cprovider-b>.toml    optional alternative\n  default.toml  → \u003Cprovider-a>.toml\n```\n\n`default.toml` is always a symlink, except for the built-ins `core`, `agent`, and `orchestration`, which have real files and no `link` entries.\n\n### config.toml\n\n```toml\n# capabilities\u002F\u003Cname>\u002Fconfig.toml\ntriggers = [\n  \"search the web for recent news on this\",\n  \"look up the latest docs online\",\n  \"find sources about this topic\",\n]\n# domains = [\"developer\"]   # omit = available in every domain\n```\n\nAuthor 5–15 short, concrete phrasings in the user's voice, not abstract descriptions. Use vocabulary specific to this capability; sibling capabilities that share generic verbs (all `messaging-*`, all `legal-*`) end in near-ties and the runtime abstains. A capability without `config.toml` or with empty triggers fails to resolve. Changing triggers changes the embedding model's training data — see the `tap-model-training` skill.\n\n### Provider file\n\n```toml\n# capabilities\u002F\u003Cname>\u002F\u003Cprovider>.toml\n# Capability: \u003Cname>\n# Provider: \u003Cprovider>\n# Title: Short Capability Title (5–60 chars)\n# Description: What this provider supplies (20–160 chars). Requires FOO_API_KEY.\n\n[deps]\nrequire = [\"org\u002Ftool\"]              # each needs deps\u002F\u003Corg>\u002F\u003Ctool>.sh + .md\n\n[roles.mcp]\nserver_refs = [\"servername\"]\nallowed_tools = [\"servername:*\"]\n\n[[mcp.servers]]\nname = \"servername\"\ntype = \"stdio\"                      # stdio | http | builtin\ncommand = \"npx\"                     # spawned directly, no shell expansion\nargs = [\"-y\", \"some-mcp@1.4.2\"]     # exact version pin\ntimeout_seconds = 60                # 1–3600, idle deadline reset by MCP progress\ntools = []                          # required; [] = all\nenv = { FOO_API_KEY = \"{{ENV:FOO_API_KEY}}\" }\n```\n\n- Sections are optional per kind: deps-only (toolchains like `programming-python`), MCP-only, or both.\n- The `# Title:`\u002F`# Description:` header is what `capability list` and `discover` show; mention required env vars there. The default provider's description (the file `default.toml` points to) is also the capability page's search snippet on octomind.run, so it must be 120–155 chars (`lint-capabilities.sh` checks it).\n- `allowed_tools`: `server:*` exposes everything; `server:tool` and trailing-`*` prefixes narrow it.\n- Built-in server refs (`core`, `octofs`, `agent`, `octocode`) need no `[[mcp.servers]]` block; every other `server_refs` entry must have one with the same `name`.\n- stdio servers take `env` (passed to the child) and optional `cwd`; http servers take `url` and optional `headers` (e.g. `Authorization = \"Bearer {{ENV:TOKEN}}\"`).\n- `{{ENV:KEY}}` in `env` or `headers` resolves from the environment at spawn time. While any key the wiring references is unset, every load path skips the capability: an agent that lists it starts without its tools (no prompt), auto-activation passes it over, and `enable` refuses it. Use the exact variable name the server reads. Literal values in `env` are passed through as-is.\n- `{{INPUT:KEY}}` is a text substitution from the user's persistent input store at manifest load; prefer `{{ENV:KEY}}` for anything a server reads from its environment.\n- `bin\u002Fload` parses capability files with a simple regex TOML subset: keep arrays on one line and avoid inline nesting beyond what the examples show.\n\n### Version pins\n\nEvery registry-launched server (`npx`, `uvx`, including inside `sh -c`) pins an exact version (`pkg@X.Y.Z`, `pkg==X.Y.Z`), so a registry publish never changes what users run. `lint-capabilities.sh` enforces presence offline; `scripts\u002Fmcp-versions.sh check|update|test` handles drift and live MCP handshakes. Keep a deliberate older pin with a `# mcp-versions: hold \u003Cpackage>` comment and the reason beside it; `update` leaves it alone.\n\n### Registration\n\nAdd both to `scripts\u002Fsetup-symlinks.sh`:\n\n```bash\nlink \"my-capability\" \"provider.toml\"\nDECLARED=( ... \"my-capability\" )\n```\n\nThen run `bash scripts\u002Fsetup-symlinks.sh` — it force-creates links, exits 1 on a missing provider file, and warns about undeclared directories.\n\n### Dep scripts\n\nEvery `require = [\"\u003Corg>\u002F\u003Ctool>\"]` needs `deps\u002F\u003Corg>\u002F\u003Ctool>.sh` plus a companion `.md`. `type: mcp` makes a server launchable (ensures `npx`\u002F`uvx`), `type: dep` installs a CLI used directly. Load the `tap-deps-authoring` skill to write them.\n\n### Creation checklist\n\n1. `capabilities\u002F\u003Cname>\u002Fconfig.toml` with triggers (and `domains` if domain-specific).\n2. `capabilities\u002F\u003Cname>\u002F\u003Cprovider>.toml` with header, wiring, pins, env.\n3. Dep scripts and companion docs for every `require` entry.\n4. `link` + `DECLARED` entries, then `bash scripts\u002Fsetup-symlinks.sh`.\n5. `bash scripts\u002Flint-capabilities.sh capabilities\u002F\u003Cname>`, `bash scripts\u002Flint-deps.sh deps\u002F\u003Corg>\u002F\u003Ctool>.sh`, `bash scripts\u002Fvalidate-capabilities.sh`.\n6. `scripts\u002Fmcp-versions.sh test \u003Cname>` for npx\u002Fuvx servers (missing-credential errors are fine if the server speaks MCP).\n7. Reference `\"\u003Cname>\"` from agents; retrain the embedding model when triggers changed.\n\n## Examples\n\n### Example 1: MCP capability with an API key\n\n```toml\n# capabilities\u002Fwebsearch\u002Ftavily.toml\n# Capability: websearch\n# Provider: tavily\n# Title: Web Search (Tavily)\n# Description: Web search, content extraction, crawling, and site mapping via the Tavily API.\n\n[deps]\nrequire = [\"tavily-ai\u002Ftavily\"]\n\n[roles.mcp]\nserver_refs = [\"tavily\"]\nallowed_tools = [\"tavily_search\", \"tavily_extract\", \"tavily_crawl\", \"tavily_map\", \"tavily_research\"]\n\n[[mcp.servers]]\nname = \"tavily\"\ntype = \"stdio\"\ncommand = \"npx\"\nargs = [\"-y\", \"tavily-mcp@0.2.22\"]\ntimeout_seconds = 60\nenv = { TAVILY_API_KEY = \"{{ENV:TAVILY_API_KEY}}\" }\ntools = []\n```\n\nBare tool names in `allowed_tools` narrow the surface to exactly those tools.\n\n### Example 2: deps-only toolchain\n\n```toml\n# capabilities\u002Fprogramming-python\u002Fuv.toml\n# Capability: programming-python\n# Provider: uv\n# Title: Python Runtime via uv\n# Description: Python runtime and package management via uv and uvx.\n\n[deps]\nrequire = [\"astral-sh\u002Fuv\"]\n```\n\n### Example 3: common mistake — secret as an argument\n\n❌ `args = [\"-y\", \"some-mcp@1.0.0\", \"--api-key\", \"{{INPUT:KEY}}\"]` — the secret shows up in process listings and the capability is never env-gated.\n\n✅ `env = { SOME_API_KEY = \"{{ENV:SOME_API_KEY}}\" }` — delivered to the child, and auto-activation waits until the key exists.\n\n## Checklist\n\n- [ ] `config.toml` has 5–15 concrete, capability-specific triggers?\n- [ ] Provider header has Title, Description, and required env vars?\n- [ ] Every non-built-in `server_refs` entry has a matching `[[mcp.servers]]` block with `timeout_seconds` and `tools`?\n- [ ] npx\u002Fuvx servers pinned to an exact version?\n- [ ] Secrets passed via `env`\u002F`headers` with `{{ENV:KEY}}` using the server's exact variable name?\n- [ ] `link` and `DECLARED` updated; `setup-symlinks.sh`, `lint-capabilities.sh`, `lint-deps.sh`, `validate-capabilities.sh` all pass?\n\n## References\n\n- `templates\u002Fcapability.toml`, `templates\u002Fcapability-config.toml` — canonical templates\n- `scripts\u002Fsetup-symlinks.sh` — default provider links\n- `scripts\u002Fmcp-versions.sh` — pin drift, updates, smoke tests\n- `tap-deps-authoring` skill — dep scripts\n","## Overview\n\nA capability is the layer between agents and MCP servers or toolchains: agents declare what they need (`capabilities = [\"websearch\"]`), the capability supplies the wiring. This skill covers the two files every capability needs, provider wiring, registration, and validation. Use it when an agent needs a tool no existing capability covers, or when adding a provider to an existing one.\n\n## Mental model\n\nOne capability, two kinds of file:\n\n- `config.toml` — routing metadata: required `triggers` (how users phrase the need) and an optional `domains` gate. It drives auto-activation, `capability discover`, and the tap's embedding model.\n- `\u003Cprovider>.toml` — how one tool fulfils the capability: `[deps]`, `[roles.mcp]`, `[[mcp.servers]]`. `default.toml` is a symlink to the active provider; users switch with `[capabilities] \u003Cname> = \"\u003Cprovider>\"` in their config.\n\nAgents never see providers, so implementations swap without touching agents.\n\n## Rules\n\n### Directory layout\n\n```\ncapabilities\u002F\u003Cname>\u002F\n  config.toml          triggers (+ optional domains)\n  \u003Cprovider-a>.toml    provider wiring\n  \u003Cprovider-b>.toml    optional alternative\n  default.toml  → \u003Cprovider-a>.toml\n```\n\n`default.toml` is always a symlink, except for the built-ins `core`, `agent`, and `orchestration`, which have real files and no `link` entries.\n\n### config.toml\n\n```toml\n# capabilities\u002F\u003Cname>\u002Fconfig.toml\ntriggers = [\n  \"search the web for recent news on this\",\n  \"look up the latest docs online\",\n  \"find sources about this topic\",\n]\n# domains = [\"developer\"]   # omit = available in every domain\n```\n\nAuthor 5–15 short, concrete phrasings in the user's voice, not abstract descriptions. Use vocabulary specific to this capability; sibling capabilities that share generic verbs (all `messaging-*`, all `legal-*`) end in near-ties and the runtime abstains. A capability without `config.toml` or with empty triggers fails to resolve. Changing triggers changes the embedding model's training data — see the `tap-model-training` skill.\n\n### Provider file\n\n```toml\n# capabilities\u002F\u003Cname>\u002F\u003Cprovider>.toml\n# Capability: \u003Cname>\n# Provider: \u003Cprovider>\n# Title: Short Capability Title (5–60 chars)\n# Description: What this provider supplies (20–160 chars). Requires FOO_API_KEY.\n\n[deps]\nrequire = [\"org\u002Ftool\"]              # each needs deps\u002F\u003Corg>\u002F\u003Ctool>.sh + .md\n\n[roles.mcp]\nserver_refs = [\"servername\"]\nallowed_tools = [\"servername:*\"]\n\n[[mcp.servers]]\nname = \"servername\"\ntype = \"stdio\"                      # stdio | http | builtin\ncommand = \"npx\"                     # spawned directly, no shell expansion\nargs = [\"-y\", \"some-mcp@1.4.2\"]     # exact version pin\ntimeout_seconds = 60                # 1–3600, idle deadline reset by MCP progress\ntools = []                          # required; [] = all\nenv = { FOO_API_KEY = \"{{ENV:FOO_API_KEY}}\" }\n```\n\n- Sections are optional per kind: deps-only (toolchains like `programming-python`), MCP-only, or both.\n- The `# Title:`\u002F`# Description:` header is what `capability list` and `discover` show; mention required env vars there. The default provider's description (the file `default.toml` points to) is also the capability page's search snippet on octomind.run, so it must be 120–155 chars (`lint-capabilities.sh` checks it).\n- `allowed_tools`: `server:*` exposes everything; `server:tool` and trailing-`*` prefixes narrow it.\n- Built-in server refs (`core`, `octofs`, `agent`, `octocode`) need no `[[mcp.servers]]` block; every other `server_refs` entry must have one with the same `name`.\n- stdio servers take `env` (passed to the child) and optional `cwd`; http servers take `url` and optional `headers` (e.g. `Authorization = \"Bearer {{ENV:TOKEN}}\"`).\n- `{{ENV:KEY}}` in `env` or `headers` resolves from the environment at spawn time. While any key the wiring references is unset, every load path skips the capability: an agent that lists it starts without its tools (no prompt), auto-activation passes it over, and `enable` refuses it. Use the exact variable name the server reads. Literal values in `env` are passed through as-is.\n- `{{INPUT:KEY}}` is a text substitution from the user's persistent input store at manifest load; prefer `{{ENV:KEY}}` for anything a server reads from its environment.\n- `bin\u002Fload` parses capability files with a simple regex TOML subset: keep arrays on one line and avoid inline nesting beyond what the examples show.\n\n### Version pins\n\nEvery registry-launched server (`npx`, `uvx`, including inside `sh -c`) pins an exact version (`pkg@X.Y.Z`, `pkg==X.Y.Z`), so a registry publish never changes what users run. `lint-capabilities.sh` enforces presence offline; `scripts\u002Fmcp-versions.sh check|update|test` handles drift and live MCP handshakes. Keep a deliberate older pin with a `# mcp-versions: hold \u003Cpackage>` comment and the reason beside it; `update` leaves it alone.\n\n### Registration\n\nAdd both to `scripts\u002Fsetup-symlinks.sh`:\n\n```bash\nlink \"my-capability\" \"provider.toml\"\nDECLARED=( ... \"my-capability\" )\n```\n\nThen run `bash scripts\u002Fsetup-symlinks.sh` — it force-creates links, exits 1 on a missing provider file, and warns about undeclared directories.\n\n### Dep scripts\n\nEvery `require = [\"\u003Corg>\u002F\u003Ctool>\"]` needs `deps\u002F\u003Corg>\u002F\u003Ctool>.sh` plus a companion `.md`. `type: mcp` makes a server launchable (ensures `npx`\u002F`uvx`), `type: dep` installs a CLI used directly. Load the `tap-deps-authoring` skill to write them.\n\n### Creation checklist\n\n1. `capabilities\u002F\u003Cname>\u002Fconfig.toml` with triggers (and `domains` if domain-specific).\n2. `capabilities\u002F\u003Cname>\u002F\u003Cprovider>.toml` with header, wiring, pins, env.\n3. Dep scripts and companion docs for every `require` entry.\n4. `link` + `DECLARED` entries, then `bash scripts\u002Fsetup-symlinks.sh`.\n5. `bash scripts\u002Flint-capabilities.sh capabilities\u002F\u003Cname>`, `bash scripts\u002Flint-deps.sh deps\u002F\u003Corg>\u002F\u003Ctool>.sh`, `bash scripts\u002Fvalidate-capabilities.sh`.\n6. `scripts\u002Fmcp-versions.sh test \u003Cname>` for npx\u002Fuvx servers (missing-credential errors are fine if the server speaks MCP).\n7. Reference `\"\u003Cname>\"` from agents; retrain the embedding model when triggers changed.\n\n## Examples\n\n### Example 1: MCP capability with an API key\n\n```toml\n# capabilities\u002Fwebsearch\u002Ftavily.toml\n# Capability: websearch\n# Provider: tavily\n# Title: Web Search (Tavily)\n# Description: Web search, content extraction, crawling, and site mapping via the Tavily API.\n\n[deps]\nrequire = [\"tavily-ai\u002Ftavily\"]\n\n[roles.mcp]\nserver_refs = [\"tavily\"]\nallowed_tools = [\"tavily_search\", \"tavily_extract\", \"tavily_crawl\", \"tavily_map\", \"tavily_research\"]\n\n[[mcp.servers]]\nname = \"tavily\"\ntype = \"stdio\"\ncommand = \"npx\"\nargs = [\"-y\", \"tavily-mcp@0.2.22\"]\ntimeout_seconds = 60\nenv = { TAVILY_API_KEY = \"{{ENV:TAVILY_API_KEY}}\" }\ntools = []\n```\n\nBare tool names in `allowed_tools` narrow the surface to exactly those tools.\n\n### Example 2: deps-only toolchain\n\n```toml\n# capabilities\u002Fprogramming-python\u002Fuv.toml\n# Capability: programming-python\n# Provider: uv\n# Title: Python Runtime via uv\n# Description: Python runtime and package management via uv and uvx.\n\n[deps]\nrequire = [\"astral-sh\u002Fuv\"]\n```\n\n### Example 3: common mistake — secret as an argument\n\n❌ `args = [\"-y\", \"some-mcp@1.0.0\", \"--api-key\", \"{{INPUT:KEY}}\"]` — the secret shows up in process listings and the capability is never env-gated.\n\n✅ `env = { SOME_API_KEY = \"{{ENV:SOME_API_KEY}}\" }` — delivered to the child, and auto-activation waits until the key exists.\n\n## Checklist\n\n- [ ] `config.toml` has 5–15 concrete, capability-specific triggers?\n- [ ] Provider header has Title, Description, and required env vars?\n- [ ] Every non-built-in `server_refs` entry has a matching `[[mcp.servers]]` block with `timeout_seconds` and `tools`?\n- [ ] npx\u002Fuvx servers pinned to an exact version?\n- [ ] Secrets passed via `env`\u002F`headers` with `{{ENV:KEY}}` using the server's exact variable name?\n- [ ] `link` and `DECLARED` updated; `setup-symlinks.sh`, `lint-capabilities.sh`, `lint-deps.sh`, `validate-capabilities.sh` all pass?\n\n## References\n\n- `templates\u002Fcapability.toml`, `templates\u002Fcapability-config.toml` — canonical templates\n- `scripts\u002Fsetup-symlinks.sh` — default provider links\n- `scripts\u002Fmcp-versions.sh` — pin drift, updates, smoke tests\n- `tap-deps-authoring` skill — dep scripts\n",{"name":5,"title":48,"domains":49,"license":14,"description":7,"compatibility":50},"Capability Authoring","octomind","Requires: an Octomind tap checkout with scripts\u002Flint-capabilities.sh and scripts\u002Fsetup-symlinks.sh.","master","e9e4a19559669b1627b1ac5ed3f77b8e36cfad95","skills\u002Ftap-capability-authoring",0,"https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap","https:\u002F\u002Foctomind.run\u002Ftap\u002F","https:\u002F\u002Fgithub.com\u002FMuvon","https:\u002F\u002Fmuvon.io","We bring ideas to life","2026-11-13 13:19:02",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Muvon\u002Foctomind-tap --skill tap-capability-authoring",{"tool":67,"command":68},"bunx","bunx skills add Muvon\u002Foctomind-tap --skill tap-capability-authoring",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Muvon\u002Foctomind-tap --skill tap-capability-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-capability-authoring\u002FSKILL.md",true,[],[76,114,141,161,184,206],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":93,"publishedAt":43},"01M70SFC5CTHRKA9B97N1ARVZ2","seo-content-refresh","Finds decaying pages, picks update, merge, redirect or remove, and briefs each refresh. Use to prioritize existing content and judge whether it helped.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fseo-content-refresh\u002FSKILL.md",[82,85,90],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000036","内容创作者",[94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113],"seo content refresh","seo","seo content","content refresh","refresh","content","posts","remove","web search","performance","search","traffic","access","drop","websearch","revamp","merge","diagnosis","update","decay",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":122,"publishedAt":43},"01M70SBWQCHGH7HGS51Y0GTKKW","marketing-review-program","Plans how to ask real customers for honest public reviews: site choice, invitation copy, incentive and disclosure rules. Use to start a review program.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketing-review-program\u002FSKILL.md",[120,121],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[123,124,125,126,127,128,102,104,129,130,131,132,133,134,135,136,137,138,139,140],"program","review","marketing review program","marketing","reviews","get","campaign","choice","how to","only","generated","ask","plan","product","generate","customer","how","request",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":43},"01M70SBB65Z2FC71Q7DEAXGJBG","geo-source-actions","Turns AI citation findings into ranked per-source actions for Reddit threads, listicles, review sites and videos. Records only. Use after a GEO audit.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fgeo-source-actions\u002FSKILL.md",[],[148,149,150,151,152,128,102,104,153,154,132,108,124,155,156,157,136,158,159,160],"actions","geo source actions","source","geo","sources","copilot","domains","llms","threads","youtube","audit","action","data",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":43},"01M70S99D3Y6GF097GTXWBXHPW","commerce-ai-readiness","Audits product feeds, markup and live pages for AI shopping assistants, then lists exact fixes. Use to make a store catalog readable to AI shoppers.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fcommerce-ai-readiness\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000031","产品经理",[171,172,173,174,175,176,177,178,179,42,104,180,153,132,106,181,182,136,158,183],"ai readiness","commerce ai readiness","commerce","readiness","feeds","ready","show","shopping","discover","up","ecommerce","documentation","recommend",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":43},"01M6DWSX45J42KTK6XASKJRGPA","tap-model-training","Train, evaluate and publish the octomind-embed model behind capability auto-activation. Use when capability triggers or skill semantic() phrases change.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-model-training\u002FSKILL.md",[190],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[192,193,25,194,195,180,196,197,198,199,200,201,38,202,203,139,204,205,29,112],"model","training","tap model training","scope","eval","uv","auto","dataset","activate","api","publish","change","embedding","re",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":213,"publishedAt":43},"01M6DWSQB7NSW53Z86XM81R1W1","tap-deps-authoring","Write dep scripts for the octomind-tap registry: header comments, platform.sh, mcp vs dep types, npx\u002Fuvx pattern. Use when editing deps\u002F\u003Corg>\u002F\u003Ctool>.sh.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-deps-authoring\u002FSKILL.md",[212],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[214,25,215,24,216,40,217,35,218,219,220,221,222,32,223,224,29,225,226,227],"deps","tap deps authoring","DEP","run","pattern","install","registry","platform","repo","tool","types","write","org","for"]