[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78JE14CD58YYHJCT0BGCPDQ":3,"skill-same:01M78JE14CD58YYHJCT0BGCPDQ":66},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M78JE14CD58YYHJCT0BGCPDQ","competitor-alternatives",null,"When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'switch from competitor,' or 'comparison content.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.","aneeba-pixel\u002Fclaude-skills","aneeba-pixel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F218186338?v=4","01M78GRXBTG70217SH410P543Y","Aneeba Saeed","01M78GRXCDZ6TA0F8H2CZMDGSS",0,"MIT","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fmarketing-skill\u002Fskills\u002Fcompetitor-alternatives\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"competitor-alternatives\"\ndescription: \"When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'switch from competitor,' or 'comparison content.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Competitor & Alternative Pages\n\nYou are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating competitor pages, understand:\n\n1. **Your Product**\n   - Core value proposition\n   - Key differentiators\n   - Ideal customer profile\n   - Pricing model\n   - Strengths and honest weaknesses\n\n2. **Competitive Landscape**\n   - Direct competitors\n   - Indirect\u002Fadjacent competitors\n   - Market positioning of each\n   - Search volume for competitor terms\n\n3. **Goals**\n   - SEO traffic capture\n   - Sales enablement\n   - Conversion from competitor users\n   - Brand positioning\n\n---\n\n## Core Principles\n\n### 1. Honesty Builds Trust\n- Acknowledge competitor strengths\n- Be accurate about your limitations\n- Don't misrepresent competitor features\n- Readers are comparing—they'll verify claims\n\n### 2. Depth Over Surface\n- Go beyond feature checklists\n- Explain *why* differences matter\n- Include use cases and scenarios\n- Show, don't just tell\n\n### 3. Help Them Decide\n- Different tools fit different needs\n- Be clear about who you're best for\n- Be clear about who competitor is best for\n- Reduce evaluation friction\n\n### 4. Modular Content Architecture\n- Competitor data should be centralized\n- Updates propagate to all pages\n- Single source of truth per competitor\n\n---\n\n## Page Formats\n\n### Format 1: [Competitor] Alternative (Singular)\n\n**Search intent**: User is actively looking to switch from a specific competitor\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]` or `\u002F[competitor]-alternative`\n\n**Target keywords**: \"[Competitor] alternative\", \"alternative to [Competitor]\", \"switch from [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (validate their pain)\n2. Summary: You as the alternative (quick positioning)\n3. Detailed comparison (features, service, pricing)\n4. Who should switch (and who shouldn't)\n5. Migration path\n6. Social proof from switchers\n7. CTA\n\n---\n\n### Format 2: [Competitor] Alternatives (Plural)\n\n**Search intent**: User is researching options, earlier in journey\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]-alternatives`\n\n**Target keywords**: \"[Competitor] alternatives\", \"best [Competitor] alternatives\", \"tools like [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (common pain points)\n2. What to look for in an alternative (criteria framework)\n3. List of alternatives (you first, but include real options)\n4. Comparison table (summary)\n5. Detailed breakdown of each alternative\n6. Recommendation by use case\n7. CTA\n\n**Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.\n\n---\n\n### Format 3: You vs [Competitor]\n\n**Search intent**: User is directly comparing you to a specific competitor\n\n**URL pattern**: `\u002Fvs\u002F[competitor]` or `\u002Fcompare\u002F[you]-vs-[competitor]`\n\n**Target keywords**: \"[You] vs [Competitor]\", \"[Competitor] vs [You]\"\n\n**Page structure**:\n1. TL;DR summary (key differences in 2-3 sentences)\n2. At-a-glance comparison table\n3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)\n4. Who [You] is best for\n5. Who [Competitor] is best for (be honest)\n6. What customers say (testimonials from switchers)\n7. Migration support\n8. CTA\n\n---\n\n### Format 4: [Competitor A] vs [Competitor B]\n\n**Search intent**: User comparing two competitors (not you directly)\n\n**URL pattern**: `\u002Fcompare\u002F[competitor-a]-vs-[competitor-b]`\n\n**Page structure**:\n1. Overview of both products\n2. Comparison by category\n3. Who each is best for\n4. The third option (introduce yourself)\n5. Comparison table (all three)\n6. CTA\n\n**Why this works**: Captures search traffic for competitor terms, positions you as knowledgeable.\n\n---\n\n## Essential Sections\n\n### TL;DR Summary\nStart every page with a quick summary for scanners—key differences in 2-3 sentences.\n\n### Paragraph Comparisons\nGo beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.\n\n### Feature Comparison\nFor each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.\n\n### Pricing Comparison\nInclude tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.\n\n### Who It's For\nBe explicit about ideal customer for each option. Honest recommendations build trust.\n\n### Migration Section\nCover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.\n\n**For detailed templates**: See [references\u002Ftemplates.md](references\u002Ftemplates.md)\n\n---\n\n## Content Architecture\n\n### Centralized Competitor Data\nCreate a single source of truth for each competitor with:\n- Positioning and target audience\n- Pricing (all tiers)\n- Feature ratings\n- Strengths and weaknesses\n- Best for \u002F not ideal for\n- Common complaints (from reviews)\n- Migration notes\n\n**For data structure and examples**: See [references\u002Fcontent-architecture.md](references\u002Fcontent-architecture.md)\n\n---\n\n## Research Process\n\n### Deep Competitor Research\n\nFor each competitor, gather:\n\n1. **Product research**: Sign up, use it, document features\u002FUX\u002Flimitations\n2. **Pricing research**: Current pricing, what's included, hidden costs\n3. **Review mining**: G2, Capterra, TrustRadius for common praise\u002Fcomplaint themes\n4. **Customer feedback**: Talk to customers who switched (both directions)\n5. **Content research**: Their positioning, their comparison pages, their changelog\n\n### Ongoing Updates\n\n- **Quarterly**: Verify pricing, check for major feature changes\n- **When notified**: Customer mentions competitor change\n- **Annually**: Full refresh of all competitor data\n\n---\n\n## SEO Considerations\n\n### Keyword Targeting\n\n| Format | Primary Keywords |\n|--------|-----------------|\n| Alternative (singular) | [Competitor] alternative, alternative to [Competitor] |\n| Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives |\n| You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] |\n| Competitor vs Competitor | [A] vs [B], [B] vs [A] |\n\n### Internal Linking\n- Link between related competitor pages\n- Link from feature pages to relevant comparisons\n- Create hub page linking to all competitor content\n\n### Schema Markup\nConsider FAQ schema for common questions like \"What is the best alternative to [Competitor]?\"\n\n---\n\n## Output Format\n\n### Competitor Data File\nComplete competitor profile in YAML format for use across all comparison pages.\n\n### Page Content\nFor each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.\n\n### Page Set Plan\nRecommended pages to create with priority order based on search volume.\n\n---\n\n## Task-Specific Questions\n\n1. What are common reasons people switch to you?\n2. Do you have customer quotes about switching?\n3. What's your pricing vs. competitors?\n4. Do you offer migration support?\n\n---\n\n## Proactive Triggers\n\nProactively offer competitor page creation when:\n\n1. **Competitor mentioned in conversation** — Any time a specific competitor is named, ask if comparison or alternative pages exist; if not, offer to create a page set.\n2. **Sales team friction** — User mentions prospects comparing them to a specific tool; immediately offer a vs-page for sales enablement.\n3. **SEO gap identified** — Keyword research shows competitor-branded terms with no coverage; propose a full alternative page set with prioritized build order.\n4. **Switcher testimonial available** — When a customer quote about switching surfaces, offer to build a migration-focused alternative page around it.\n5. **Pricing page review** — When reviewing pricing, note that pricing comparison tables belong on dedicated competitor pages, not the pricing page itself.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Competitor Intelligence File | YAML data file | Centralized competitor profile: pricing, features, weaknesses, review themes |\n| Page Set Plan | Prioritized list | Ranked list of pages to build with target keywords and search volume estimates |\n| Alternative Page (Singular) | Full page copy | Complete `\u002F[competitor]-alternative` page with all sections |\n| Vs Page | Full page copy | Complete `\u002Fvs\u002F[competitor]` page with comparison table and CTA |\n| Migration Guide Section | Markdown block | Reusable migration copy for inclusion across multiple pages |\n\n---\n\n## Communication\n\nAll competitor page outputs should be factually accurate, legally safe (no false claims), and fair to competitors. Acknowledge genuine competitor strengths — pages that only disparage competitors lose credibility with evaluators. Reference `marketing-context` for ICP and positioning before writing any comparison copy. Quality bar: every claim must be verifiable from public sources or customer quotes.\n\n---\n\n## Related Skills\n\n- **seo-audit** — USE to validate that competitor pages meet on-page SEO requirements before publishing; NOT as a replacement for the keyword strategy built here.\n- **copywriting** — USE for writing the narrative sections and CTAs on comparison pages; NOT when the task is purely competitor research and architecture.\n- **content-strategy** — USE when planning a full competitive content program across multiple pages; NOT for single-page execution.\n- **competitive-intel** — USE when C-level strategic competitive analysis is needed beyond page creation; NOT for tactical page writing.\n- **marketing-context** — USE as foundation before any competitor page work to align positioning; always load first.\n","# Competitor & Alternative Pages\n\nYou are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating competitor pages, understand:\n\n1. **Your Product**\n   - Core value proposition\n   - Key differentiators\n   - Ideal customer profile\n   - Pricing model\n   - Strengths and honest weaknesses\n\n2. **Competitive Landscape**\n   - Direct competitors\n   - Indirect\u002Fadjacent competitors\n   - Market positioning of each\n   - Search volume for competitor terms\n\n3. **Goals**\n   - SEO traffic capture\n   - Sales enablement\n   - Conversion from competitor users\n   - Brand positioning\n\n---\n\n## Core Principles\n\n### 1. Honesty Builds Trust\n- Acknowledge competitor strengths\n- Be accurate about your limitations\n- Don't misrepresent competitor features\n- Readers are comparing—they'll verify claims\n\n### 2. Depth Over Surface\n- Go beyond feature checklists\n- Explain *why* differences matter\n- Include use cases and scenarios\n- Show, don't just tell\n\n### 3. Help Them Decide\n- Different tools fit different needs\n- Be clear about who you're best for\n- Be clear about who competitor is best for\n- Reduce evaluation friction\n\n### 4. Modular Content Architecture\n- Competitor data should be centralized\n- Updates propagate to all pages\n- Single source of truth per competitor\n\n---\n\n## Page Formats\n\n### Format 1: [Competitor] Alternative (Singular)\n\n**Search intent**: User is actively looking to switch from a specific competitor\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]` or `\u002F[competitor]-alternative`\n\n**Target keywords**: \"[Competitor] alternative\", \"alternative to [Competitor]\", \"switch from [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (validate their pain)\n2. Summary: You as the alternative (quick positioning)\n3. Detailed comparison (features, service, pricing)\n4. Who should switch (and who shouldn't)\n5. Migration path\n6. Social proof from switchers\n7. CTA\n\n---\n\n### Format 2: [Competitor] Alternatives (Plural)\n\n**Search intent**: User is researching options, earlier in journey\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]-alternatives`\n\n**Target keywords**: \"[Competitor] alternatives\", \"best [Competitor] alternatives\", \"tools like [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (common pain points)\n2. What to look for in an alternative (criteria framework)\n3. List of alternatives (you first, but include real options)\n4. Comparison table (summary)\n5. Detailed breakdown of each alternative\n6. Recommendation by use case\n7. CTA\n\n**Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.\n\n---\n\n### Format 3: You vs [Competitor]\n\n**Search intent**: User is directly comparing you to a specific competitor\n\n**URL pattern**: `\u002Fvs\u002F[competitor]` or `\u002Fcompare\u002F[you]-vs-[competitor]`\n\n**Target keywords**: \"[You] vs [Competitor]\", \"[Competitor] vs [You]\"\n\n**Page structure**:\n1. TL;DR summary (key differences in 2-3 sentences)\n2. At-a-glance comparison table\n3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)\n4. Who [You] is best for\n5. Who [Competitor] is best for (be honest)\n6. What customers say (testimonials from switchers)\n7. Migration support\n8. CTA\n\n---\n\n### Format 4: [Competitor A] vs [Competitor B]\n\n**Search intent**: User comparing two competitors (not you directly)\n\n**URL pattern**: `\u002Fcompare\u002F[competitor-a]-vs-[competitor-b]`\n\n**Page structure**:\n1. Overview of both products\n2. Comparison by category\n3. Who each is best for\n4. The third option (introduce yourself)\n5. Comparison table (all three)\n6. CTA\n\n**Why this works**: Captures search traffic for competitor terms, positions you as knowledgeable.\n\n---\n\n## Essential Sections\n\n### TL;DR Summary\nStart every page with a quick summary for scanners—key differences in 2-3 sentences.\n\n### Paragraph Comparisons\nGo beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.\n\n### Feature Comparison\nFor each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.\n\n### Pricing Comparison\nInclude tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.\n\n### Who It's For\nBe explicit about ideal customer for each option. Honest recommendations build trust.\n\n### Migration Section\nCover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.\n\n**For detailed templates**: See [references\u002Ftemplates.md](references\u002Ftemplates.md)\n\n---\n\n## Content Architecture\n\n### Centralized Competitor Data\nCreate a single source of truth for each competitor with:\n- Positioning and target audience\n- Pricing (all tiers)\n- Feature ratings\n- Strengths and weaknesses\n- Best for \u002F not ideal for\n- Common complaints (from reviews)\n- Migration notes\n\n**For data structure and examples**: See [references\u002Fcontent-architecture.md](references\u002Fcontent-architecture.md)\n\n---\n\n## Research Process\n\n### Deep Competitor Research\n\nFor each competitor, gather:\n\n1. **Product research**: Sign up, use it, document features\u002FUX\u002Flimitations\n2. **Pricing research**: Current pricing, what's included, hidden costs\n3. **Review mining**: G2, Capterra, TrustRadius for common praise\u002Fcomplaint themes\n4. **Customer feedback**: Talk to customers who switched (both directions)\n5. **Content research**: Their positioning, their comparison pages, their changelog\n\n### Ongoing Updates\n\n- **Quarterly**: Verify pricing, check for major feature changes\n- **When notified**: Customer mentions competitor change\n- **Annually**: Full refresh of all competitor data\n\n---\n\n## SEO Considerations\n\n### Keyword Targeting\n\n| Format | Primary Keywords |\n|--------|-----------------|\n| Alternative (singular) | [Competitor] alternative, alternative to [Competitor] |\n| Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives |\n| You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] |\n| Competitor vs Competitor | [A] vs [B], [B] vs [A] |\n\n### Internal Linking\n- Link between related competitor pages\n- Link from feature pages to relevant comparisons\n- Create hub page linking to all competitor content\n\n### Schema Markup\nConsider FAQ schema for common questions like \"What is the best alternative to [Competitor]?\"\n\n---\n\n## Output Format\n\n### Competitor Data File\nComplete competitor profile in YAML format for use across all comparison pages.\n\n### Page Content\nFor each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.\n\n### Page Set Plan\nRecommended pages to create with priority order based on search volume.\n\n---\n\n## Task-Specific Questions\n\n1. What are common reasons people switch to you?\n2. Do you have customer quotes about switching?\n3. What's your pricing vs. competitors?\n4. Do you offer migration support?\n\n---\n\n## Proactive Triggers\n\nProactively offer competitor page creation when:\n\n1. **Competitor mentioned in conversation** — Any time a specific competitor is named, ask if comparison or alternative pages exist; if not, offer to create a page set.\n2. **Sales team friction** — User mentions prospects comparing them to a specific tool; immediately offer a vs-page for sales enablement.\n3. **SEO gap identified** — Keyword research shows competitor-branded terms with no coverage; propose a full alternative page set with prioritized build order.\n4. **Switcher testimonial available** — When a customer quote about switching surfaces, offer to build a migration-focused alternative page around it.\n5. **Pricing page review** — When reviewing pricing, note that pricing comparison tables belong on dedicated competitor pages, not the pricing page itself.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Competitor Intelligence File | YAML data file | Centralized competitor profile: pricing, features, weaknesses, review themes |\n| Page Set Plan | Prioritized list | Ranked list of pages to build with target keywords and search volume estimates |\n| Alternative Page (Singular) | Full page copy | Complete `\u002F[competitor]-alternative` page with all sections |\n| Vs Page | Full page copy | Complete `\u002Fvs\u002F[competitor]` page with comparison table and CTA |\n| Migration Guide Section | Markdown block | Reusable migration copy for inclusion across multiple pages |\n\n---\n\n## Communication\n\nAll competitor page outputs should be factually accurate, legally safe (no false claims), and fair to competitors. Acknowledge genuine competitor strengths — pages that only disparage competitors lose credibility with evaluators. Reference `marketing-context` for ICP and positioning before writing any comparison copy. Quality bar: every claim must be verifiable from public sources or customer quotes.\n\n---\n\n## Related Skills\n\n- **seo-audit** — USE to validate that competitor pages meet on-page SEO requirements before publishing; NOT as a replacement for the keyword strategy built here.\n- **copywriting** — USE for writing the narrative sections and CTAs on comparison pages; NOT when the task is purely competitor research and architecture.\n- **content-strategy** — USE when planning a full competitive content program across multiple pages; NOT for single-page execution.\n- **competitive-intel** — USE when C-level strategic competitive analysis is needed beyond page creation; NOT for tactical page writing.\n- **marketing-context** — USE as foundation before any competitor page work to align positioning; always load first.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","claude\u002Fopen-prs-review-Of9HK","a48d8438efe8e36550acc4c2006bdcddf62911db","marketing-skill\u002Fskills\u002Fcompetitor-alternatives","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Faneeba-pixel","Student at University of Gujrat","2026-07-14 21:41:17",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add aneeba-pixel\u002Fclaude-skills --skill competitor-alternatives",{"tool":42,"command":43},"bunx","bunx skills add aneeba-pixel\u002Fclaude-skills --skill competitor-alternatives",{"tool":45,"command":46},"pnpm","pnpm dlx skills add aneeba-pixel\u002Fclaude-skills --skill competitor-alternatives","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fmarketing-skill\u002Fskills\u002Fcompetitor-alternatives\u002FSKILL.md",true,[50,56,60],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcontent-architecture.md","REFERENCE","参考文档",7370,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fmarketing-skill\u002Fskills\u002Fcompetitor-alternatives\u002Freferences\u002Fcontent-architecture.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Ftemplates.md",5084,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fmarketing-skill\u002Fskills\u002Fcompetitor-alternatives\u002Freferences\u002Ftemplates.md",{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Fcomparison_matrix_builder.py","SCRIPT","脚本",14448,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fmarketing-skill\u002Fskills\u002Fcompetitor-alternatives\u002Fscripts\u002Fcomparison_matrix_builder.py",[67,74,81,88,95,102],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78K120A3JKH3NH8GC19YG4M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78K0QS9AGDJ43CPQYEHM5S0","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78K0FV3HMJ94SK965CWMNNP","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M78K04E77B04KYBB6M01EV3J","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M78JZW8XEFZP6HSF53M8D4M1","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M78JZHX45S2Y0GPY9Z5V6TQ3","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]