[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4Z2X8SR6C2C4JQGCGP0VJ":3,"skill-same:01M7F4Z2X8SR6C2C4JQGCGP0VJ":45},{"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},"01M7F4Z2X8SR6C2C4JQGCGP0VJ","occasional-poem-drafting",null,"Draft a personal occasional poem from a locked occasion brief, a detail brief, and a binding form specification, setting tone register, emotional arc, line breaks and sound texture for the delivery mode. Use when writing a first draft of a wedding, eulogy, birthday, retirement, anniversary, toast or gift poem.","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\u002Foccasional-poet\u002Fskills\u002Foccasional-poem-drafting\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: occasional-poem-drafting\ndescription: Draft a personal occasional poem from a locked occasion brief, a detail brief, and a binding form specification, setting tone register, emotional arc, line breaks and sound texture for the delivery mode. Use when writing a first draft of a wedding, eulogy, birthday, retirement, anniversary, toast or gift poem.\n---\n\n# Occasional Poem Drafting\n\nA method for producing a first draft that fits the occasion, the room, and the form contract on the first pass.\n\n## Inputs\n\n- **Occasion brief** (from the lead) covers the occasion, audience, delivery mode, target length, and tone.\n- **Detail brief** (from the interviewer) covers names, relationships, stories, specifics, and the avoid list.\n- **Form specification** (from the form specialist) covers meter, rhyme scheme, stanza shape, length, and read-aloud rhythm.\n\nIf any input is missing, draft only from what exists. List what is missing as open questions. Never fill gaps with invented facts.\n\n## Step 1 — Set the tone register\n\nPick one primary register and at most one secondary register. Each has its own rules:\n\n| Register | Typical occasions | Rules |\n|----------|-------------------|-------|\n| Tender | Anniversaries, gifts, weddings | Quiet images and domestic specifics. Understatement over declaration. |\n| Celebratory | Birthdays, weddings, retirements | Momentum and bright verbs. Lists of vivid specifics. End with a lift toward the future. |\n| Humorous | Toasts, milestone birthdays, retirements | Affectionate teasing about habits, never about body, age or failure. Every joke should resolve into warmth. |\n| Consoling | Eulogies, memorials, sympathy gifts | Honor the life through ordinary specifics. Acknowledge loss plainly. Do not rush to comfort or explain death. |\n\nA secondary register is placed deliberately. Examples are a single laugh in a eulogy or one tender stanza in a roast-style toast. The poem must return from it.\n\n## Step 2 — Plan the arc\n\nWrite one line each for the three beats:\n\n1. **Opening.** Ground the listener in a specific place, object or moment. Do not open with the occasion's abstract name.\n2. **Turn.** The shift that gives the poem meaning. Examples: from past to present, from habit to what it revealed, from loss to what remains.\n3. **Landing.** The final line or couplet the room will remember. Draft it now, before the middle.\n\n## Step 3 — Draft to the form contract\n\n- Build stanza by stanza. Each stanza must carry at least one concrete detail from the detail brief.\n- Honor the meter and rhyme scheme. If the form specification forces inverted syntax, filler words or a false rhyme, rewrite the line instead.\n- If no rewrite works, propose a minimal deviation and note it.\n- Hold the length. For spoken poems, estimate read-aloud time at roughly 130 to 150 words per minute. Slow to about 110 for eulogies.\n\n## Step 4 — Tune for delivery mode\n\n**Spoken (toast, reading, eulogy):**\n- End-stop most lines so the speaker can breathe.\n- Put the key word at the end of the line.\n- Avoid consonant pile-ups and tongue-twisting names in stressed positions.\n- Use rhyme and refrain as memory anchors for the audience.\n\n**Read on a card or page:**\n- Enjambment and quieter internal sound are available.\n- White space can carry pauses.\n\n**Framed or keepsake:**\n- Favor a compact shape that looks balanced on the page.\n- Every line must bear rereading for years.\n\n## Step 5 — Self-check before submitting\n\n- [ ] Every line passes the only-these-people test (it could not belong to another subject).\n- [ ] No stock phrases: journey, forever and always, soulmate, angels, golden years, two hearts as one, gone too soon.\n- [ ] Tone register holds, and any secondary turn is deliberate and resolved.\n- [ ] Form specification is met, or each deviation is noted with its reason.\n- [ ] Length and read-aloud time are within target.\n- [ ] Nothing from the avoid list appears, directly or obliquely.\n- [ ] Names are spelled exactly as in the detail brief.\n","# Occasional Poem Drafting\n\nA method for producing a first draft that fits the occasion, the room, and the form contract on the first pass.\n\n## Inputs\n\n- **Occasion brief** (from the lead) covers the occasion, audience, delivery mode, target length, and tone.\n- **Detail brief** (from the interviewer) covers names, relationships, stories, specifics, and the avoid list.\n- **Form specification** (from the form specialist) covers meter, rhyme scheme, stanza shape, length, and read-aloud rhythm.\n\nIf any input is missing, draft only from what exists. List what is missing as open questions. Never fill gaps with invented facts.\n\n## Step 1 — Set the tone register\n\nPick one primary register and at most one secondary register. Each has its own rules:\n\n| Register | Typical occasions | Rules |\n|----------|-------------------|-------|\n| Tender | Anniversaries, gifts, weddings | Quiet images and domestic specifics. Understatement over declaration. |\n| Celebratory | Birthdays, weddings, retirements | Momentum and bright verbs. Lists of vivid specifics. End with a lift toward the future. |\n| Humorous | Toasts, milestone birthdays, retirements | Affectionate teasing about habits, never about body, age or failure. Every joke should resolve into warmth. |\n| Consoling | Eulogies, memorials, sympathy gifts | Honor the life through ordinary specifics. Acknowledge loss plainly. Do not rush to comfort or explain death. |\n\nA secondary register is placed deliberately. Examples are a single laugh in a eulogy or one tender stanza in a roast-style toast. The poem must return from it.\n\n## Step 2 — Plan the arc\n\nWrite one line each for the three beats:\n\n1. **Opening.** Ground the listener in a specific place, object or moment. Do not open with the occasion's abstract name.\n2. **Turn.** The shift that gives the poem meaning. Examples: from past to present, from habit to what it revealed, from loss to what remains.\n3. **Landing.** The final line or couplet the room will remember. Draft it now, before the middle.\n\n## Step 3 — Draft to the form contract\n\n- Build stanza by stanza. Each stanza must carry at least one concrete detail from the detail brief.\n- Honor the meter and rhyme scheme. If the form specification forces inverted syntax, filler words or a false rhyme, rewrite the line instead.\n- If no rewrite works, propose a minimal deviation and note it.\n- Hold the length. For spoken poems, estimate read-aloud time at roughly 130 to 150 words per minute. Slow to about 110 for eulogies.\n\n## Step 4 — Tune for delivery mode\n\n**Spoken (toast, reading, eulogy):**\n- End-stop most lines so the speaker can breathe.\n- Put the key word at the end of the line.\n- Avoid consonant pile-ups and tongue-twisting names in stressed positions.\n- Use rhyme and refrain as memory anchors for the audience.\n\n**Read on a card or page:**\n- Enjambment and quieter internal sound are available.\n- White space can carry pauses.\n\n**Framed or keepsake:**\n- Favor a compact shape that looks balanced on the page.\n- Every line must bear rereading for years.\n\n## Step 5 — Self-check before submitting\n\n- [ ] Every line passes the only-these-people test (it could not belong to another subject).\n- [ ] No stock phrases: journey, forever and always, soulmate, angels, golden years, two hearts as one, gone too soon.\n- [ ] Tone register holds, and any secondary turn is deliberate and resolved.\n- [ ] Form specification is met, or each deviation is noted with its reason.\n- [ ] Length and read-aloud time are within target.\n- [ ] Nothing from the avoid list appears, directly or obliquely.\n- [ ] Names are spelled exactly as in the detail brief.\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Foccasional-poet\u002Fskills\u002Foccasional-poem-drafting","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 occasional-poem-drafting",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill occasional-poem-drafting",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill occasional-poem-drafting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Foccasional-poet\u002Fskills\u002Foccasional-poem-drafting\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[]]