[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MHA7SN73WRF47VHD77KTX":3,"skill-same:01M75MHA7SN73WRF47VHD77KTX":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75MHA7SN73WRF47VHD77KTX","pitching-tech-cfps",null,"Draft a technology conference CFP package: title, abstract, outline, speaker bio, and organizer notes. Use for talk proposals and conference submissions.","jkomyno\u002F.dotfiles","jkomyno","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12381818?v=4","01M75MA8EK2FJFP0274GEB1RNB","Alberto Schiabel","01M75MA8FKQN5GTW089WN3838D",5,"MIT","https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Fpitching-tech-cfps\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: pitching-tech-cfps\ndescription: \"Draft a technology conference CFP package: title, abstract, outline, speaker bio, and organizer notes. Use for talk proposals and conference submissions.\"\n---\n\n# Pitching Tech Conference CFPs\n\nGenerate compelling Call for Papers (CFP) proposals that stand out from hundreds of submissions and get your talk accepted at tech conferences.\n\n## Quick Start\n\nAsk the user for:\n1. **Conference name and URL** (to tailor the proposal)\n2. **Talk idea** (topic, angle, or problem being solved)\n3. **Speaker background** (relevant experience, unique perspective)\n\nThen generate a complete CFP submission package.\n\n## Understanding CFP Platforms\n\nMost tech conferences use one of these platforms:\n\n**Sessionize** fields:\n- Session title (required)\n- Session description (required)\n- Session format (lightning, talk, workshop)\n- Track\u002Ftopic category\n- Audience level (beginner, intermediate, advanced)\n- Speaker name, email, tagline, biography\n- Custom fields per conference\n\n**PaperCall** fields:\n- Talk title\n- Elevator pitch (short summary)\n- Talk description \u002F abstract\n- Notes to organizers (private)\n- Session format\n- Audience level\n- Tags \u002F topics\n\n**Custom forms** (Google Forms, Airtable, etc.) vary but typically ask for a subset of the above.\n\n## The CFP Submission Package\n\nGenerate all of the following components for each proposal:\n\n### 1. Talk Title\n\nCraft a title that is:\n- **Specific and descriptive** over clever or punny\n- **Problem-oriented** — frames what the audience gains\n- **Concise** — under 80 characters\n- **Memorable** — stands out scanning a conference schedule\n\nGood examples:\n- \"K8s at Lightspeed: Managing 1000 Clusters in 60 Seconds\"\n- \"Type-Safe Database Queries Without an ORM\"\n- \"From 12s to 200ms: A Real-World Performance Debugging Story\"\n\nBad examples:\n- \"Scaling Kubernetes\" (too vague)\n- \"My Journey with React\" (self-focused, not audience-focused)\n- \"Things I Learned\" (says nothing)\n\n### 2. Abstract \u002F Description (150-400 words)\n\nThis is the public-facing blurb attendees see. It must accomplish three things:\n\n**a) Hook with a real problem (1-2 sentences)**\nOpen with a concrete pain point the audience recognizes. Use a scenario, a statistic, or a provocative question.\n\n**b) Promise specific outcomes (2-3 sentences)**\nState exactly what attendees will learn or be able to do after the talk. Use active verbs: \"build,\" \"implement,\" \"debug,\" \"evaluate\" — not \"learn about\" or \"gain insights.\"\n\n**c) Establish credibility through specifics (1-2 sentences)**\nMention concrete technologies, scale numbers, or real results. Show domain depth without being a sales pitch.\n\n**d) Leave them wanting more (1 sentence)**\nEnd with an inviting forward look or a hint at surprising findings.\n\nStructure template:\n```\n[Problem hook — why should anyone care?]\n\n[What you'll cover — be specific about topics and techniques]\n\n[What attendees walk away with — concrete, actionable outcomes]\n\n[Credibility signal — why you're the right person \u002F why now]\n```\n\n### 3. Elevator Pitch (1-2 sentences, ~300 characters)\n\nA punchy summary for quick scanning. Formula:\n```\n[Audience] will learn [specific skill\u002Finsight] by [approach\u002Fangle], enabling them to [concrete outcome].\n```\n\n### 4. Talk Outline (private, for organizers)\n\nProvide a structured breakdown showing you've thought through the talk:\n\n```\n- Introduction & problem framing (3 min)\n- [Section 1: Context\u002FBackground] (5 min)\n- [Section 2: Core technique\u002Fsolution] (8 min)\n- [Section 3: Demo \u002F case study] (7 min)\n- Key takeaways & resources (2 min)\n```\n\nAdjust timing to match the session format (lightning: 5-10 min, talk: 25-45 min, workshop: 60-120 min).\n\n### 5. Notes to Organizers (private)\n\nThis is your chance to speak candidly to the selection committee. Include:\n- **Why this talk matters now** for their specific audience\n- **Your unique qualification** — what experience or perspective makes you the right speaker\n- **Prior speaking experience** (if any) with links to recordings\n- **Anything else relevant** — first-time speaker willingness to do a dry run, flexibility on format, etc.\n\nKeep it under 200 words. Be genuine, not boastful.\n\n### 6. Speaker Bio (50-100 words)\n\nWrite in third person. Include:\n- Current role and company\n- Relevant domain expertise\n- One humanizing detail (hobby, community involvement, etc.)\n- No more than 2 sentences of credentials\n\n### 7. Audience Level Recommendation\n\nClassify as one of:\n- **Beginner** — No prior knowledge needed; introductory concepts\n- **Intermediate** — Assumes working knowledge of the domain\n- **Advanced** — Deep dive requiring significant prior experience\n\nJustify the classification briefly.\n\n## Tailoring to the Conference\n\nBefore writing, research and consider:\n- **Conference themes and tracks** — align your proposal to announced topics\n- **Past speakers and talks** — differentiate from what's been covered\n- **Audience profile** — startup developers vs enterprise architects vs students\n- **Conference values** — some prioritize diversity, first-time speakers, open source, practical content\n- **Blind review** — if the CFP is anonymized, avoid identifying information in the abstract and description; put personal details only in speaker fields\n\n## What Reviewers Actually Evaluate\n\nReviewers read hundreds of proposals. They assess:\n\n1. **Relevance** — Does it fit the conference topics and audience?\n2. **Clarity** — Can they immediately understand what the talk is about?\n3. **Specificity** — Are concrete outcomes promised, not vague \"insights\"?\n4. **Novelty** — Does it offer something attendees can't just Google?\n5. **Speaker fit** — Is there evidence this person can deliver on the topic?\n6. **Audience value** — Will attendees walk away with actionable knowledge?\n\n## Proposal Enhancement Strategies\n\nAfter drafting, improve the proposal by:\n\n- **Cut filler words** — remove \"very,\" \"really,\" \"just,\" \"actually,\" \"I think\"\n- **Replace passive voice** — \"Patterns will be explored\" becomes \"You'll implement three patterns\"\n- **Add numbers** — \"We reduced latency\" becomes \"We reduced p99 latency from 12s to 200ms\"\n- **Check the \"so what?\" test** — every sentence should pass \"why would an attendee care?\"\n- **Read it as a reviewer** — imagine reading it as proposal #187 of 300 at 11pm\n\n## Multi-Submission Strategy\n\nMaximize acceptance chances:\n\n- Submit 3-5 proposals per conference (quality over quantity)\n- Vary formats: one talk, one lightning talk, one workshop\n- Cover different tracks if the conference has multiple\n- Reuse and adapt proposals across conferences — but always tailor the abstract to each audience\n- Track submissions in a spreadsheet with deadlines, statuses, and notes\n\n## Guidelines\n\n- Never include sales pitches, product marketing, or company promotion in proposals\n- Focus on what the audience learns, not what the speaker knows\n- Use second person (\"you'll learn\") in abstracts, third person in bios\n- Avoid jargon unless the audience is explicitly technical\n- If the conference has a code of conduct, ensure the proposal aligns with it\n- For blind review CFPs, keep all identifying information out of the abstract and outline\n- Offer to generate multiple proposal variants so the user can pick the strongest\n\n## Workflow\n\n1. Gather context: conference details, talk idea, speaker background\n2. Research the conference (themes, tracks, audience, past talks)\n3. Draft the full submission package (all 7 components above)\n4. Review against the \"What Reviewers Evaluate\" checklist\n5. Suggest improvements and alternatives\n6. If the user wants, generate 2-3 title\u002Fabstract variants to choose from\n\nFor detailed examples of accepted and rejected proposals, see [examples.md](examples.md).\n","# Pitching Tech Conference CFPs\n\nGenerate compelling Call for Papers (CFP) proposals that stand out from hundreds of submissions and get your talk accepted at tech conferences.\n\n## Quick Start\n\nAsk the user for:\n1. **Conference name and URL** (to tailor the proposal)\n2. **Talk idea** (topic, angle, or problem being solved)\n3. **Speaker background** (relevant experience, unique perspective)\n\nThen generate a complete CFP submission package.\n\n## Understanding CFP Platforms\n\nMost tech conferences use one of these platforms:\n\n**Sessionize** fields:\n- Session title (required)\n- Session description (required)\n- Session format (lightning, talk, workshop)\n- Track\u002Ftopic category\n- Audience level (beginner, intermediate, advanced)\n- Speaker name, email, tagline, biography\n- Custom fields per conference\n\n**PaperCall** fields:\n- Talk title\n- Elevator pitch (short summary)\n- Talk description \u002F abstract\n- Notes to organizers (private)\n- Session format\n- Audience level\n- Tags \u002F topics\n\n**Custom forms** (Google Forms, Airtable, etc.) vary but typically ask for a subset of the above.\n\n## The CFP Submission Package\n\nGenerate all of the following components for each proposal:\n\n### 1. Talk Title\n\nCraft a title that is:\n- **Specific and descriptive** over clever or punny\n- **Problem-oriented** — frames what the audience gains\n- **Concise** — under 80 characters\n- **Memorable** — stands out scanning a conference schedule\n\nGood examples:\n- \"K8s at Lightspeed: Managing 1000 Clusters in 60 Seconds\"\n- \"Type-Safe Database Queries Without an ORM\"\n- \"From 12s to 200ms: A Real-World Performance Debugging Story\"\n\nBad examples:\n- \"Scaling Kubernetes\" (too vague)\n- \"My Journey with React\" (self-focused, not audience-focused)\n- \"Things I Learned\" (says nothing)\n\n### 2. Abstract \u002F Description (150-400 words)\n\nThis is the public-facing blurb attendees see. It must accomplish three things:\n\n**a) Hook with a real problem (1-2 sentences)**\nOpen with a concrete pain point the audience recognizes. Use a scenario, a statistic, or a provocative question.\n\n**b) Promise specific outcomes (2-3 sentences)**\nState exactly what attendees will learn or be able to do after the talk. Use active verbs: \"build,\" \"implement,\" \"debug,\" \"evaluate\" — not \"learn about\" or \"gain insights.\"\n\n**c) Establish credibility through specifics (1-2 sentences)**\nMention concrete technologies, scale numbers, or real results. Show domain depth without being a sales pitch.\n\n**d) Leave them wanting more (1 sentence)**\nEnd with an inviting forward look or a hint at surprising findings.\n\nStructure template:\n```\n[Problem hook — why should anyone care?]\n\n[What you'll cover — be specific about topics and techniques]\n\n[What attendees walk away with — concrete, actionable outcomes]\n\n[Credibility signal — why you're the right person \u002F why now]\n```\n\n### 3. Elevator Pitch (1-2 sentences, ~300 characters)\n\nA punchy summary for quick scanning. Formula:\n```\n[Audience] will learn [specific skill\u002Finsight] by [approach\u002Fangle], enabling them to [concrete outcome].\n```\n\n### 4. Talk Outline (private, for organizers)\n\nProvide a structured breakdown showing you've thought through the talk:\n\n```\n- Introduction & problem framing (3 min)\n- [Section 1: Context\u002FBackground] (5 min)\n- [Section 2: Core technique\u002Fsolution] (8 min)\n- [Section 3: Demo \u002F case study] (7 min)\n- Key takeaways & resources (2 min)\n```\n\nAdjust timing to match the session format (lightning: 5-10 min, talk: 25-45 min, workshop: 60-120 min).\n\n### 5. Notes to Organizers (private)\n\nThis is your chance to speak candidly to the selection committee. Include:\n- **Why this talk matters now** for their specific audience\n- **Your unique qualification** — what experience or perspective makes you the right speaker\n- **Prior speaking experience** (if any) with links to recordings\n- **Anything else relevant** — first-time speaker willingness to do a dry run, flexibility on format, etc.\n\nKeep it under 200 words. Be genuine, not boastful.\n\n### 6. Speaker Bio (50-100 words)\n\nWrite in third person. Include:\n- Current role and company\n- Relevant domain expertise\n- One humanizing detail (hobby, community involvement, etc.)\n- No more than 2 sentences of credentials\n\n### 7. Audience Level Recommendation\n\nClassify as one of:\n- **Beginner** — No prior knowledge needed; introductory concepts\n- **Intermediate** — Assumes working knowledge of the domain\n- **Advanced** — Deep dive requiring significant prior experience\n\nJustify the classification briefly.\n\n## Tailoring to the Conference\n\nBefore writing, research and consider:\n- **Conference themes and tracks** — align your proposal to announced topics\n- **Past speakers and talks** — differentiate from what's been covered\n- **Audience profile** — startup developers vs enterprise architects vs students\n- **Conference values** — some prioritize diversity, first-time speakers, open source, practical content\n- **Blind review** — if the CFP is anonymized, avoid identifying information in the abstract and description; put personal details only in speaker fields\n\n## What Reviewers Actually Evaluate\n\nReviewers read hundreds of proposals. They assess:\n\n1. **Relevance** — Does it fit the conference topics and audience?\n2. **Clarity** — Can they immediately understand what the talk is about?\n3. **Specificity** — Are concrete outcomes promised, not vague \"insights\"?\n4. **Novelty** — Does it offer something attendees can't just Google?\n5. **Speaker fit** — Is there evidence this person can deliver on the topic?\n6. **Audience value** — Will attendees walk away with actionable knowledge?\n\n## Proposal Enhancement Strategies\n\nAfter drafting, improve the proposal by:\n\n- **Cut filler words** — remove \"very,\" \"really,\" \"just,\" \"actually,\" \"I think\"\n- **Replace passive voice** — \"Patterns will be explored\" becomes \"You'll implement three patterns\"\n- **Add numbers** — \"We reduced latency\" becomes \"We reduced p99 latency from 12s to 200ms\"\n- **Check the \"so what?\" test** — every sentence should pass \"why would an attendee care?\"\n- **Read it as a reviewer** — imagine reading it as proposal #187 of 300 at 11pm\n\n## Multi-Submission Strategy\n\nMaximize acceptance chances:\n\n- Submit 3-5 proposals per conference (quality over quantity)\n- Vary formats: one talk, one lightning talk, one workshop\n- Cover different tracks if the conference has multiple\n- Reuse and adapt proposals across conferences — but always tailor the abstract to each audience\n- Track submissions in a spreadsheet with deadlines, statuses, and notes\n\n## Guidelines\n\n- Never include sales pitches, product marketing, or company promotion in proposals\n- Focus on what the audience learns, not what the speaker knows\n- Use second person (\"you'll learn\") in abstracts, third person in bios\n- Avoid jargon unless the audience is explicitly technical\n- If the conference has a code of conduct, ensure the proposal aligns with it\n- For blind review CFPs, keep all identifying information out of the abstract and outline\n- Offer to generate multiple proposal variants so the user can pick the strongest\n\n## Workflow\n\n1. Gather context: conference details, talk idea, speaker background\n2. Research the conference (themes, tracks, audience, past talks)\n3. Draft the full submission package (all 7 components above)\n4. Review against the \"What Reviewers Evaluate\" checklist\n5. Suggest improvements and alternatives\n6. If the user wants, generate 2-3 title\u002Fabstract variants to choose from\n\nFor detailed examples of accepted and rejected proposals, see [examples.md](examples.md).\n",{"name":5,"description":7},"main","9e160012bf175f264279507807d206dbe17e9aac","target\u002Fhome\u002F.agents\u002Fskills\u002Fpitching-tech-cfps",3,"https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles","https:\u002F\u002Fgithub.com\u002Fjkomyno","https:\u002F\u002Fjkomyno.dev","AX engineer working on agentic dev tools. Previously Senior SWE @prisma & mathematical optimisation @cvut. International tech speaker.","2026-11-14 21:45:28",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jkomyno\u002F.dotfiles --skill pitching-tech-cfps",{"tool":39,"command":40},"bunx","bunx skills add jkomyno\u002F.dotfiles --skill pitching-tech-cfps",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jkomyno\u002F.dotfiles --skill pitching-tech-cfps","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Fpitching-tech-cfps\u002FSKILL.md",true,[],[48,56,63,70,77,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7DY814SMBRJFBZF4NTY2ZCK","potetomode","Load pstack's poteto-mode workflow for concise responses, deliberate delegation, simple code, and verified work. Use when the user requests potetomode or \u002Fpotetomode.","https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Fpotetomode\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M7DY7YG4V89VKPN5ZQ64EXAV","bro","Restate the last assistant message in plain, concise language using pstack's bro skill. Use when the user requests bro or \u002Fbro.","https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Fbro\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75MJWVSC460HY537YJ5W6MX","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\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75MJSKK9BZGSTMZ308DM1HA","using-exe-dev","Operate exe.dev virtual machines. Use when the task mentions exe.dev, exe VMs, *.exe.xyz hosts, or exe.dev infrastructure.","https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Fusing-exe-dev\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M75MJNT911P56SE62DZSQTX8","unlazy","Prove substantial work complete with file-backed gates and runnable checks. Use for exhaustive completion, a Depth Tree, or a completion ledger.","https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Funlazy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Funlazy\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M75MJHN22B60A6BNT0W4H7NH","sync-skills","Sync vendored third-party skills against their upstream repositories, re-apply local patches, and flag new upstream skills. Invoke explicitly with \u002Fsync-skills.","https:\u002F\u002Fgithub.com\u002Fjkomyno\u002F.dotfiles\u002Fblob\u002Fmain\u002Ftarget\u002Fhome\u002F.agents\u002Fskills\u002Fsync-skills\u002FSKILL.md",[],[]]