[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAMQ75Z1116T495AR0NAWN":3,"skill-same:01M7FAMQ75Z1116T495AR0NAWN":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FAMQ75Z1116T495AR0NAWN","account-based-marketing",null,"Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Faccount-based-marketing\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: account-based-marketing\ndescription: Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.\n---\n\n# Account-based marketing\n\nAccount-based marketing inverts the usual model: instead of generating leads and finding out which\naccounts they came from, you choose the accounts and work them. It is a good fit for a narrow set\nof businesses and an expensive mistake for the rest.\n\n## Qualify the model before adopting it\n\nIt works when deal sizes are large enough to justify per-account effort, the addressable market is\nsmall enough to enumerate, buying groups have several people, and sales cycles are long enough for\nsustained effort to compound.\n\n**It does not work when the deal size cannot carry the cost**, when the market is too large to name,\nor when marketing and sales will not actually coordinate. That last one is the usual failure: the\ntooling gets bought, the account list gets built, and the program becomes a more expensive way to\nrun the same campaigns.\n\nRun the arithmetic first. Total program cost divided by the number of accounts, against expected\ndeal value and a realistic win rate, tells you the tier structure you can afford — or that you\ncannot afford this at all.\n\n## Build the list from fit and evidence, then hold it still\n\nStart from the accounts that already look like your best customers — not by revenue but by why they\nbought and whether they stayed. Add observable signals: hiring, technology in use, funding,\nregulatory pressure, a change in leadership.\n\n**Then commit.** A list that churns quarterly cannot compound, and compounding is the only reason\nthis model beats broad demand generation. Agree the list with sales and get their explicit\nacceptance, because a list sales does not believe in is a list sales will not work.\n\n## Map the buying group, not the contact\n\nPurchases at this size are made by several people with different concerns: the person with the\nproblem, the person with the budget, the person who will operate it, and whoever can veto on\nsecurity, legal or procurement grounds.\n\nReaching one champion and mistaking that for account coverage is the most common structural error.\nTrack how many roles you have reached within each account, and treat single-threading as a status\nthat needs fixing rather than a warning to note.\n\n## Tier the effort, because one-to-one does not scale\n\n- **One-to-one** for a small number of the highest-value accounts: genuinely bespoke research and\n  content, executive engagement.\n- **One-to-few** for clusters that share an industry or a problem: shared narrative, light\n  customization per account.\n- **One-to-many** for the rest of the named list: programmatic personalization at segment level.\n\nBeing honest about which tier an account is in prevents the common outcome where everything is\nnominally one-to-one and nothing is actually customized.\n\n## Coordinate, or the account experiences three campaigns\n\nThe account should see one coherent effort. That requires marketing and sales working the same\nplan, with agreed timing, agreed messaging, and an agreed sequence of who reaches out when.\n\nSet up a shared cadence between the two teams for the tiered accounts and hold it. Without that\nmeeting the program degrades into marketing sending things and sales prospecting separately, which\nis the status quo with extra software.\n\n## Measure account progression, not lead volume\n\nLead counts are the wrong instrument. What matters is how accounts move: coverage of the buying\ngroup, engagement across it rather than by one person, movement into and through pipeline, and\neventually win rate and deal size against non-target accounts.\n\nExpect the timeline to be long. Judging an account-based program on a quarter is judging it before\nany of its mechanism has had time to work, and canceling it there is the most common way the\ninvestment is wasted entirely.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Adopt the model without checking whether the deal size carries the per-account cost.\n- Run a target list sales has not explicitly accepted.\n- Treat one engaged champion as account coverage.\n- Judge the program on lead volume, or on a single quarter.\n","# Account-based marketing\n\nAccount-based marketing inverts the usual model: instead of generating leads and finding out which\naccounts they came from, you choose the accounts and work them. It is a good fit for a narrow set\nof businesses and an expensive mistake for the rest.\n\n## Qualify the model before adopting it\n\nIt works when deal sizes are large enough to justify per-account effort, the addressable market is\nsmall enough to enumerate, buying groups have several people, and sales cycles are long enough for\nsustained effort to compound.\n\n**It does not work when the deal size cannot carry the cost**, when the market is too large to name,\nor when marketing and sales will not actually coordinate. That last one is the usual failure: the\ntooling gets bought, the account list gets built, and the program becomes a more expensive way to\nrun the same campaigns.\n\nRun the arithmetic first. Total program cost divided by the number of accounts, against expected\ndeal value and a realistic win rate, tells you the tier structure you can afford — or that you\ncannot afford this at all.\n\n## Build the list from fit and evidence, then hold it still\n\nStart from the accounts that already look like your best customers — not by revenue but by why they\nbought and whether they stayed. Add observable signals: hiring, technology in use, funding,\nregulatory pressure, a change in leadership.\n\n**Then commit.** A list that churns quarterly cannot compound, and compounding is the only reason\nthis model beats broad demand generation. Agree the list with sales and get their explicit\nacceptance, because a list sales does not believe in is a list sales will not work.\n\n## Map the buying group, not the contact\n\nPurchases at this size are made by several people with different concerns: the person with the\nproblem, the person with the budget, the person who will operate it, and whoever can veto on\nsecurity, legal or procurement grounds.\n\nReaching one champion and mistaking that for account coverage is the most common structural error.\nTrack how many roles you have reached within each account, and treat single-threading as a status\nthat needs fixing rather than a warning to note.\n\n## Tier the effort, because one-to-one does not scale\n\n- **One-to-one** for a small number of the highest-value accounts: genuinely bespoke research and\n  content, executive engagement.\n- **One-to-few** for clusters that share an industry or a problem: shared narrative, light\n  customization per account.\n- **One-to-many** for the rest of the named list: programmatic personalization at segment level.\n\nBeing honest about which tier an account is in prevents the common outcome where everything is\nnominally one-to-one and nothing is actually customized.\n\n## Coordinate, or the account experiences three campaigns\n\nThe account should see one coherent effort. That requires marketing and sales working the same\nplan, with agreed timing, agreed messaging, and an agreed sequence of who reaches out when.\n\nSet up a shared cadence between the two teams for the tiered accounts and hold it. Without that\nmeeting the program degrades into marketing sending things and sales prospecting separately, which\nis the status quo with extra software.\n\n## Measure account progression, not lead volume\n\nLead counts are the wrong instrument. What matters is how accounts move: coverage of the buying\ngroup, engagement across it rather than by one person, movement into and through pipeline, and\neventually win rate and deal size against non-target accounts.\n\nExpect the timeline to be long. Judging an account-based program on a quarter is judging it before\nany of its mechanism has had time to work, and canceling it there is the most common way the\ninvestment is wasted entirely.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Adopt the model without checking whether the deal size carries the per-account cost.\n- Run a target list sales has not explicitly accepted.\n- Treat one engaged champion as account coverage.\n- Judge the program on lead volume, or on a single quarter.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Faccount-based-marketing",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill account-based-marketing",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill account-based-marketing",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill account-based-marketing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Faccount-based-marketing\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",1063,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Faccount-based-marketing\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]