[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QAY96TS3TV8ZKSCVJ2A7Q5":3,"skill-same:01M6QAY96TS3TV8ZKSCVJ2A7Q5":67},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6QAY96TS3TV8ZKSCVJ2A7Q5","benchmark-methodology",null,"Score a scoped competitor set into comparable profile cards: nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client tension) with 1-5 evidence-anchored rubrics and a tension 2x2 plot. Use when benchmarking or scoring competitors, building a competitive comparison matrix, or grading rival positioning before assembling the report; runs after competitive-platform-analysis and before competitive-report-structure.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbenchmark-methodology\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"benchmark","methodology","benchmark methodology","competitor","benchmarking","matrix","competitive","platform","grading","leadership","positioning","structure","dimensions","scoring","craft","evidence","packaging","competitors","analysis","SET","2026-11-10 10:12:30",false,"---\nname: benchmark-methodology\ndescription: \"Score a scoped competitor set into comparable profile cards: nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client tension) with 1-5 evidence-anchored rubrics and a tension 2x2 plot. Use when benchmarking or scoring competitors, building a competitive comparison matrix, or grading rival positioning before assembling the report; runs after competitive-platform-analysis and before competitive-report-structure.\"\nlicense: MIT\n---\n\n# Benchmark Methodology\n\nUse this skill to turn a scoped competitor set into **comparable, defensible\nscores**. Each competitor is assessed on the same nine dimensions, with\nexplicit 1–5 rubrics, then captured in a uniform profile card. Consistency is\nthe point: scores are only useful if the same evidence would earn the same\nnumber for any competitor.\n\n## When to Activate\n\n- A scoped, tiered competitor set from competitive-platform-analysis is ready to score.\n- Need comparable, evidence-anchored scores across competitors — not gut-feel rankings.\n- Client's strategic tension (the paired axes defining their target white-space) has been established.\n- Preparing to produce profile cards for assembly in competitive-report-structure.\n\n## Client positioning brief (establish first)\n\nBefore scoring, establish the client's positioning brief. It supplies:\n\n- **Strategic tension** — the two axes (e.g., memorability × hireability) whose\n  intersection marks the client's target white-space. Dimension 9 is always\n  the client's named tension; report both poles separately, never averaged.\n- **Differentiator** — what makes the client's moat. This informs which\n  dimensions matter most for the client's positioning argument.\n- **Brand balance** — the intended mix of distinct strategic emphases. Strategic\n  recommendations must not break this balance without flagging it.\n\n## Why these dimensions\n\nThe client competes on a **specific tension held across two poles**, not on\nservice breadth. The dimensions are weighted to reflect that moat. Two\ndimensions — the tension poles — are scored **separately and never averaged\ntogether**, because the client's strategic question is precisely whether a rival\nachieves both simultaneously.\n\n## The nine dimensions (with weights)\n\nWeights guide synthesis emphasis, not a single blended score (avoid a false\ncomposite — see Bias controls). Sum = 100%.\n\n1. **Positioning clarity & distinctiveness** (18%) — Is the studio's position\n   sharp, ownable, and instantly legible? Or generic?\n2. **Brand voice \u002F verbal distinctiveness** (15%) — Does the copy have an\n   ownable register, or is it interchangeable agency-speak?\n3. **Visual identity & site craft** (15%) — Quality and ownership of the visual\n   system; site as proof-of-craft.\n4. **Service offer & packaging** (12%) — Productized and legible (named\n   sprints\u002Faudits) vs vague. Packaging maturity.\n5. **Evidence & credibility** (12%) — Named clients, quantified outcomes,\n   case-study depth. Proof beyond assertion.\n6. **Enterprise-readiness \u002F commercial maturity** (10%) — Signals they can land\n   and hold SaaS\u002Ffintech\u002FB2B\u002Fenterprise work (process, logos, scale, contracts).\n7. **Thought leadership \u002F content presence** (8%) — Owned POV: writing, talks,\n   newsletters, frameworks. Depth over volume.\n8. **Pricing transparency & engagement model** (5%) — Is pricing\u002Fengagement\n   legible? Productized vs bespoke vs opaque.\n9. **[Client's strategic tension]** (5% as a flag; **score BOTH poles,\n   report separately**) — Read the tension name and axis descriptions from the\n   client's positioning brief. Plot both; the gap is the insight. The client's\n   target quadrant is the single most important finding: who else is already\n   there?\n\n## Scoring rubric (1–5, applies to dimensions 1–8)\n\nAnchor every score to observable evidence. Generic descriptors below; adapt the\nspecifics per dimension but keep the level meaning constant.\n\n- **1 — Absent \u002F generic.** No discernible position or craft; indistinguishable\n  from a template. Active liability.\n- **2 — Below par.** Some intent but inconsistent, derivative, or unconvincing.\n  Wouldn't survive a side-by-side.\n- **3 — Competent \u002F table-stakes.** Solid, professional, unremarkable. Meets\n  expectation, ownable by nobody.\n- **4 — Strong \u002F distinctive.** Clearly above peers; a real strength a buyer\n  would notice and cite.\n- **5 — Category-defining.** Best-in-class, ownable, hard to imitate. Sets the\n  bar others react to.\n\n### Tension axes (dimension 9) — score each 1–5\n\nRead the axis labels and their 1\u002F3\u002F5 anchors from the client's positioning\nbrief. Example anchors for a memorability × credibility tension:\n\n- **Memorability** — 1: forgotten instantly · 3: recognizable in context ·\n  5: unforgettable, talked-about, distinctively owned.\n- **Credibility** — 1: feels risky\u002Famateur · 3: safe, competent,\n  unexciting · 5: enterprise-trusted, obvious safe choice.\n\nPlot competitors on the tension 2×2. The client's target quadrant is named in\nthe positioning brief. Who else occupies that quadrant is the single most\nimportant finding of the benchmark.\n\n## How to collect the data\n\nFor each competitor, work the dimensions in this order (cheapest signal first):\n\n1. **Competitor's own site** — positioning, voice, offer packaging, pricing\n   posture, named clients, manifesto\u002FPOV. Screenshot the homepage + one case\n   study.\n2. **Case studies \u002F work** — evidence depth, quantified outcomes, client names.\n   Distinguish *asserted* (\"we delivered X\") from *proven* (metrics, named,\n   verifiable).\n3. **Review directories** — corroborate clients, project size, engagement model\n   → credibility & enterprise-readiness (e.g. Clutch.co or the niche equivalent).\n4. **LinkedIn** — team size\u002Fmodel, founder narrative, content cadence →\n   thought leadership, model.\n5. **Portfolio \u002F craft platforms** — craft register (use the showcase native to\n   the niche: design boards, showreels, published samples, etc.).\n6. **Content channels** — newsletter\u002Ftalks\u002Fwriting → thought-leadership depth.\n\n**What to record per dimension:** the score, one-line justification, and the\nsource link\u002Fscreenshot that earned it. No score without evidence.\n\n## Bias controls\n\n- **No single composite score.** Report dimension scores and the tension plot\n  separately. A weighted average hides the asymmetry that matters.\n- **Asserted vs proven.** Downgrade credibility\u002Fevidence scores for\n  self-reported claims with no corroboration. Site copy is marketing, not fact.\n- **Aesthetic affinity bias.** Reviewers may over-score studios whose aesthetic\n  they share and under-score rivals' commercial strength. Score craft and\n  credibility independently; a \"boring\" site may be winning bigger clients.\n- **Recency \u002F flashiness bias.** Award-winning, showpiece work dazzles but may\n  lack commercial depth — verify with directories\u002Fclients before scoring\n  credibility.\n- **Survivorship.** The visible, well-marketed studios aren't the whole market;\n  note strong-but-quiet operators found via directories\u002Freviews.\n- **Calibrate across the set, not in isolation.** Before finalizing, re-read\n  scores side-by-side — a \"4\" must mean the same thing for every competitor.\n  Adjust outliers.\n\n## Competitor profile card (output format)\n\nProduce one card per profiled competitor — the atomic unit the report assembles\nfrom:\n\n```\n## \u003CCompetitor name>\n- **Profile \u002F Tier:** \u003Cpositioning stance · specialization · size band> \u002F \u003CDirect | Adjacent | Aspirational>\n- **One-liner:** \u003Chow they position themselves, in their words>\n- **Model \u002F size \u002F geography:** \u003Csolo|micro|boutique> · \u003Cregion> · \u003Cpricing\u002Fengagement model>\n- **Notable clients \u002F evidence:** \u003Cnamed, with proven\u002Fasserted tag>\n\n### Dimension scores\n| Dimension | Score (1–5) | Justification (1 line) | Source |\n|---|---|---|---|\n| Positioning clarity & distinctiveness | | | |\n| Brand voice \u002F verbal distinctiveness | | | |\n| Visual identity & site craft | | | |\n| Service offer & packaging | | | |\n| Evidence & credibility | | | |\n| Enterprise-readiness \u002F commercial maturity | | | |\n| Thought leadership \u002F content presence | | | |\n| Pricing transparency & engagement model | | | |\n\n### Tension plot\n- **[Axis 1 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **[Axis 2 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **Quadrant:** \u003Chigh\u002Fhigh | high-1\u002Flow-2 | low-1\u002Fhigh-2 | low\u002Flow>\n\n### Read for [client]\n- **Strength to learn from:** \u003C…>\n- **Weakness to exploit \u002F white-space it exposes:** \u003C…>\n- **Threat to [client]:** \u003C…>\n```\n\nHand the completed cards plus the tension plot to `competitive-report-structure`.\n\n## Anti-Patterns\n\n- **Averaging the tension axes.** The two poles of the client's strategic tension must be scored and reported separately. Averaging destroys the insight — the gap between poles is the finding.\n- **Scoring without evidence.** Every score requires a one-line justification and a source link. A score without evidence is an opinion, not a benchmark.\n- **Creating a single composite score.** Report dimension scores individually. A weighted average hides the asymmetric strengths that matter for positioning.\n- **Applying generic rubric anchors without adapting.** The 1–5 anchors must be calibrated to the specific dimension and competitor set. The generic descriptions are a starting point, not a fixed standard.\n- **Running before the competitor set is scoped.** Use competitive-platform-analysis first to produce a tiered, pruned set. Scoring an unscoped list wastes effort on irrelevant competitors.\n\n## Related Skills\n\n- `competitive-platform-analysis` — the prerequisite; produces the tiered competitor set this skill scores.\n- `competitive-report-structure` — the next step; assembles the scored profile cards into a client-deliverable report.\n","# Benchmark Methodology\n\nUse this skill to turn a scoped competitor set into **comparable, defensible\nscores**. Each competitor is assessed on the same nine dimensions, with\nexplicit 1–5 rubrics, then captured in a uniform profile card. Consistency is\nthe point: scores are only useful if the same evidence would earn the same\nnumber for any competitor.\n\n## When to Activate\n\n- A scoped, tiered competitor set from competitive-platform-analysis is ready to score.\n- Need comparable, evidence-anchored scores across competitors — not gut-feel rankings.\n- Client's strategic tension (the paired axes defining their target white-space) has been established.\n- Preparing to produce profile cards for assembly in competitive-report-structure.\n\n## Client positioning brief (establish first)\n\nBefore scoring, establish the client's positioning brief. It supplies:\n\n- **Strategic tension** — the two axes (e.g., memorability × hireability) whose\n  intersection marks the client's target white-space. Dimension 9 is always\n  the client's named tension; report both poles separately, never averaged.\n- **Differentiator** — what makes the client's moat. This informs which\n  dimensions matter most for the client's positioning argument.\n- **Brand balance** — the intended mix of distinct strategic emphases. Strategic\n  recommendations must not break this balance without flagging it.\n\n## Why these dimensions\n\nThe client competes on a **specific tension held across two poles**, not on\nservice breadth. The dimensions are weighted to reflect that moat. Two\ndimensions — the tension poles — are scored **separately and never averaged\ntogether**, because the client's strategic question is precisely whether a rival\nachieves both simultaneously.\n\n## The nine dimensions (with weights)\n\nWeights guide synthesis emphasis, not a single blended score (avoid a false\ncomposite — see Bias controls). Sum = 100%.\n\n1. **Positioning clarity & distinctiveness** (18%) — Is the studio's position\n   sharp, ownable, and instantly legible? Or generic?\n2. **Brand voice \u002F verbal distinctiveness** (15%) — Does the copy have an\n   ownable register, or is it interchangeable agency-speak?\n3. **Visual identity & site craft** (15%) — Quality and ownership of the visual\n   system; site as proof-of-craft.\n4. **Service offer & packaging** (12%) — Productized and legible (named\n   sprints\u002Faudits) vs vague. Packaging maturity.\n5. **Evidence & credibility** (12%) — Named clients, quantified outcomes,\n   case-study depth. Proof beyond assertion.\n6. **Enterprise-readiness \u002F commercial maturity** (10%) — Signals they can land\n   and hold SaaS\u002Ffintech\u002FB2B\u002Fenterprise work (process, logos, scale, contracts).\n7. **Thought leadership \u002F content presence** (8%) — Owned POV: writing, talks,\n   newsletters, frameworks. Depth over volume.\n8. **Pricing transparency & engagement model** (5%) — Is pricing\u002Fengagement\n   legible? Productized vs bespoke vs opaque.\n9. **[Client's strategic tension]** (5% as a flag; **score BOTH poles,\n   report separately**) — Read the tension name and axis descriptions from the\n   client's positioning brief. Plot both; the gap is the insight. The client's\n   target quadrant is the single most important finding: who else is already\n   there?\n\n## Scoring rubric (1–5, applies to dimensions 1–8)\n\nAnchor every score to observable evidence. Generic descriptors below; adapt the\nspecifics per dimension but keep the level meaning constant.\n\n- **1 — Absent \u002F generic.** No discernible position or craft; indistinguishable\n  from a template. Active liability.\n- **2 — Below par.** Some intent but inconsistent, derivative, or unconvincing.\n  Wouldn't survive a side-by-side.\n- **3 — Competent \u002F table-stakes.** Solid, professional, unremarkable. Meets\n  expectation, ownable by nobody.\n- **4 — Strong \u002F distinctive.** Clearly above peers; a real strength a buyer\n  would notice and cite.\n- **5 — Category-defining.** Best-in-class, ownable, hard to imitate. Sets the\n  bar others react to.\n\n### Tension axes (dimension 9) — score each 1–5\n\nRead the axis labels and their 1\u002F3\u002F5 anchors from the client's positioning\nbrief. Example anchors for a memorability × credibility tension:\n\n- **Memorability** — 1: forgotten instantly · 3: recognizable in context ·\n  5: unforgettable, talked-about, distinctively owned.\n- **Credibility** — 1: feels risky\u002Famateur · 3: safe, competent,\n  unexciting · 5: enterprise-trusted, obvious safe choice.\n\nPlot competitors on the tension 2×2. The client's target quadrant is named in\nthe positioning brief. Who else occupies that quadrant is the single most\nimportant finding of the benchmark.\n\n## How to collect the data\n\nFor each competitor, work the dimensions in this order (cheapest signal first):\n\n1. **Competitor's own site** — positioning, voice, offer packaging, pricing\n   posture, named clients, manifesto\u002FPOV. Screenshot the homepage + one case\n   study.\n2. **Case studies \u002F work** — evidence depth, quantified outcomes, client names.\n   Distinguish *asserted* (\"we delivered X\") from *proven* (metrics, named,\n   verifiable).\n3. **Review directories** — corroborate clients, project size, engagement model\n   → credibility & enterprise-readiness (e.g. Clutch.co or the niche equivalent).\n4. **LinkedIn** — team size\u002Fmodel, founder narrative, content cadence →\n   thought leadership, model.\n5. **Portfolio \u002F craft platforms** — craft register (use the showcase native to\n   the niche: design boards, showreels, published samples, etc.).\n6. **Content channels** — newsletter\u002Ftalks\u002Fwriting → thought-leadership depth.\n\n**What to record per dimension:** the score, one-line justification, and the\nsource link\u002Fscreenshot that earned it. No score without evidence.\n\n## Bias controls\n\n- **No single composite score.** Report dimension scores and the tension plot\n  separately. A weighted average hides the asymmetry that matters.\n- **Asserted vs proven.** Downgrade credibility\u002Fevidence scores for\n  self-reported claims with no corroboration. Site copy is marketing, not fact.\n- **Aesthetic affinity bias.** Reviewers may over-score studios whose aesthetic\n  they share and under-score rivals' commercial strength. Score craft and\n  credibility independently; a \"boring\" site may be winning bigger clients.\n- **Recency \u002F flashiness bias.** Award-winning, showpiece work dazzles but may\n  lack commercial depth — verify with directories\u002Fclients before scoring\n  credibility.\n- **Survivorship.** The visible, well-marketed studios aren't the whole market;\n  note strong-but-quiet operators found via directories\u002Freviews.\n- **Calibrate across the set, not in isolation.** Before finalizing, re-read\n  scores side-by-side — a \"4\" must mean the same thing for every competitor.\n  Adjust outliers.\n\n## Competitor profile card (output format)\n\nProduce one card per profiled competitor — the atomic unit the report assembles\nfrom:\n\n```\n## \u003CCompetitor name>\n- **Profile \u002F Tier:** \u003Cpositioning stance · specialization · size band> \u002F \u003CDirect | Adjacent | Aspirational>\n- **One-liner:** \u003Chow they position themselves, in their words>\n- **Model \u002F size \u002F geography:** \u003Csolo|micro|boutique> · \u003Cregion> · \u003Cpricing\u002Fengagement model>\n- **Notable clients \u002F evidence:** \u003Cnamed, with proven\u002Fasserted tag>\n\n### Dimension scores\n| Dimension | Score (1–5) | Justification (1 line) | Source |\n|---|---|---|---|\n| Positioning clarity & distinctiveness | | | |\n| Brand voice \u002F verbal distinctiveness | | | |\n| Visual identity & site craft | | | |\n| Service offer & packaging | | | |\n| Evidence & credibility | | | |\n| Enterprise-readiness \u002F commercial maturity | | | |\n| Thought leadership \u002F content presence | | | |\n| Pricing transparency & engagement model | | | |\n\n### Tension plot\n- **[Axis 1 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **[Axis 2 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **Quadrant:** \u003Chigh\u002Fhigh | high-1\u002Flow-2 | low-1\u002Fhigh-2 | low\u002Flow>\n\n### Read for [client]\n- **Strength to learn from:** \u003C…>\n- **Weakness to exploit \u002F white-space it exposes:** \u003C…>\n- **Threat to [client]:** \u003C…>\n```\n\nHand the completed cards plus the tension plot to `competitive-report-structure`.\n\n## Anti-Patterns\n\n- **Averaging the tension axes.** The two poles of the client's strategic tension must be scored and reported separately. Averaging destroys the insight — the gap between poles is the finding.\n- **Scoring without evidence.** Every score requires a one-line justification and a source link. A score without evidence is an opinion, not a benchmark.\n- **Creating a single composite score.** Report dimension scores individually. A weighted average hides the asymmetric strengths that matter for positioning.\n- **Applying generic rubric anchors without adapting.** The 1–5 anchors must be calibrated to the specific dimension and competitor set. The generic descriptions are a starting point, not a fixed standard.\n- **Running before the competitor set is scoped.** Use competitive-platform-analysis first to produce a tiered, pruned set. Scoring an unscoped list wastes effort on irrelevant competitors.\n\n## Related Skills\n\n- `competitive-platform-analysis` — the prerequisite; produces the tiered competitor set this skill scores.\n- `competitive-report-structure` — the next step; assembles the scored profile cards into a client-deliverable report.\n",{"name":5,"license":15,"description":7},"main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fbenchmark-methodology","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill benchmark-methodology",{"tool":59,"command":60},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill benchmark-methodology",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill benchmark-methodology","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbenchmark-methodology\u002FSKILL.md",true,[],[68,100,122,148,173,197],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":39},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":39},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[107,108,109,110,84,111,112,113,114,36,115,116,117,118,119,26,120,121,25,96],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","analyze","engine","write","strategy","use","grow","posting",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":131,"publishedAt":39},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发",[132,117,133,134,135,136,137,138,119,139,140,44,141,30,142,143,144,145,146,147],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":39},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,163,119,164,91,165,166,167,168,169,170,171,172],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":39},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[179],{"categoryNo":129,"categoryName":130,"taxonomyType":77,"taxonomyTypeDesc":78},[181,182,183,184,185,134,160,186,187,188,189,190,117,191,90,192,193,194,195,196],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":39},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[204,205,206,207,208,209,210,211,212,189,213,214,215,216,217,218,92,219,220,172],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]