[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CER7Z2T6WYN70ZQ040D43V":3,"skill-same:01M7CER7Z2T6WYN70ZQ040D43V":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CER7Z2T6WYN70ZQ040D43V","dry-three-copy-tests",null,"Write and revise marketing copy using Harry Dry's tests for vivid imagery, checkable claims, and earned brand specificity. Use for ads, headlines, landing pages, emails, calls to action, and copy critiques.","getedgehq\u002Fskills","getedgehq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F327350993?v=4","01M7CEH5YJQYF1PB3MDG9PA5HX","01M7CEH5ZAPY8TX4H3E04KM875",5,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dry-three-copy-tests\ndescription: \"Write and revise marketing copy using Harry Dry's tests for vivid imagery, checkable claims, and earned brand specificity. Use for ads, headlines, landing pages, emails, calls to action, and copy critiques.\"\n---\n\n# Harry Dry's Three Copy Tests\n\nBased on Harry Dry's public method. Not affiliated with or endorsed by Harry Dry.\n\n## When to use\n\nUse this skill when marketing copy needs to help a particular reader understand an offer and take a next step. It suits both new drafts and revisions, especially polished sentences that hide the product behind abstractions or could fit almost any advertiser. The deliverable is finished copy accompanied, when useful, by a brief explanation of its imagery, evidence, and distinctive truth. [S1][S2]\n\nApply the tests most closely to the main selling promise. Supporting lines can explain the mechanism, substantiate the promise, and answer objections. A button or factual label need not carry an entire sales case. Adapt the scope to the requested channel and length; use this as a writing method rather than a requirement to redesign every page. [S3]\n\nBefore drafting, read the relevant sections of [references\u002Fmethod.md](references\u002Fmethod.md). The examples illustrate decisions, not reusable claims. Source citations identify the public advice behind the method; they are never evidence that a user's product delivers a particular result.\n\n## Procedure\n\n1. **Define the assignment.** Record the reader, channel, desired action, length, and reader's most important problem. Use the brief fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Choose one primary promise so the copy has a clear job; do not silently widen a headline request into a full campaign.\n\n2. **Gather usable facts.** Inventory the actual offer, mechanism, constraints, proof, and objections. Separate supplied evidence from assumptions and missing information using [references\u002Fmethod.md](references\u002Fmethod.md), section \"Build the evidence base.\" Ask for a fact only when it changes the promise; otherwise draft within what is known.\n\n3. **Listen for customer language.** Extract recurring frustrations and desired outcomes from supplied interviews, reviews, or support notes. Follow \"Build the evidence base\" in [references\u002Fmethod.md](references\u002Fmethod.md). Preserve meaning without inventing testimonials or making one comment represent everyone. If no customer material exists, label audience assumptions. [S4]\n\n4. **Write a plain proposition.** State what the reader gets and how the offer supplies it. Follow \"Choose the selling angle\" in [references\u002Fmethod.md](references\u002Fmethod.md). Explain an unfamiliar product directly; for a familiar category, consider a supported objection, audience, or mechanism as the hook. [S3]\n\n5. **Find the visible moment.** Replace abstract benefits with relevant objects, actions, or situations. Use \"Test 1: Picture\" in [references\u002Fmethod.md](references\u002Fmethod.md), and compare the tool-library illustration in [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md). Keep the scene connected to the offer rather than adding decoration.\n\n6. **Identify the truth test.** For each important assertion, describe what observation would confirm or contradict it. Follow \"Test 2: Check\" in [references\u002Fmethod.md](references\u002Fmethod.md). Replace untestable praise with a bounded fact or observable mechanism. A number without evidence remains unusable.\n\n7. **Find earned specificity.** Substitute a plausible competitor's name and inspect whether the line remains natural and true. Follow \"Test 3: Belong\" in [references\u002Fmethod.md](references\u002Fmethod.md). Use meaningful facts about the actual offer; if no difference is established, record that limitation instead of inventing exclusivity.\n\n8. **Compare concrete angles.** Draft a few materially different options, such as a use moment, an objection, or a product mechanism. Apply the three tests separately using the audit fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Choose the strongest truthful option; a memorable but unsupported line cannot win.\n\n9. **Make the whole unit understandable.** Read the headline with its subtitle, proof, visual, and next step where those elements exist. Follow \"Context and channel\" in [references\u002Fmethod.md](references\u002Fmethod.md). Show how the offer works and ensure the button describes a next step it actually provides. [S3]\n\n10. **Edit for a human reader.** Read aloud and remove inflated wording, repetition, and unnecessary modifiers without stripping useful personality. Apply \"Voice and explicit warnings\" in [references\u002Fmethod.md](references\u002Fmethod.md). Retain qualifications that keep the promise accurate. [S5][S6]\n\n11. **Review and repair.** Run [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md). Revisit facts when the idea fails all three tests; rewrite the relevant line when a local weakness remains. Record unresolved evidence or specificity gaps explicitly. Stop when further edits add style without improving clarity, support, or relevance.\n\n12. **Deliver the requested copy first.** Use [templates\u002Foutput-template.md](templates\u002Foutput-template.md) for the handoff. Include a concise audit and open items when the user wants reasoning. For final-copy-only requests, perform the audit internally and return only supported copy in the requested format.\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, usage scope, and the agent's drafting and revision loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed tests, evidence rules, channel decisions, edge cases, and warnings.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered register of the six public sources actually fetched.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Invented before-and-after illustrations with rule audits.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in copy deliverable and field-by-field guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review, common failures, and targeted fixes.\n","# Harry Dry's Three Copy Tests\n\nBased on Harry Dry's public method. Not affiliated with or endorsed by Harry Dry.\n\n## When to use\n\nUse this skill when marketing copy needs to help a particular reader understand an offer and take a next step. It suits both new drafts and revisions, especially polished sentences that hide the product behind abstractions or could fit almost any advertiser. The deliverable is finished copy accompanied, when useful, by a brief explanation of its imagery, evidence, and distinctive truth. [S1][S2]\n\nApply the tests most closely to the main selling promise. Supporting lines can explain the mechanism, substantiate the promise, and answer objections. A button or factual label need not carry an entire sales case. Adapt the scope to the requested channel and length; use this as a writing method rather than a requirement to redesign every page. [S3]\n\nBefore drafting, read the relevant sections of [references\u002Fmethod.md](references\u002Fmethod.md). The examples illustrate decisions, not reusable claims. Source citations identify the public advice behind the method; they are never evidence that a user's product delivers a particular result.\n\n## Procedure\n\n1. **Define the assignment.** Record the reader, channel, desired action, length, and reader's most important problem. Use the brief fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Choose one primary promise so the copy has a clear job; do not silently widen a headline request into a full campaign.\n\n2. **Gather usable facts.** Inventory the actual offer, mechanism, constraints, proof, and objections. Separate supplied evidence from assumptions and missing information using [references\u002Fmethod.md](references\u002Fmethod.md), section \"Build the evidence base.\" Ask for a fact only when it changes the promise; otherwise draft within what is known.\n\n3. **Listen for customer language.** Extract recurring frustrations and desired outcomes from supplied interviews, reviews, or support notes. Follow \"Build the evidence base\" in [references\u002Fmethod.md](references\u002Fmethod.md). Preserve meaning without inventing testimonials or making one comment represent everyone. If no customer material exists, label audience assumptions. [S4]\n\n4. **Write a plain proposition.** State what the reader gets and how the offer supplies it. Follow \"Choose the selling angle\" in [references\u002Fmethod.md](references\u002Fmethod.md). Explain an unfamiliar product directly; for a familiar category, consider a supported objection, audience, or mechanism as the hook. [S3]\n\n5. **Find the visible moment.** Replace abstract benefits with relevant objects, actions, or situations. Use \"Test 1: Picture\" in [references\u002Fmethod.md](references\u002Fmethod.md), and compare the tool-library illustration in [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md). Keep the scene connected to the offer rather than adding decoration.\n\n6. **Identify the truth test.** For each important assertion, describe what observation would confirm or contradict it. Follow \"Test 2: Check\" in [references\u002Fmethod.md](references\u002Fmethod.md). Replace untestable praise with a bounded fact or observable mechanism. A number without evidence remains unusable.\n\n7. **Find earned specificity.** Substitute a plausible competitor's name and inspect whether the line remains natural and true. Follow \"Test 3: Belong\" in [references\u002Fmethod.md](references\u002Fmethod.md). Use meaningful facts about the actual offer; if no difference is established, record that limitation instead of inventing exclusivity.\n\n8. **Compare concrete angles.** Draft a few materially different options, such as a use moment, an objection, or a product mechanism. Apply the three tests separately using the audit fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Choose the strongest truthful option; a memorable but unsupported line cannot win.\n\n9. **Make the whole unit understandable.** Read the headline with its subtitle, proof, visual, and next step where those elements exist. Follow \"Context and channel\" in [references\u002Fmethod.md](references\u002Fmethod.md). Show how the offer works and ensure the button describes a next step it actually provides. [S3]\n\n10. **Edit for a human reader.** Read aloud and remove inflated wording, repetition, and unnecessary modifiers without stripping useful personality. Apply \"Voice and explicit warnings\" in [references\u002Fmethod.md](references\u002Fmethod.md). Retain qualifications that keep the promise accurate. [S5][S6]\n\n11. **Review and repair.** Run [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md). Revisit facts when the idea fails all three tests; rewrite the relevant line when a local weakness remains. Record unresolved evidence or specificity gaps explicitly. Stop when further edits add style without improving clarity, support, or relevance.\n\n12. **Deliver the requested copy first.** Use [templates\u002Foutput-template.md](templates\u002Foutput-template.md) for the handoff. Include a concise audit and open items when the user wants reasoning. For final-copy-only requests, perform the audit internally and return only supported copy in the requested format.\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, usage scope, and the agent's drafting and revision loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed tests, evidence rules, channel decisions, edge cases, and warnings.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered register of the six public sources actually fetched.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Invented before-and-after illustrations with rule audits.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in copy deliverable and field-by-field guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review, common failures, and targeted fixes.\n",{"name":5,"description":7},"main","01960aeb08909dbd0c1a2d4f219cdb300099b8b9",0,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills","https:\u002F\u002Fgetedge.cc","https:\u002F\u002Fgithub.com\u002Fgetedgehq","2026-11-12 10:05:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add getedgehq\u002Fskills --skill dry-three-copy-tests",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill dry-three-copy-tests",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill dry-three-copy-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002FSKILL.md",true,[45,51,55,59,63,67,71],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"checklists\u002Freview-checklist.md","REFERENCE","参考文档",4273,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002Fchecklists\u002Freview-checklist.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"DERIVATION.json",2244,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002FDERIVATION.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Fworked-examples.md",5089,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002Fexamples\u002Fworked-examples.md",{"path":60,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":15},"LICENSE","许可证",10756,{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmethod.md",9097,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002Freferences\u002Fmethod.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsources.md",2229,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002Freferences\u002Fsources.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Foutput-template.md",4007,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fdry-three-copy-tests\u002Ftemplates\u002Foutput-template.md",[76,84,92,99,106,114],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CFVPC1P7JN60J5AN9AZZ5G","zero-downtime-cloud-move","Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CFVH8VN6G2KE8PBFD1CRMN","zayats-ceo-branding","Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CFV9BB7G8K8CX9RKZ3GECX","yc-app-roast","YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks \"what would a YC partner think\", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-roast\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CFV11Z1HB9EEWFQ6PCJ98X","yc-app-review","YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press \"Send my notes\" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-review\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CFTSVJV7XCSW62W39MX8CZ","x-growth-playbook","X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says \"analyse my X posts\", \"what works on my Twitter\", \"how do I grow on X\", \"what should I post next on X\", \"audit my X account\", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7CFTK101S3P00MQ129G5YNH","workplan","Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: \"workplan\", \"work plan\", \"create a plan\", \"what's the plan\", \"where was I\", or when Claude detects a multi-step task that needs tracking.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FSKILL.md",[],[]]