[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWH93HYS7CPJ7EVZ2QAGPX":3,"skill-same:01M7CWH93HYS7CPJ7EVZ2QAGPX":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},"01M7CWH93HYS7CPJ7EVZ2QAGPX","competitive-platform-analysis",null,"Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong to, and which sources to mine. First step in the three-skill competitive pipeline; precedes benchmark-methodology.","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-platform-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competitive-platform-analysis\ndescription: >-\n  Use when scoping a competitive landscape — identifying, categorising, and\n  score-filtering a competitor set before any benchmarking begins. Decides who\n  counts as a competitor, which tier they belong to, and which sources to mine.\n  First step in the three-skill competitive pipeline; precedes\n  benchmark-methodology.\n---\n\n# Competitive Platform Analysis\n\nUse this skill to decide **who to benchmark** and **where to find them** before\nany scoring begins. A competitive analysis is only as good as its frame: the\nwrong set makes the client look either unbeatable or doomed. The goal is a\ndefensible, decision-relevant set — not an exhaustive census.\n\n## When to Activate\n\n- About to start a competitive benchmarking project and need to define the competitor set first.\n- Unsure which companies belong in Direct \u002F Adjacent \u002F Aspirational tiers.\n- Need a defensible, pruned scope for a market landscape report.\n- Has a positioning brief and wants to identify who contests that position.\n- First step before running benchmark-methodology.\n\n## Client positioning brief (establish first)\n\nBefore scoping the set, establish the client's positioning brief. If you don't\nalready have it, run a short brand-discovery interview to elicit it — do **not**\ninvent one and do **not** scope the set blind. The brief supplies:\n\n- **Identity \u002F aesthetic register** — what kind of studio or company this is and\n  how it presents itself.\n- **Offer** — what services or products it delivers.\n- **Target clients** — who it sells to.\n- **Differentiator** — the moat or positioning argument the client believes in.\n- **Scoping consequence** — the implication for how to weight competitors (e.g.,\n  prioritize by distinctiveness vs. capability overlap vs. price).\n- **Strategic tension** — the paired axes that define the client's white-space\n  (e.g., memorability × hireability).\n\n**Do not proceed without the positioning brief.** A competitor list scoped\nwithout the client's lens is noise, not intelligence. The scoping consequence in\nparticular determines which competitors are *strong* rivals (those that contest\nthe client's moat) vs. merely overlapping on service menu.\n\n## Selection criteria\n\nFor each candidate, capture these axes — they decide both inclusion and tier:\n\n- **Size \u002F model** — solo, micro-studio (2–8), boutique (sub-30), mid-size\n  agency. Match the client's own band; same-band studios are the realistic\n  head-to-head set.\n- **Niche \u002F specialization** — how closely the candidate's focus overlaps with\n  the client's offer. Tighter overlap = more direct.\n- **Geography \u002F market** — EU vs US vs global-remote; language; time-zone reach.\n  Note whether they win the same clients the client targets.\n- **Pricing & engagement model** — productized sprints, retainer, project,\n  day-rate; transparent vs \"contact us\". Signals positioning maturity.\n- **Portfolio style** — generic vs. opinionated\u002Feditorial vs. contrarian. Closer\n  to the client's aesthetic register = more they contest the client's\n  distinctiveness.\n- **Technical depth \u002F craft maturity** — relevant if the client's credibility\n  story includes public process work, open tooling, or documented systems.\n- **Brand strength** — does the studio have an ownable verbal\u002Fvisual identity, or\n  is it interchangeable? Weight this per the client's scoping consequence.\n\n## Player taxonomy — axes to populate across\n\nDon't sort competitors into niche-specific buckets; sort them along a few\ngeneric axes so the landscape isn't skewed toward one archetype. These axes\napply to any creative-service market (design, motion, copywriting, branding,\ncontent, film, etc.). Aim for breadth across each axis first, then prune to the\nmost instructive.\n\n1. **Positioning stance** — *brand-led \u002F editorial* (competes on identity,\n   voice, POV) vs *capability-led* (competes on craft, throughput, outcomes).\n   Populate both poles; the client's closest mirror sits at its own end.\n2. **Specialization** — *specialist* (one tight discipline or vertical) vs\n   *generalist* (broad service menu). Tighter overlap with the client's focus =\n   more direct.\n3. **Size \u002F model** — *solo \u002F micro* vs *boutique* vs *mid-size* vs\n   *enterprise-scale*. Same-band players are the realistic head-to-head; larger\n   bands are the aspirational\u002Fcommercial-maturity reference.\n4. **Engagement format** — *productized* (named sprints, audits, fixed packages)\n   vs *bespoke* (custom project \u002F retainer). Signals positioning maturity.\n5. **Distinctiveness posture** — *conventional \u002F safe* vs *contrarian \u002F\n   manifesto-driven*. The opinionated end is key for distinctiveness\n   benchmarking in any niche.\n6. **Evidence \u002F credibility model** — *outcome-led* (metrics, named clients,\n   case depth) vs *aesthetic-led* (portfolio, awards). Tells you how each player\n   earns trust.\n7. **Brand strength of the operator** — *interchangeable* vs *cult \u002F ownable\n   identity* (including senior independents who prove the \"memorable solo brand\"\n   model).\n8. **Market \u002F reach** — *local \u002F regional* vs *global-remote*; note whether they\n   win the same clients the client targets.\n\nPlot each candidate on the relevant axes; a competitor is *direct* when it sits\nnear the client on positioning, specialization, size, and market at once.\n\n## Competitive tiers (how the set resolves)\n\nGroup the final set into three tiers — this structure carries through to the\nreport:\n\n- **Direct** — same band, overlapping offer, same client targets. The realistic\n  head-to-head.\n- **Adjacent** — partial overlap (one capability, or a different client size)\n  that pressures at the edges.\n- **Aspirational** — players the client is not competing with today but whose\n  brand or commercial maturity sets the bar to aim at.\n- *(Watch also for substitutes: no-code\u002FAI tools, in-house teams, generalist\n  freelancers — note as a threat vector, not a profiled competitor unless\n  materially relevant.)*\n\n## Data sources (where to look)\n\nMatch the source to the dimension you need. The platform *types* below are\ngeneric; substitute the ones native to the client's niche (e.g. Dribbble\u002FBehance\nfor design, showreel\u002FVimeo for motion, writing samples\u002Fpublished work for copy):\n\n- **Portfolio \u002F craft platforms** — craft quality, range, aesthetic register\n  (e.g. Dribbble, Behance, Vimeo, or the niche's equivalent showcase).\n- **Awards \u002F curated showcases** — craft ambition and editorial recognition;\n  over-indexes on flashy, so cross-check commercial credibility (e.g. Awwwards,\n  industry award lists).\n- **Competitor's own site** — primary source for positioning, voice, offer\n  packaging, pricing posture, named clients, manifesto\u002FPOV.\n- **LinkedIn** — team size\u002Fmodel, founder narrative, post cadence, client logos,\n  geography.\n- **Review directories** — reviews, named clients, project sizes, engagement\n  models; strongest signal for commercial credibility and enterprise-readiness\n  (e.g. Clutch.co or the niche's equivalent).\n- **Open \u002F public work** — process repos, published samples, open creative\n  output: depth and craft-transparency evidence.\n- **Conference talks \u002F podcasts \u002F newsletters** — thought-leadership depth and\n  POV ownership.\n\nAlways **verify claims across at least two sources** before treating a competitor\nattribute as fact (self-reported site copy ≠ verified outcome). Carry an\nadversarial-verification discipline into every profile.\n\n## Scoring matrix template (selection stage)\n\nA lightweight pre-filter to decide who graduates into full benchmarking. Score\n1–5; keep candidates that score high on **either** distinctiveness **or**\ncredibility — the client's strategic tension means both poles are instructive.\n\n| Candidate | Positioning stance | Specialization | Size band | Tier | Offer overlap (1–5) | Distinctiveness (1–5) | Commercial credibility (1–5) | Craft proximity (1–5) | Include? |\n|-----------|--------------------|----------------|-----------|------|---------------------|------------------------|------------------------------|------------------------|----------|\n\nRules of thumb (apply per the client's scoping consequence in the positioning brief):\n\n- High distinctiveness **and** high credibility → must-profile (proves the\n  client's target tension is achievable).\n- High distinctiveness, low credibility → cautionary case (memorable but\n  un-hireable — a potential failure mode to learn from).\n- High credibility, low distinctiveness → \"competent but forgettable\" mass the\n  client defines itself against.\n- Low on both → drop unless needed for landscape breadth.\n\n## Output of this stage\n\nA scoped, tiered competitor set (typically 10–18 candidates → 8–12 profiled),\neach tagged with its axis positions, tier, and source links, ready to hand to\n`benchmark-methodology`.\n\n## Anti-Patterns\n\n- **Scoping without a positioning brief.** A competitor list built without the client's lens is noise. The brief determines what counts as a real rival.\n- **Listing every similar company.** The goal is a defensible 10–18 candidate set, not a census. Breadth without pruning makes benchmarking unmanageable.\n- **Blurring the Direct\u002FAdjacent\u002FAspirational tiers.** These tiers serve different strategic purposes. Mixing them produces a flat list that can't drive decisions.\n- **Relying on a single source per competitor.** Self-reported site copy is marketing, not fact. Verify attributes across at least two sources.\n- **Jumping straight to scoring.** This skill scopes and tiers the set. Benchmark-methodology handles scoring. Don't conflate the two steps.\n\n## Examples\n\n**Scenario:** A boutique brand-identity studio (2-person, EU-remote, productized\nsprints, contrarian\u002Fmanifesto-driven aesthetic) wants to scope its competitive\nset before benchmarking. The strategic tension from the positioning brief is\n*memorability × hireability*.\n\n**Step 1 — eight-axis population (sample candidates):**\n\n| Candidate | Positioning stance | Specialization | Size band | Engagement | Distinctiveness | Evidence model | Brand strength | Market |\n|---|---|---|---|---|---|---|---|---|\n| Studio A | brand-led \u002F editorial | identity only | micro | productized | contrarian | aesthetic-led | cult | global-remote |\n| Studio B | capability-led | broad DS+motion | boutique | bespoke | conventional | outcome-led | interchangeable | US |\n| Agency C | capability-led | brand+digital | mid-size | retainer | conventional | outcome-led | interchangeable | EU |\n| Freelancer D | brand-led | brand voice only | solo | day-rate | editorial | aesthetic-led | ownable | global |\n| Studio E | brand-led | brand strategy | micro | productized | manifesto-driven | outcome-led | cult | EU-remote |\n\n**Step 2 — pre-filter scoring (client scoping consequence: weight distinctiveness\nbecause the client's moat is POV-first, not capability breadth):**\n\n| Candidate | Offer overlap (1–5) | Distinctiveness (1–5) | Commercial credibility (1–5) | Craft proximity (1–5) | Tier | Include? |\n|---|---|---|---|---|---|---|\n| Studio A | 5 | 5 | 3 | 5 | Direct | ✓ must-profile |\n| Studio B | 3 | 2 | 5 | 3 | Adjacent | ✓ credibility anchor |\n| Agency C | 2 | 1 | 5 | 2 | Aspirational | ✓ scale reference |\n| Freelancer D | 4 | 4 | 2 | 4 | Direct | ✓ cautionary case |\n| Studio E | 5 | 5 | 4 | 4 | Direct | ✓ must-profile |\n\n**Step 3 — output handed to `benchmark-methodology`:**\nFive candidates (3 Direct, 1 Adjacent, 1 Aspirational), each tagged with\naxis positions, tier, and source links. Studio A and Studio E are the\nsharpest head-to-head rivals; Freelancer D is the \"memorable but\nun-hireable\" cautionary case to learn from.\n\n## Related Skills\n\n- `brand-discovery` — use first to establish the positioning brief and strategic tension that scopes the competitor set.\n- `benchmark-methodology` — the next step; takes the tiered set and scores each competitor across nine dimensions.\n","# Competitive Platform Analysis\n\nUse this skill to decide **who to benchmark** and **where to find them** before\nany scoring begins. A competitive analysis is only as good as its frame: the\nwrong set makes the client look either unbeatable or doomed. The goal is a\ndefensible, decision-relevant set — not an exhaustive census.\n\n## When to Activate\n\n- About to start a competitive benchmarking project and need to define the competitor set first.\n- Unsure which companies belong in Direct \u002F Adjacent \u002F Aspirational tiers.\n- Need a defensible, pruned scope for a market landscape report.\n- Has a positioning brief and wants to identify who contests that position.\n- First step before running benchmark-methodology.\n\n## Client positioning brief (establish first)\n\nBefore scoping the set, establish the client's positioning brief. If you don't\nalready have it, run a short brand-discovery interview to elicit it — do **not**\ninvent one and do **not** scope the set blind. The brief supplies:\n\n- **Identity \u002F aesthetic register** — what kind of studio or company this is and\n  how it presents itself.\n- **Offer** — what services or products it delivers.\n- **Target clients** — who it sells to.\n- **Differentiator** — the moat or positioning argument the client believes in.\n- **Scoping consequence** — the implication for how to weight competitors (e.g.,\n  prioritize by distinctiveness vs. capability overlap vs. price).\n- **Strategic tension** — the paired axes that define the client's white-space\n  (e.g., memorability × hireability).\n\n**Do not proceed without the positioning brief.** A competitor list scoped\nwithout the client's lens is noise, not intelligence. The scoping consequence in\nparticular determines which competitors are *strong* rivals (those that contest\nthe client's moat) vs. merely overlapping on service menu.\n\n## Selection criteria\n\nFor each candidate, capture these axes — they decide both inclusion and tier:\n\n- **Size \u002F model** — solo, micro-studio (2–8), boutique (sub-30), mid-size\n  agency. Match the client's own band; same-band studios are the realistic\n  head-to-head set.\n- **Niche \u002F specialization** — how closely the candidate's focus overlaps with\n  the client's offer. Tighter overlap = more direct.\n- **Geography \u002F market** — EU vs US vs global-remote; language; time-zone reach.\n  Note whether they win the same clients the client targets.\n- **Pricing & engagement model** — productized sprints, retainer, project,\n  day-rate; transparent vs \"contact us\". Signals positioning maturity.\n- **Portfolio style** — generic vs. opinionated\u002Feditorial vs. contrarian. Closer\n  to the client's aesthetic register = more they contest the client's\n  distinctiveness.\n- **Technical depth \u002F craft maturity** — relevant if the client's credibility\n  story includes public process work, open tooling, or documented systems.\n- **Brand strength** — does the studio have an ownable verbal\u002Fvisual identity, or\n  is it interchangeable? Weight this per the client's scoping consequence.\n\n## Player taxonomy — axes to populate across\n\nDon't sort competitors into niche-specific buckets; sort them along a few\ngeneric axes so the landscape isn't skewed toward one archetype. These axes\napply to any creative-service market (design, motion, copywriting, branding,\ncontent, film, etc.). Aim for breadth across each axis first, then prune to the\nmost instructive.\n\n1. **Positioning stance** — *brand-led \u002F editorial* (competes on identity,\n   voice, POV) vs *capability-led* (competes on craft, throughput, outcomes).\n   Populate both poles; the client's closest mirror sits at its own end.\n2. **Specialization** — *specialist* (one tight discipline or vertical) vs\n   *generalist* (broad service menu). Tighter overlap with the client's focus =\n   more direct.\n3. **Size \u002F model** — *solo \u002F micro* vs *boutique* vs *mid-size* vs\n   *enterprise-scale*. Same-band players are the realistic head-to-head; larger\n   bands are the aspirational\u002Fcommercial-maturity reference.\n4. **Engagement format** — *productized* (named sprints, audits, fixed packages)\n   vs *bespoke* (custom project \u002F retainer). Signals positioning maturity.\n5. **Distinctiveness posture** — *conventional \u002F safe* vs *contrarian \u002F\n   manifesto-driven*. The opinionated end is key for distinctiveness\n   benchmarking in any niche.\n6. **Evidence \u002F credibility model** — *outcome-led* (metrics, named clients,\n   case depth) vs *aesthetic-led* (portfolio, awards). Tells you how each player\n   earns trust.\n7. **Brand strength of the operator** — *interchangeable* vs *cult \u002F ownable\n   identity* (including senior independents who prove the \"memorable solo brand\"\n   model).\n8. **Market \u002F reach** — *local \u002F regional* vs *global-remote*; note whether they\n   win the same clients the client targets.\n\nPlot each candidate on the relevant axes; a competitor is *direct* when it sits\nnear the client on positioning, specialization, size, and market at once.\n\n## Competitive tiers (how the set resolves)\n\nGroup the final set into three tiers — this structure carries through to the\nreport:\n\n- **Direct** — same band, overlapping offer, same client targets. The realistic\n  head-to-head.\n- **Adjacent** — partial overlap (one capability, or a different client size)\n  that pressures at the edges.\n- **Aspirational** — players the client is not competing with today but whose\n  brand or commercial maturity sets the bar to aim at.\n- *(Watch also for substitutes: no-code\u002FAI tools, in-house teams, generalist\n  freelancers — note as a threat vector, not a profiled competitor unless\n  materially relevant.)*\n\n## Data sources (where to look)\n\nMatch the source to the dimension you need. The platform *types* below are\ngeneric; substitute the ones native to the client's niche (e.g. Dribbble\u002FBehance\nfor design, showreel\u002FVimeo for motion, writing samples\u002Fpublished work for copy):\n\n- **Portfolio \u002F craft platforms** — craft quality, range, aesthetic register\n  (e.g. Dribbble, Behance, Vimeo, or the niche's equivalent showcase).\n- **Awards \u002F curated showcases** — craft ambition and editorial recognition;\n  over-indexes on flashy, so cross-check commercial credibility (e.g. Awwwards,\n  industry award lists).\n- **Competitor's own site** — primary source for positioning, voice, offer\n  packaging, pricing posture, named clients, manifesto\u002FPOV.\n- **LinkedIn** — team size\u002Fmodel, founder narrative, post cadence, client logos,\n  geography.\n- **Review directories** — reviews, named clients, project sizes, engagement\n  models; strongest signal for commercial credibility and enterprise-readiness\n  (e.g. Clutch.co or the niche's equivalent).\n- **Open \u002F public work** — process repos, published samples, open creative\n  output: depth and craft-transparency evidence.\n- **Conference talks \u002F podcasts \u002F newsletters** — thought-leadership depth and\n  POV ownership.\n\nAlways **verify claims across at least two sources** before treating a competitor\nattribute as fact (self-reported site copy ≠ verified outcome). Carry an\nadversarial-verification discipline into every profile.\n\n## Scoring matrix template (selection stage)\n\nA lightweight pre-filter to decide who graduates into full benchmarking. Score\n1–5; keep candidates that score high on **either** distinctiveness **or**\ncredibility — the client's strategic tension means both poles are instructive.\n\n| Candidate | Positioning stance | Specialization | Size band | Tier | Offer overlap (1–5) | Distinctiveness (1–5) | Commercial credibility (1–5) | Craft proximity (1–5) | Include? |\n|-----------|--------------------|----------------|-----------|------|---------------------|------------------------|------------------------------|------------------------|----------|\n\nRules of thumb (apply per the client's scoping consequence in the positioning brief):\n\n- High distinctiveness **and** high credibility → must-profile (proves the\n  client's target tension is achievable).\n- High distinctiveness, low credibility → cautionary case (memorable but\n  un-hireable — a potential failure mode to learn from).\n- High credibility, low distinctiveness → \"competent but forgettable\" mass the\n  client defines itself against.\n- Low on both → drop unless needed for landscape breadth.\n\n## Output of this stage\n\nA scoped, tiered competitor set (typically 10–18 candidates → 8–12 profiled),\neach tagged with its axis positions, tier, and source links, ready to hand to\n`benchmark-methodology`.\n\n## Anti-Patterns\n\n- **Scoping without a positioning brief.** A competitor list built without the client's lens is noise. The brief determines what counts as a real rival.\n- **Listing every similar company.** The goal is a defensible 10–18 candidate set, not a census. Breadth without pruning makes benchmarking unmanageable.\n- **Blurring the Direct\u002FAdjacent\u002FAspirational tiers.** These tiers serve different strategic purposes. Mixing them produces a flat list that can't drive decisions.\n- **Relying on a single source per competitor.** Self-reported site copy is marketing, not fact. Verify attributes across at least two sources.\n- **Jumping straight to scoring.** This skill scopes and tiers the set. Benchmark-methodology handles scoring. Don't conflate the two steps.\n\n## Examples\n\n**Scenario:** A boutique brand-identity studio (2-person, EU-remote, productized\nsprints, contrarian\u002Fmanifesto-driven aesthetic) wants to scope its competitive\nset before benchmarking. The strategic tension from the positioning brief is\n*memorability × hireability*.\n\n**Step 1 — eight-axis population (sample candidates):**\n\n| Candidate | Positioning stance | Specialization | Size band | Engagement | Distinctiveness | Evidence model | Brand strength | Market |\n|---|---|---|---|---|---|---|---|---|\n| Studio A | brand-led \u002F editorial | identity only | micro | productized | contrarian | aesthetic-led | cult | global-remote |\n| Studio B | capability-led | broad DS+motion | boutique | bespoke | conventional | outcome-led | interchangeable | US |\n| Agency C | capability-led | brand+digital | mid-size | retainer | conventional | outcome-led | interchangeable | EU |\n| Freelancer D | brand-led | brand voice only | solo | day-rate | editorial | aesthetic-led | ownable | global |\n| Studio E | brand-led | brand strategy | micro | productized | manifesto-driven | outcome-led | cult | EU-remote |\n\n**Step 2 — pre-filter scoring (client scoping consequence: weight distinctiveness\nbecause the client's moat is POV-first, not capability breadth):**\n\n| Candidate | Offer overlap (1–5) | Distinctiveness (1–5) | Commercial credibility (1–5) | Craft proximity (1–5) | Tier | Include? |\n|---|---|---|---|---|---|---|\n| Studio A | 5 | 5 | 3 | 5 | Direct | ✓ must-profile |\n| Studio B | 3 | 2 | 5 | 3 | Adjacent | ✓ credibility anchor |\n| Agency C | 2 | 1 | 5 | 2 | Aspirational | ✓ scale reference |\n| Freelancer D | 4 | 4 | 2 | 4 | Direct | ✓ cautionary case |\n| Studio E | 5 | 5 | 4 | 4 | Direct | ✓ must-profile |\n\n**Step 3 — output handed to `benchmark-methodology`:**\nFive candidates (3 Direct, 1 Adjacent, 1 Aspirational), each tagged with\naxis positions, tier, and source links. Studio A and Studio E are the\nsharpest head-to-head rivals; Freelancer D is the \"memorable but\nun-hireable\" cautionary case to learn from.\n\n## Related Skills\n\n- `brand-discovery` — use first to establish the positioning brief and strategic tension that scopes the competitor set.\n- `benchmark-methodology` — the next step; takes the tiered set and scores each competitor across nine dimensions.\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","seo\u002Fcompetitive-platform-analysis","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-platform-analysis",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill competitive-platform-analysis",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill competitive-platform-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fcompetitive-platform-analysis\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",298,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fseo\u002Fcompetitive-platform-analysis\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",[],[]]