[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DWCD22TY9PR4029R6PJSMB":3,"skill-same:01M6DWCD22TY9PR4029R6PJSMB":101},{"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":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":74,"repositoryHtmlUrl":75,"repositoryHomepageUrl":76,"ownerHtmlUrl":77,"ownerBlogUrl":78,"ownerDescription":79,"updatedAt":80,"install":81,"resources":94},"01M6DWCD22TY9PR4029R6PJSMB","analytical-report",null,"Turn raw data into a decision-ready report: answer-first Minto Pyramid, traced numbers, charts, HTML that prints to PDF. Use for data reports.","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\u002Fanalytical-report\u002FSKILL.md",[17,22,25,30],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000034","行政与办公人员",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":31,"categoryName":32,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000009","前端开发",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"analytical","report","analytical report","reports","when","data reports","Charts","professional","craft","read","markdown","human","generate","self","logs","analysis","decision","default","PDF","ready","2026-11-10 10:12:30",false,"---\nname: analytical-report\ntitle: \"Analytical Report Craft\"\ndescription: \"Turn raw data into a decision-ready report: answer-first Minto Pyramid, traced numbers, charts, HTML that prints to PDF. Use for data reports.\"\nlicense: Apache-2.0\ncompatibility: \"Produces self-contained HTML by default; markdown or PDF when requested and a renderer is available.\"\ndomains: data\nrules:\n  - data(report)\n  - data(analysis-report)\n  - match(\\b(generate|build|write|make)\\s+(a|the|an)\\s+(report|analytics report|data report)\\b)\n  - match(\\breport\\s+(from|on)\\s+(this|the|my)\\s+(data|csv|metrics|logs|numbers)\\b)\n  - match(\\b(pdf|html)\\s+report\\b)\n  - semantic(turn this data into a readable report)\n  - semantic(generate a professional analytics report from these numbers)\n  - semantic(make a PDF report a human can read)\n---\n\n## Overview\n\nA report exists to help a human decide something. Most data reports fail two ways: they bury the answer under process (a chronological data dump), or they fabricate\u002Fround numbers the underlying data doesn't support. This skill encodes how to produce a report that leads with the answer, proves it with real numbers traced to the data, and is delivered in a form a person can actually read and print.\n\n## Mental model\n\nTwo non-negotiables: the pyramid (answer first) for readability, and the grounding gate (every number computed from the data) for trust. Everything else — chart choice, layout, print CSS — serves one of those two.\n\n## Instructions\n\n### Structure — the Minto Pyramid (answer first)\n\nExecutives read top-down and have little time; match that. Structure every report as a pyramid:\n\n1. Headline finding — the single most important takeaway, in one sentence, at the very top. If the reader stops here, they have the answer.\n2. Executive summary — 3–5 key findings (the rule of 3–5), strongest first, each one sentence with its supporting number. This is the whole report in a glance.\n3. Supporting sections — one per key finding, in the same order. Each leads with its finding (not a heading like \"Data\"), then shows the evidence: the chart, the table, the method in a line.\n4. Recommendations \u002F next steps — what to do about it, when the report's purpose is decision-support.\n5. Appendix \u002F method — data sources, date range, caveats, and how figures were computed, for the reader who wants to verify.\n\nNever open with \"This report analyzes…\" or a methodology wall. Open with the finding.\n\n### Grounding gate — every number traced to the data\n\n- Compute every statistic from the actual data (load it, run the numbers — don't estimate). Report figures at the precision the data supports; don't invent decimals or round in a way that changes the story.\n- No fabricated or illustrative numbers. If a figure can't be computed from the provided data, say so — never fill the gap with a plausible-looking number.\n- State the data source, the date range\u002Fscope, and any filtering. Show the method in one line where a number could be questioned (\"median of 1,204 sessions, bot traffic excluded\").\n- Flag uncertainty honestly: small samples, missing data, outliers that move the result. Give a range or interval next to any estimate that a decision hinges on. A caveat is cheaper than a wrong decision.\n- Correlation is not causation — describe what the data shows, not a causal story it can't support.\n\n### Charts — the right one, labelled, self-contained\n\nPick the chart by the question, not by variety:\n- Trend over time -> line. Comparison across categories -> bar. Part-to-whole -> stacked bar (pie only for 2–4 slices, sparingly). Distribution -> histogram. Relationship -> scatter. A single number that matters -> a big bold stat, not a chart.\n- Label directly (values on\u002Fnext to marks) over forcing the eye to a legend and axis. Title each chart with its takeaway, not its variable names (\"Signups fell 40% after the April change\", not \"Signups by month\").\n- One visual system: consistent colours, fonts, and sizing across every chart so the report reads as one document. Use colour to encode meaning, not decoration; keep it colour-blind-safe and readable in greyscale (it will be printed).\n- Render charts as inline SVG embedded in the HTML — self-contained, styleable by the print CSS, no external image files or CDN dependencies. Plot with matplotlib and the bundled house style (`report.mplstyle`, listed under Skill Resources): `plt.style.use(\"\u003Cpath>\u002Freport.mplstyle\")`, grey the context series and color the one that carries the message, `ax.set_title(\u003Ctakeaway>)`, `ax.bar_label()` or `ax.annotate()` for direct labels, then `fig.savefig(buf, format=\"svg\")` and inline the SVG. Run it with `uv run --with matplotlib python chart.py` when matplotlib isn't installed. Hand-written SVG only for sparklines and single bars; drawn-by-hand axes and labels come out misaligned.\n- Make every chart readable without sight: `role=\"img\"` plus a `\u003Ctitle>` (and `\u003Cdesc>` for the takeaway) inside the SVG, and the underlying numbers available as a table nearby or in the appendix. Keep marks at 3:1 contrast against the background and never rely on colour alone — add labels, patterns, or direct annotation.\n\n### Delivery — self-contained HTML that prints to clean PDF\n\nDefault output is a single self-contained HTML file: all CSS inline in a `\u003Cstyle>` block, all charts inline SVG, web-safe or embedded fonts — no external requests. It opens in any browser (human-readable immediately) and prints to PDF via the browser (Print -> Save as PDF) with no tools installed.\n\nMake it print cleanly:\n\n```css\n@media print {\n  @page { size: A4; margin: 18mm; }\n  .no-print { display: none; }\n  h2, h3 { break-after: avoid; }\n  table, figure, .card { break-inside: avoid; }\n  a { color: inherit; text-decoration: none; }\n}\nbody { font: 11pt\u002F1.5 -apple-system, \"Segoe UI\", Roboto, Helvetica, Arial, sans-serif; color: #1a1a1a; }\ntd.num, .stat { font-variant-numeric: tabular-nums; text-align: right; }\n```\n\nUse absolute units (pt, mm) for print layout, `break-inside: avoid` on tables\u002Ffigures\u002Fcards (the older `page-break-*` properties are legacy aliases), and a print-only footer (page context, source, date). Keep the on-screen version clean too — this is one document for both. Set `\u003Chtml lang>` and a real `\u003Ctitle>`, and use semantic headings and `\u003Ctable>` with `\u003Cth scope>` so the HTML and the PDF exported from it stay accessible.\n\nTypography and layout for humans: generous line height, a readable measure (not full-width text), clear heading hierarchy, tables for enumerable facts with right-aligned numbers, a stat-tile row for the headline metrics, whitespace over density. Restraint reads as authoritative.\n\nFormat flexibility: HTML is the default and the most useful (browser + PDF in one). Produce Markdown if the request asks for it, or a rendered PDF if a renderer is available in the environment (the agent can render the HTML via a shell tool when one is present); otherwise deliver the HTML and tell the reader to open it and Print -> Save as PDF.\n\n## Examples\n\nWeak opening (process-first, no answer): \"This report presents an analysis of user engagement data collected between January and June 2026 across all platform surfaces, using the following methodology…\"\n\nStrong opening (answer-first, pyramid): \"Engagement is up 22% — but entirely from existing power users; new-user activation actually fell 15%, and that's the risk. The three findings below, then the detail.\"\n\nChart title, weak: \"Sessions by Month\". Chart title, strong: \"Sessions doubled after launch, then plateaued in Q2 — the growth engine has stalled.\"\n\n## Checklist\n\nBefore finalizing:\n\n- [ ] The first sentence gives the answer.\n- [ ] Every key finding is readable from the executive summary alone.\n- [ ] Every number traces to the data, with its method, at the precision the data supports; nothing is illustrative or estimated.\n- [ ] Every chart is the right type, directly labelled, titled with its takeaway, part of one visual system, and has a text alternative.\n- [ ] Caveats name sample size, missing data, and anything correlational.\n- [ ] The HTML renders standalone with no external requests and prints without broken tables or clipped charts.\n","## Overview\n\nA report exists to help a human decide something. Most data reports fail two ways: they bury the answer under process (a chronological data dump), or they fabricate\u002Fround numbers the underlying data doesn't support. This skill encodes how to produce a report that leads with the answer, proves it with real numbers traced to the data, and is delivered in a form a person can actually read and print.\n\n## Mental model\n\nTwo non-negotiables: the pyramid (answer first) for readability, and the grounding gate (every number computed from the data) for trust. Everything else — chart choice, layout, print CSS — serves one of those two.\n\n## Instructions\n\n### Structure — the Minto Pyramid (answer first)\n\nExecutives read top-down and have little time; match that. Structure every report as a pyramid:\n\n1. Headline finding — the single most important takeaway, in one sentence, at the very top. If the reader stops here, they have the answer.\n2. Executive summary — 3–5 key findings (the rule of 3–5), strongest first, each one sentence with its supporting number. This is the whole report in a glance.\n3. Supporting sections — one per key finding, in the same order. Each leads with its finding (not a heading like \"Data\"), then shows the evidence: the chart, the table, the method in a line.\n4. Recommendations \u002F next steps — what to do about it, when the report's purpose is decision-support.\n5. Appendix \u002F method — data sources, date range, caveats, and how figures were computed, for the reader who wants to verify.\n\nNever open with \"This report analyzes…\" or a methodology wall. Open with the finding.\n\n### Grounding gate — every number traced to the data\n\n- Compute every statistic from the actual data (load it, run the numbers — don't estimate). Report figures at the precision the data supports; don't invent decimals or round in a way that changes the story.\n- No fabricated or illustrative numbers. If a figure can't be computed from the provided data, say so — never fill the gap with a plausible-looking number.\n- State the data source, the date range\u002Fscope, and any filtering. Show the method in one line where a number could be questioned (\"median of 1,204 sessions, bot traffic excluded\").\n- Flag uncertainty honestly: small samples, missing data, outliers that move the result. Give a range or interval next to any estimate that a decision hinges on. A caveat is cheaper than a wrong decision.\n- Correlation is not causation — describe what the data shows, not a causal story it can't support.\n\n### Charts — the right one, labelled, self-contained\n\nPick the chart by the question, not by variety:\n- Trend over time -> line. Comparison across categories -> bar. Part-to-whole -> stacked bar (pie only for 2–4 slices, sparingly). Distribution -> histogram. Relationship -> scatter. A single number that matters -> a big bold stat, not a chart.\n- Label directly (values on\u002Fnext to marks) over forcing the eye to a legend and axis. Title each chart with its takeaway, not its variable names (\"Signups fell 40% after the April change\", not \"Signups by month\").\n- One visual system: consistent colours, fonts, and sizing across every chart so the report reads as one document. Use colour to encode meaning, not decoration; keep it colour-blind-safe and readable in greyscale (it will be printed).\n- Render charts as inline SVG embedded in the HTML — self-contained, styleable by the print CSS, no external image files or CDN dependencies. Plot with matplotlib and the bundled house style (`report.mplstyle`, listed under Skill Resources): `plt.style.use(\"\u003Cpath>\u002Freport.mplstyle\")`, grey the context series and color the one that carries the message, `ax.set_title(\u003Ctakeaway>)`, `ax.bar_label()` or `ax.annotate()` for direct labels, then `fig.savefig(buf, format=\"svg\")` and inline the SVG. Run it with `uv run --with matplotlib python chart.py` when matplotlib isn't installed. Hand-written SVG only for sparklines and single bars; drawn-by-hand axes and labels come out misaligned.\n- Make every chart readable without sight: `role=\"img\"` plus a `\u003Ctitle>` (and `\u003Cdesc>` for the takeaway) inside the SVG, and the underlying numbers available as a table nearby or in the appendix. Keep marks at 3:1 contrast against the background and never rely on colour alone — add labels, patterns, or direct annotation.\n\n### Delivery — self-contained HTML that prints to clean PDF\n\nDefault output is a single self-contained HTML file: all CSS inline in a `\u003Cstyle>` block, all charts inline SVG, web-safe or embedded fonts — no external requests. It opens in any browser (human-readable immediately) and prints to PDF via the browser (Print -> Save as PDF) with no tools installed.\n\nMake it print cleanly:\n\n```css\n@media print {\n  @page { size: A4; margin: 18mm; }\n  .no-print { display: none; }\n  h2, h3 { break-after: avoid; }\n  table, figure, .card { break-inside: avoid; }\n  a { color: inherit; text-decoration: none; }\n}\nbody { font: 11pt\u002F1.5 -apple-system, \"Segoe UI\", Roboto, Helvetica, Arial, sans-serif; color: #1a1a1a; }\ntd.num, .stat { font-variant-numeric: tabular-nums; text-align: right; }\n```\n\nUse absolute units (pt, mm) for print layout, `break-inside: avoid` on tables\u002Ffigures\u002Fcards (the older `page-break-*` properties are legacy aliases), and a print-only footer (page context, source, date). Keep the on-screen version clean too — this is one document for both. Set `\u003Chtml lang>` and a real `\u003Ctitle>`, and use semantic headings and `\u003Ctable>` with `\u003Cth scope>` so the HTML and the PDF exported from it stay accessible.\n\nTypography and layout for humans: generous line height, a readable measure (not full-width text), clear heading hierarchy, tables for enumerable facts with right-aligned numbers, a stat-tile row for the headline metrics, whitespace over density. Restraint reads as authoritative.\n\nFormat flexibility: HTML is the default and the most useful (browser + PDF in one). Produce Markdown if the request asks for it, or a rendered PDF if a renderer is available in the environment (the agent can render the HTML via a shell tool when one is present); otherwise deliver the HTML and tell the reader to open it and Print -> Save as PDF.\n\n## Examples\n\nWeak opening (process-first, no answer): \"This report presents an analysis of user engagement data collected between January and June 2026 across all platform surfaces, using the following methodology…\"\n\nStrong opening (answer-first, pyramid): \"Engagement is up 22% — but entirely from existing power users; new-user activation actually fell 15%, and that's the risk. The three findings below, then the detail.\"\n\nChart title, weak: \"Sessions by Month\". Chart title, strong: \"Sessions doubled after launch, then plateaued in Q2 — the growth engine has stalled.\"\n\n## Checklist\n\nBefore finalizing:\n\n- [ ] The first sentence gives the answer.\n- [ ] Every key finding is readable from the executive summary alone.\n- [ ] Every number traces to the data, with its method, at the precision the data supports; nothing is illustrative or estimated.\n- [ ] Every chart is the right type, directly labelled, titled with its takeaway, part of one visual system, and has a text alternative.\n- [ ] Caveats name sample size, missing data, and anything correlational.\n- [ ] The HTML renders standalone with no external requests and prints without broken tables or clipped charts.\n",{"name":5,"rules":59,"title":68,"domains":69,"license":14,"description":7,"compatibility":70},[60,61,62,63,64,65,66,67],"data(report)","data(analysis-report)","match(\\b(generate|build|write|make)\\s+(a|the|an)\\s+(report|analytics report|data report)\\b)","match(\\breport\\s+(from|on)\\s+(this|the|my)\\s+(data|csv|metrics|logs|numbers)\\b)","match(\\b(pdf|html)\\s+report\\b)","semantic(turn this data into a readable report)","semantic(generate a professional analytics report from these numbers)","semantic(make a PDF report a human can read)","Analytical Report Craft","data","Produces self-contained HTML by default; markdown or PDF when requested and a renderer is available.","master","e9e4a19559669b1627b1ac5ed3f77b8e36cfad95","skills\u002Fanalytical-report",1,"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-10 20:30:54",{"source":8,"skillName":5,"commands":82,"prompt":92,"zipAvailable":93},[83,86,89],{"tool":84,"command":85},"npx","npx skills add Muvon\u002Foctomind-tap --skill analytical-report",{"tool":87,"command":88},"bunx","bunx skills add Muvon\u002Foctomind-tap --skill analytical-report",{"tool":90,"command":91},"pnpm","pnpm dlx skills add Muvon\u002Foctomind-tap --skill analytical-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fanalytical-report\u002FSKILL.md",true,[95],{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"assets\u002Freport.mplstyle","ASSET","资产文件",1037,"https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fanalytical-report\u002Fassets\u002Freport.mplstyle",[102,138,164,183,206,232],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":117,"publishedAt":54},"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",[108,111,114],{"categoryNo":109,"categoryName":110,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000035","市场营销",{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"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":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":146,"publishedAt":54},"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",[144,145],{"categoryNo":109,"categoryName":110,"taxonomyType":28,"taxonomyTypeDesc":29},{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},[147,148,149,150,151,152,126,128,153,154,155,156,157,158,159,160,46,161,162,163],"program","review","marketing review program","marketing","reviews","get","campaign","choice","how to","only","generated","ask","plan","product","customer","how","request",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":54},"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",[],[171,172,173,174,175,152,126,128,176,177,156,132,148,178,179,180,160,181,182,69],"actions","geo source actions","source","geo","sources","copilot","domains","llms","threads","youtube","audit","action",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":192,"publishedAt":54},"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",[189],{"categoryNo":190,"categoryName":191,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理",[193,194,195,196,197,53,198,199,200,201,128,202,176,156,130,203,204,160,181,205],"ai readiness","commerce ai readiness","commerce","readiness","feeds","show","shopping","discover","checkout","up","ecommerce","documentation","recommend",{"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":215,"publishedAt":54},"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",[212],{"categoryNo":213,"categoryName":214,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000023","Skill与智能体开发",[216,217,218,219,220,202,221,222,223,224,225,226,227,228,229,162,230,231,38,136],"model","training","tap","tap model training","scope","eval","uv","auto","dataset","activate","api","capabilities","publish","change","embedding","re",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":239,"publishedAt":54},"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",[238],{"categoryNo":213,"categoryName":214,"taxonomyType":28,"taxonomyTypeDesc":29},[240,218,241,242,243,244,245,246,247,248,249,250,251,252,253,254,38,255,256,257],"deps","tap deps authoring","authoring","DEP","MCP","run","scripts","pattern","install","registry","platform","repo","editing","tool","types","write","org","for"]