[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWHEM37ZF7HS94H6YSBQCB":3,"skill-same:01M7CWHEM37ZF7HS94H6YSBQCB":52},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CWHEM37ZF7HS94H6YSBQCB","competitive-report-structure",null,"Use after benchmark-methodology has produced scored competitor profile cards. Assembles findings into a decision-grade report: landscape map, competitor profiles, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Final step in the three-skill competitive pipeline.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fcompetitive-report-structure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competitive-report-structure\ndescription: >-\n  Use after benchmark-methodology has produced scored competitor profile cards.\n  Assembles findings into a decision-grade report: landscape map, competitor\n  profiles, benchmarking matrix, white-space analysis, strategic recommendations,\n  and team alignment trigger questions. Final step in the three-skill competitive\n  pipeline.\n---\n\n# Competitive Report Structure\n\nUse this skill to assemble scored competitor cards into a decision-grade report.\nThe report must answer three questions for the client: **who do we compete with,\nhow do we compete, and where is our defensible white-space?** Every section\nearns its place by moving toward those answers — cut anything that doesn't.\n\n## When to Activate\n\n- All competitor profile cards from benchmark-methodology are complete and ready to assemble.\n- Need to present competitive findings to a founder, leadership team, or board.\n- The report must drive decisions (who to compete with, how, where the moat is) — not just document the landscape.\n- Preparing a client deliverable that must be auditable and defensible.\n\n## Client positioning brief (establish first)\n\nBefore assembling the report, establish the client's positioning brief. It\nsupplies:\n\n- **Strategic tension** — the paired axes (e.g., memorability × hireability)\n  that define the client's target white-space. All maps and synthesis resolve\n  back to this tension.\n- **Brand balance** — the intended proportional mix of the client's strategic\n  emphases (e.g., 60% strategy\u002Fevidence, 25% distinctiveness, 15% craft).\n  Every recommendation must be checked against this balance; flag any that\n  would shift it.\n- **Differentiator** — the framing principle for the executive summary and\n  white-space section.\n- **Target quadrant** — where the client intends to sit in the tension map;\n  confirming whether that quadrant is genuinely open is the report's central\n  empirical question.\n\n## Framing principle\n\nThe whole report is organized around the client's strategic tension and\nrecommendations resolve back to the client's deliberate brand balance.\nRecommendations that would break that balance must be flagged against it\nexplicitly — \"this move shifts the balance from X\u002FY\u002FZ toward A\u002FB\u002FC; confirm\nintent.\"\n\n## Report sections\n\n### 1. Executive summary\n3–5 takeaways, decision-first. State the most important findings in plain\nlanguage: where the client is strong, where it's exposed, who occupies its\ntarget white-space, and the top 2–3 moves. Written so a founder\u002FPM reads only\nthis and knows what to do. No methodology here.\n\n### 2. Market landscape & category framing\nDefine the category and map it. Use a **multi-axis map** — at minimum a 2×2\n(e.g., *brand-led \u003C-> capability-led* × *boutique \u003C-> enterprise-scale*), and\nideally the **client's tension plot** from `benchmark-methodology` as the\nheadline map. Place every profiled competitor and the client. The map should\nmake the client's intended position visually obvious and show how crowded (or\nempty) it is.\n\n### 3. Competitor tiers\nOrganize the set into **Direct \u002F Adjacent \u002F Aspirational** (from\n`competitive-platform-analysis`). One short paragraph per tier explaining who's\nin it and why it matters to the client. This sets reader expectations before\nthe detail.\n\n### 4. Benchmarking matrix\nThe full **competitors × dimensions** table — the quantitative spine. Rows =\ncompetitors (grouped by tier), columns = the nine benchmark dimensions (note:\ndimension 9 — strategic tension — has two poles (e.g., Memorability and\nHireability for a brand-studio client; substitute the client's own paired axes);\nrepresent them as two separate sub-columns rather than averaging them). Include\nthe client's own honest self-assessment as a row for contrast. Use a **heatmap**\n(color or symbol scale) so strength\u002Fweakness patterns are scannable. Do **not**\nadd a blended total column — report dimensions separately (per the bias\ncontrols). Call out the columns where the client leads and where it trails.\n\n### 5. Deep dives\n3–5 most instructive competitors in narrative form (from their profile cards).\nChoose for instruction, not ranking: the best exemplar of the target tension\n(high on both poles), the cautionary \"one pole only\" case, the \"competent but\nforgettable\" archetype the client defines against, plus any direct threat. Each\ndeep dive: what they do, what the client should learn, what the client should\navoid.\n\n### 6. White-space & threats\nThe strategic heart. Two parts:\n\n- **White-space:** the position the client can own that rivals don't — argued\n  from the maps and matrix, not asserted. Confirm whether the target quadrant\n  (from the positioning brief) is genuinely open.\n- **Threats:** who\u002Fwhat pressures the client — a rival closing the gap,\n  substitutes (no-code\u002FAI tools, in-house teams, generalist freelancers), or\n  category shifts. Be honest about the client's own risks (e.g., a bold identity\n  reading as un-serious to risk-averse buyers).\n\n### 7. Strategic recommendations\nConcrete, prioritized moves: who the client competes with, how it differentiates,\nand where to invest (offer packaging, evidence\u002Fcase studies, thought leadership,\nbrand sharpening). **Tie every recommendation back to the brand balance from the\npositioning brief** and flag any that would shift it. Sequence by impact ×\neffort.\n\n### 8. Sources \u002F methodology appendix\nThe dimensions, weights, rubrics, the scoped set with tiers, source links per\ncompetitor, and verification notes (asserted vs proven). This is what makes the\nreport auditable and defensible — carry the adversarial citation discipline\nthrough.\n\n## How to present data\n\n- **2×2 \u002F positioning maps** — for landscape and the tension plot. Lead with\n  these; they carry the argument faster than prose.\n- **Heatmap matrix** — for the competitors × dimensions comparison (section 4).\n- **Profile cards** — the source unit feeding deep dives (section 5).\n- **Quadrant callouts** — name who sits in each quadrant explicitly, especially\n  the client's target one.\n- Keep tables scannable; push raw evidence and links to the appendix.\n\n## Decision framework (the report must resolve these)\n\n- **Who do we compete with?** — Name the Direct tier specifically; that's the\n  real fight.\n- **How do we compete?** — State the client's differentiator in one sentence,\n  grounded in the matrix (which dimensions the client owns).\n- **Where are our differentiators defensible?** — Identify the\n  dimensions\u002Fquadrant rivals can't easily copy (the moat), vs. the ones that\n  are table-stakes.\n\n## Trigger questions for the team alignment session\n\nEnd with questions that force decisions, not admiration of the analysis:\n\n- Is the target quadrant truly open, or is a rival already moving in?\n- Which Direct competitor is the sharpest threat in the next 12 months, and\n  what's the counter?\n- Does the brand balance still hold given the landscape — should any emphasis\n  shift?\n- Which dimension where the client trails is worth closing, and which to\n  deliberately concede?\n- What's the one move that most widens distinctiveness *without* costing\n  hireability \u002F credibility?\n\n## Anti-Patterns\n\n- **Leading with methodology.** The executive summary opens with the most important finding, not an explanation of how the benchmark was run. Methodology belongs in the appendix.\n- **Presenting scores without the tension plot.** The 2×2 tension map is the headline artefact. A table of numbers without the map buries the strategic insight.\n- **Omitting the decision framework.** The report must resolve the three questions (who to compete with, how, where the moat is). Leaving these unanswered turns the report into a literature review.\n- **Starting before all profile cards are complete.** Benchmark-methodology must finish before assembly begins. Partial data produces gaps that undermine the heatmap and white-space analysis.\n- **Adding a blended total column to the matrix.** Explicitly excluded — it creates a false composite that obscures the asymmetry the client needs to act on.\n\n## Related Skills\n\n- `benchmark-methodology` — the prerequisite; produces the scored competitor profile cards this skill assembles.\n- `competitive-platform-analysis` — provides the tier structure (Direct \u002F Adjacent \u002F Aspirational) used in Section 3.\n- `brand-discovery` — use to establish the client's positioning brief if it hasn't been defined.\n","# Competitive Report Structure\n\nUse this skill to assemble scored competitor cards into a decision-grade report.\nThe report must answer three questions for the client: **who do we compete with,\nhow do we compete, and where is our defensible white-space?** Every section\nearns its place by moving toward those answers — cut anything that doesn't.\n\n## When to Activate\n\n- All competitor profile cards from benchmark-methodology are complete and ready to assemble.\n- Need to present competitive findings to a founder, leadership team, or board.\n- The report must drive decisions (who to compete with, how, where the moat is) — not just document the landscape.\n- Preparing a client deliverable that must be auditable and defensible.\n\n## Client positioning brief (establish first)\n\nBefore assembling the report, establish the client's positioning brief. It\nsupplies:\n\n- **Strategic tension** — the paired axes (e.g., memorability × hireability)\n  that define the client's target white-space. All maps and synthesis resolve\n  back to this tension.\n- **Brand balance** — the intended proportional mix of the client's strategic\n  emphases (e.g., 60% strategy\u002Fevidence, 25% distinctiveness, 15% craft).\n  Every recommendation must be checked against this balance; flag any that\n  would shift it.\n- **Differentiator** — the framing principle for the executive summary and\n  white-space section.\n- **Target quadrant** — where the client intends to sit in the tension map;\n  confirming whether that quadrant is genuinely open is the report's central\n  empirical question.\n\n## Framing principle\n\nThe whole report is organized around the client's strategic tension and\nrecommendations resolve back to the client's deliberate brand balance.\nRecommendations that would break that balance must be flagged against it\nexplicitly — \"this move shifts the balance from X\u002FY\u002FZ toward A\u002FB\u002FC; confirm\nintent.\"\n\n## Report sections\n\n### 1. Executive summary\n3–5 takeaways, decision-first. State the most important findings in plain\nlanguage: where the client is strong, where it's exposed, who occupies its\ntarget white-space, and the top 2–3 moves. Written so a founder\u002FPM reads only\nthis and knows what to do. No methodology here.\n\n### 2. Market landscape & category framing\nDefine the category and map it. Use a **multi-axis map** — at minimum a 2×2\n(e.g., *brand-led \u003C-> capability-led* × *boutique \u003C-> enterprise-scale*), and\nideally the **client's tension plot** from `benchmark-methodology` as the\nheadline map. Place every profiled competitor and the client. The map should\nmake the client's intended position visually obvious and show how crowded (or\nempty) it is.\n\n### 3. Competitor tiers\nOrganize the set into **Direct \u002F Adjacent \u002F Aspirational** (from\n`competitive-platform-analysis`). One short paragraph per tier explaining who's\nin it and why it matters to the client. This sets reader expectations before\nthe detail.\n\n### 4. Benchmarking matrix\nThe full **competitors × dimensions** table — the quantitative spine. Rows =\ncompetitors (grouped by tier), columns = the nine benchmark dimensions (note:\ndimension 9 — strategic tension — has two poles (e.g., Memorability and\nHireability for a brand-studio client; substitute the client's own paired axes);\nrepresent them as two separate sub-columns rather than averaging them). Include\nthe client's own honest self-assessment as a row for contrast. Use a **heatmap**\n(color or symbol scale) so strength\u002Fweakness patterns are scannable. Do **not**\nadd a blended total column — report dimensions separately (per the bias\ncontrols). Call out the columns where the client leads and where it trails.\n\n### 5. Deep dives\n3–5 most instructive competitors in narrative form (from their profile cards).\nChoose for instruction, not ranking: the best exemplar of the target tension\n(high on both poles), the cautionary \"one pole only\" case, the \"competent but\nforgettable\" archetype the client defines against, plus any direct threat. Each\ndeep dive: what they do, what the client should learn, what the client should\navoid.\n\n### 6. White-space & threats\nThe strategic heart. Two parts:\n\n- **White-space:** the position the client can own that rivals don't — argued\n  from the maps and matrix, not asserted. Confirm whether the target quadrant\n  (from the positioning brief) is genuinely open.\n- **Threats:** who\u002Fwhat pressures the client — a rival closing the gap,\n  substitutes (no-code\u002FAI tools, in-house teams, generalist freelancers), or\n  category shifts. Be honest about the client's own risks (e.g., a bold identity\n  reading as un-serious to risk-averse buyers).\n\n### 7. Strategic recommendations\nConcrete, prioritized moves: who the client competes with, how it differentiates,\nand where to invest (offer packaging, evidence\u002Fcase studies, thought leadership,\nbrand sharpening). **Tie every recommendation back to the brand balance from the\npositioning brief** and flag any that would shift it. Sequence by impact ×\neffort.\n\n### 8. Sources \u002F methodology appendix\nThe dimensions, weights, rubrics, the scoped set with tiers, source links per\ncompetitor, and verification notes (asserted vs proven). This is what makes the\nreport auditable and defensible — carry the adversarial citation discipline\nthrough.\n\n## How to present data\n\n- **2×2 \u002F positioning maps** — for landscape and the tension plot. Lead with\n  these; they carry the argument faster than prose.\n- **Heatmap matrix** — for the competitors × dimensions comparison (section 4).\n- **Profile cards** — the source unit feeding deep dives (section 5).\n- **Quadrant callouts** — name who sits in each quadrant explicitly, especially\n  the client's target one.\n- Keep tables scannable; push raw evidence and links to the appendix.\n\n## Decision framework (the report must resolve these)\n\n- **Who do we compete with?** — Name the Direct tier specifically; that's the\n  real fight.\n- **How do we compete?** — State the client's differentiator in one sentence,\n  grounded in the matrix (which dimensions the client owns).\n- **Where are our differentiators defensible?** — Identify the\n  dimensions\u002Fquadrant rivals can't easily copy (the moat), vs. the ones that\n  are table-stakes.\n\n## Trigger questions for the team alignment session\n\nEnd with questions that force decisions, not admiration of the analysis:\n\n- Is the target quadrant truly open, or is a rival already moving in?\n- Which Direct competitor is the sharpest threat in the next 12 months, and\n  what's the counter?\n- Does the brand balance still hold given the landscape — should any emphasis\n  shift?\n- Which dimension where the client trails is worth closing, and which to\n  deliberately concede?\n- What's the one move that most widens distinctiveness *without* costing\n  hireability \u002F credibility?\n\n## Anti-Patterns\n\n- **Leading with methodology.** The executive summary opens with the most important finding, not an explanation of how the benchmark was run. Methodology belongs in the appendix.\n- **Presenting scores without the tension plot.** The 2×2 tension map is the headline artefact. A table of numbers without the map buries the strategic insight.\n- **Omitting the decision framework.** The report must resolve the three questions (who to compete with, how, where the moat is). Leaving these unanswered turns the report into a literature review.\n- **Starting before all profile cards are complete.** Benchmark-methodology must finish before assembly begins. Partial data produces gaps that undermine the heatmap and white-space analysis.\n- **Adding a blended total column to the matrix.** Explicitly excluded — it creates a false composite that obscures the asymmetry the client needs to act on.\n\n## Related Skills\n\n- `benchmark-methodology` — the prerequisite; produces the scored competitor profile cards this skill assembles.\n- `competitive-platform-analysis` — provides the tier structure (Direct \u002F Adjacent \u002F Aspirational) used in Section 3.\n- `brand-discovery` — use to establish the client's positioning brief if it hasn't been defined.\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","seo\u002Fcompetitive-report-structure","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill competitive-report-structure",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill competitive-report-structure",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill competitive-report-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fcompetitive-report-structure\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",312,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fcompetitive-report-structure\u002Fagents\u002Fopenai.yaml",[53,60,67,75,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]