[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P6GTTNZFHVMQRT98XSFP16":3,"skill-same:01M6P6GTTNZFHVMQRT98XSFP16":74},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":21,"commitSha":55,"skillDirectory":56,"forksCount":13,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6P6GTTNZFHVMQRT98XSFP16","idea-autopsy",null,"Autopsy a business idea before you build it: kill-list check, five hard filters, a free-AI one-prompt test, live ad-market verification, and a verdict with a named kill-pattern.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fidea-autopsy\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"idea","idea autopsy","autopsy","main","verification","before you build","you","free","critical","live","ideas","pattern","license","gemini","community","kill","filters","market-research","list","product","2026-11-10 10:12:30",false,"---\nname: idea-autopsy\ndescription: \"Autopsy a business idea before you build it: kill-list check, five hard filters, a free-AI one-prompt test, live ad-market verification, and a verdict with a named kill-pattern.\"\ncategory: product\nrisk: critical\nsource: community\nsource_repo: hafiz-actyte\u002Fidea-autopsy\nsource_type: community\ndate_added: \"2026-07-10\"\nauthor: hafiz-actyte\ntags: [business-ideas, idea-validation, market-research, startup, founders]\ntools: [claude, cursor, gemini]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fhafiz-actyte\u002Fidea-autopsy\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Idea Autopsy\n\n## Overview\n\nTurns the agent into a ruthless business-idea pathologist: instead of encouraging\nthe user, it hunts for the one sentence that kills an idea — before any money or\nweeks are spent building it. Built from a real founder kill-list of 42 dead ideas\n(including a 9\u002F10-scored idea and one that turned out to be federally illegal to\ncharge for). Every autopsy ends in a hard verdict: DEAD with a named kill-pattern,\nor SURVIVED with the one cheapest test that could still kill it.\n\n## When to Use This Skill\n\n- Use when the user proposes a new business, product, or side-project idea\n- Use when the user asks \"should I build X?\" or \"validate this idea\"\n- Use when the user says \"autopsy my idea\"\n- Use before any market-research or build-planning task for a new venture\n\n## How It Works\n\n### Step 1: Kill-list check\n\nIf the project contains a `REJECTION.md` (the user's personal kill-list), read it\nfirst. A NICHE match (same niche as a killed row) = verdict DEAD, cite the row,\nstop. A KILL-PATTERN match alone (new niche, previously-seen pattern) is a strong\nprior, NOT a verdict: name the matching pattern, then run the specific check for\nthat pattern (the relevant filter or test below) to confirm it actually applies\nbefore declaring death. If no kill-list exists, ask the user for permission to create one\nwith exactly this schema — this autopsy writes its first row:\n\n```markdown\n# REJECTION.md — my kill-list\n\n## Killed ideas\n\n| # | Idea\u002FNiche | Killed (date) | Hard reason (one line) | Pattern |\n|---|-----------|---------------|------------------------|---------|\n\n## Survivors under test\n\n| Idea | Passed filters (date) | Pending test | Deadline |\n|------|----------------------|--------------|----------|\n```\n\n### Step 2: The five filters\n\nDemand evidence, not optimism. One hard NO = dead.\n\n1. **Real pain?** 2am-problem, or a nice-to-have \"vitamin\"?\n2. **Buyer has money?** Right now — not after the product helps them.\n3. **Proven demand?** Can the user name a single live competitor ad?\n4. **Legal to charge for?** Regulated, licensed, or illegal in the target market? Name the law if suspicion exists.\n5. **A moat?** What stops the 50th copycat next month?\n\n### Step 3: The free-AI test\n\nTry to produce the idea's core deliverable with one prompt to a frontier model.\nIf one prompt produces the whole deliverable free, the verdict is DEAD with\nkill-pattern `free-AI`: the user doesn't have a product, they have a prompt.\n\n### Step 4: Live-market verification (own eyes)\n\nDesk research lies. Walk the user through the Meta Ad Library (or equivalent) with\nan explicit checklist: number of ACTIVE advertisers, age of the oldest running ad\n(90+ days = someone is paying because it works), and the three traps — zero ads\n(`wrong-channel`), a few giants (`incumbent-owned`), or hundreds of ads\n(`crowded` commodity knife-fight: demand ≠ room for you).\n\n### Step 5: Verdict\n\n```\nVERDICT: DEAD | SURVIVED\nKILL-PATTERN: \u003Cname>            (if dead)\nTHE ONE SENTENCE: \u003Cthe single finding that decided it>\nEVIDENCE: \u003C2-4 hard facts with sources\u002Fnumbers>\nNEXT: \u003Cif survived: the ONE cheapest test that could still kill it>\n```\n\nThen record the result — gated on consent: if `REJECTION.md` exists, or the user\napproved creating it in Step 1, append a one-line row (dead) or note the survivor\nwith the date and pending test. If the user declined the kill-list, do NOT create\nor write the file — print the proposed row as text so they can save it wherever\nthey prefer. The kill-list is the compounding asset — every autopsy makes the\nnext one faster, but only with the user's consent.\n\n## Examples\n\n### Example 1: Idea that dies on the free-AI test\n\n```\nUser: Should I build a chargeback-response kit for Shopify sellers? Ready-to-send\n      evidence packets, $29 one-time.\nAgent: Running the autopsy... Step 3 kills it: one prompt to a frontier model\n      produces a complete, usable evidence packet for free.\n      VERDICT: DEAD. KILL-PATTERN: free-AI.\n      THE ONE SENTENCE: If AI ships your whole deliverable in one prompt, you\n      don't have a product — you have a prompt.\n```\n\n### Example 2: Proven demand that still dies\n\n```\nUser: An app that identifies plants from a photo — there are over a thousand\n      active ads for these, demand is proven!\nAgent: Step 4 confirms ~1,100 active advertisers — and that's the trap. The AI is\n      free, the datasets are public, everyone could build it, so everyone did.\n      VERDICT: DEAD. KILL-PATTERN: no-moat.\n      THE ONE SENTENCE: Demand tells you a market exists; it doesn't tell you\n      there's room for you.\n```\n\n## Best Practices\n\n- ✅ Demand a number, a law, a live ad, or a quote for every claim\n- ✅ Treat a fast honest kill as a WIN — it saves weeks and dollars\n- ✅ Make the user verify ad-library findings with their own eyes\n- ❌ Don't soften verdicts to be encouraging — \"it depends\" is a failed autopsy\n- ❌ Don't let buildability excitement skip the buyer questions; building was never the problem\n\n## Limitations\n\n- This skill does not replace legal advice, financial advice, or professional market research.\n- Kill-patterns are priors, not verdicts — a new niche matching an old pattern still deserves a fresh check that the pattern applies.\n- Ad-library checks reflect one acquisition channel; some categories legitimately sell through search or app stores.\n- Stop and ask for clarification if the idea's target market, buyer, or deliverable is unclear.\n\n## Security & Safety Notes\n\n- This skill performs no shell commands, network calls, or credential handling.\n- It modifies project state in exactly one place: creating or appending rows to the project's own `REJECTION.md` (hence `risk: critical`). It never edits other files; ask permission before creating the file on first run.\n- Web checks (ad libraries) are performed by the USER in their own browser; the skill only provides the checklist.\n","# Idea Autopsy\n\n## Overview\n\nTurns the agent into a ruthless business-idea pathologist: instead of encouraging\nthe user, it hunts for the one sentence that kills an idea — before any money or\nweeks are spent building it. Built from a real founder kill-list of 42 dead ideas\n(including a 9\u002F10-scored idea and one that turned out to be federally illegal to\ncharge for). Every autopsy ends in a hard verdict: DEAD with a named kill-pattern,\nor SURVIVED with the one cheapest test that could still kill it.\n\n## When to Use This Skill\n\n- Use when the user proposes a new business, product, or side-project idea\n- Use when the user asks \"should I build X?\" or \"validate this idea\"\n- Use when the user says \"autopsy my idea\"\n- Use before any market-research or build-planning task for a new venture\n\n## How It Works\n\n### Step 1: Kill-list check\n\nIf the project contains a `REJECTION.md` (the user's personal kill-list), read it\nfirst. A NICHE match (same niche as a killed row) = verdict DEAD, cite the row,\nstop. A KILL-PATTERN match alone (new niche, previously-seen pattern) is a strong\nprior, NOT a verdict: name the matching pattern, then run the specific check for\nthat pattern (the relevant filter or test below) to confirm it actually applies\nbefore declaring death. If no kill-list exists, ask the user for permission to create one\nwith exactly this schema — this autopsy writes its first row:\n\n```markdown\n# REJECTION.md — my kill-list\n\n## Killed ideas\n\n| # | Idea\u002FNiche | Killed (date) | Hard reason (one line) | Pattern |\n|---|-----------|---------------|------------------------|---------|\n\n## Survivors under test\n\n| Idea | Passed filters (date) | Pending test | Deadline |\n|------|----------------------|--------------|----------|\n```\n\n### Step 2: The five filters\n\nDemand evidence, not optimism. One hard NO = dead.\n\n1. **Real pain?** 2am-problem, or a nice-to-have \"vitamin\"?\n2. **Buyer has money?** Right now — not after the product helps them.\n3. **Proven demand?** Can the user name a single live competitor ad?\n4. **Legal to charge for?** Regulated, licensed, or illegal in the target market? Name the law if suspicion exists.\n5. **A moat?** What stops the 50th copycat next month?\n\n### Step 3: The free-AI test\n\nTry to produce the idea's core deliverable with one prompt to a frontier model.\nIf one prompt produces the whole deliverable free, the verdict is DEAD with\nkill-pattern `free-AI`: the user doesn't have a product, they have a prompt.\n\n### Step 4: Live-market verification (own eyes)\n\nDesk research lies. Walk the user through the Meta Ad Library (or equivalent) with\nan explicit checklist: number of ACTIVE advertisers, age of the oldest running ad\n(90+ days = someone is paying because it works), and the three traps — zero ads\n(`wrong-channel`), a few giants (`incumbent-owned`), or hundreds of ads\n(`crowded` commodity knife-fight: demand ≠ room for you).\n\n### Step 5: Verdict\n\n```\nVERDICT: DEAD | SURVIVED\nKILL-PATTERN: \u003Cname>            (if dead)\nTHE ONE SENTENCE: \u003Cthe single finding that decided it>\nEVIDENCE: \u003C2-4 hard facts with sources\u002Fnumbers>\nNEXT: \u003Cif survived: the ONE cheapest test that could still kill it>\n```\n\nThen record the result — gated on consent: if `REJECTION.md` exists, or the user\napproved creating it in Step 1, append a one-line row (dead) or note the survivor\nwith the date and pending test. If the user declined the kill-list, do NOT create\nor write the file — print the proposed row as text so they can save it wherever\nthey prefer. The kill-list is the compounding asset — every autopsy makes the\nnext one faster, but only with the user's consent.\n\n## Examples\n\n### Example 1: Idea that dies on the free-AI test\n\n```\nUser: Should I build a chargeback-response kit for Shopify sellers? Ready-to-send\n      evidence packets, $29 one-time.\nAgent: Running the autopsy... Step 3 kills it: one prompt to a frontier model\n      produces a complete, usable evidence packet for free.\n      VERDICT: DEAD. KILL-PATTERN: free-AI.\n      THE ONE SENTENCE: If AI ships your whole deliverable in one prompt, you\n      don't have a product — you have a prompt.\n```\n\n### Example 2: Proven demand that still dies\n\n```\nUser: An app that identifies plants from a photo — there are over a thousand\n      active ads for these, demand is proven!\nAgent: Step 4 confirms ~1,100 active advertisers — and that's the trap. The AI is\n      free, the datasets are public, everyone could build it, so everyone did.\n      VERDICT: DEAD. KILL-PATTERN: no-moat.\n      THE ONE SENTENCE: Demand tells you a market exists; it doesn't tell you\n      there's room for you.\n```\n\n## Best Practices\n\n- ✅ Demand a number, a law, a live ad, or a quote for every claim\n- ✅ Treat a fast honest kill as a WIN — it saves weeks and dollars\n- ✅ Make the user verify ad-library findings with their own eyes\n- ❌ Don't soften verdicts to be encouraging — \"it depends\" is a failed autopsy\n- ❌ Don't let buildability excitement skip the buyer questions; building was never the problem\n\n## Limitations\n\n- This skill does not replace legal advice, financial advice, or professional market research.\n- Kill-patterns are priors, not verdicts — a new niche matching an old pattern still deserves a fresh check that the pattern applies.\n- Ad-library checks reflect one acquisition channel; some categories legitimately sell through search or app stores.\n- Stop and ask for clarification if the idea's target market, buyer, or deliverable is unclear.\n\n## Security & Safety Notes\n\n- This skill performs no shell commands, network calls, or credential handling.\n- It modifies project state in exactly one place: creating or appending rows to the project's own `REJECTION.md` (hence `risk: critical`). It never edits other files; ask permission before creating the file on first run.\n- Web checks (ad libraries) are performed by the USER in their own browser; the skill only provides the checklist.\n",{"name":5,"risk":26,"tags":43,"tools":48,"author":51,"source":32,"license":14,"category":37,"date_added":52,"description":7,"source_repo":53,"source_type":32,"license_source":54},[44,45,35,46,47],"business-ideas","idea-validation","startup","founders",[49,50,31],"claude","cursor","hafiz-actyte","2026-07-10","hafiz-actyte\u002Fidea-autopsy","https:\u002F\u002Fgithub.com\u002Fhafiz-actyte\u002Fidea-autopsy\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fidea-autopsy","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill idea-autopsy",{"tool":66,"command":67},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill idea-autopsy",{"tool":69,"command":70},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill idea-autopsy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fidea-autopsy\u002FSKILL.md",true,[],[75,102,126,150,176,200],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":38},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[87,88,89,90,91,22,77,92,93,94,95,96,32,21,97,26,98,99,100,101],"ZeRO","trust","zero trust","architecture","assessment","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":38},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[109,110,111,112,113,114,115,116,117,118,119,120,121,96,122,32,123,124,26,125],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":38},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[133,134,135,136,137,138,139,30,140,141,142,143,144,32,21,145,146,147,148,149],"transcript","youtube transcript","youtube","safe","github","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":167,"publishedAt":38},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[156,159,162],{"categoryNo":157,"categoryName":158,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":160,"categoryName":161,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":163,"categoryName":164,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[133,134,135,168,136,31,137,138,30,169,170,171,172,142,173,32,21,25,174,175],"youtube transcript skills","search","api","Video","browse","api-integration","card","channels",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":186,"publishedAt":38},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[182,185],{"categoryNo":183,"categoryName":184,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":160,"categoryName":161,"taxonomyType":84,"taxonomyTypeDesc":85},[135,187,188,113,136,189,190,191,192,30,171,193,194,195,196,21,197,145,198,199],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":207,"publishedAt":38},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[206],{"categoryNo":157,"categoryName":158,"taxonomyType":84,"taxonomyTypeDesc":85},[208,135,209,210,136,31,169,211,212,170,171,172,142,213,173,32,21,25,214,148],"youtube full","full","google","server","dlp","credits","automatic"]