[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CFM8WFEJQ7QSQCFGHJA6FD":3,"skill-same:01M7CFM8WFEJQ7QSQCFGHJA6FD":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},"01M7CFM8WFEJQ7QSQCFGHJA6FD","shapiro-writing-well",null,"Develop and revise nonfiction using Julian Shapiro's public Writing Well method. Use for essays, articles, blog posts, and nonfiction chapters that need stronger insights, curiosity, clarity, concision, and an authentic voice.","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\u002Fshapiro-writing-well\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: shapiro-writing-well\ndescription: \"Develop and revise nonfiction using Julian Shapiro's public Writing Well method. Use for essays, articles, blog posts, and nonfiction chapters that need stronger insights, curiosity, clarity, concision, and an authentic voice.\"\n---\n\n# Writing Well with Julian Shapiro's Method\n\nBased on Julian Shapiro's public method. Not affiliated with or endorsed by Julian Shapiro.\n\n## When to use\n\nUse this skill when developing a nonfiction idea, turning notes into a substantive article, or revising a draft that feels obvious, bloated, lifeless, or difficult to finish. The deliverable is a finished nonfiction piece, with a brief editorial note or feedback request only when useful or requested. Writing should help uncover the argument, rather than merely transcribe conclusions already reached. [S1]\n\nStart from the user's objective, audience, evidence, desired format, and existing voice. For revision, preserve the intended meaning while questioning the structure and wording. For ideation, explore until there is something worthwhile to say. Apply the method proportionately: a short post needs less scaffolding than a chapter. Shapiro treats his frameworks as flexible approaches, so the goal is useful, interesting writing rather than mechanical compliance. [S6]\n\nThis package supports nonfiction craft, not a substitute for subject research or factual verification. Do not manufacture an author's experiences, empirical findings, or reader responses to make the piece compelling. The examples are invented illustrations, not evidence. These are operational safeguards for applying the method with an agent.\n\n## Procedure\n\n1. **Establish the writing brief.** Record the reader, purpose, constraints, available material, and what the author wants to understand or change. If the objective is uncertain, explore a short rough passage before choosing it. See [method: Objective and motivation](references\u002Fmethod.md#objective-and-motivation) and the brief fields in [the output template](templates\u002Foutput-template.md). [S2]\n\n2. **Locate the worthwhile insight.** Identify what challenges expectations, explains a mechanism, clarifies an experience, or makes a familiar feeling newly legible. Test significance as well as surprise. See [method: Novelty and resonance](references\u002Fmethod.md#novelty-and-resonance). [S2] [S3]\n\n3. **Draft competing openings.** Try several questions, partial narratives, or claims. Choose the opening that gives the reader enough context to care and creates an answerable promise. Seek early reader reactions when available. See [method: Introduction and promises](references\u002Fmethod.md#introduction-and-promises). [S2] [S6]\n\n4. **Build a flexible outline.** Turn the opening's questions into talking points. Separate prerequisites and supporting reasoning from consequences. Leave room for discoveries that improve the direction. See [method: Exploratory drafting](references\u002Fmethod.md#exploratory-drafting) and [the output template](templates\u002Foutput-template.md). [S3]\n\n5. **Generate before polishing.** Fill the outline quickly; use explicit placeholders for missing support. Develop weak ideas enough to diagnose their shortcomings, then try stronger alternatives. See [method: Exploratory drafting](references\u002Fmethod.md#exploratory-drafting) and [worked examples](examples\u002Fworked-examples.md). [S3] [S7]\n\n6. **Repair reasoning and clarity.** Identify each section's actual claim, evidence, and connection to the objective. Replace abstraction with concrete explanations and fewer ideas per sentence, while preserving nuance. See [method: Clarity and reasoning](references\u002Fmethod.md#clarity-and-reasoning). [S4]\n\n7. **Rebuild, then compress.** Reconstruct sprawling sections around their essentials before trimming individual words. Rephrase paragraphs and test whether the idea earns the requested length. See [method: Succinctness](references\u002Fmethod.md#succinctness) and the compression notes in [worked examples](examples\u002Fworked-examples.md). [S4]\n\n8. **Arrange curiosity and payoff.** Strengthen the opening, concentrate the strongest insight into a recognizable peak, and end by showing what the reader gained. Resolve every important promise. See [method: Intrigue and narrative](references\u002Fmethod.md#intrigue-and-narrative). [S4] [S8]\n\n9. **Add resonance in the author's voice.** Use a relevant example, analogy, anecdote, or vivid detail where it improves understanding or emotional recognition. Remove borrowed mannerisms and decoration. See [method: Voice and vividness](references\u002Fmethod.md#voice-and-vividness). [S5]\n\n10. **Use feedback honestly.** Request reactions from intended readers when possible. Revise confusion, dull stretches, and underdeveloped discoveries; stop chasing universal approval. If feedback is unavailable, mark that check pending. See [method: Feedback and stopping](references\u002Fmethod.md#feedback-and-stopping) and [the review checklist](checklists\u002Freview-checklist.md). [S4]\n\n11. **Copy edit and deliver.** Check punctuation, word choice, paragraph weight, unresolved placeholders, and factual boundaries. Run [the review checklist](checklists\u002Freview-checklist.md), then present the piece using [the output template](templates\u002Foutput-template.md), omitting planning fields from reader-facing copy. See [method: Copy editing](references\u002Fmethod.md#copy-editing). [S6] [S9]\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, scope, and the eleven-step writing loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed principles, decisions, cautions, and agent adaptations.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered inventory of the nine public pages fetched for this package.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Two invented revisions showing how the rules change the result.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in brief, piece structure, and optional editorial handoff.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review criteria and common failure repairs.\n","# Writing Well with Julian Shapiro's Method\n\nBased on Julian Shapiro's public method. Not affiliated with or endorsed by Julian Shapiro.\n\n## When to use\n\nUse this skill when developing a nonfiction idea, turning notes into a substantive article, or revising a draft that feels obvious, bloated, lifeless, or difficult to finish. The deliverable is a finished nonfiction piece, with a brief editorial note or feedback request only when useful or requested. Writing should help uncover the argument, rather than merely transcribe conclusions already reached. [S1]\n\nStart from the user's objective, audience, evidence, desired format, and existing voice. For revision, preserve the intended meaning while questioning the structure and wording. For ideation, explore until there is something worthwhile to say. Apply the method proportionately: a short post needs less scaffolding than a chapter. Shapiro treats his frameworks as flexible approaches, so the goal is useful, interesting writing rather than mechanical compliance. [S6]\n\nThis package supports nonfiction craft, not a substitute for subject research or factual verification. Do not manufacture an author's experiences, empirical findings, or reader responses to make the piece compelling. The examples are invented illustrations, not evidence. These are operational safeguards for applying the method with an agent.\n\n## Procedure\n\n1. **Establish the writing brief.** Record the reader, purpose, constraints, available material, and what the author wants to understand or change. If the objective is uncertain, explore a short rough passage before choosing it. See [method: Objective and motivation](references\u002Fmethod.md#objective-and-motivation) and the brief fields in [the output template](templates\u002Foutput-template.md). [S2]\n\n2. **Locate the worthwhile insight.** Identify what challenges expectations, explains a mechanism, clarifies an experience, or makes a familiar feeling newly legible. Test significance as well as surprise. See [method: Novelty and resonance](references\u002Fmethod.md#novelty-and-resonance). [S2] [S3]\n\n3. **Draft competing openings.** Try several questions, partial narratives, or claims. Choose the opening that gives the reader enough context to care and creates an answerable promise. Seek early reader reactions when available. See [method: Introduction and promises](references\u002Fmethod.md#introduction-and-promises). [S2] [S6]\n\n4. **Build a flexible outline.** Turn the opening's questions into talking points. Separate prerequisites and supporting reasoning from consequences. Leave room for discoveries that improve the direction. See [method: Exploratory drafting](references\u002Fmethod.md#exploratory-drafting) and [the output template](templates\u002Foutput-template.md). [S3]\n\n5. **Generate before polishing.** Fill the outline quickly; use explicit placeholders for missing support. Develop weak ideas enough to diagnose their shortcomings, then try stronger alternatives. See [method: Exploratory drafting](references\u002Fmethod.md#exploratory-drafting) and [worked examples](examples\u002Fworked-examples.md). [S3] [S7]\n\n6. **Repair reasoning and clarity.** Identify each section's actual claim, evidence, and connection to the objective. Replace abstraction with concrete explanations and fewer ideas per sentence, while preserving nuance. See [method: Clarity and reasoning](references\u002Fmethod.md#clarity-and-reasoning). [S4]\n\n7. **Rebuild, then compress.** Reconstruct sprawling sections around their essentials before trimming individual words. Rephrase paragraphs and test whether the idea earns the requested length. See [method: Succinctness](references\u002Fmethod.md#succinctness) and the compression notes in [worked examples](examples\u002Fworked-examples.md). [S4]\n\n8. **Arrange curiosity and payoff.** Strengthen the opening, concentrate the strongest insight into a recognizable peak, and end by showing what the reader gained. Resolve every important promise. See [method: Intrigue and narrative](references\u002Fmethod.md#intrigue-and-narrative). [S4] [S8]\n\n9. **Add resonance in the author's voice.** Use a relevant example, analogy, anecdote, or vivid detail where it improves understanding or emotional recognition. Remove borrowed mannerisms and decoration. See [method: Voice and vividness](references\u002Fmethod.md#voice-and-vividness). [S5]\n\n10. **Use feedback honestly.** Request reactions from intended readers when possible. Revise confusion, dull stretches, and underdeveloped discoveries; stop chasing universal approval. If feedback is unavailable, mark that check pending. See [method: Feedback and stopping](references\u002Fmethod.md#feedback-and-stopping) and [the review checklist](checklists\u002Freview-checklist.md). [S4]\n\n11. **Copy edit and deliver.** Check punctuation, word choice, paragraph weight, unresolved placeholders, and factual boundaries. Run [the review checklist](checklists\u002Freview-checklist.md), then present the piece using [the output template](templates\u002Foutput-template.md), omitting planning fields from reader-facing copy. See [method: Copy editing](references\u002Fmethod.md#copy-editing). [S6] [S9]\n\n## Files in this skill\n\n- [SKILL.md](SKILL.md): Entry point, scope, and the eleven-step writing loop.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Detailed principles, decisions, cautions, and agent adaptations.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered inventory of the nine public pages fetched for this package.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Two invented revisions showing how the rules change the result.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Fill-in brief, piece structure, and optional editorial handoff.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail review criteria and common failure repairs.\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 shapiro-writing-well",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill shapiro-writing-well",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill shapiro-writing-well","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\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","参考文档",5542,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\u002Fchecklists\u002Freview-checklist.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"DERIVATION.json",2351,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\u002FDERIVATION.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Fworked-examples.md",6633,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\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",14500,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\u002Freferences\u002Fmethod.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsources.md",2387,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\u002Freferences\u002Fsources.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Foutput-template.md",4215,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fshapiro-writing-well\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",[],[]]