[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F50SDDWNVR786KVQP63ZNN":3,"skill-same:01M7F50SDDWNVR786KVQP63ZNN":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},"01M7F50SDDWNVR786KVQP63ZNN","read-aloud-rhythm-design",null,"Design how a poem will sound when spoken or look when printed by setting a timing budget, breath units, line breaks, pause and laugh points, the placement of the landing line, and keepsake page layout. Use when an occasional poem will be read aloud at a toast, eulogy, ceremony, or recording, when the reader is a non-performer, or when the poem will be framed, printed, or written in a card.","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\u002Fpoetic-form-specialist\u002Fskills\u002Fread-aloud-rhythm-design\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: read-aloud-rhythm-design\ndescription: Design how a poem will sound when spoken or look when printed by setting a timing budget, breath units, line breaks, pause and laugh points, the placement of the landing line, and keepsake page layout. Use when an occasional poem will be read aloud at a toast, eulogy, ceremony, or recording, when the reader is a non-performer, or when the poem will be framed, printed, or written in a card.\n---\n\n# Read-Aloud Rhythm Design\n\nA poem for an occasion lives or dies in delivery. This skill converts delivery mode into concrete rhythm and layout instructions.\n\n## Spoken Delivery\n\n### Timing Budget\n\n- Comfortable spoken pace is 130 to 150 words per minute. Nervous readers speed up, so plan for roughly 140.\n- Typical budgets:\n  - Toast: 30 to 90 seconds, or 70 to 200 words\n  - Ceremony reading: 1 to 2 minutes, or 140 to 280 words\n  - Eulogy poem: 1 to 3 minutes, or 140 to 400 words\n  - Birthday or retirement verse: 45 to 120 seconds\n- Reserve time for laughter and applause, typically 3 to 5 seconds per planned laugh line.\n\n### Breath Units\n\n- One line should equal one breath for the actual reader.\n- For non-performers, keep lines to 6 to 10 syllables. For confident readers, pentameter of about 10 syllables is fine.\n- Prefer end-stopped lines. A listener cannot see enjambment, and inexperienced readers often pause at line ends regardless of the punctuation.\n- Use enjambment only for a deliberate effect, and mark it for the reader.\n\n### Audibility\n\n- Listeners cannot reread, so make structure audible through rhyme, refrain, anaphora, or a clear stanza pattern.\n- Put names, places, and punchlines at line ends, where the voice naturally lands.\n- Avoid tongue-twister clusters and sibilant pileups, and avoid homophones that confuse the ear.\n\n### Landing Line\n\n- Every spoken occasional poem needs one landing line: the line the audience remembers and responds to.\n- **Toast:** the final line cues the raise, so it should be short, rhymed if possible, and include the honoree's name.\n- **Eulogy:** the consolation line comes near the end, followed by a quiet closing line rather than a flourish.\n- **Wedding:** the final line faces forward to the future or to a blessing.\n- **Birthday or retirement:** the final line lands the biggest laugh or the warmest turn.\n\n### Pause and Laugh Points\n\n- Mark stanza breaks as beats.\n- Place laugh lines at stanza ends so laughter does not bury the next line.\n- In grief pieces, place one deliberate pause before the turn toward consolation.\n\n## Keepsake Delivery\n\n### Medium Constraints\n\n| Medium | Guidance |\n|--------|----------|\n| Greeting card | 4 to 12 lines, short lines, and a title only if the space allows |\n| Framed print | 12 to 24 lines, visually balanced stanzas, and line lengths that center cleanly |\n| Ceremony program | Under half a page, with a title and attribution line |\n| Gift book or engraving | Very short, and every word must be permanent-worthy |\n\n### Page Shape\n\n- Eye poems may use enjambment, white space, and irregular stanzas for effect.\n- Keep stanza lengths visually consistent unless the variation carries meaning.\n- For acrostics, confirm that the spine letters are visible in the chosen typography.\n- Specify title treatment and whether to include date, names, or dedication lines.\n\n## Dual Delivery\n\nIf the poem is both read aloud and given as a keepsake, design for the ear first and then check the page. Audible structure reads fine on paper, but page-first structure often fails when spoken.\n\n## Output Checklist\n\n- Timing or space budget, converted to words and lines\n- Breath unit rule for this reader\n- Landing line position and function\n- Pause and laugh point positions\n- Layout notes for the keepsake, if one applies\n","# Read-Aloud Rhythm Design\n\nA poem for an occasion lives or dies in delivery. This skill converts delivery mode into concrete rhythm and layout instructions.\n\n## Spoken Delivery\n\n### Timing Budget\n\n- Comfortable spoken pace is 130 to 150 words per minute. Nervous readers speed up, so plan for roughly 140.\n- Typical budgets:\n  - Toast: 30 to 90 seconds, or 70 to 200 words\n  - Ceremony reading: 1 to 2 minutes, or 140 to 280 words\n  - Eulogy poem: 1 to 3 minutes, or 140 to 400 words\n  - Birthday or retirement verse: 45 to 120 seconds\n- Reserve time for laughter and applause, typically 3 to 5 seconds per planned laugh line.\n\n### Breath Units\n\n- One line should equal one breath for the actual reader.\n- For non-performers, keep lines to 6 to 10 syllables. For confident readers, pentameter of about 10 syllables is fine.\n- Prefer end-stopped lines. A listener cannot see enjambment, and inexperienced readers often pause at line ends regardless of the punctuation.\n- Use enjambment only for a deliberate effect, and mark it for the reader.\n\n### Audibility\n\n- Listeners cannot reread, so make structure audible through rhyme, refrain, anaphora, or a clear stanza pattern.\n- Put names, places, and punchlines at line ends, where the voice naturally lands.\n- Avoid tongue-twister clusters and sibilant pileups, and avoid homophones that confuse the ear.\n\n### Landing Line\n\n- Every spoken occasional poem needs one landing line: the line the audience remembers and responds to.\n- **Toast:** the final line cues the raise, so it should be short, rhymed if possible, and include the honoree's name.\n- **Eulogy:** the consolation line comes near the end, followed by a quiet closing line rather than a flourish.\n- **Wedding:** the final line faces forward to the future or to a blessing.\n- **Birthday or retirement:** the final line lands the biggest laugh or the warmest turn.\n\n### Pause and Laugh Points\n\n- Mark stanza breaks as beats.\n- Place laugh lines at stanza ends so laughter does not bury the next line.\n- In grief pieces, place one deliberate pause before the turn toward consolation.\n\n## Keepsake Delivery\n\n### Medium Constraints\n\n| Medium | Guidance |\n|--------|----------|\n| Greeting card | 4 to 12 lines, short lines, and a title only if the space allows |\n| Framed print | 12 to 24 lines, visually balanced stanzas, and line lengths that center cleanly |\n| Ceremony program | Under half a page, with a title and attribution line |\n| Gift book or engraving | Very short, and every word must be permanent-worthy |\n\n### Page Shape\n\n- Eye poems may use enjambment, white space, and irregular stanzas for effect.\n- Keep stanza lengths visually consistent unless the variation carries meaning.\n- For acrostics, confirm that the spine letters are visible in the chosen typography.\n- Specify title treatment and whether to include date, names, or dedication lines.\n\n## Dual Delivery\n\nIf the poem is both read aloud and given as a keepsake, design for the ear first and then check the page. Audible structure reads fine on paper, but page-first structure often fails when spoken.\n\n## Output Checklist\n\n- Timing or space budget, converted to words and lines\n- Breath unit rule for this reader\n- Landing line position and function\n- Pause and laugh point positions\n- Layout notes for the keepsake, if one applies\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fpoetic-form-specialist\u002Fskills\u002Fread-aloud-rhythm-design","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 read-aloud-rhythm-design",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill read-aloud-rhythm-design",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill read-aloud-rhythm-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fpoetic-form-specialist\u002Fskills\u002Fread-aloud-rhythm-design\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",[],[]]