[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70SFC5CTHRKA9B97N1ARVZ2":3,"skill-same:01M70SFC5CTHRKA9B97N1ARVZ2":90},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M70SFC5CTHRKA9B97N1ARVZ2","seo-content-refresh",null,"Finds decaying pages, picks update, merge, redirect or remove, and briefs each refresh. Use to prioritize existing content and judge whether it helped.","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\u002Fseo-content-refresh\u002FSKILL.md",[17,22,27],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"seo","seo content","content refresh","refresh","content","seo content refresh","decay","update","diagnosis","merge","revamp","websearch","drop","access","traffic","search","performance","web search","remove","posts","2026-11-10 10:12:30",false,"---\nname: seo-content-refresh\ntitle: \"Content Refresh: Decaying Page Queue\"\ndescription: \"Finds decaying pages, picks update, merge, redirect or remove, and briefs each refresh. Use to prioritize existing content and judge whether it helped.\"\nlicense: Apache-2.0\ncompatibility: \"Requires web search and page fetching. Decay diagnosis needs authorized Search Console access or a supplied performance export.\"\ncapabilities: websearch webfetch seo-data\ndomains: seo\nrules:\n  - match(\\b(refresh|update|rewrite|republish|revamp)\\w*\\s+(\\w+\\s+){0,3}?(old|stale|existing|outdated|out-of-date)\\s+(\\w+\\s+)?(content|posts?|pages?|articles?)\\b)\n  - match(\\b(old|stale|existing|outdated|out-of-date)\\s+(content|posts?|pages?|articles?)\\b.{0,40}\\b(refresh|update|rewrite|republish)\\w*)\n  - match(\\bcontent\\s+(decay|pruning|refresh)\\b)\n  - match(\\b(decaying|decayed)\\s+(content|pages?|posts?|articles?)\\b)\n  - match(\\b(losing|lost|declining|dropping|falling)\\s+(\\w+\\s+)?(traffic|clicks|rankings?)\\b)\n  - match(\\b(traffic|clicks|rankings?)\\s+(are\\s+|is\\s+|have\\s+|has\\s+)?(drop\\w*|declin\\w+|decay\\w*|loss|fall\\w*|fell)\\b)\n---\n\n## Overview\n\nThis skill decides which existing pages need work, what kind of work, and how to tell whether it helped. It returns a prioritized refresh queue and, when planning, a brief per page. It never edits site files; writing the revision belongs to whoever owns the content. For judging a single page's quality, use `seo-content-audit`; this skill decides which pages deserve that effort.\n\n## Mental model\n\nDecay signal → cause → decision → priority → page brief → implemented change → logged review. Content decay means a page's clicks, impressions or rankings fall over time. A refresh is a change to what the page says, not to the date it shows. A traffic drop is an observation; the cause is a separate finding.\n\n## Rules\n\n### Data and its limits\n\n- Primary input is authorized Search Console access or a supplied export (URL, query, clicks, impressions, CTR, position, date).\n- Without it, audit public evidence only: dated claims, old statistics, prices, versions, screenshots, dead links. Mark decay Unverified. Missing data is Unknown, not zero.\n- Search Console Web results include AI Overviews and AI Mode, so Web totals are not organic-only (Google, AI features, checked 2026-11-09). Don't infer AI-specific clicks from them.\n\n### Find decay and separate causes\n\nCompare two equal windows. For seasonal topics, also compare the same window last year. Flag a page when clicks fall by more than 20 percent across windows and the drop is not seasonal (practitioner default, not a Google threshold). Then split the cause:\n\n| Pattern | Likely cause | Check |\n|---|---|---|\n| Impressions down | Demand fell, or indexing\u002Fcanonical problem | Trends for the topic, URL inspection |\n| Position down | Competitors improved, or the page aged or drifted from intent | Current top results, intent re-check |\n| CTR down, position stable | SERP features or AI features take clicks, or snippet is weak | Live results capture, title and description |\n| All flat but facts wrong | Hidden accuracy risk | Source check |\n\nThese are hypotheses until the evidence for the named cause is shown.\n\n### Decide per page\n\n| Decision | Evidence needed |\n|---|---|\n| Update | Page is the right target; facts or coverage have aged; intent unchanged |\n| Expand a section | One named question in the current results is answered poorly or missing |\n| Merge | Two or more pages compete for one intent in the queries data; name the survivor |\n| Redirect | Page is obsolete but a close replacement exists |\n| Remove | No traffic, links or purpose, and no replacement; confirm in backlinks and analytics first |\n| Leave alone | Healthy, seasonal dip, or accurate evergreen page |\n\n### What counts as a refresh\n\nA refresh has at least one of: facts re-verified against primary sources, information added, intent re-checked against the current results. Changing only the date is not a refresh. Google lists \"changing the date of pages to make them seem fresh when the content has not substantially changed\" among signs of search-engine-first content (Google, helpful content, checked 2026-11-09). Change the visible date, `dateModified` and sitemap `lastmod` only when the main content changes; Google uses `lastmod` only if it is consistently and verifiably accurate, and counts main content, structured data and link updates as significant but a copyright-year change as not (Google, sitemaps, checked 2026-11-09). Visible and structured dates must match (Google, publication dates, checked 2026-11-09).\n\n### Prioritize\n\n1. Accuracy-sensitive pages first, whatever their traffic: pricing, policy, health, legal, security, version-specific.\n2. Pages tied to buyer decisions, and pages cited in AI answers, especially citations graded Outdated or Contradicted in `geo-visibility-audit`.\n3. Pages with measured traffic loss.\n\nWithin a tier rank by value, evidence, confidence, then effort. State each as high, medium or low with the reason; these are judgments.\n\n### Freshness and AI answers\n\nEvidence is correlational. Ahrefs (2025-07-28) analyzed about 17 million cited URLs: those cited by AI assistants averaged 1,064 days since publication against 1,432 for organic Google results, and 909 against 1,047 days since update. ChatGPT preferred newer pages most; Google AI Overviews cited pages slightly older than organic. Ahrefs notes cited pages still averaged about 2.9 years old and that low-quality pages gain nothing from frequent updates. Seer Interactive (2026-07-24) found 75 percent of dateable pages cited in ChatGPT, Gemini and Perplexity answers had been updated within a year. It studied cited pages only, with no uncited comparison group, covered four brands over four months, and could not tell minor edits from real ones. Neither study shows that updating a page raises its chance of citation. Both are vendor studies. Justify a refresh by accuracy and buyer value; treat any AI-freshness effect as unproven.\n\n### Cadence\n\nRefresh on triggers: a product, price or regulation change; a decay flag; a citation graded Outdated. For fast-moving topics a calendar check is a convention, not a requirement. Set no fixed monthly rewrite quota.\n\n### Measurement log\n\nPer refreshed page record: URL, change date, what changed, baseline windows, concurrent changes (site, algorithm, seasonality, other edits), review date, outcome. Allow time to recrawl before reviewing; 4 to 8 weeks is a convention, so say so and extend it for slow-crawled sites. Compare against equal windows and, when possible, against similar unrefreshed pages. An uncontrolled before\u002Fafter supports no causal claim.\n\n### Output\n\nRespect the host role. In diagnostic mode, return a queue table (URL, evidence, cause, decision, priority, owner, review date) with one fix direction per page. In planning mode, start from an existing queue or supplied findings and add one brief per page: what is wrong with passage references; facts to re-verify with primary-source pointers; what to add; what to remove; what must stay (ranking sections, working links, accurate claims). Pages with no diagnosis go back for one. Save as `seo-refresh-[slug]-[YYYY-MM-DD].md`.\n\n## Examples\n\n- Wrong: \"Traffic fell on 40 posts; update all of them monthly.\" Right: \"Eleven posts lost over 20 percent of clicks in equal 90-day windows; nine show position loss to newer results, two show CTR loss at stable position. Brief the nine, test titles on the two.\"\n- Wrong: \"Set `lastmod` to today on every page so Google sees fresh content.\" Right: \"Change `lastmod` and the visible date only on the three pages whose main content changed.\"\n- Wrong: \"No Search Console access, so decay is zero.\" Right: \"Decay Unverified. Public evidence: the pricing table cites 2023 plans. Request a 16-month export to confirm.\"\n\n## Checklist\n\n- [ ] Data source named; absent data marked Unverified, not zero.\n- [ ] Equal windows compared, with last year's window for seasonal topics.\n- [ ] Cause stated separately from the drop, with its evidence.\n- [ ] Each page has one decision from the table and its required evidence.\n- [ ] Accuracy-sensitive pages ranked before traffic-loss pages.\n- [ ] Dates change only where main content changes.\n- [ ] No claim that freshness raises AI citations.\n- [ ] Review dates and concurrent changes logged; no causal claim from before\u002Fafter.\n- [ ] Output saved with the dated filename; no site files edited.\n\n## Composition \u002F References\n\n- `seo-content-audit` for page-quality scoring of a queued page; `geo-visibility-audit` for citation grading that feeds the queue.\n- [Google: AI features and your website](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fai-features)\n- [Google: creating helpful content](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fcreating-helpful-content)\n- [Google: publication dates](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fpublication-dates)\n- [Google: build a sitemap](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fsitemaps\u002Fbuild-sitemap)\n- [Ahrefs: do AI assistants prefer to cite fresh content](https:\u002F\u002Fahrefs.com\u002Fblog\u002Fdo-ai-assistants-prefer-to-cite-fresh-content\u002F)\n- [Seer Interactive: content recency and AI visibility](https:\u002F\u002Fwww.seerinteractive.com\u002Finsights\u002Fstudy-content-recencys-impact-on-ai-visibility-in-2026)\n\nSources reviewed 2026-11-09. The 20 percent threshold, the 4 to 8 week wait and calendar checks are practitioner conventions, not published rules.\n","## Overview\n\nThis skill decides which existing pages need work, what kind of work, and how to tell whether it helped. It returns a prioritized refresh queue and, when planning, a brief per page. It never edits site files; writing the revision belongs to whoever owns the content. For judging a single page's quality, use `seo-content-audit`; this skill decides which pages deserve that effort.\n\n## Mental model\n\nDecay signal → cause → decision → priority → page brief → implemented change → logged review. Content decay means a page's clicks, impressions or rankings fall over time. A refresh is a change to what the page says, not to the date it shows. A traffic drop is an observation; the cause is a separate finding.\n\n## Rules\n\n### Data and its limits\n\n- Primary input is authorized Search Console access or a supplied export (URL, query, clicks, impressions, CTR, position, date).\n- Without it, audit public evidence only: dated claims, old statistics, prices, versions, screenshots, dead links. Mark decay Unverified. Missing data is Unknown, not zero.\n- Search Console Web results include AI Overviews and AI Mode, so Web totals are not organic-only (Google, AI features, checked 2026-11-09). Don't infer AI-specific clicks from them.\n\n### Find decay and separate causes\n\nCompare two equal windows. For seasonal topics, also compare the same window last year. Flag a page when clicks fall by more than 20 percent across windows and the drop is not seasonal (practitioner default, not a Google threshold). Then split the cause:\n\n| Pattern | Likely cause | Check |\n|---|---|---|\n| Impressions down | Demand fell, or indexing\u002Fcanonical problem | Trends for the topic, URL inspection |\n| Position down | Competitors improved, or the page aged or drifted from intent | Current top results, intent re-check |\n| CTR down, position stable | SERP features or AI features take clicks, or snippet is weak | Live results capture, title and description |\n| All flat but facts wrong | Hidden accuracy risk | Source check |\n\nThese are hypotheses until the evidence for the named cause is shown.\n\n### Decide per page\n\n| Decision | Evidence needed |\n|---|---|\n| Update | Page is the right target; facts or coverage have aged; intent unchanged |\n| Expand a section | One named question in the current results is answered poorly or missing |\n| Merge | Two or more pages compete for one intent in the queries data; name the survivor |\n| Redirect | Page is obsolete but a close replacement exists |\n| Remove | No traffic, links or purpose, and no replacement; confirm in backlinks and analytics first |\n| Leave alone | Healthy, seasonal dip, or accurate evergreen page |\n\n### What counts as a refresh\n\nA refresh has at least one of: facts re-verified against primary sources, information added, intent re-checked against the current results. Changing only the date is not a refresh. Google lists \"changing the date of pages to make them seem fresh when the content has not substantially changed\" among signs of search-engine-first content (Google, helpful content, checked 2026-11-09). Change the visible date, `dateModified` and sitemap `lastmod` only when the main content changes; Google uses `lastmod` only if it is consistently and verifiably accurate, and counts main content, structured data and link updates as significant but a copyright-year change as not (Google, sitemaps, checked 2026-11-09). Visible and structured dates must match (Google, publication dates, checked 2026-11-09).\n\n### Prioritize\n\n1. Accuracy-sensitive pages first, whatever their traffic: pricing, policy, health, legal, security, version-specific.\n2. Pages tied to buyer decisions, and pages cited in AI answers, especially citations graded Outdated or Contradicted in `geo-visibility-audit`.\n3. Pages with measured traffic loss.\n\nWithin a tier rank by value, evidence, confidence, then effort. State each as high, medium or low with the reason; these are judgments.\n\n### Freshness and AI answers\n\nEvidence is correlational. Ahrefs (2025-07-28) analyzed about 17 million cited URLs: those cited by AI assistants averaged 1,064 days since publication against 1,432 for organic Google results, and 909 against 1,047 days since update. ChatGPT preferred newer pages most; Google AI Overviews cited pages slightly older than organic. Ahrefs notes cited pages still averaged about 2.9 years old and that low-quality pages gain nothing from frequent updates. Seer Interactive (2026-07-24) found 75 percent of dateable pages cited in ChatGPT, Gemini and Perplexity answers had been updated within a year. It studied cited pages only, with no uncited comparison group, covered four brands over four months, and could not tell minor edits from real ones. Neither study shows that updating a page raises its chance of citation. Both are vendor studies. Justify a refresh by accuracy and buyer value; treat any AI-freshness effect as unproven.\n\n### Cadence\n\nRefresh on triggers: a product, price or regulation change; a decay flag; a citation graded Outdated. For fast-moving topics a calendar check is a convention, not a requirement. Set no fixed monthly rewrite quota.\n\n### Measurement log\n\nPer refreshed page record: URL, change date, what changed, baseline windows, concurrent changes (site, algorithm, seasonality, other edits), review date, outcome. Allow time to recrawl before reviewing; 4 to 8 weeks is a convention, so say so and extend it for slow-crawled sites. Compare against equal windows and, when possible, against similar unrefreshed pages. An uncontrolled before\u002Fafter supports no causal claim.\n\n### Output\n\nRespect the host role. In diagnostic mode, return a queue table (URL, evidence, cause, decision, priority, owner, review date) with one fix direction per page. In planning mode, start from an existing queue or supplied findings and add one brief per page: what is wrong with passage references; facts to re-verify with primary-source pointers; what to add; what to remove; what must stay (ranking sections, working links, accurate claims). Pages with no diagnosis go back for one. Save as `seo-refresh-[slug]-[YYYY-MM-DD].md`.\n\n## Examples\n\n- Wrong: \"Traffic fell on 40 posts; update all of them monthly.\" Right: \"Eleven posts lost over 20 percent of clicks in equal 90-day windows; nine show position loss to newer results, two show CTR loss at stable position. Brief the nine, test titles on the two.\"\n- Wrong: \"Set `lastmod` to today on every page so Google sees fresh content.\" Right: \"Change `lastmod` and the visible date only on the three pages whose main content changed.\"\n- Wrong: \"No Search Console access, so decay is zero.\" Right: \"Decay Unverified. Public evidence: the pricing table cites 2023 plans. Request a 16-month export to confirm.\"\n\n## Checklist\n\n- [ ] Data source named; absent data marked Unverified, not zero.\n- [ ] Equal windows compared, with last year's window for seasonal topics.\n- [ ] Cause stated separately from the drop, with its evidence.\n- [ ] Each page has one decision from the table and its required evidence.\n- [ ] Accuracy-sensitive pages ranked before traffic-loss pages.\n- [ ] Dates change only where main content changes.\n- [ ] No claim that freshness raises AI citations.\n- [ ] Review dates and concurrent changes logged; no causal claim from before\u002Fafter.\n- [ ] Output saved with the dated filename; no site files edited.\n\n## Composition \u002F References\n\n- `seo-content-audit` for page-quality scoring of a queued page; `geo-visibility-audit` for citation grading that feeds the queue.\n- [Google: AI features and your website](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fai-features)\n- [Google: creating helpful content](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fcreating-helpful-content)\n- [Google: publication dates](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fpublication-dates)\n- [Google: build a sitemap](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fsitemaps\u002Fbuild-sitemap)\n- [Ahrefs: do AI assistants prefer to cite fresh content](https:\u002F\u002Fahrefs.com\u002Fblog\u002Fdo-ai-assistants-prefer-to-cite-fresh-content\u002F)\n- [Seer Interactive: content recency and AI visibility](https:\u002F\u002Fwww.seerinteractive.com\u002Finsights\u002Fstudy-content-recencys-impact-on-ai-visibility-in-2026)\n\nSources reviewed 2026-11-09. The 20 percent threshold, the 4 to 8 week wait and calendar checks are practitioner conventions, not published rules.\n",{"name":5,"rules":56,"title":63,"domains":31,"license":14,"description":7,"capabilities":64,"compatibility":65},[57,58,59,60,61,62],"match(\\b(refresh|update|rewrite|republish|revamp)\\w*\\s+(\\w+\\s+){0,3}?(old|stale|existing|outdated|out-of-date)\\s+(\\w+\\s+)?(content|posts?|pages?|articles?)\\b)","match(\\b(old|stale|existing|outdated|out-of-date)\\s+(content|posts?|pages?|articles?)\\b.{0,40}\\b(refresh|update|rewrite|republish)\\w*)","match(\\bcontent\\s+(decay|pruning|refresh)\\b)","match(\\b(decaying|decayed)\\s+(content|pages?|posts?|articles?)\\b)","match(\\b(losing|lost|declining|dropping|falling)\\s+(\\w+\\s+)?(traffic|clicks|rankings?)\\b)","match(\\b(traffic|clicks|rankings?)\\s+(are\\s+|is\\s+|have\\s+|has\\s+)?(drop\\w*|declin\\w+|decay\\w*|loss|fall\\w*|fell)\\b)","Content Refresh: Decaying Page Queue","websearch webfetch seo-data","Requires web search and page fetching. Decay diagnosis needs authorized Search Console access or a supplied performance export.","master","4305fbfaa04244af84957971d583a52600c5f02a","skills\u002Fseo-content-refresh",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-12 23:55:54",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add Muvon\u002Foctomind-tap --skill seo-content-refresh",{"tool":82,"command":83},"bunx","bunx skills add Muvon\u002Foctomind-tap --skill seo-content-refresh",{"tool":85,"command":86},"pnpm","pnpm dlx skills add Muvon\u002Foctomind-tap --skill seo-content-refresh","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fseo-content-refresh\u002FSKILL.md",true,[],[91,118,138,162,189,215],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":99,"publishedAt":51},"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",[97,98],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[100,101,102,103,104,105,48,46,106,107,108,109,110,111,112,113,114,115,116,117],"program","review","marketing review program","marketing","reviews","get","campaign","choice","how to","only","generated","ask","plan","product","generate","customer","how","request",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":51},"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",[],[125,126,127,128,129,105,48,46,130,131,109,42,101,132,133,134,113,135,136,137],"actions","geo source actions","source","geo","sources","copilot","domains","llms","threads","youtube","audit","action","data",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":51},"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",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000031","产品经理",[148,149,150,151,152,153,154,155,156,157,46,158,130,109,44,159,160,113,135,161],"ai readiness","commerce ai readiness","commerce","readiness","feeds","ready","show","shopping","discover","checkout","up","ecommerce","documentation","recommend",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":51},"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",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[172,173,174,175,176,158,177,178,179,180,181,182,183,184,185,116,186,187,188,38],"model","training","tap","tap model training","scope","eval","uv","auto","dataset","activate","api","capabilities","publish","change","embedding","re","when",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":51},"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",[195],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},[197,174,198,199,200,201,202,203,204,205,206,207,208,209,210,211,188,212,213,214],"deps","tap deps authoring","authoring","DEP","MCP","run","scripts","pattern","install","registry","platform","repo","editing","tool","types","write","org","for",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":51},"01M6DWSKJ5215FDYSZQK7M3T7S","tap-capability-authoring","Create Octomind capabilities: config.toml triggers, provider files, MCP server wiring, version pins, symlinks. Use when editing capabilities\u002F\u003Cname>\u002F files.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-capability-authoring\u002FSKILL.md",[221],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},[174,223,199,224,157,225,201,226,183,227,228,203,229,230,209,231,232,188,233,234],"tap capability authoring","capability","files","mcp server","with scripts","server","config","provider","toml","triggers","wiring","create"]