[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7854ASXF58EWNGVRJ75V7G2":3,"skill-same:01M7854ASXF58EWNGVRJ75V7G2":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":49},"01M7854ASXF58EWNGVRJ75V7G2","seo-content",null,"Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when user says \"content quality\", \"E-E-A-T\", \"content analysis\", \"readability check\", \"thin content\", or \"content audit\".","optimisticjp\u002FPrangan-One","optimisticjp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F287997793?v=4","01M7839VP6393NGATJTSP7FD99","01M7839VPST0N0M97782JZGYC6",0,"MIT","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-content\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-content\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-content\ndescription: >\n  Content quality and E-E-A-T analysis with AI citation readiness assessment.\n  Use when user says \"content quality\", \"E-E-A-T\", \"content analysis\",\n  \"readability check\", \"thin content\", or \"content audit\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.0\"\n  category: seo\n---\n\n# Content Quality & E-E-A-T Analysis\n\n## Google's \"Who \u002F How \u002F Why\" Test (canonical heuristic)\n\nBefore scoring E-E-A-T sub-factors, every page audit should pass Google's\nown three-question heuristic from the helpful-content guide:\n\n| Question | What to look for |\n|---|---|\n| **Who** created it? | Visible byline, author bio page, professional credentials. Required where readers expect it; non-negotiable for YMYL. |\n| **How** was it created? | Process disclosure where readers would reasonably ask — especially for AI-assisted content. Original research \u002F first-hand evidence \u002F lived experience. |\n| **Why** does it exist? | \"To help people\" rather than \"to attract search clicks.\" Watch for niche entry without expertise, content churn for freshness signals, content written to a word-count target. |\n\nPrimary source:\nhttps:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fcreating-helpful-content\n\nWhen all three answers are weak, the page is at risk under the core ranking\nsystem's helpfulness signals (formerly the standalone Helpful Content System,\nmerged into core during the March 2024 update).\n\n## E-E-A-T Framework (updated Sept 2025 QRG)\n\nRead `skills\u002Fseo\u002Freferences\u002Feeat-framework.md` for full criteria.\n\n### Experience (first-hand signals)\n- Original research, case studies, before\u002Fafter results\n- Personal anecdotes, process documentation\n- Unique data, proprietary insights\n- Photos\u002Fvideos from direct experience\n\n### Expertise\n- Author credentials, certifications, bio\n- Professional background relevant to topic\n- Technical depth appropriate for audience\n- Accurate, well-sourced claims\n\n### Authoritativeness\n- External citations, backlinks from authoritative sources\n- Brand mentions, industry recognition\n- Published in recognized outlets\n- Cited by other experts\n\n### Trustworthiness\n- Contact information, physical address\n- Privacy policy, terms of service\n- Customer testimonials, reviews\n- Date stamps, transparent corrections\n- Secure site (HTTPS)\n\n## Content Metrics\n\n### Word Count Analysis\nCompare against page type minimums:\n| Page Type | Minimum |\n|-----------|---------|\n| Homepage | 500 |\n| Service page | 800 |\n| Blog post | 1,500 |\n| Product page | 300+ (400+ for complex products) |\n| Location page | 500-600 |\n\n> **Important:** These are **topical coverage floors**, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage; a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements.\n\n### Readability\n- Flesch Reading Ease: target 60-70 for general audience\n\n> **Note:** Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly.\n- Grade level: match target audience\n- Sentence length: average 15-20 words\n- Paragraph length: 2-4 sentences\n\n### Keyword Optimization\n- Primary keyword in title, H1, first 100 words\n- Natural density (1-3%)\n- Semantic variations present\n- No keyword stuffing\n\n### Content Structure\n- Logical heading hierarchy (H1 -> H2 -> H3)\n- Scannable sections with descriptive headings\n- Bullet\u002Fnumbered lists where appropriate\n- Table of contents for long-form content\n\n### Multimedia\n- Relevant images with proper alt text\n- Videos where appropriate\n- Infographics for complex data\n- Charts\u002Fgraphs for statistics\n\n### Internal Linking\n- 3-5 relevant internal links per 1000 words\n- Descriptive anchor text\n- Links to related content\n- No orphan pages\n\n### External Linking\n- Cite authoritative sources\n- Open in new tab for user experience\n- Reasonable count (not excessive)\n\n## AI Content Assessment (Sept 2025 QRG addition)\n\nGoogle's raters now formally assess whether content appears AI-generated.\n\n### Acceptable AI Content\n- Demonstrates genuine E-E-A-T\n- Provides unique value\n- Has human oversight and editing\n- Contains original insights\n\n### Low-Quality AI Content Markers\n- Generic phrasing, lack of specificity\n- No original insight\n- Repetitive structure across pages\n- No author attribution\n- Factual inaccuracies\n\n> **Helpful Content System (March 2024):** The Helpful Content System was merged into Google's core ranking algorithm during the March 2024 core update. It no longer operates as a standalone classifier. Helpfulness signals are now weighted within every core update. The same principles apply (people-first content, demonstrating E-E-A-T, satisfying user intent), but enforcement is continuous rather than through separate HCU updates.\n\n## AI Citation Readiness (GEO signals)\n\nOptimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews):\n\n- Clear, quotable statements with statistics\u002Ffacts\n- Structured data (especially for data points)\n- Strong heading hierarchy (H1->H2->H3 flow)\n- Answer-first formatting for key questions\n- Tables and lists for comparative data\n- Clear attribution and source citations\n\n### AI Search Visibility & GEO (2025-2026)\n\n**Google AI Mode** is Google's conversational AI search surface — powered by **Gemini 3.5 Flash** since I\u002FO 2026 (May 2026) and now past **1 billion monthly users** globally. Unlike AI Overviews (which appear above organic results), AI Mode is a fully conversational experience with **zero organic blue links**, making AI citation the only visibility mechanism. It is a *distinct citation engine* from AI Overviews — the two share only ~14% of cited URLs — so optimize for both surfaces, not one (see the `seo-geo` skill).\n\n**Key optimization strategies for AI citation:**\n- **Structured answers:** Clear question-answer formats, definition patterns, and step-by-step instructions that AI systems can extract and cite\n- **First-party data:** Original research, statistics, case studies, and unique datasets are highly cited by AI systems\n- **Schema markup:** Article, FAQPage (Google retired FAQ *rich results* in May 2026, but the markup still aids AI parsing\u002Fentity resolution) or QAPage for genuine user Q&A, and structured content schemas help AI systems parse and attribute content\n- **Topical authority:** AI systems preferentially cite sources that demonstrate deep expertise. Build content clusters, not isolated pages\n- **Entity clarity:** Ensure brand, authors, and key concepts are clearly defined with structured data (Organization, Person schema)\n- **Multi-platform tracking:** Monitor visibility across Google AI Overviews, AI Mode, ChatGPT, Perplexity, and Bing Copilot, not just traditional rankings. Treat AI citation as a standalone KPI alongside organic rankings and traffic.\n\n**Generative Engine Optimization (GEO):**\nPer Google's AI optimization guide, \"AEO\" and \"GEO\" are rebranded labels for SEO — AI Overviews and AI Mode are grounded in the same ranking and quality systems as classic Search. The optimization signals that matter (quotability, attribution, heading hierarchy, freshness) are SEO fundamentals applied to AI-search surfaces, not a separate discipline. Cross-reference the `seo-geo` skill for detailed workflows; both surfaces share the primary-source synthesis in `skills\u002Fseo-geo\u002Freferences\u002Fgoogle-ai-optimization-guide.md`.\n\n## Content Freshness\n\n- Publication date visible\n- Last updated date if content has been revised\n- Flag content older than 12 months without update for fast-changing topics\n\n## Output\n\n### Content Quality Score: XX\u002F100\n\n### E-E-A-T Breakdown\n| Factor | Score | Key Signals |\n|--------|-------|-------------|\n| Experience | XX\u002F25 | ... |\n| Expertise | XX\u002F25 | ... |\n| Authoritativeness | XX\u002F25 | ... |\n| Trustworthiness | XX\u002F25 | ... |\n\n### AI Citation Readiness: XX\u002F100\n\n### Issues Found\n### Recommendations\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `kw_data_google_ads_search_volume` for real keyword volume data, `dataforseo_labs_bulk_keyword_difficulty` for difficulty scores, `dataforseo_labs_search_intent` for intent classification, and `content_analysis_summary` for content quality analysis.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Content behind paywall (402\u002F403, login wall) | Report that the content is not publicly accessible. Analyze only the visible portion (meta tags, headers) and note the limitation. |\n| Thin content (fewer than 100 words retrievable) | Report the findings as-is rather than guessing. Flag the page as potentially JavaScript-rendered or gated, and suggest the user provide the full text directly. |\n\n## FLOW Framework Integration\n\nFor prompt-guided content optimization, use `\u002Fseo flow optimize \u003Curl>` and `\u002Fseo flow win \u003Curl>` — FLOW's optimize and win prompts provide structured E-E-A-T improvement and BOFU conversion workflows.\n","# Content Quality & E-E-A-T Analysis\n\n## Google's \"Who \u002F How \u002F Why\" Test (canonical heuristic)\n\nBefore scoring E-E-A-T sub-factors, every page audit should pass Google's\nown three-question heuristic from the helpful-content guide:\n\n| Question | What to look for |\n|---|---|\n| **Who** created it? | Visible byline, author bio page, professional credentials. Required where readers expect it; non-negotiable for YMYL. |\n| **How** was it created? | Process disclosure where readers would reasonably ask — especially for AI-assisted content. Original research \u002F first-hand evidence \u002F lived experience. |\n| **Why** does it exist? | \"To help people\" rather than \"to attract search clicks.\" Watch for niche entry without expertise, content churn for freshness signals, content written to a word-count target. |\n\nPrimary source:\nhttps:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fcreating-helpful-content\n\nWhen all three answers are weak, the page is at risk under the core ranking\nsystem's helpfulness signals (formerly the standalone Helpful Content System,\nmerged into core during the March 2024 update).\n\n## E-E-A-T Framework (updated Sept 2025 QRG)\n\nRead `skills\u002Fseo\u002Freferences\u002Feeat-framework.md` for full criteria.\n\n### Experience (first-hand signals)\n- Original research, case studies, before\u002Fafter results\n- Personal anecdotes, process documentation\n- Unique data, proprietary insights\n- Photos\u002Fvideos from direct experience\n\n### Expertise\n- Author credentials, certifications, bio\n- Professional background relevant to topic\n- Technical depth appropriate for audience\n- Accurate, well-sourced claims\n\n### Authoritativeness\n- External citations, backlinks from authoritative sources\n- Brand mentions, industry recognition\n- Published in recognized outlets\n- Cited by other experts\n\n### Trustworthiness\n- Contact information, physical address\n- Privacy policy, terms of service\n- Customer testimonials, reviews\n- Date stamps, transparent corrections\n- Secure site (HTTPS)\n\n## Content Metrics\n\n### Word Count Analysis\nCompare against page type minimums:\n| Page Type | Minimum |\n|-----------|---------|\n| Homepage | 500 |\n| Service page | 800 |\n| Blog post | 1,500 |\n| Product page | 300+ (400+ for complex products) |\n| Location page | 500-600 |\n\n> **Important:** These are **topical coverage floors**, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage; a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements.\n\n### Readability\n- Flesch Reading Ease: target 60-70 for general audience\n\n> **Note:** Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly.\n- Grade level: match target audience\n- Sentence length: average 15-20 words\n- Paragraph length: 2-4 sentences\n\n### Keyword Optimization\n- Primary keyword in title, H1, first 100 words\n- Natural density (1-3%)\n- Semantic variations present\n- No keyword stuffing\n\n### Content Structure\n- Logical heading hierarchy (H1 -> H2 -> H3)\n- Scannable sections with descriptive headings\n- Bullet\u002Fnumbered lists where appropriate\n- Table of contents for long-form content\n\n### Multimedia\n- Relevant images with proper alt text\n- Videos where appropriate\n- Infographics for complex data\n- Charts\u002Fgraphs for statistics\n\n### Internal Linking\n- 3-5 relevant internal links per 1000 words\n- Descriptive anchor text\n- Links to related content\n- No orphan pages\n\n### External Linking\n- Cite authoritative sources\n- Open in new tab for user experience\n- Reasonable count (not excessive)\n\n## AI Content Assessment (Sept 2025 QRG addition)\n\nGoogle's raters now formally assess whether content appears AI-generated.\n\n### Acceptable AI Content\n- Demonstrates genuine E-E-A-T\n- Provides unique value\n- Has human oversight and editing\n- Contains original insights\n\n### Low-Quality AI Content Markers\n- Generic phrasing, lack of specificity\n- No original insight\n- Repetitive structure across pages\n- No author attribution\n- Factual inaccuracies\n\n> **Helpful Content System (March 2024):** The Helpful Content System was merged into Google's core ranking algorithm during the March 2024 core update. It no longer operates as a standalone classifier. Helpfulness signals are now weighted within every core update. The same principles apply (people-first content, demonstrating E-E-A-T, satisfying user intent), but enforcement is continuous rather than through separate HCU updates.\n\n## AI Citation Readiness (GEO signals)\n\nOptimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews):\n\n- Clear, quotable statements with statistics\u002Ffacts\n- Structured data (especially for data points)\n- Strong heading hierarchy (H1->H2->H3 flow)\n- Answer-first formatting for key questions\n- Tables and lists for comparative data\n- Clear attribution and source citations\n\n### AI Search Visibility & GEO (2025-2026)\n\n**Google AI Mode** is Google's conversational AI search surface — powered by **Gemini 3.5 Flash** since I\u002FO 2026 (May 2026) and now past **1 billion monthly users** globally. Unlike AI Overviews (which appear above organic results), AI Mode is a fully conversational experience with **zero organic blue links**, making AI citation the only visibility mechanism. It is a *distinct citation engine* from AI Overviews — the two share only ~14% of cited URLs — so optimize for both surfaces, not one (see the `seo-geo` skill).\n\n**Key optimization strategies for AI citation:**\n- **Structured answers:** Clear question-answer formats, definition patterns, and step-by-step instructions that AI systems can extract and cite\n- **First-party data:** Original research, statistics, case studies, and unique datasets are highly cited by AI systems\n- **Schema markup:** Article, FAQPage (Google retired FAQ *rich results* in May 2026, but the markup still aids AI parsing\u002Fentity resolution) or QAPage for genuine user Q&A, and structured content schemas help AI systems parse and attribute content\n- **Topical authority:** AI systems preferentially cite sources that demonstrate deep expertise. Build content clusters, not isolated pages\n- **Entity clarity:** Ensure brand, authors, and key concepts are clearly defined with structured data (Organization, Person schema)\n- **Multi-platform tracking:** Monitor visibility across Google AI Overviews, AI Mode, ChatGPT, Perplexity, and Bing Copilot, not just traditional rankings. Treat AI citation as a standalone KPI alongside organic rankings and traffic.\n\n**Generative Engine Optimization (GEO):**\nPer Google's AI optimization guide, \"AEO\" and \"GEO\" are rebranded labels for SEO — AI Overviews and AI Mode are grounded in the same ranking and quality systems as classic Search. The optimization signals that matter (quotability, attribution, heading hierarchy, freshness) are SEO fundamentals applied to AI-search surfaces, not a separate discipline. Cross-reference the `seo-geo` skill for detailed workflows; both surfaces share the primary-source synthesis in `skills\u002Fseo-geo\u002Freferences\u002Fgoogle-ai-optimization-guide.md`.\n\n## Content Freshness\n\n- Publication date visible\n- Last updated date if content has been revised\n- Flag content older than 12 months without update for fast-changing topics\n\n## Output\n\n### Content Quality Score: XX\u002F100\n\n### E-E-A-T Breakdown\n| Factor | Score | Key Signals |\n|--------|-------|-------------|\n| Experience | XX\u002F25 | ... |\n| Expertise | XX\u002F25 | ... |\n| Authoritativeness | XX\u002F25 | ... |\n| Trustworthiness | XX\u002F25 | ... |\n\n### AI Citation Readiness: XX\u002F100\n\n### Issues Found\n### Recommendations\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `kw_data_google_ads_search_volume` for real keyword volume data, `dataforseo_labs_bulk_keyword_difficulty` for difficulty scores, `dataforseo_labs_search_intent` for intent classification, and `content_analysis_summary` for content quality analysis.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Content behind paywall (402\u002F403, login wall) | Report that the content is not publicly accessible. Analyze only the visible portion (meta tags, headers) and note the limitation. |\n| Thin content (fewer than 100 words retrievable) | Report the findings as-is rather than guessing. Flag the page as potentially JavaScript-rendered or gated, and suggest the user provide the full text directly. |\n\n## FLOW Framework Integration\n\nFor prompt-guided content optimization, use `\u002Fseo flow optimize \u003Curl>` and `\u002Fseo flow win \u003Curl>` — FLOW's optimize and win prompts provide structured E-E-A-T improvement and BOFU conversion workflows.\n",{"name":5,"license":14,"metadata":24,"description":28,"argument-hint":29,"user-invocable":30},{"author":25,"version":26,"category":27},"AgriciDaniel","2.2.0","seo","Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when user says \"content quality\", \"E-E-A-T\", \"content analysis\", \"readability check\", \"thin content\", or \"content audit\".\n","[url]",true,"main","a5e70e5129a5fe99bc71b4c89f24890efda8cb61",".claude\u002Fskills\u002Fseo-content","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One","https:\u002F\u002Fgithub.com\u002Foptimisticjp","2026-10-09 19:00:46",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":30},[39,42,45],{"tool":40,"command":41},"npx","npx skills add optimisticjp\u002FPrangan-One --skill seo-content",{"tool":43,"command":44},"bunx","bunx skills add optimisticjp\u002FPrangan-One --skill seo-content",{"tool":46,"command":47},"pnpm","pnpm dlx skills add optimisticjp\u002FPrangan-One --skill seo-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-content\u002FSKILL.md",[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",143,[56,63,70,77,84,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M785JBXDEJ8PYZWRRP0SBXK6","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M785GBBW2Y6SGT2Z7VC6YCWA","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvenue-templates\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M785G4F7S186ZAK1R8Z30T65","vaex","Use this skill for processing and analyzing large tabular datasets (billions of rows) that exceed available RAM. Vaex excels at out-of-core DataFrame operations, lazy evaluation, fast aggregations, efficient visualization of big data, and machine learning on large datasets. Apply when users need to work with large CSV\u002FHDF5\u002FArrow\u002FParquet files, perform fast statistics on massive datasets, create visualizations of big data, or build ML pipelines that do not fit in memory.","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvaex\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M785G13P2T9CP37JMKB6V8PE","usfiscaldata","Query the U.S. Treasury Fiscal Data REST API for federal financial data. No API key required. Use for national debt (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates, foreign exchange rates, savings bonds, or U.S. government revenue and spending statistics.","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fusfiscaldata\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M785F4RSRGPR0APFJ6N9G3A6","ckm:ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M785ENP34D6KNV5V0H5AZ950","treatment-plans","Generate concise (3-4 page), focused medical treatment plans in LaTeX\u002FPDF format for all clinical specialties. Supports general medical treatment, rehabilitation therapy, mental health care, chronic disease management, perioperative care, and pain management. Includes SMART goal frameworks, evidence-based interventions with minimal text citations, regulatory compliance (HIPAA), and professional formatting. Prioritizes brevity and clinical actionability.","https:\u002F\u002Fgithub.com\u002Foptimisticjp\u002FPrangan-One\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftreatment-plans\u002FSKILL.md",[],[]]