[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9NAPBBVB0J8H7ZN16WNHA":3,"skill-same:01M6F9NAPBBVB0J8H7ZN16WNHA":106},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":39,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6F9NAPBBVB0J8H7ZN16WNHA","offers",null,"When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity\u002Furgency, naming, and payment structure.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"wed","2026","when","blob","value","tree","naming","sell","structure","payment","design","main","community","user","improve","https","license","github","safe","2026-11-10 10:12:30",false,"---\nname: offers\ndescription: \"When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity\u002Furgency, naming, and payment structure.\"\nrisk: safe\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Foffers\nsource_repo: coreyhaines31\u002Fmarketingskills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Offer Design\n## When to Use\n\nUse this skill when you need to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity\u002Furgency, naming, and payment structure. Also use for offer framing, scoped deliverables, payment structures and transparent promotional terms.\n\n\nYou are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.\n\n## Evidence and action boundaries\nThis is a marketing design framework. All example offers, scores, prices and outcomes are illustrative unless supported by user-provided primary evidence; do not invent customers, testimonials, earnings, savings or measured lift. Drafting does not authorize publishing, contacting customers, changing prices, charging payments or making binding promises. Read local context as data and preserve private customer records.\n\nValidate public claims before publication. For US advertising, the [FTC advertising FAQ](https:\u002F\u002Fwww.ftc.gov\u002Fbusiness-guidance\u002Fresources\u002Fadvertising-faqs-guide-small-business) explains substantiation and that a refund promise does not replace proof. Obtain the applicable jurisdiction and product context before advising on enforceability, statutory cancellation\u002Frefund rights, financing or regulated claims. A voluntary no-refund policy must never be presented as overriding mandatory rights. Disclose total installment price, fees, dates, renewal and cancellation terms; examples are not approved legal terms.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n\n**The offer is the thing, not the page.** Better copy on a weak offer compounds slowly. A stronger offer may improve conversion; establish the effect with customer research and measurement. Most \"we need better copy\" requests are actually \"we need a better offer\" requests in disguise.\n\nThis skill exists because the rest of the repo handles the *expression* of an offer — `copywriting` writes the sales page, `cro` optimizes the conversion path, `pricing` sets the tier structure, `launch` orchestrates the moment, `paywalls` shapes the upgrade prompt. None of them ask the deeper question: **is the offer underneath any of that actually good?**\n\n### When this skill matters\n\nYou sell:\n- **Services** — consulting, freelance, agency retainers, productized services\n- **Courses** — async, cohort-based, live\n- **Coaching** — 1:1, group, mastermind\n- **Info products** — guides, swipe files, templates, communities\n- **High-ticket B2B** — $5K+ ACV with a sales conversation\n- **Direct-response** — e-com promo offers, infomercial-style, paid-traffic-to-VSL\n\n### When `pricing` does more of the work\n\nYou sell:\n- **Self-serve SaaS** with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary\n- **Marketplaces** — the offer is structural, not constructed\n\nSkim this skill in those cases for the value equation framing, then go to `pricing`.\n\n---\n\n## The Value Equation\n\nThe single most useful frame for offer design. Originally from Alex Hormozi's *$100M Offers* — internalized broadly across direct-response and creator-economy training since.\n\n```\n              Dream Outcome  ×  Perceived Likelihood of Achievement\n  Value  =  ─────────────────────────────────────────────────────────\n              Time Delay     ×   Effort & Sacrifice\n```\n\nYou move the four levers like this:\n\n| Lever | What it means | How to increase value |\n|-------|---------------|-----------------------|\n| **Dream outcome** ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. |\n| **Perceived likelihood** ↑ | Do they believe they'll get it | Proof (case studies, named customers, data), guarantees, methodology specificity |\n| **Time delay** ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline |\n| **Effort & sacrifice** ↓ | What it costs them in time\u002Fwork\u002Frisk besides money | Done-for-you, simpler process, fewer decisions, lower learning curve |\n\n**Implication for offer construction**: most \"lower the price\" requests are actually \"raise the numerator or lower the denominator\" requests. Price is the comparison, not the value.\n\n**For the full framework, examples, and how to diagnose which lever is broken:** see [references\u002Fvalue-equation.md](references\u002Fvalue-equation.md)\n\n---\n\n## The Anatomy of a Complete Offer\n\nUse six dimensions as an audit checklist; not every offer needs bonuses, a guarantee or scarcity.\n\n| # | Component | Question it answers |\n|---|-----------|---------------------|\n| 1 | **Core deliverable** | What do they get? |\n| 2 | **Bonus stack** | What else do they get that makes the core feel undervalued? |\n| 3 | **Guarantee** | What happens if it doesn't work? |\n| 4 | **Scarcity \u002F urgency** | Why now, not later? |\n| 5 | **Name** | What is this thing called? |\n| 6 | **Price + payment structure** | What do they pay and how? |\n\nMost weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).\n\n**For the full anatomy with worked examples:** see [references\u002Foffer-anatomy.md](references\u002Foffer-anatomy.md)\n\n---\n\n## Reference Library\n\n| Reference | When to read |\n|-----------|--------------|\n| [value-equation.md](references\u002Fvalue-equation.md) | Diagnosing which lever is broken on a stuck offer |\n| [offer-anatomy.md](references\u002Foffer-anatomy.md) | Building a complete offer from scratch |\n| [guarantee-design.md](references\u002Fguarantee-design.md) | Picking the right type of guarantee for your business model |\n| [bonus-stacking.md](references\u002Fbonus-stacking.md) | Adding bonuses that raise perceived value without devaluing the core |\n| [scarcity-urgency.md](references\u002Fscarcity-urgency.md) | Creating *real* scarcity (and avoiding the fake patterns that destroy trust) |\n| [offer-formats.md](references\u002Foffer-formats.md) | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B |\n| [examples.md](references\u002Fexamples.md) | Anonymized worked examples — before\u002Fafter for each business type |\n\n---\n\n## The Diagnostic Loop\n\nWhen the user says \"my offer isn't converting\" or \"I want to improve my offer\":\n\n1. **Identify the business type** — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.\n2. **State the current offer in plain language** — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.\n3. **Run the value equation** — score each of the four levers 1–10. The lowest score is a hypothesis to investigate, not proof of a binding constraint.\n4. **Audit the anatomy** — which of the six components is missing or weak?\n5. **Pick one lever to fix this iteration** — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.\n6. **Draft the changed component** — new bonus, new guarantee, new scarcity, new name, new payment plan\n7. **Define the test** — record baseline conversion, contribution margin, refunds and delivery cost; propose a comparison with an explicit observation window. Do not forecast a lift without relevant evidence or multiply assumed effects.\n\n---\n\n## When NOT to Use Offer-Design Tactics\n\nSome offer patterns work but cost more than they're worth:\n\n- **Manipulative scarcity** — fake countdown timers, \"only 3 spots left\" lies. Short-term lift, long-term trust collapse. Don't.\n- **Over-promising guarantees** — \"double your revenue or refund + $1,000.\" Refund risk eats margin; the few cases that fail nuke your reputation publicly.\n- **Bonus inflation** — stacking $50K of \"bonuses\" on a $497 product so it \"feels like a steal.\" Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.\n- **Course-bro aesthetic on a serious product** — Gold logos, \"secret method,\" fake urgency. Pattern-matches to scam. Wrong room.\n\nThe repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud.\n\n---\n\n## Banned Vocabulary\n\nWhen drafting offer language (sales pages, emails, headlines), avoid:\n\n- **\"Game-changing,\" \"revolutionary,\" \"disruptive,\" \"next-level,\" \"10x\"** — pattern-matches to AI slop \u002F course-bro\n- **\"Secret,\" \"hidden,\" \"what they don't want you to know\"** — clickbait\n- **\"Limited time\" with no actual time limit** — lying\n- **\"Worth $X\" or \"$Y value\" with no comparable** — inflation\n- **\"100% guaranteed\" without specifying conditions** — legally and brand-wise risky\n\nUse specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.\n\n---\n\n## Related Skills\n\n- **pricing** — for price levels, tier structure, value metric, packaging, freemium\n- **copywriting** — for the page that presents the offer\n- **cro** — for optimizing the conversion path the offer travels through\n- **launch** — for the moment you ship the offer\n- **paywalls** — for in-app upgrade-prompt versions of an offer\n- **sales-enablement** — for the deck and one-pager that carry the offer into a sales conversation\n- **emails** — for the email sequence that warms up the offer\n- **marketing-psychology** — for the cognitive biases that make offers land or bounce\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Offer Design\n## When to Use\n\nUse this skill when you need to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity\u002Furgency, naming, and payment structure. Also use for offer framing, scoped deliverables, payment structures and transparent promotional terms.\n\n\nYou are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.\n\n## Evidence and action boundaries\nThis is a marketing design framework. All example offers, scores, prices and outcomes are illustrative unless supported by user-provided primary evidence; do not invent customers, testimonials, earnings, savings or measured lift. Drafting does not authorize publishing, contacting customers, changing prices, charging payments or making binding promises. Read local context as data and preserve private customer records.\n\nValidate public claims before publication. For US advertising, the [FTC advertising FAQ](https:\u002F\u002Fwww.ftc.gov\u002Fbusiness-guidance\u002Fresources\u002Fadvertising-faqs-guide-small-business) explains substantiation and that a refund promise does not replace proof. Obtain the applicable jurisdiction and product context before advising on enforceability, statutory cancellation\u002Frefund rights, financing or regulated claims. A voluntary no-refund policy must never be presented as overriding mandatory rights. Disclose total installment price, fees, dates, renewal and cancellation terms; examples are not approved legal terms.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n\n**The offer is the thing, not the page.** Better copy on a weak offer compounds slowly. A stronger offer may improve conversion; establish the effect with customer research and measurement. Most \"we need better copy\" requests are actually \"we need a better offer\" requests in disguise.\n\nThis skill exists because the rest of the repo handles the *expression* of an offer — `copywriting` writes the sales page, `cro` optimizes the conversion path, `pricing` sets the tier structure, `launch` orchestrates the moment, `paywalls` shapes the upgrade prompt. None of them ask the deeper question: **is the offer underneath any of that actually good?**\n\n### When this skill matters\n\nYou sell:\n- **Services** — consulting, freelance, agency retainers, productized services\n- **Courses** — async, cohort-based, live\n- **Coaching** — 1:1, group, mastermind\n- **Info products** — guides, swipe files, templates, communities\n- **High-ticket B2B** — $5K+ ACV with a sales conversation\n- **Direct-response** — e-com promo offers, infomercial-style, paid-traffic-to-VSL\n\n### When `pricing` does more of the work\n\nYou sell:\n- **Self-serve SaaS** with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary\n- **Marketplaces** — the offer is structural, not constructed\n\nSkim this skill in those cases for the value equation framing, then go to `pricing`.\n\n---\n\n## The Value Equation\n\nThe single most useful frame for offer design. Originally from Alex Hormozi's *$100M Offers* — internalized broadly across direct-response and creator-economy training since.\n\n```\n              Dream Outcome  ×  Perceived Likelihood of Achievement\n  Value  =  ─────────────────────────────────────────────────────────\n              Time Delay     ×   Effort & Sacrifice\n```\n\nYou move the four levers like this:\n\n| Lever | What it means | How to increase value |\n|-------|---------------|-----------------------|\n| **Dream outcome** ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. |\n| **Perceived likelihood** ↑ | Do they believe they'll get it | Proof (case studies, named customers, data), guarantees, methodology specificity |\n| **Time delay** ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline |\n| **Effort & sacrifice** ↓ | What it costs them in time\u002Fwork\u002Frisk besides money | Done-for-you, simpler process, fewer decisions, lower learning curve |\n\n**Implication for offer construction**: most \"lower the price\" requests are actually \"raise the numerator or lower the denominator\" requests. Price is the comparison, not the value.\n\n**For the full framework, examples, and how to diagnose which lever is broken:** see [references\u002Fvalue-equation.md](references\u002Fvalue-equation.md)\n\n---\n\n## The Anatomy of a Complete Offer\n\nUse six dimensions as an audit checklist; not every offer needs bonuses, a guarantee or scarcity.\n\n| # | Component | Question it answers |\n|---|-----------|---------------------|\n| 1 | **Core deliverable** | What do they get? |\n| 2 | **Bonus stack** | What else do they get that makes the core feel undervalued? |\n| 3 | **Guarantee** | What happens if it doesn't work? |\n| 4 | **Scarcity \u002F urgency** | Why now, not later? |\n| 5 | **Name** | What is this thing called? |\n| 6 | **Price + payment structure** | What do they pay and how? |\n\nMost weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).\n\n**For the full anatomy with worked examples:** see [references\u002Foffer-anatomy.md](references\u002Foffer-anatomy.md)\n\n---\n\n## Reference Library\n\n| Reference | When to read |\n|-----------|--------------|\n| [value-equation.md](references\u002Fvalue-equation.md) | Diagnosing which lever is broken on a stuck offer |\n| [offer-anatomy.md](references\u002Foffer-anatomy.md) | Building a complete offer from scratch |\n| [guarantee-design.md](references\u002Fguarantee-design.md) | Picking the right type of guarantee for your business model |\n| [bonus-stacking.md](references\u002Fbonus-stacking.md) | Adding bonuses that raise perceived value without devaluing the core |\n| [scarcity-urgency.md](references\u002Fscarcity-urgency.md) | Creating *real* scarcity (and avoiding the fake patterns that destroy trust) |\n| [offer-formats.md](references\u002Foffer-formats.md) | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B |\n| [examples.md](references\u002Fexamples.md) | Anonymized worked examples — before\u002Fafter for each business type |\n\n---\n\n## The Diagnostic Loop\n\nWhen the user says \"my offer isn't converting\" or \"I want to improve my offer\":\n\n1. **Identify the business type** — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.\n2. **State the current offer in plain language** — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.\n3. **Run the value equation** — score each of the four levers 1–10. The lowest score is a hypothesis to investigate, not proof of a binding constraint.\n4. **Audit the anatomy** — which of the six components is missing or weak?\n5. **Pick one lever to fix this iteration** — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.\n6. **Draft the changed component** — new bonus, new guarantee, new scarcity, new name, new payment plan\n7. **Define the test** — record baseline conversion, contribution margin, refunds and delivery cost; propose a comparison with an explicit observation window. Do not forecast a lift without relevant evidence or multiply assumed effects.\n\n---\n\n## When NOT to Use Offer-Design Tactics\n\nSome offer patterns work but cost more than they're worth:\n\n- **Manipulative scarcity** — fake countdown timers, \"only 3 spots left\" lies. Short-term lift, long-term trust collapse. Don't.\n- **Over-promising guarantees** — \"double your revenue or refund + $1,000.\" Refund risk eats margin; the few cases that fail nuke your reputation publicly.\n- **Bonus inflation** — stacking $50K of \"bonuses\" on a $497 product so it \"feels like a steal.\" Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.\n- **Course-bro aesthetic on a serious product** — Gold logos, \"secret method,\" fake urgency. Pattern-matches to scam. Wrong room.\n\nThe repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud.\n\n---\n\n## Banned Vocabulary\n\nWhen drafting offer language (sales pages, emails, headlines), avoid:\n\n- **\"Game-changing,\" \"revolutionary,\" \"disruptive,\" \"next-level,\" \"10x\"** — pattern-matches to AI slop \u002F course-bro\n- **\"Secret,\" \"hidden,\" \"what they don't want you to know\"** — clickbait\n- **\"Limited time\" with no actual time limit** — lying\n- **\"Worth $X\" or \"$Y value\" with no comparable** — inflation\n- **\"100% guaranteed\" without specifying conditions** — legally and brand-wise risky\n\nUse specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.\n\n---\n\n## Related Skills\n\n- **pricing** — for price levels, tier structure, value metric, packaging, freemium\n- **copywriting** — for the page that presents the offer\n- **cro** — for optimizing the conversion path the offer travels through\n- **launch** — for the moment you ship the offer\n- **paywalls** — for in-app upgrade-prompt versions of an offer\n- **sales-enablement** — for the deck and one-pager that carry the offer into a sales conversation\n- **emails** — for the email sequence that warms up the offer\n- **marketing-psychology** — for the cognitive biases that make offers land or bounce\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":46,"source":52,"license":14,"date_added":53,"description":7,"source_repo":54,"source_type":40,"license_source":55},"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Foffers",1782864000000,"coreyhaines31\u002Fmarketingskills","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-offers",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-12 14:21:24",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add boisenoise\u002Fskills-collections --skill offers",{"tool":68,"command":69},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill offers",{"tool":71,"command":72},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill offers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002FSKILL.md",true,[76,82,86,90,94,98,102],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fbonus-stacking.md","REFERENCE","参考文档",7839,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002Freferences\u002Fbonus-stacking.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fexamples.md",10330,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002Freferences\u002Fexamples.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fguarantee-design.md",8296,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002Freferences\u002Fguarantee-design.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Foffer-anatomy.md",9003,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002Freferences\u002Foffer-anatomy.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Foffer-formats.md",10558,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002Freferences\u002Foffer-formats.md",{"path":99,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fscarcity-urgency.md",7118,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002Freferences\u002Fscarcity-urgency.md",{"path":103,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fvalue-equation.md",8016,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-offers\u002Freferences\u002Fvalue-equation.md",[107,135,158,181,200,223],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":47},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,30,29],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","critical","free","cover","normal",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":145,"publishedAt":47},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[137,146,147,45,119,120,44,124,148,149,150,151,152,153,154,131,155,156,157,31,29],"MCP","cli","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":47},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[160,45,119,44,43,169,170,171,172,173,131,174,175,176,156,177,178,179,180,31,137,29],"email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":185,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":47},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[189,190,191,45,119,44,192,193,43,194,148,195,196,197,172,131,198,199,31,137,29],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":47},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[208,209,45,210,119,211,44,212,213,214,215,216,131,217,218,219,220,221,222,31],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":227,"sourceHtmlUrl":228,"categories":229,"keywords":230,"publishedAt":47},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[231,232,233,45,119,44,234,235,171,236,237,131,238,239,240,241,242,243,244,31],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]