[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2JDY9SQ8F52R13TZX5AW4":3,"skill-same:01M7B2JDY9SQ8F52R13TZX5AW4":50},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B2JDY9SQ8F52R13TZX5AW4","investor-materials",null,"Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Finvestor-materials\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: investor-materials\ndescription: Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.\nmetadata:\n  origin: ECC\n---\n\n# Investor Materials\n\nBuild investor-facing materials that are consistent, credible, and easy to defend.\n\n## When to Activate\n\n- creating or revising a pitch deck\n- writing an investor memo or one-pager\n- building a financial model, milestone plan, or use-of-funds table\n- answering accelerator or incubator application questions\n- aligning multiple fundraising docs around one source of truth\n\n## Golden Rule\n\nAll investor materials must agree with each other.\n\nCreate or confirm a single source of truth before writing:\n- traction metrics\n- pricing and revenue assumptions\n- raise size and instrument\n- use of funds\n- team bios and titles\n- milestones and timelines\n\nIf conflicting numbers appear, stop and resolve them before drafting.\n\n## Core Workflow\n\n1. inventory the canonical facts\n2. identify missing assumptions\n3. choose the asset type\n4. draft the asset with explicit logic\n5. cross-check every number against the source of truth\n\n## Asset Guidance\n\n### Pitch Deck\nRecommended flow:\n1. company + wedge\n2. problem\n3. solution\n4. product \u002F demo\n5. market\n6. business model\n7. traction\n8. team\n9. competition \u002F differentiation\n10. ask\n11. use of funds \u002F milestones\n12. appendix\n\nIf the user wants a web-native deck, pair this skill with `frontend-slides`.\n\n### One-Pager \u002F Memo\n- state what the company does in one clean sentence\n- show why now\n- include traction and proof points early\n- make the ask precise\n- keep claims easy to verify\n\n### Financial Model\nInclude:\n- explicit assumptions\n- bear \u002F base \u002F bull cases when useful\n- clean layer-by-layer revenue logic\n- milestone-linked spending\n- sensitivity analysis where the decision hinges on assumptions\n\n### Accelerator Applications\n- answer the exact question asked\n- prioritize traction, insight, and team advantage\n- avoid puffery\n- keep internal metrics consistent with the deck and model\n\n## Red Flags to Avoid\n\n- unverifiable claims\n- fuzzy market sizing without assumptions\n- inconsistent team roles or titles\n- revenue math that does not sum cleanly\n- inflated certainty where assumptions are fragile\n\n## Quality Gate\n\nBefore delivering:\n- every number matches the current source of truth\n- use of funds and revenue layers sum correctly\n- assumptions are visible, not buried\n- the story is clear without hype language\n- the final asset is defensible in a partner meeting\n","# Investor Materials\n\nBuild investor-facing materials that are consistent, credible, and easy to defend.\n\n## When to Activate\n\n- creating or revising a pitch deck\n- writing an investor memo or one-pager\n- building a financial model, milestone plan, or use-of-funds table\n- answering accelerator or incubator application questions\n- aligning multiple fundraising docs around one source of truth\n\n## Golden Rule\n\nAll investor materials must agree with each other.\n\nCreate or confirm a single source of truth before writing:\n- traction metrics\n- pricing and revenue assumptions\n- raise size and instrument\n- use of funds\n- team bios and titles\n- milestones and timelines\n\nIf conflicting numbers appear, stop and resolve them before drafting.\n\n## Core Workflow\n\n1. inventory the canonical facts\n2. identify missing assumptions\n3. choose the asset type\n4. draft the asset with explicit logic\n5. cross-check every number against the source of truth\n\n## Asset Guidance\n\n### Pitch Deck\nRecommended flow:\n1. company + wedge\n2. problem\n3. solution\n4. product \u002F demo\n5. market\n6. business model\n7. traction\n8. team\n9. competition \u002F differentiation\n10. ask\n11. use of funds \u002F milestones\n12. appendix\n\nIf the user wants a web-native deck, pair this skill with `frontend-slides`.\n\n### One-Pager \u002F Memo\n- state what the company does in one clean sentence\n- show why now\n- include traction and proof points early\n- make the ask precise\n- keep claims easy to verify\n\n### Financial Model\nInclude:\n- explicit assumptions\n- bear \u002F base \u002F bull cases when useful\n- clean layer-by-layer revenue logic\n- milestone-linked spending\n- sensitivity analysis where the decision hinges on assumptions\n\n### Accelerator Applications\n- answer the exact question asked\n- prioritize traction, insight, and team advantage\n- avoid puffery\n- keep internal metrics consistent with the deck and model\n\n## Red Flags to Avoid\n\n- unverifiable claims\n- fuzzy market sizing without assumptions\n- inconsistent team roles or titles\n- revenue math that does not sum cleanly\n- inflated certainty where assumptions are fragile\n\n## Quality Gate\n\nBefore delivering:\n- every number matches the current source of truth\n- use of funds and revenue layers sum correctly\n- assumptions are visible, not buried\n- the story is clear without hype language\n- the final asset is defensible in a partner meeting\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Finvestor-materials",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill investor-materials",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill investor-materials",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill investor-materials","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Finvestor-materials\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]