[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C9CVCCSR0775FEDZDFVRZ4":3,"skill-same:01M7C9CVCCSR0775FEDZDFVRZ4":49},{"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":6,"updatedAt":34,"install":35,"resources":48},"01M7C9CVCCSR0775FEDZDFVRZ4","programmatic-seo",null,"When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions \"programmatic SEO,\" \"template pages,\" \"pages at scale,\" \"directory pages,\" \"location pages,\" \"[keyword] + [city] pages,\" \"comparison pages,\" \"integration pages,\" or \"building many pages for SEO.\" For auditing existing SEO issues, see seo-audit.","azhri1990\u002Fjarvis-mega-repo","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7C4WMQVQ450E0NA99BG7BHA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Fprogrammatic-seo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"programmatic-seo\"\ndescription: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions \"programmatic SEO,\" \"template pages,\" \"pages at scale,\" \"directory pages,\" \"location pages,\" \"[keyword] + [city] pages,\" \"comparison pages,\" \"integration pages,\" or \"building many pages for SEO.\" For auditing existing SEO issues, see seo-audit.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Programmatic SEO\n\nYou are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.\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 designing a programmatic SEO strategy, understand:\n\n1. **Business Context**\n   - What's the product\u002Fservice?\n   - Who is the target audience?\n   - What's the conversion goal for these pages?\n\n2. **Opportunity Assessment**\n   - What search patterns exist?\n   - How many potential pages?\n   - What's the search volume distribution?\n\n3. **Competitive Landscape**\n   - Who ranks for these terms now?\n   - What do their pages look like?\n   - Can you realistically compete?\n\n---\n\n## Core Principles\n\n### 1. Unique Value Per Page\n- Every page must provide value specific to that page\n- Not just swapped variables in a template\n- Maximize unique content—the more differentiated, the better\n\n### 2. Proprietary Data Wins\nHierarchy of data defensibility:\n1. Proprietary (you created it)\n2. Product-derived (from your users)\n3. User-generated (your community)\n4. Licensed (exclusive access)\n5. Public (anyone can use—weakest)\n\n### 3. Clean URL Structure\n**Always use subfolders, not subdomains**:\n- Good: `yoursite.com\u002Ftemplates\u002Fresume\u002F`\n- Bad: `templates.yoursite.com\u002Fresume\u002F`\n\n### 4. Genuine Search Intent Match\nPages must actually answer what people are searching for.\n\n### 5. Quality Over Quantity\nBetter to have 100 great pages than 10,000 thin ones.\n\n### 6. Avoid Google Penalties\n- No doorway pages\n- No keyword stuffing\n- No duplicate content\n- Genuine utility for users\n\n---\n\n## The 12 Playbooks (Overview)\n\n| Playbook | Pattern | Example |\n|----------|---------|---------|\n| Templates | \"[Type] template\" | \"resume template\" |\n| Curation | \"best [category]\" | \"best website builders\" |\n| Conversions | \"[X] to [Y]\" | \"$10 USD to GBP\" |\n| Comparisons | \"[X] vs [Y]\" | \"webflow vs wordpress\" |\n| Examples | \"[type] examples\" | \"landing page examples\" |\n| Locations | \"[service] in [location]\" | \"dentists in austin\" |\n| Personas | \"[product] for [audience]\" | \"crm for real estate\" |\n| Integrations | \"[product A] [product B] integration\" | \"slack asana integration\" |\n| Glossary | \"what is [term]\" | \"what is pSEO\" |\n| Translations | Content in multiple languages | Localized content |\n| Directory | \"[category] tools\" | \"ai copywriting tools\" |\n| Profiles | \"[entity name]\" | \"stripe ceo\" |\n\n---\n\n## Choosing Your Playbook\n\n| If you have... | Consider... |\n|----------------|-------------|\n| Proprietary data | Directories, Profiles |\n| Product with integrations | Integrations |\n| Design\u002Fcreative product | Templates, Examples |\n| Multi-segment audience | Personas |\n| Local presence | Locations |\n| Tool or utility product | Conversions |\n| Content\u002Fexpertise | Glossary, Curation |\n| Competitor landscape | Comparisons |\n\nYou can layer multiple playbooks (e.g., \"Best coworking spaces in San Diego\").\n\n---\n\n## Implementation Framework\n\n### 1. Keyword Pattern Research\n\n**Identify the pattern:**\n- What's the repeating structure?\n- What are the variables?\n- How many unique combinations exist?\n\n**Validate demand:**\n- Aggregate search volume\n- Volume distribution (head vs. long tail)\n- Trend direction\n\n### 2. Data Requirements\n\n**Identify data sources:**\n- What data populates each page?\n- Is it first-party, scraped, licensed, public?\n- How is it updated?\n\n### 3. URL Pattern Generation (bundled tool)\n\nGenerate and sanity-check the URL space before building templates:\n\n```bash\npython3 scripts\u002Furl_pattern_generator.py pattern.json --json   # no arg = embedded demo\n```\n\nGive it the template (e.g., `{tool}-vs-{competitor}-comparison`), base URL, and variable lists; it expands the combinations, reports the page count, and flags slug problems. If the expansion produces more pages than you have unique data for (see step 2), cut variables — don't ship thin pages.\n\n### 4. Template Design\n\n**Page structure:**\n- Header with target keyword\n- Unique intro (not just variables swapped)\n- Data-driven sections\n- Related pages \u002F internal links\n- CTAs appropriate to intent\n\n**Ensuring uniqueness:**\n- Each page needs unique value\n- Conditional content based on data\n- Original insights\u002Fanalysis per page\n\n### 5. Internal Linking Architecture\n\n**Hub and spoke model:**\n- Hub: Main category page\n- Spokes: Individual programmatic pages\n- Cross-links between related spokes\n\n**Avoid orphan pages:**\n- Every page reachable from main site\n- XML sitemap for all pages\n- Breadcrumbs with structured data\n\n### 6. Indexation Strategy\n\n- Prioritize high-volume patterns\n- Noindex very thin variations\n- Manage crawl budget thoughtfully\n- Separate sitemaps by page type\n\n---\n\n## Quality Checks\n\n### Pre-Launch Checklist\n\n**Content quality:**\n- [ ] Each page provides unique value\n- [ ] Answers search intent\n- [ ] Readable and useful\n\n**Technical SEO:**\n- [ ] Unique titles and meta descriptions\n- [ ] Proper heading structure\n- [ ] Schema markup implemented\n- [ ] Page speed acceptable\n\n**Internal linking:**\n- [ ] Connected to site architecture\n- [ ] Related pages linked\n- [ ] No orphan pages\n\n**Indexation:**\n- [ ] In XML sitemap\n- [ ] Crawlable\n- [ ] No conflicting noindex\n\n### Post-Launch Monitoring\n\nTrack: Indexation rate, Rankings, Traffic, Engagement, Conversion\n\nWatch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors\n\n---\n\n## Common Mistakes\n\n- **Thin content**: Just swapping city names in identical content\n- **Keyword cannibalization**: Multiple pages targeting same keyword\n- **Over-generation**: Creating pages with no search demand\n- **Poor data quality**: Outdated or incorrect information\n- **Ignoring UX**: Pages exist for Google, not users\n\n---\n\n## Output Format\n\n### Strategy Document\n- Opportunity analysis\n- Implementation plan\n- Content guidelines\n\n### Page Template\n- URL structure\n- Title\u002Fmeta templates\n- Content outline\n- Schema markup\n\n---\n\n## Task-Specific Questions\n\n1. What keyword patterns are you targeting?\n2. What data do you have (or can acquire)?\n3. How many pages are you planning?\n4. What does your site authority look like?\n5. Who currently ranks for these terms?\n6. What's your technical stack?\n\n---\n\n## Related Skills\n\n- **seo-audit** — WHEN: programmatic pages are live and you need to verify indexation, detect thin content penalties, or diagnose ranking drops across the page set. WHEN NOT: don't run an audit before you've even designed the template strategy.\n- **schema-markup** — WHEN: the chosen playbook benefits from structured data (e.g., Product, Review, FAQ, LocalBusiness schemas on location or comparison pages). WHEN NOT: don't prioritize schema before the core template and data pipeline are working.\n- **competitor-alternatives** — WHEN: the playbook selected is Comparisons (\"[X] vs [Y]\") or Alternatives; that skill has dedicated comparison page frameworks. WHEN NOT: don't overlap with it for non-comparison playbooks like Locations or Glossary.\n- **content-strategy** — WHEN: user needs to decide which pSEO playbook to pursue or how it fits into a broader editorial strategy. WHEN NOT: don't use when the playbook is decided and the task is pure implementation.\n- **site-architecture** — WHEN: the pSEO build is large (500+ pages) and hub-and-spoke or crawl budget management decisions need explicit architectural planning. WHEN NOT: skip for small pSEO pilots (\u003C100 pages) where default hub-and-spoke is sufficient.\n- **marketing-context** — WHEN: always check `.claude\u002Fproduct-marketing-context.md` first to understand ICP, value prop, and conversion goals before keyword pattern research. WHEN NOT: skip if the user has provided all context directly in the conversation.\n\n---\n\n## Communication\n\nAll programmatic SEO output follows this quality standard:\n- Lead with the **Opportunity Analysis** — estimated page count, aggregate search volume, and data source feasibility\n- Strategy documents use the **Strategy → Template → Checklist** structure consistently\n- Every playbook recommendation is paired with a real-world example and a data source suggestion\n- Call out thin-content risk explicitly when the data source is public\u002Fscraped\n- Pre-launch checklists are always included before any \"go build it\" instruction\n- Post-launch monitoring metrics are defined before launch, not after problems appear\n\n---\n\n## Proactive Triggers\n\nAutomatically surface programmatic-seo when:\n\n1. **\"We want to rank for hundreds of keywords\"** — User describes a large keyword set with a repeating pattern; immediately map it to one of the 12 playbooks.\n2. **Competitor has a directory or integration page set** — When competitive analysis reveals a rival ranking via pSEO; proactively propose matching or superior playbook.\n3. **Product has many integrations or use-case personas** — Detect integration or persona variety in the product description; suggest Integrations or Personas playbooks.\n4. **Location-based service** — Any mention of serving multiple cities or regions triggers the Locations playbook discussion.\n5. **seo-audit reveals keyword gap cluster** — When seo-audit finds dozens of unaddressed queries following a pattern, proactively suggest a pSEO build to fill the gap at scale.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Opportunity Analysis | Markdown table | Keyword patterns × estimated volume × data source × difficulty rating |\n| Playbook Selection Matrix | Table | If\u002Fthen mapping of business context to recommended playbook with rationale |\n| Page Template Spec | Markdown with annotated sections | URL pattern, title\u002Fmeta templates, content block structure, unique value rules |\n| Pre-Launch Checklist | Checkbox list | Content quality, technical SEO, internal linking, indexation gates |\n| Post-Launch Monitoring Plan | Table | Metrics to track × tools × alert thresholds × review cadence |\n","# Programmatic SEO\n\nYou are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.\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 designing a programmatic SEO strategy, understand:\n\n1. **Business Context**\n   - What's the product\u002Fservice?\n   - Who is the target audience?\n   - What's the conversion goal for these pages?\n\n2. **Opportunity Assessment**\n   - What search patterns exist?\n   - How many potential pages?\n   - What's the search volume distribution?\n\n3. **Competitive Landscape**\n   - Who ranks for these terms now?\n   - What do their pages look like?\n   - Can you realistically compete?\n\n---\n\n## Core Principles\n\n### 1. Unique Value Per Page\n- Every page must provide value specific to that page\n- Not just swapped variables in a template\n- Maximize unique content—the more differentiated, the better\n\n### 2. Proprietary Data Wins\nHierarchy of data defensibility:\n1. Proprietary (you created it)\n2. Product-derived (from your users)\n3. User-generated (your community)\n4. Licensed (exclusive access)\n5. Public (anyone can use—weakest)\n\n### 3. Clean URL Structure\n**Always use subfolders, not subdomains**:\n- Good: `yoursite.com\u002Ftemplates\u002Fresume\u002F`\n- Bad: `templates.yoursite.com\u002Fresume\u002F`\n\n### 4. Genuine Search Intent Match\nPages must actually answer what people are searching for.\n\n### 5. Quality Over Quantity\nBetter to have 100 great pages than 10,000 thin ones.\n\n### 6. Avoid Google Penalties\n- No doorway pages\n- No keyword stuffing\n- No duplicate content\n- Genuine utility for users\n\n---\n\n## The 12 Playbooks (Overview)\n\n| Playbook | Pattern | Example |\n|----------|---------|---------|\n| Templates | \"[Type] template\" | \"resume template\" |\n| Curation | \"best [category]\" | \"best website builders\" |\n| Conversions | \"[X] to [Y]\" | \"$10 USD to GBP\" |\n| Comparisons | \"[X] vs [Y]\" | \"webflow vs wordpress\" |\n| Examples | \"[type] examples\" | \"landing page examples\" |\n| Locations | \"[service] in [location]\" | \"dentists in austin\" |\n| Personas | \"[product] for [audience]\" | \"crm for real estate\" |\n| Integrations | \"[product A] [product B] integration\" | \"slack asana integration\" |\n| Glossary | \"what is [term]\" | \"what is pSEO\" |\n| Translations | Content in multiple languages | Localized content |\n| Directory | \"[category] tools\" | \"ai copywriting tools\" |\n| Profiles | \"[entity name]\" | \"stripe ceo\" |\n\n---\n\n## Choosing Your Playbook\n\n| If you have... | Consider... |\n|----------------|-------------|\n| Proprietary data | Directories, Profiles |\n| Product with integrations | Integrations |\n| Design\u002Fcreative product | Templates, Examples |\n| Multi-segment audience | Personas |\n| Local presence | Locations |\n| Tool or utility product | Conversions |\n| Content\u002Fexpertise | Glossary, Curation |\n| Competitor landscape | Comparisons |\n\nYou can layer multiple playbooks (e.g., \"Best coworking spaces in San Diego\").\n\n---\n\n## Implementation Framework\n\n### 1. Keyword Pattern Research\n\n**Identify the pattern:**\n- What's the repeating structure?\n- What are the variables?\n- How many unique combinations exist?\n\n**Validate demand:**\n- Aggregate search volume\n- Volume distribution (head vs. long tail)\n- Trend direction\n\n### 2. Data Requirements\n\n**Identify data sources:**\n- What data populates each page?\n- Is it first-party, scraped, licensed, public?\n- How is it updated?\n\n### 3. URL Pattern Generation (bundled tool)\n\nGenerate and sanity-check the URL space before building templates:\n\n```bash\npython3 scripts\u002Furl_pattern_generator.py pattern.json --json   # no arg = embedded demo\n```\n\nGive it the template (e.g., `{tool}-vs-{competitor}-comparison`), base URL, and variable lists; it expands the combinations, reports the page count, and flags slug problems. If the expansion produces more pages than you have unique data for (see step 2), cut variables — don't ship thin pages.\n\n### 4. Template Design\n\n**Page structure:**\n- Header with target keyword\n- Unique intro (not just variables swapped)\n- Data-driven sections\n- Related pages \u002F internal links\n- CTAs appropriate to intent\n\n**Ensuring uniqueness:**\n- Each page needs unique value\n- Conditional content based on data\n- Original insights\u002Fanalysis per page\n\n### 5. Internal Linking Architecture\n\n**Hub and spoke model:**\n- Hub: Main category page\n- Spokes: Individual programmatic pages\n- Cross-links between related spokes\n\n**Avoid orphan pages:**\n- Every page reachable from main site\n- XML sitemap for all pages\n- Breadcrumbs with structured data\n\n### 6. Indexation Strategy\n\n- Prioritize high-volume patterns\n- Noindex very thin variations\n- Manage crawl budget thoughtfully\n- Separate sitemaps by page type\n\n---\n\n## Quality Checks\n\n### Pre-Launch Checklist\n\n**Content quality:**\n- [ ] Each page provides unique value\n- [ ] Answers search intent\n- [ ] Readable and useful\n\n**Technical SEO:**\n- [ ] Unique titles and meta descriptions\n- [ ] Proper heading structure\n- [ ] Schema markup implemented\n- [ ] Page speed acceptable\n\n**Internal linking:**\n- [ ] Connected to site architecture\n- [ ] Related pages linked\n- [ ] No orphan pages\n\n**Indexation:**\n- [ ] In XML sitemap\n- [ ] Crawlable\n- [ ] No conflicting noindex\n\n### Post-Launch Monitoring\n\nTrack: Indexation rate, Rankings, Traffic, Engagement, Conversion\n\nWatch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors\n\n---\n\n## Common Mistakes\n\n- **Thin content**: Just swapping city names in identical content\n- **Keyword cannibalization**: Multiple pages targeting same keyword\n- **Over-generation**: Creating pages with no search demand\n- **Poor data quality**: Outdated or incorrect information\n- **Ignoring UX**: Pages exist for Google, not users\n\n---\n\n## Output Format\n\n### Strategy Document\n- Opportunity analysis\n- Implementation plan\n- Content guidelines\n\n### Page Template\n- URL structure\n- Title\u002Fmeta templates\n- Content outline\n- Schema markup\n\n---\n\n## Task-Specific Questions\n\n1. What keyword patterns are you targeting?\n2. What data do you have (or can acquire)?\n3. How many pages are you planning?\n4. What does your site authority look like?\n5. Who currently ranks for these terms?\n6. What's your technical stack?\n\n---\n\n## Related Skills\n\n- **seo-audit** — WHEN: programmatic pages are live and you need to verify indexation, detect thin content penalties, or diagnose ranking drops across the page set. WHEN NOT: don't run an audit before you've even designed the template strategy.\n- **schema-markup** — WHEN: the chosen playbook benefits from structured data (e.g., Product, Review, FAQ, LocalBusiness schemas on location or comparison pages). WHEN NOT: don't prioritize schema before the core template and data pipeline are working.\n- **competitor-alternatives** — WHEN: the playbook selected is Comparisons (\"[X] vs [Y]\") or Alternatives; that skill has dedicated comparison page frameworks. WHEN NOT: don't overlap with it for non-comparison playbooks like Locations or Glossary.\n- **content-strategy** — WHEN: user needs to decide which pSEO playbook to pursue or how it fits into a broader editorial strategy. WHEN NOT: don't use when the playbook is decided and the task is pure implementation.\n- **site-architecture** — WHEN: the pSEO build is large (500+ pages) and hub-and-spoke or crawl budget management decisions need explicit architectural planning. WHEN NOT: skip for small pSEO pilots (\u003C100 pages) where default hub-and-spoke is sufficient.\n- **marketing-context** — WHEN: always check `.claude\u002Fproduct-marketing-context.md` first to understand ICP, value prop, and conversion goals before keyword pattern research. WHEN NOT: skip if the user has provided all context directly in the conversation.\n\n---\n\n## Communication\n\nAll programmatic SEO output follows this quality standard:\n- Lead with the **Opportunity Analysis** — estimated page count, aggregate search volume, and data source feasibility\n- Strategy documents use the **Strategy → Template → Checklist** structure consistently\n- Every playbook recommendation is paired with a real-world example and a data source suggestion\n- Call out thin-content risk explicitly when the data source is public\u002Fscraped\n- Pre-launch checklists are always included before any \"go build it\" instruction\n- Post-launch monitoring metrics are defined before launch, not after problems appear\n\n---\n\n## Proactive Triggers\n\nAutomatically surface programmatic-seo when:\n\n1. **\"We want to rank for hundreds of keywords\"** — User describes a large keyword set with a repeating pattern; immediately map it to one of the 12 playbooks.\n2. **Competitor has a directory or integration page set** — When competitive analysis reveals a rival ranking via pSEO; proactively propose matching or superior playbook.\n3. **Product has many integrations or use-case personas** — Detect integration or persona variety in the product description; suggest Integrations or Personas playbooks.\n4. **Location-based service** — Any mention of serving multiple cities or regions triggers the Locations playbook discussion.\n5. **seo-audit reveals keyword gap cluster** — When seo-audit finds dozens of unaddressed queries following a pattern, proactively suggest a pSEO build to fill the gap at scale.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Opportunity Analysis | Markdown table | Keyword patterns × estimated volume × data source × difficulty rating |\n| Playbook Selection Matrix | Table | If\u002Fthen mapping of business context to recommended playbook with rationale |\n| Page Template Spec | Markdown with annotated sections | URL pattern, title\u002Fmeta templates, content block structure, unique value rules |\n| Pre-Launch Checklist | Checkbox list | Content quality, technical SEO, internal linking, indexation gates |\n| Post-Launch Monitoring Plan | Table | Metrics to track × tools × alert thresholds × review cadence |\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Fprogrammatic-seo","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill programmatic-seo",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill programmatic-seo",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill programmatic-seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Fprogrammatic-seo\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CYPF9V9EMA4ZXS1TTCMBFH","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. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CYNRJDTQCRF5KGPMBMSB1S","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. Use when the user requests multi-source recency intelligence on a topic (e.g., '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]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CYNAVSE84QD7HAWZWTY2FS","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. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). 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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CYN0CE8P5ZN7WV2X06HKPC","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CYMHZ3QRJ9BKRB859KW8TQ","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.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' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., '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 use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CYM3D8YKV7R6DT4RNJSF0A","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]