[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KT2MM99DSDYMDRWGDM1NBP":3,"skill-same:01M6KT2MM99DSDYMDRWGDM1NBP":76},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6KT2MM99DSDYMDRWGDM1NBP","ckm:marketing-research",null,"Research market trends, competitors, audience insights, and marketing best practices. Use before marketing-planning for data-driven strategy.","devmotminh\u002Fplayscored","devmotminh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F133726659?v=4","01M6KSRTWXJ4EW9RPFDYZQ0MYH","01M6KSRV19QN8MN1MNQHNE46JS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketing-research\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"research","marketing","ckm","ckm:marketing research","planning","best practices","data","competitors","strategy","use","Market","driven","trends","insights","for","data-driven","2026-11-10 10:12:30",false,"---\nname: ckm:marketing-research\ndescription: Research market trends, competitors, audience insights, and marketing best practices. Use before marketing-planning for data-driven strategy.\nargument-hint: \"[topic or market]\"\nlicense: MIT\nmetadata:\n  author: claudekit\n  version: \"1.0.0\"\n---\n\n# Marketing Research\n\n## Research Methodology\n\nFocus on actionable marketing intelligence: market trends, competitor analysis, audience insights, and campaign benchmarks.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### Phase 1: Scope Definition\n\nFirst, clearly define the marketing research scope by:\n- Identifying target market segments and audience personas\n- Determining competitive landscape boundaries\n- Establishing KPIs and success metrics to benchmark\n- Setting boundaries for research depth (industry, geography, timeframe)\n\n### Phase 2: Systematic Information Gathering\n\nYou will employ a multi-source research strategy:\n\n1. **Search Strategy**:\n   - Check if `gemini` bash command is available, if so, execute `gemini -m gemini-2.5-flash -p \"...your search prompt...\"` bash command (timeout: 10 minutes) and save the output using `Report:` path from `## Naming` section (including all citations).\n   - If `gemini` bash command is not available, fallback to `WebSearch` tool.\n   - Run multiple `gemini` bash commands or `WebSearch` tools in parallel to search for relevant information.\n   - Craft precise search queries with relevant keywords\n   - Include terms like \"best practices\", \"2024\", \"latest\", \"security\", \"performance\"\n   - Search for official documentation, GitHub repositories, and authoritative blogs\n   - Prioritize results from recognized authorities (official docs, major tech companies, respected developers)\n   - **IMPORTANT:** You are allowed to perform at most **5 researches (max 5 tool calls)**, user might request less than this amount, **strictly respect it**, think carefully based on the task before performing each related research topic.\n\n2. **Deep Content Analysis**:\n   - When you found a potential Github repository URL, use `docs-seeker` skill to find read it.\n   - Focus on official documentation, API references, and technical specifications\n   - Analyze README files from popular GitHub repositories\n   - Review changelog and release notes for version-specific information\n\n3. **Video Content Research**:\n   - Prioritize content from official channels, recognized experts, and major conferences\n   - Focus on practical demonstrations and real-world implementations\n\n4. **Cross-Reference Validation**:\n   - Verify information across multiple independent sources\n   - Check publication dates to ensure currency\n   - Identify consensus vs. controversial approaches\n   - Note any conflicting information or debates in the community\n\n### Phase 3: Analysis and Synthesis\n\nYou will analyze gathered information by:\n- Identifying common patterns and best practices\n- Evaluating pros and cons of different approaches\n- Assessing maturity and stability of technologies\n- Recognizing security implications and performance considerations\n- Determining compatibility and integration requirements\n\n### Phase 4: Report Generation\n\n**Notes:**\n- Research reports are saved using `Report:` path from `## Naming` section.\n- If `## Naming` section is not available, ask main agent to provide the output path.\n\nYou will create a comprehensive markdown report with the following structure:\n\n```markdown\n# Research Report: [Topic]\n\n## Executive Summary\n[2-3 paragraph overview of key findings and recommendations]\n\n## Research Methodology\n- Sources consulted: [number]\n- Date range of materials: [earliest to most recent]\n- Key search terms used: [list]\n\n## Key Findings\n\n### 1. Technology Overview\n[Comprehensive description of the technology\u002Ftopic]\n\n### 2. Current State & Trends\n[Latest developments, version information, adoption trends]\n\n### 3. Best Practices\n[Detailed list of recommended practices with explanations]\n\n### 4. Security Considerations\n[Security implications, vulnerabilities, and mitigation strategies]\n\n### 5. Performance Insights\n[Performance characteristics, optimization techniques, benchmarks]\n\n## Comparative Analysis\n[If applicable, comparison of different solutions\u002Fapproaches]\n\n## Implementation Recommendations\n\n### Quick Start Guide\n[Step-by-step getting started instructions]\n\n### Code Examples\n[Relevant code snippets with explanations]\n\n### Common Pitfalls\n[Mistakes to avoid and their solutions]\n\n## Resources & References\n\n### Official Documentation\n- [Linked list of official docs]\n\n### Recommended Tutorials\n- [Curated list with descriptions]\n\n### Community Resources\n- [Forums, Discord servers, Stack Overflow tags]\n\n### Further Reading\n- [Advanced topics and deep dives]\n\n## Appendices\n\n### A. Glossary\n[Technical terms and definitions]\n\n### B. Version Compatibility Matrix\n[If applicable]\n\n### C. Raw Research Notes\n[Optional: detailed notes from research process]\n```\n\n## Quality Standards\n\nYou will ensure all research meets these criteria:\n- **Accuracy**: Information is verified across multiple sources\n- **Currency**: Prioritize information from the last 12 months unless historical context is needed\n- **Completeness**: Cover all aspects requested by the user\n- **Actionability**: Provide practical, implementable recommendations\n- **Clarity**: Use clear language, define technical terms, provide examples\n- **Attribution**: Always cite sources and provide links for verification\n\n## Special Considerations\n\n- When researching security topics, always check for recent CVEs and security advisories\n- For performance-related research, look for benchmarks and real-world case studies\n- When investigating new technologies, assess community adoption and support levels\n- For API documentation, verify endpoint availability and authentication requirements\n- Always note deprecation warnings and migration paths for older technologies\n\n## Output Requirements\n\nYour final report must:\n1. Be saved using the `Report:` path from `## Naming` section with a descriptive filename\n2. Include a timestamp of when the research was conducted\n3. Provide clear section navigation with a table of contents for longer reports\n4. Use code blocks with appropriate syntax highlighting\n5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)\n6. Conclude with specific, actionable next steps\n\n**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.\n**IMPORTANT:** In reports, list any unresolved questions at the end, if any.\n\n**Remember:** You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.","# Marketing Research\n\n## Research Methodology\n\nFocus on actionable marketing intelligence: market trends, competitor analysis, audience insights, and campaign benchmarks.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### Phase 1: Scope Definition\n\nFirst, clearly define the marketing research scope by:\n- Identifying target market segments and audience personas\n- Determining competitive landscape boundaries\n- Establishing KPIs and success metrics to benchmark\n- Setting boundaries for research depth (industry, geography, timeframe)\n\n### Phase 2: Systematic Information Gathering\n\nYou will employ a multi-source research strategy:\n\n1. **Search Strategy**:\n   - Check if `gemini` bash command is available, if so, execute `gemini -m gemini-2.5-flash -p \"...your search prompt...\"` bash command (timeout: 10 minutes) and save the output using `Report:` path from `## Naming` section (including all citations).\n   - If `gemini` bash command is not available, fallback to `WebSearch` tool.\n   - Run multiple `gemini` bash commands or `WebSearch` tools in parallel to search for relevant information.\n   - Craft precise search queries with relevant keywords\n   - Include terms like \"best practices\", \"2024\", \"latest\", \"security\", \"performance\"\n   - Search for official documentation, GitHub repositories, and authoritative blogs\n   - Prioritize results from recognized authorities (official docs, major tech companies, respected developers)\n   - **IMPORTANT:** You are allowed to perform at most **5 researches (max 5 tool calls)**, user might request less than this amount, **strictly respect it**, think carefully based on the task before performing each related research topic.\n\n2. **Deep Content Analysis**:\n   - When you found a potential Github repository URL, use `docs-seeker` skill to find read it.\n   - Focus on official documentation, API references, and technical specifications\n   - Analyze README files from popular GitHub repositories\n   - Review changelog and release notes for version-specific information\n\n3. **Video Content Research**:\n   - Prioritize content from official channels, recognized experts, and major conferences\n   - Focus on practical demonstrations and real-world implementations\n\n4. **Cross-Reference Validation**:\n   - Verify information across multiple independent sources\n   - Check publication dates to ensure currency\n   - Identify consensus vs. controversial approaches\n   - Note any conflicting information or debates in the community\n\n### Phase 3: Analysis and Synthesis\n\nYou will analyze gathered information by:\n- Identifying common patterns and best practices\n- Evaluating pros and cons of different approaches\n- Assessing maturity and stability of technologies\n- Recognizing security implications and performance considerations\n- Determining compatibility and integration requirements\n\n### Phase 4: Report Generation\n\n**Notes:**\n- Research reports are saved using `Report:` path from `## Naming` section.\n- If `## Naming` section is not available, ask main agent to provide the output path.\n\nYou will create a comprehensive markdown report with the following structure:\n\n```markdown\n# Research Report: [Topic]\n\n## Executive Summary\n[2-3 paragraph overview of key findings and recommendations]\n\n## Research Methodology\n- Sources consulted: [number]\n- Date range of materials: [earliest to most recent]\n- Key search terms used: [list]\n\n## Key Findings\n\n### 1. Technology Overview\n[Comprehensive description of the technology\u002Ftopic]\n\n### 2. Current State & Trends\n[Latest developments, version information, adoption trends]\n\n### 3. Best Practices\n[Detailed list of recommended practices with explanations]\n\n### 4. Security Considerations\n[Security implications, vulnerabilities, and mitigation strategies]\n\n### 5. Performance Insights\n[Performance characteristics, optimization techniques, benchmarks]\n\n## Comparative Analysis\n[If applicable, comparison of different solutions\u002Fapproaches]\n\n## Implementation Recommendations\n\n### Quick Start Guide\n[Step-by-step getting started instructions]\n\n### Code Examples\n[Relevant code snippets with explanations]\n\n### Common Pitfalls\n[Mistakes to avoid and their solutions]\n\n## Resources & References\n\n### Official Documentation\n- [Linked list of official docs]\n\n### Recommended Tutorials\n- [Curated list with descriptions]\n\n### Community Resources\n- [Forums, Discord servers, Stack Overflow tags]\n\n### Further Reading\n- [Advanced topics and deep dives]\n\n## Appendices\n\n### A. Glossary\n[Technical terms and definitions]\n\n### B. Version Compatibility Matrix\n[If applicable]\n\n### C. Raw Research Notes\n[Optional: detailed notes from research process]\n```\n\n## Quality Standards\n\nYou will ensure all research meets these criteria:\n- **Accuracy**: Information is verified across multiple sources\n- **Currency**: Prioritize information from the last 12 months unless historical context is needed\n- **Completeness**: Cover all aspects requested by the user\n- **Actionability**: Provide practical, implementable recommendations\n- **Clarity**: Use clear language, define technical terms, provide examples\n- **Attribution**: Always cite sources and provide links for verification\n\n## Special Considerations\n\n- When researching security topics, always check for recent CVEs and security advisories\n- For performance-related research, look for benchmarks and real-world case studies\n- When investigating new technologies, assess community adoption and support levels\n- For API documentation, verify endpoint availability and authentication requirements\n- Always note deprecation warnings and migration paths for older technologies\n\n## Output Requirements\n\nYour final report must:\n1. Be saved using the `Report:` path from `## Naming` section with a descriptive filename\n2. Include a timestamp of when the research was conducted\n3. Provide clear section navigation with a table of contents for longer reports\n4. Use code blocks with appropriate syntax highlighting\n5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)\n6. Conclude with specific, actionable next steps\n\n**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.\n**IMPORTANT:** In reports, list any unresolved questions at the end, if any.\n\n**Remember:** You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.",{"name":5,"license":14,"metadata":52,"description":7,"argument-hint":55},{"author":53,"version":54},"claudekit","1.0.0","[topic or market]","main","fa3098ef56c24a44b365d9f1727c4c86b98dfd20",".claude\u002Fskills\u002Fmarketing-research","https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored","https:\u002F\u002Fgithub.com\u002Fdevmotminh","2026-05-04 12:54:25",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add devmotminh\u002Fplayscored --skill \"ckm:marketing-research\"",{"tool":68,"command":69},"bunx","bunx skills add devmotminh\u002Fplayscored --skill \"ckm:marketing-research\"",{"tool":71,"command":72},"pnpm","pnpm dlx skills add devmotminh\u002Fplayscored --skill \"ckm:marketing-research\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketing-research\u002FSKILL.md",true,[],[77,109,136,160,186,209],{"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":89,"publishedAt":47},"01M6KTQ1G3XCP03TVWRW3ZC12B","ckm:youtube-thumbnail-design","Design YouTube thumbnails with 17 styles, niche-specific guides, and CTR optimization. Generate complete thumbnails with text using Gemini Nano Banana Pro (4K text rendering). Actions: design, create, generate thumbnail. Niches: tech, gaming, education, cooking, fitness, business. Styles: facecam, before-after, listicle, diagram, whiteboard, bold-text, mystery, dark-dramatic. Features: AI generation with text baked in, brand identity, reference face, arrows, Google Font support.","https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[83,86],{"categoryNo":84,"categoryName":85,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":87,"categoryName":88,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师",[90,91,92,33,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"design","youtube","thumbnail","ckm:youtube thumbnail design","ckm:youtube","diagram","create","generate","nano banana pro","actions","text","thumbnails","before-after","banana","ctr","niches","niche","guides","whiteboard",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":47},"01M6KTPMRWPGHSCT8AAPDHKSZ1","ck:web-frameworks","Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined\u002Ffilled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.","https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135],"web","web frameworks","frameworks","ck:web frameworks","ck","performance","components","react","libraries","projects","monorepo","router","up","caching","strategies","shared","app","remote","Server Components","implementing",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":144,"publishedAt":47},"01M6KTNK7R4AD3ZDHE4WXCSTQ1","ck: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\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fui-styling\u002FSKILL.md",[142,143],{"categoryNo":84,"categoryName":85,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":87,"categoryName":88,"taxonomyType":28,"taxonomyTypeDesc":29},[145,146,147,148,120,90,149,150,122,151,96,152,153,154,155,156,157,158,159,135],"ui styling","ui","styling","ck:ui styling","css","canvas","component","design systems","Tailwind","forms","across","layout","themes","utility","mode",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":47},"01M6KTND8TD6D7C273Q99VVQNQ","ck:threejs","Build 3D web apps with Three.js (WebGL\u002FWebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR\u002FXR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.","https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fthreejs\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",[170,162,120,171,96,172,99,173,174,175,176,177,178,179,180,181,182,183,184,185],"threejs","webgpu","shaders","api","Animation","3D","Audio","model","integrations","physics","apps","add","processing","post-processing","vr","effects",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":47},"01M6KTM3HB7WWZRW64HH35G6TN","ck:sequential-thinking","Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.","https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[193,194,195,120,196,35,197,198,199,200,40,201,202,203,204,205,206,45,207,208],"sequential thinking","thinking","ck:sequential thinking","tasks","verification","analysis","analyze","work","problem-solving","scope","problem","multi","with","course","adaptive","apply",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":47},"01M6KTJ0QCSSY0ZGEKP99W3HKQ","ck:payment-integration","Integrate payments with SePay (VietQR), Polar (SaaS subscriptions), Stripe (global payments). Use for checkout, webhooks, QR codes, subscriptions, currency conversion, multi-provider order management, commission systems.","https:\u002F\u002Fgithub.com\u002Fdevmotminh\u002Fplayscored\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fpayment-integration\u002FSKILL.md",[],[216,217,218,219,120,220,221,40,222,223,224,225,226,227,228,204,205,229,45,230],"integration","payment integration","payment","ck:payment integration","payments","saas","conversion","provider","subscriptions","task","currency","checkout","codes","qr","order management"]