[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CFBGEW1FFKB334X5TCBNXY":3,"skill-same:01M7CFBGEW1FFKB334X5TCBNXY":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},"01M7CFBGEW1FFKB334X5TCBNXY","loomer-master-brief",null,"Build or audit a Meta ads strategy brief using Jon Loomer's eight public principles, with evidence-led campaign simplicity, creative diversification, tracking, attribution, and lead-quality decisions. Use for planning, troubleshooting, or reviewing Meta advertising.","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\u002Floomer-master-brief\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: loomer-master-brief\ndescription: \"Build or audit a Meta ads strategy brief using Jon Loomer's eight public principles, with evidence-led campaign simplicity, creative diversification, tracking, attribution, and lead-quality decisions. Use for planning, troubleshooting, or reviewing Meta advertising.\"\n---\n\n# Loomer Master Brief\n\nBased on Jon Loomer's public method. Not affiliated with or endorsed by Jon Loomer.\n\n## When to use\n\nUse this skill to create a practical Meta advertising brief, review an existing account, diagnose disappointing results, or decide whether a proposed change has enough evidence behind it. The deliverable connects a business outcome to the performance goal, campaign structure, creative plan, measurement approach, and next decision. It should explain why each exception earns its place.\n\nThe method favors consolidated budgets, algorithmic delivery, genuinely different ads, and decisions based on meaningful aggregate results. It also recognizes that inexpensive leads, clicks, or attributed conversions may have little business value. It supplies a reasoning framework rather than a universal campaign recipe or a promise of performance.\n\nUse the public-source record to establish provenance. The free Master Brief is a July 2026 snapshot; this package does not reproduce the paid, maintained member resource. Verify changing feature availability in the actual account before specifying implementation. Preserve the user's business constraints and requested scope. Producing a recommendation does not itself authorize publishing ads, changing account settings, or spending money.\n\n## Procedure\n\n1. **Frame the assignment.** Read the intake guidance in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Identify the business outcome, offer, geography, budget, economics, sales cycle, and whether this is a launch or an audit. Record unavailable inputs as unknowns instead of inventing account history or customer behavior.\n\n2. **Establish the method and its date.** Read the provenance section in [references\u002Fmethod.md](references\u002Fmethod.md) and check [references\u002Fsources.md](references\u002Fsources.md). Distinguish the eight-principle article from the thematic Master Brief. Attribute the underlying approach to Loomer and label this package's worksheets and calculations as implementation aids.\n\n3. **Choose what delivery should pursue.** Apply principle P4 and the goal-selection guidance in [references\u002Fmethod.md](references\u002Fmethod.md). Separate the business outcome from the platform's requested action. Explain why purchases, purchase value, leads, or a deeper quality event fit the available signal, and how success will be measured beyond inexpensive activity.\n\n4. **Validate the measurement foundation.** Follow the tracking and attribution guidance in [references\u002Fmethod.md](references\u002Fmethod.md). Check event timing, browser and server coverage, deduplication, CRM feedback, and reporting definitions. If the data cannot support a performance conclusion, state the measurement repair needed before optimization.\n\n5. **Build the simplest viable structure.** Apply P1 and P3 in [references\u002Fmethod.md](references\u002Fmethod.md). Start with consolidated funding for the primary goal, then justify necessary separations for business goals, products, locations, or genuine constraints. Estimate event volume per funded unit and explain the cost of fragmentation.\n\n6. **Audit every departure from the baseline.** Use P2, P5, and the exception rules in [references\u002Fmethod.md](references\u002Fmethod.md). For each restriction, extra ad set, placement change, bid control, or enhancement choice, record the observed problem and supporting evidence. Distinguish enforceable controls from audience suggestions and reporting segments.\n\n7. **Resolve quality and remarketing questions.** Use the specialized branches in [references\u002Fmethod.md](references\u002Fmethod.md). Check downstream lead value, follow-up, and natural warm-audience delivery. Consider value rules only when the advertiser has relevant information Meta lacks and a material delivery problem exists. Never reuse another account's bid percentages as defaults.\n\n8. **Develop differentiated creative.** Apply P6 and the creative guidance in [references\u002Fmethod.md](references\u002Fmethod.md). Connect personas, pains, solutions, desired feelings, proof, offers, and calls to action. Start with a feasible batch and distinguish conceptual diversity from minor visual edits. Use [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) to calibrate the reasoning.\n\n9. **Define evaluation and diagnosis.** Apply P7 and P8 in [references\u002Fmethod.md](references\u002Fmethod.md). Set the aggregate evaluation unit, reporting windows, quality measures, and attribution views. Diagnose attention, conversion, then attribution problems. Record uncertainty when sparse results or sales-cycle delays prevent a reliable decision.\n\n10. **Write the decision brief.** Fill [templates\u002Foutput-template.md](templates\u002Foutput-template.md), including the evidence for each proposed change, alternatives, expected outcome, and review condition. Explain hold, repair, revise creative, test, or scale decisions in business terms. Avoid presenting a low-spend asset's average CPA as proof it deserves more budget.\n\n11. **Review and deliver.** Run [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md). Correct failed items, cite method-based claims, and keep account facts separate from hypotheses. Deliver the brief with concrete next actions and unresolved questions that affect implementation. Do not obscure missing evidence with confident numerical predictions.\n\n## Files in this skill\n\n- [SLUG.txt](SLUG.txt): Package identifier for naming and indexing.\n- [SKILL.md](SKILL.md): Entry point, usage boundaries, and procedure.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Eight principles, decision branches, exceptions, and evidence discipline.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered public sources, fetch provenance, and contributions.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Invented weak drafts and improved briefs with rule explanations.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Deliverable fields with completion guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail quality review and fixes for recurring mistakes.\n","# Loomer Master Brief\n\nBased on Jon Loomer's public method. Not affiliated with or endorsed by Jon Loomer.\n\n## When to use\n\nUse this skill to create a practical Meta advertising brief, review an existing account, diagnose disappointing results, or decide whether a proposed change has enough evidence behind it. The deliverable connects a business outcome to the performance goal, campaign structure, creative plan, measurement approach, and next decision. It should explain why each exception earns its place.\n\nThe method favors consolidated budgets, algorithmic delivery, genuinely different ads, and decisions based on meaningful aggregate results. It also recognizes that inexpensive leads, clicks, or attributed conversions may have little business value. It supplies a reasoning framework rather than a universal campaign recipe or a promise of performance.\n\nUse the public-source record to establish provenance. The free Master Brief is a July 2026 snapshot; this package does not reproduce the paid, maintained member resource. Verify changing feature availability in the actual account before specifying implementation. Preserve the user's business constraints and requested scope. Producing a recommendation does not itself authorize publishing ads, changing account settings, or spending money.\n\n## Procedure\n\n1. **Frame the assignment.** Read the intake guidance in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Identify the business outcome, offer, geography, budget, economics, sales cycle, and whether this is a launch or an audit. Record unavailable inputs as unknowns instead of inventing account history or customer behavior.\n\n2. **Establish the method and its date.** Read the provenance section in [references\u002Fmethod.md](references\u002Fmethod.md) and check [references\u002Fsources.md](references\u002Fsources.md). Distinguish the eight-principle article from the thematic Master Brief. Attribute the underlying approach to Loomer and label this package's worksheets and calculations as implementation aids.\n\n3. **Choose what delivery should pursue.** Apply principle P4 and the goal-selection guidance in [references\u002Fmethod.md](references\u002Fmethod.md). Separate the business outcome from the platform's requested action. Explain why purchases, purchase value, leads, or a deeper quality event fit the available signal, and how success will be measured beyond inexpensive activity.\n\n4. **Validate the measurement foundation.** Follow the tracking and attribution guidance in [references\u002Fmethod.md](references\u002Fmethod.md). Check event timing, browser and server coverage, deduplication, CRM feedback, and reporting definitions. If the data cannot support a performance conclusion, state the measurement repair needed before optimization.\n\n5. **Build the simplest viable structure.** Apply P1 and P3 in [references\u002Fmethod.md](references\u002Fmethod.md). Start with consolidated funding for the primary goal, then justify necessary separations for business goals, products, locations, or genuine constraints. Estimate event volume per funded unit and explain the cost of fragmentation.\n\n6. **Audit every departure from the baseline.** Use P2, P5, and the exception rules in [references\u002Fmethod.md](references\u002Fmethod.md). For each restriction, extra ad set, placement change, bid control, or enhancement choice, record the observed problem and supporting evidence. Distinguish enforceable controls from audience suggestions and reporting segments.\n\n7. **Resolve quality and remarketing questions.** Use the specialized branches in [references\u002Fmethod.md](references\u002Fmethod.md). Check downstream lead value, follow-up, and natural warm-audience delivery. Consider value rules only when the advertiser has relevant information Meta lacks and a material delivery problem exists. Never reuse another account's bid percentages as defaults.\n\n8. **Develop differentiated creative.** Apply P6 and the creative guidance in [references\u002Fmethod.md](references\u002Fmethod.md). Connect personas, pains, solutions, desired feelings, proof, offers, and calls to action. Start with a feasible batch and distinguish conceptual diversity from minor visual edits. Use [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) to calibrate the reasoning.\n\n9. **Define evaluation and diagnosis.** Apply P7 and P8 in [references\u002Fmethod.md](references\u002Fmethod.md). Set the aggregate evaluation unit, reporting windows, quality measures, and attribution views. Diagnose attention, conversion, then attribution problems. Record uncertainty when sparse results or sales-cycle delays prevent a reliable decision.\n\n10. **Write the decision brief.** Fill [templates\u002Foutput-template.md](templates\u002Foutput-template.md), including the evidence for each proposed change, alternatives, expected outcome, and review condition. Explain hold, repair, revise creative, test, or scale decisions in business terms. Avoid presenting a low-spend asset's average CPA as proof it deserves more budget.\n\n11. **Review and deliver.** Run [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md). Correct failed items, cite method-based claims, and keep account facts separate from hypotheses. Deliver the brief with concrete next actions and unresolved questions that affect implementation. Do not obscure missing evidence with confident numerical predictions.\n\n## Files in this skill\n\n- [SLUG.txt](SLUG.txt): Package identifier for naming and indexing.\n- [SKILL.md](SKILL.md): Entry point, usage boundaries, and procedure.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Eight principles, decision branches, exceptions, and evidence discipline.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered public sources, fetch provenance, and contributions.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Invented weak drafts and improved briefs with rule explanations.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Deliverable fields with completion guidance.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail quality review and fixes for recurring mistakes.\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 loomer-master-brief",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill loomer-master-brief",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill loomer-master-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\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","参考文档",5223,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\u002Fchecklists\u002Freview-checklist.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"DERIVATION.json",3583,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\u002FDERIVATION.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Fworked-examples.md",8169,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\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",14869,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\u002Freferences\u002Fmethod.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsources.md",6097,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\u002Freferences\u002Fsources.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Foutput-template.md",5736,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Floomer-master-brief\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",[],[]]