[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5FY74RTG6GR193GYRF4SY":3,"skill-same:01M7F5FY74RTG6GR193GYRF4SY":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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F5FY74RTG6GR193GYRF4SY","generalized-methodology-extractor",null,"Extract an actionable, source-linked method from one or more captured YouTube transcripts and optionally consolidate the methods into a reusable playbook. Use only when the user explicitly asks for a methodology, process, framework, playbook, operating system, or cross-video synthesis; do not activate for transcript-only requests.","cwik-tech\u002Foctopus","cwik-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54542292?v=4","01M7F42E123GEHVK6RWC5MSWJ9","Tomasz Cwik","01M7F42E1PD4P54MTG8PG32VCV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: generalized-methodology-extractor\ndescription: Extract an actionable, source-linked method from one or more captured YouTube transcripts and optionally consolidate the methods into a reusable playbook. Use only when the user explicitly asks for a methodology, process, framework, playbook, operating system, or cross-video synthesis; do not activate for transcript-only requests.\n---\n\n# Generalized Methodology Extractor\n\nTransform conversational transcripts into faithful operating guidance. Keep extraction and synthesis separate so the result remains traceable to each source.\n\n## Templates\n\nAuthor every artifact by copying and filling the matching template. Do not improvise structure.\n\n- `templates\u002Fextraction-report.md` — the run's final report. Always produced. A short human-readable document with the video title, URL, publish date, and a plain-language summary of what the video is about. The report is for a human reader, not a developer debugging the run — it must not contain status tables, artifact path inventories, capture-method names, or user-action sections. That information lives in the run's `output\u002Fyoutube-manifest.json` and the UI delivery panel.\n- `templates\u002Fsource-method.md` — one per video, persisted via `write_methodology` as `output\u002Fmethods\u002F\u003CvideoId>.md`.\n- `templates\u002Fconsolidated-playbook.md` — one per multi-video run, persisted via `write_consolidation` under `output\u002Fgeneralized-methodology\u002F`.\n\nThe reference contracts (`references\u002Fextraction-contract.md` and `references\u002Fconsolidation-contract.md`) are the maintainer-facing spec the templates implement. When templates and contracts disagree, the contract is authoritative.\n\n## Workflow\n\n1. Confirm that the user requested methodology extraction. For transcript-only requests, stop after transcript capture and still write `extraction-report.md` from the template.\n2. Capture transcripts with `youtube_extract`. Never infer a method from titles, descriptions, or partial browser text when a transcript is available.\n3. For each successful video, read every transcript chunk in order with `read_transcript`.\n4. Extract one source method per video by filling `templates\u002Fsource-method.md`. Preserve the speaker's terminology, prerequisites, sequence, decisions, examples, failure conditions, and caveats. Mark interpretation explicitly.\n5. Save each method with `write_methodology` using the source video ID.\n6. For multiple videos, consolidate only after all available source methods are saved. Fill `templates\u002Fconsolidated-playbook.md`, merging equivalent concepts, retaining meaningful disagreements, and distinguishing source-backed rules from synthesis.\n7. Save the final playbook with `write_consolidation`.\n8. Always finish by composing `extraction-report.md` from `templates\u002Fextraction-report.md`.\n\n## Source Method Contract\n\nEach source method must be independently usable and auditable. The template's section order is mandatory. Include source metadata, intended outcome, prerequisites, ordered steps, decision points, named tools, examples, metrics, failure modes, caveats, ambiguities, and timestamped provenance.\n\nUse these evidence labels where interpretation matters:\n\n- `Source states` for a claim directly supported by the transcript.\n- `Source demonstrates` for an example shown or narrated.\n- `Interpretation` for a reasonable implication not explicitly stated.\n- `Unresolved` when the transcript does not support a reliable conclusion.\n\nNever fill a gap with general knowledge without marking it as interpretation. See `references\u002Fextraction-contract.md`.\n\n## Consolidation Contract\n\nConsolidation combines completed per-video methods, not raw transcript fragments. De-duplicate equivalent steps while preserving differing prerequisites, sequencing, and scope.\n\nEvery generalized rule must map to one or more video IDs and timestamps in the provenance mapping table. Represent material disagreement directly as conditional branches. The result must separate source consensus, source-specific variants, agent synthesis, and unresolved questions. See `references\u002Fconsolidation-contract.md`.\n\n## Quality Gate\n\nBefore saving, verify that every transcript chunk was read, every key step is traceable via the provenance mapping, ordering is preserved where it matters, caveats survived compression, and no missing transcript was treated as evidence.\n","# Generalized Methodology Extractor\n\nTransform conversational transcripts into faithful operating guidance. Keep extraction and synthesis separate so the result remains traceable to each source.\n\n## Templates\n\nAuthor every artifact by copying and filling the matching template. Do not improvise structure.\n\n- `templates\u002Fextraction-report.md` — the run's final report. Always produced. A short human-readable document with the video title, URL, publish date, and a plain-language summary of what the video is about. The report is for a human reader, not a developer debugging the run — it must not contain status tables, artifact path inventories, capture-method names, or user-action sections. That information lives in the run's `output\u002Fyoutube-manifest.json` and the UI delivery panel.\n- `templates\u002Fsource-method.md` — one per video, persisted via `write_methodology` as `output\u002Fmethods\u002F\u003CvideoId>.md`.\n- `templates\u002Fconsolidated-playbook.md` — one per multi-video run, persisted via `write_consolidation` under `output\u002Fgeneralized-methodology\u002F`.\n\nThe reference contracts (`references\u002Fextraction-contract.md` and `references\u002Fconsolidation-contract.md`) are the maintainer-facing spec the templates implement. When templates and contracts disagree, the contract is authoritative.\n\n## Workflow\n\n1. Confirm that the user requested methodology extraction. For transcript-only requests, stop after transcript capture and still write `extraction-report.md` from the template.\n2. Capture transcripts with `youtube_extract`. Never infer a method from titles, descriptions, or partial browser text when a transcript is available.\n3. For each successful video, read every transcript chunk in order with `read_transcript`.\n4. Extract one source method per video by filling `templates\u002Fsource-method.md`. Preserve the speaker's terminology, prerequisites, sequence, decisions, examples, failure conditions, and caveats. Mark interpretation explicitly.\n5. Save each method with `write_methodology` using the source video ID.\n6. For multiple videos, consolidate only after all available source methods are saved. Fill `templates\u002Fconsolidated-playbook.md`, merging equivalent concepts, retaining meaningful disagreements, and distinguishing source-backed rules from synthesis.\n7. Save the final playbook with `write_consolidation`.\n8. Always finish by composing `extraction-report.md` from `templates\u002Fextraction-report.md`.\n\n## Source Method Contract\n\nEach source method must be independently usable and auditable. The template's section order is mandatory. Include source metadata, intended outcome, prerequisites, ordered steps, decision points, named tools, examples, metrics, failure modes, caveats, ambiguities, and timestamped provenance.\n\nUse these evidence labels where interpretation matters:\n\n- `Source states` for a claim directly supported by the transcript.\n- `Source demonstrates` for an example shown or narrated.\n- `Interpretation` for a reasonable implication not explicitly stated.\n- `Unresolved` when the transcript does not support a reliable conclusion.\n\nNever fill a gap with general knowledge without marking it as interpretation. See `references\u002Fextraction-contract.md`.\n\n## Consolidation Contract\n\nConsolidation combines completed per-video methods, not raw transcript fragments. De-duplicate equivalent steps while preserving differing prerequisites, sequencing, and scope.\n\nEvery generalized rule must map to one or more video IDs and timestamps in the provenance mapping table. Represent material disagreement directly as conditional branches. The result must separate source consensus, source-specific variants, agent synthesis, and unresolved questions. See `references\u002Fconsolidation-contract.md`.\n\n## Quality Gate\n\nBefore saving, verify that every transcript chunk was read, every key step is traceable via the provenance mapping, ordering is preserved where it matters, caveats survived compression, and no missing transcript was treated as evidence.\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus","www.cuteoctopus.site","https:\u002F\u002Fgithub.com\u002Fcwik-tech","2026-10-27 06:12:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cwik-tech\u002Foctopus --skill generalized-methodology-extractor",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill generalized-methodology-extractor",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill generalized-methodology-extractor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fconsolidation-contract.md","REFERENCE","参考文档",528,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor\u002Freferences\u002Fconsolidation-contract.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fextraction-contract.md",693,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor\u002Freferences\u002Fextraction-contract.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"templates\u002Fconsolidated-playbook.md",3431,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor\u002Ftemplates\u002Fconsolidated-playbook.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"templates\u002Fextraction-report.md",3398,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor\u002Ftemplates\u002Fextraction-report.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"templates\u002Fsource-method.md",2787,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fyoutube-extractor\u002Fskills\u002Fgeneralized-methodology-extractor\u002Ftemplates\u002Fsource-method.md",[68,75,82,89,96,103],{"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":74,"publishedAt":19},"01M7F5MQVQ3CHGM77Q51M4B1AC","twenty-year-land-plan","Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Ftwenty-year-land-plan\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7F5MGQ8JSV27SFDQVVGFQE3","thematic-gut-check","Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fthematic-gut-check\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F5M8V64Y0ZD8PTPWEJQXJ9","supply-pipeline-gut-check","Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fsupply-pipeline-gut-check\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7F5M3J2Q146BJC13TD3YCXF","ruin-scenario-mapping","Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fruin-scenario-mapping\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7F5KZDS0DYD172P6HS0WXEM","revenue-cost-architecture","Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Frevenue-cost-architecture\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7F5KP1CNQMYAVCDTV4EEW3J","replacement-cost-stress-test","Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Freplacement-cost-stress-test\u002FSKILL.md",[],[]]