[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71APTEDSNECKBAM0PJYM7QG":3,"skill-same:01M71APTEDSNECKBAM0PJYM7QG":67},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M71APTEDSNECKBAM0PJYM7QG","linkedin-posts",null,"When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions \"LinkedIn post\", \"LinkedIn article\", \"professional post\" or \"post to LinkedIn\". For LinkedIn ads, use linkedin-ads.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fplatforms\u002Flinkedin\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"linkedin","linkedin posts","posts","user","copy","article","linkedin post","linkedin-ads","ads","post","optimize","create","when","use","linkedin ads","for","professional","2026-11-10 10:12:30",false,"---\nname: linkedin-posts\ndescription: When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions \"LinkedIn post\", \"LinkedIn article\", \"professional post\" or \"post to LinkedIn\". For LinkedIn ads, use linkedin-ads.\nmetadata:\n  version: 1.2.0\n---\n\n# Platforms: LinkedIn\n\nGuides LinkedIn post copy creation and optimization. Use for generating publish-ready professional content. Suitable for copy agents and design agents (image specs).\n\n**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Output: Publish-Ready Copy\n\nThis skill enables agents to generate LinkedIn post copy optimized for engagement. Output includes character-counted text and structure for the \"See more\" threshold.\n\n## Post Types and Entry Points (organic)\n\n| Kind | What to know |\n|------|----------------|\n| **Start a post** | Short update; can include **link preview** if you paste a URL. Same feed format as other updates. |\n| **Photo** | Single or multiple images (carousel in feed). |\n| **Video** | Uploaded file (distinct from **LinkedIn Live**, which is live streaming and has separate gating). |\n| **Write article** | **Article** = long-form editor, **separate** from the short post box; long URL, better for depth and some **off-site** discoverability. |\n| **Document** | PDF \u002F PPT \u002F DOC (slides in feed). Official limits (check current help): on the order of **~100MB \u002F ~300 pages** per file—verify when publishing. |\n| **Poll** | Engagement driver; keep question and options scannable. |\n| **More** (menu) | Often includes **celebrations**, **hiring**-style share, **Find an expert**, etc. (varies by product\u002Fregion). |\n| **Reshare** | Reshare or **quote** another member’s post with your take—adds context; avoid empty reshares. |\n| **Newsletter** | **Series** subscription; not the same as a one-off post but compound reach over time. |\n| **Event** | Create\u002Fpromote events via a dedicated flow, not the same as a plain text post. |\n\n**Product detail**: [Get started with posting on LinkedIn](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa518996) · [Upload and share documents](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa518909)\n\n**Why it matters for copy**: Match CTA and length to the **form** (e.g. a document deck vs a 5-line hot take). Do not treat a **short post** and an **Article** as interchangeable.\n\n## How the Feed Ranks (what to write for)\n\n- The feed is **not** a pure reverse-chronological friend list. It blends **1st-degree connections, follows, company\u002Ftopic interest, and recommended “out of network”** content from the **Economic Graph**, plus ads. [How the Feed ranks content](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa9554004)\n- Relevance uses **context** of the post, **profile and network signals**, and **behavior** (read, react, comment, share, **dwell**). Demographics like age or gender are **not** used to rank feed visibility (per public help guidance).\n- Platform direction in recent public communications: more **LLM\u002Fsemantic** understanding, less **inauthentic engagement** and **engagement-bait** \u002F low-quality repetition; favor **real expertise** and **meaningful** discussion. [Background on feed engineering (blog)](https:\u002F\u002Fwww.linkedin.com\u002Fblog\u002Fengineering\u002Ffeed\u002Fengineering-the-next-generation-of-linkedins-feed)\n\n**Writing implications**: Strong **first line** and **on-topic depth**; comments that add substance; avoid templates that look automated or “pod” coordinated.\n\n## Off-Site SEO and GEO (brief)\n\n- **Short feed posts** are often **login-gated** for crawlers; do **not** assume every post is indexed on Google like a blog post.\n- **Public profile, Company Page, and Articles** (where public) are stronger for **name\u002Fcompany\u002Frole** style queries. Align **headline, about, and entity names** with your site and other public bios for **E-E-A-T**-style consistency.\n- **GEO** (AI\u002Fsearch answers): one clear, quotable line **who you help** + links to **evidence** (site, case study, talk) in profile or long-form, not only in DMs or groups.\n- For **link previews** on social: **open-graph**; for people\u002Forg **entities**: **entity-seo**; for **generative\u002FAI search** strategy: **generative-engine-optimization**.\n\n## Character Limits\n\n| Type | Limit | Notes |\n|------|-------|-------|\n| **Post** | 3,000 characters | Optimal: 1,300–1,600 |\n| **First line (critical)** | 210–235 chars | Visible before \"See more\"; 60–80% decide here |\n| **Short posts** | 100–200 chars | Polls, announcements, quotes |\n\n## Optimal Length by Content Type\n\n| Type | Characters | Use |\n|------|------------|-----|\n| **Short** | 100–200 | Polls, announcements, quotes |\n| **Medium** | 300–1,200 | Case studies, tips, BTS |\n| **Long** | 1,200–2,000 | Thought leadership, analysis |\n| **Sweet spot** | 1,300–1,600 | Highest engagement |\n| **Avoid** | >2,000 | ~35% engagement drop |\n\n## First Line (Hook)\n\n- **Place key message in first 140 chars**\n- **Strong openings**: Specific results, pain points, bold claims, surprising stats\n- **Avoid**: Vague teases, hashtag-first, generic greetings\n\n## Image Specs (for Design Agents)\n\n| Format | Dimensions | Use |\n|--------|------------|-----|\n| **Single image** | 1200×627 (1.91:1) | Feed; link previews |\n| **Square** | 1200×1200 | Single image |\n| **Carousel (organic)** | Up to 20 images | Multi-image post |\n| **File** | ≤10 MB; JPG\u002FPNG | Native uploads perform better |\n| **Vertical** | Preferred | 88% browse on mobile |\n\n## Best Practices\n\n- **Mobile-first**: 88% users on mobile\n- **Polls and document (PDF) posts**: Often strong for reach; pair with a clear takeaway\n- **Post frequency**: Weekly minimum is a common bar for company pages; individuals often **several times per week** if sustainable\n- **Alt text**: Add for accessibility\n- **B2B tone**: Professional and constructive; see **influencer-marketing** and **about-page-generator** for voice alignment with profile\u002Fbrand\n\n## Output Format\n\nWhen generating LinkedIn copy, provide:\n\n1. **First line** (≤210 chars; hook)\n2. **Full post** with character count\n3. **Hashtags** (a few, relevant; end of post)\n4. **Image specs** (if design agent needs dimensions)\n5. **Form note** if not a plain post (e.g. “pair with a 5-slide document” or “use Article for 1,200+ words”)\n\n## Related Skills\n\n- **linkedin-ads**: Paid promotion; same professional tone as organic\n- **open-graph**: Link share previews (Facebook, LinkedIn, etc.)\n- **entity-seo**: People\u002Forg **sameAs** and entity consistency\n- **generative-engine-optimization**: AI search \u002F answer visibility (cross-platform; not only LinkedIn)\n- **influencer-marketing**: LinkedIn influencers for B2B\n- **about-page-generator**: Professional brand alignment\n- **visual-content**: Cross-channel visual planning; LinkedIn image specs in context\n\n## Official references (index)\n\n- [Get started with posting](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa518996) · [Feed ranking (help)](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa9554004) · [Share photos](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa527229) · [Share videos](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa7174587)\n","# Platforms: LinkedIn\n\nGuides LinkedIn post copy creation and optimization. Use for generating publish-ready professional content. Suitable for copy agents and design agents (image specs).\n\n**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Output: Publish-Ready Copy\n\nThis skill enables agents to generate LinkedIn post copy optimized for engagement. Output includes character-counted text and structure for the \"See more\" threshold.\n\n## Post Types and Entry Points (organic)\n\n| Kind | What to know |\n|------|----------------|\n| **Start a post** | Short update; can include **link preview** if you paste a URL. Same feed format as other updates. |\n| **Photo** | Single or multiple images (carousel in feed). |\n| **Video** | Uploaded file (distinct from **LinkedIn Live**, which is live streaming and has separate gating). |\n| **Write article** | **Article** = long-form editor, **separate** from the short post box; long URL, better for depth and some **off-site** discoverability. |\n| **Document** | PDF \u002F PPT \u002F DOC (slides in feed). Official limits (check current help): on the order of **~100MB \u002F ~300 pages** per file—verify when publishing. |\n| **Poll** | Engagement driver; keep question and options scannable. |\n| **More** (menu) | Often includes **celebrations**, **hiring**-style share, **Find an expert**, etc. (varies by product\u002Fregion). |\n| **Reshare** | Reshare or **quote** another member’s post with your take—adds context; avoid empty reshares. |\n| **Newsletter** | **Series** subscription; not the same as a one-off post but compound reach over time. |\n| **Event** | Create\u002Fpromote events via a dedicated flow, not the same as a plain text post. |\n\n**Product detail**: [Get started with posting on LinkedIn](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa518996) · [Upload and share documents](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa518909)\n\n**Why it matters for copy**: Match CTA and length to the **form** (e.g. a document deck vs a 5-line hot take). Do not treat a **short post** and an **Article** as interchangeable.\n\n## How the Feed Ranks (what to write for)\n\n- The feed is **not** a pure reverse-chronological friend list. It blends **1st-degree connections, follows, company\u002Ftopic interest, and recommended “out of network”** content from the **Economic Graph**, plus ads. [How the Feed ranks content](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa9554004)\n- Relevance uses **context** of the post, **profile and network signals**, and **behavior** (read, react, comment, share, **dwell**). Demographics like age or gender are **not** used to rank feed visibility (per public help guidance).\n- Platform direction in recent public communications: more **LLM\u002Fsemantic** understanding, less **inauthentic engagement** and **engagement-bait** \u002F low-quality repetition; favor **real expertise** and **meaningful** discussion. [Background on feed engineering (blog)](https:\u002F\u002Fwww.linkedin.com\u002Fblog\u002Fengineering\u002Ffeed\u002Fengineering-the-next-generation-of-linkedins-feed)\n\n**Writing implications**: Strong **first line** and **on-topic depth**; comments that add substance; avoid templates that look automated or “pod” coordinated.\n\n## Off-Site SEO and GEO (brief)\n\n- **Short feed posts** are often **login-gated** for crawlers; do **not** assume every post is indexed on Google like a blog post.\n- **Public profile, Company Page, and Articles** (where public) are stronger for **name\u002Fcompany\u002Frole** style queries. Align **headline, about, and entity names** with your site and other public bios for **E-E-A-T**-style consistency.\n- **GEO** (AI\u002Fsearch answers): one clear, quotable line **who you help** + links to **evidence** (site, case study, talk) in profile or long-form, not only in DMs or groups.\n- For **link previews** on social: **open-graph**; for people\u002Forg **entities**: **entity-seo**; for **generative\u002FAI search** strategy: **generative-engine-optimization**.\n\n## Character Limits\n\n| Type | Limit | Notes |\n|------|-------|-------|\n| **Post** | 3,000 characters | Optimal: 1,300–1,600 |\n| **First line (critical)** | 210–235 chars | Visible before \"See more\"; 60–80% decide here |\n| **Short posts** | 100–200 chars | Polls, announcements, quotes |\n\n## Optimal Length by Content Type\n\n| Type | Characters | Use |\n|------|------------|-----|\n| **Short** | 100–200 | Polls, announcements, quotes |\n| **Medium** | 300–1,200 | Case studies, tips, BTS |\n| **Long** | 1,200–2,000 | Thought leadership, analysis |\n| **Sweet spot** | 1,300–1,600 | Highest engagement |\n| **Avoid** | >2,000 | ~35% engagement drop |\n\n## First Line (Hook)\n\n- **Place key message in first 140 chars**\n- **Strong openings**: Specific results, pain points, bold claims, surprising stats\n- **Avoid**: Vague teases, hashtag-first, generic greetings\n\n## Image Specs (for Design Agents)\n\n| Format | Dimensions | Use |\n|--------|------------|-----|\n| **Single image** | 1200×627 (1.91:1) | Feed; link previews |\n| **Square** | 1200×1200 | Single image |\n| **Carousel (organic)** | Up to 20 images | Multi-image post |\n| **File** | ≤10 MB; JPG\u002FPNG | Native uploads perform better |\n| **Vertical** | Preferred | 88% browse on mobile |\n\n## Best Practices\n\n- **Mobile-first**: 88% users on mobile\n- **Polls and document (PDF) posts**: Often strong for reach; pair with a clear takeaway\n- **Post frequency**: Weekly minimum is a common bar for company pages; individuals often **several times per week** if sustainable\n- **Alt text**: Add for accessibility\n- **B2B tone**: Professional and constructive; see **influencer-marketing** and **about-page-generator** for voice alignment with profile\u002Fbrand\n\n## Output Format\n\nWhen generating LinkedIn copy, provide:\n\n1. **First line** (≤210 chars; hook)\n2. **Full post** with character count\n3. **Hashtags** (a few, relevant; end of post)\n4. **Image specs** (if design agent needs dimensions)\n5. **Form note** if not a plain post (e.g. “pair with a 5-slide document” or “use Article for 1,200+ words”)\n\n## Related Skills\n\n- **linkedin-ads**: Paid promotion; same professional tone as organic\n- **open-graph**: Link share previews (Facebook, LinkedIn, etc.)\n- **entity-seo**: People\u002Forg **sameAs** and entity consistency\n- **generative-engine-optimization**: AI search \u002F answer visibility (cross-platform; not only LinkedIn)\n- **influencer-marketing**: LinkedIn influencers for B2B\n- **about-page-generator**: Professional brand alignment\n- **visual-content**: Cross-channel visual planning; LinkedIn image specs in context\n\n## Official references (index)\n\n- [Get started with posting](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa518996) · [Feed ranking (help)](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa9554004) · [Share photos](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa527229) · [Share videos](https:\u002F\u002Fwww.linkedin.com\u002Fhelp\u002Flinkedin\u002Fanswer\u002Fa7174587)\n",{"name":5,"metadata":41,"description":7},{"version":42},"1.2.0","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fplatforms\u002Flinkedin",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-01 12:36:50",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add ariadoss\u002Fsuperskills --skill linkedin-posts",{"tool":59,"command":60},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill linkedin-posts",{"tool":62,"command":63},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill linkedin-posts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fplatforms\u002Flinkedin\u002FSKILL.md",true,[],[68,94,118,137,165,181],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":36},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[70,22,80,81,82,83,84,85,86,31,87,88,89,90,91,32,92,93],"download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":36},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[101,102,82,103,104,105,106,107,108,31,109,110,111,112,113,34,114,115,116,117],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":36},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[120,125,126,127,32,128,129,130,131,132,133,104,134,31,135,136],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":146,"publishedAt":36},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发",[147,148,149,150,151,152,29,153,154,31,155,156,157,158,159,160,161,162,163,164],"web","perf","web perf","resources","MCP","layout","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":36},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[167,112,172,173,133,104,174,175,31,176,32,177,178,179,180],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":36},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[188,189,190,191,192,193,194,31,195,32,196],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]