[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R8ZDTYMFYR8FMPTMKGQPAQ":3,"skill-same:01M6R8ZDTYMFYR8FMPTMKGQPAQ":78},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6R8ZDTYMFYR8FMPTMKGQPAQ","asb-needs-stack",null,"Builds a customer Needs Stack — the ladder in which every need is a means to the end one level up (buy infrastructure → set up a WordPress site → have a personal website → get a book deal). Anchors the level the user's product satisfies, phrased as the customer's own goal in the customer's own words, then walks downward (the steps the product makes obsolete) and upward (what the customer really wants), crystallizing every level — specific wording, a true means-to-an-end link, named real-world occupants — before moving on. Records the stack in NEEDS-STACK.md with the user's level marked and each level's positioning role: what you do, promise, reference as aspiration, or brag about obviating. Load when the user asks what their customer really wants, what level their product operates at, who their real alternatives (not just competitors) are, or to 'build our needs stack.' Do NOT load to rewrite marketing copy from a finished stack — that is a separate positioning task that consumes this file.","Nairon-AI\u002Fagentic-starter-pack","Nairon-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260662138?v=4","01M6R8PZ1Y8CSQGFN61VACZGTH","Nairon AI","01M6R8PZ6184VR3BA88YZFBC3N",4,"MIT","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fbusiness\u002Fasb-needs-stack\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"asb needs stack","stack","world","when","at","which","you","end","get","positioning","promise","personal","goal","up","competitors","marketing","SET","website","product","customer","2026-11-10 10:12:30",false,"---\nname: asb-needs-stack\ndescription: \"Builds a customer Needs Stack — the ladder in which every need is a means to the end one level up (buy infrastructure → set up a WordPress site → have a personal website → get a book deal). Anchors the level the user's product satisfies, phrased as the customer's own goal in the customer's own words, then walks downward (the steps the product makes obsolete) and upward (what the customer really wants), crystallizing every level — specific wording, a true means-to-an-end link, named real-world occupants — before moving on. Records the stack in NEEDS-STACK.md with the user's level marked and each level's positioning role: what you do, promise, reference as aspiration, or brag about obviating. Load when the user asks what their customer really wants, what level their product operates at, who their real alternatives (not just competitors) are, or to 'build our needs stack.' Do NOT load to rewrite marketing copy from a finished stack — that is a separate positioning task that consumes this file.\"\n---\n\n# The Needs Stack: What Your Customer Actually Wants\n\nNobody's life ambition is to buy your product. Whatever your product\ndoes, it is a means to an end — and that end is a means to a higher\nend, and so on, up a ladder this method calls the **Needs Stack**.\nMapping the stack tells you who your real alternatives are (not just\nyour competitors), what outcome you may honestly promise, which steps\nyou should brag about making obsolete, and where your company's higher\npurpose lives. This skill builds that map with the user: anchor the\nlevel the product satisfies, walk down, then walk up — one level per\nexchange, each level crystallized before the next.\n\n## The mental model\n\n### A worked stack\n\nCharlie signs up for AWS to buy cloud infrastructure — servers,\nstorage, network. But \"buy infrastructure\" isn't what Charlie wants;\nit's an obstacle in the way of the WordPress website Charlie actually\nwants. And a WordPress site isn't the end either: it's a means to a\npersonal website for content and self-promotion. Which is itself a\nmeans: Charlie really wants a book deal, and the way to get one is to\nhave built an online following first. Written as a stack, top ends\nabove bottom means:\n\n- ★ Get a book deal.\n- → Have a personal website for content and self-promotion.\n- → Set up a WordPress website.\n- → Buy infrastructure.\n\nEvery level is real, every level has vendors serving it (Substack and\nsocial media at the following level; Wix, Squarespace, and Webflow at\nthe website level; WP Engine at the WordPress level; AWS, GCP, and\nAzure at the infrastructure level), and every level is *only a means*\nto the one above it.\n\n### The obviation rule\n\nA product that satisfies a need in the stack makes the products below\nit **obsolete** for that customer. Charlie never wanted infrastructure\nand still doesn't — so a company that delivers a working WordPress\nsite without the customer ever touching infrastructure wins Charlie,\nand the infrastructure vendors never even see Charlie. Charlie\ndisappears from that market. This is why the stack matters\ncompetitively: the vendors one level above you are not your\n*competitors* (they don't sell what you sell) but they are your\n**alternatives** — they can remove your customer from your market\nentirely. Ask a vendor who their competitors are and they'll name the\nother vendors at their own level; the stack reveals the alternatives\nabove, which is where disruption actually comes from.\n\n### The trade-off between high and low\n\nHigher levels offer the shortest path to the goal; lower levels offer\nflexibility and customization. An all-in-one product gets the customer\nto the outcome fastest but constrains them to its fixed menu; building\nfrom lower-level parts takes longer but bends to any requirement. This\nis why a level being \"obviated\" doesn't kill the vendors below it —\ncustomers who need the flexibility still buy low. It's also each\nlevel's standing defense against the level above: name what your\ncustomer keeps by buying at your level.\n\n### The trap: stopping at your own level\n\nEveryone wants to stop mapping when they reach the level they operate\non — \"we sell websites, and customers want websites, done.\" There is\nalways another level up, and the levels above yours are exactly the\nones that determine what you may promise and who can obviate you.\nKeep climbing until the stack tops out.\n\n### Where the stack tops out: purpose levels\n\nHigh enough, the needs stop being product-shaped: recognition, ego,\nlegacy, self-actualization. No product satisfies these directly (some\nwould argue meditation and therapy come closest). Record one or two of\nthese **purpose levels** and mark them: they are not promises and not\nmarkets, but they are the raw material for the company's higher\npurpose — the true stories worth telling on the website and\ncelebrating internally when a customer actually gets there.\n\n### What each level is for downstream\n\nPositioning consumes the stack by role, relative to the user's level:\n\n- **Your level** — *what you do.* Features live here. A customer whose\n  current thought (and search query) is at this level wants specs and\n  features, not lifestyle benefits — a builder searching for a 5\u002F16\"\n  socket wrench does not want to be told the light \"helps you see.\"\n- **One level up** — *what you promise.* The outcome you claim as the\n  consequence of what you do. This is the strongest honest benefit.\n- **Levels far above** — *aspirations.* Never promise them; show the\n  part you play in them, with testimonials and how-to content proving\n  it's possible.\n- **Levels above, held by others** — *counter-positioning.* The\n  vendors there are obviating you; answer with what the customer keeps\n  by buying at your level (flexibility, customization, uniqueness).\n- **Levels below** — *advancements.* Brag that you make these steps\n  obsolete: no time spent, nothing to manage, nothing to learn.\n\nThe stack also picks your most strategic metric — measure whether\ncustomers succeed **one level up** from you, not just whether your\nproduct delivered (a store-builder can deliver a perfect store whose\nowner sells nothing and churns; the vendor that measures its\ncustomers' sales sees the truth) — and it warns against the tempting\npivot: moving your product up a level is usually a different product,\na different business, and a smaller market. Partial climbs (vertical\nsub-brands, add-on features, content that helps with the next level)\nare the realistic versions.\n\n### Whose stack it is\n\nA stack belongs to one kind of customer. Different customers climbing\nthrough the same product diverge at higher levels — an agency, a\nhobbyist, and an e-commerce store may all \"set up a website\" for\nentirely different ends. Build the stack for the *ideal* customer —\nthe one the business most wants to win. And when a sale has two heads\n(the buyer and the user are different people, common in business\nsoftware), each may need their own stack; both can decide the sale.\n\n### Vocabulary\n\n- **Level (N1, N2, …)** — one need, phrased as the customer's goal;\n  numbered in the order settled (numbers are frozen; position in the\n  file carries stack order).\n- **Your level** — the need the user's product satisfies; the anchor.\n- **Obviation** — a higher-level product making lower levels\n  irrelevant for that customer.\n- **Occupants** — who serves a level today: vendors, products, DIY\n  methods, agencies. Real names.\n- **Purpose level** — a top level no product satisfies directly;\n  material for meaning, not marketing promises.\n\n## The elicitor's posture\n\n### Be clear, not clever\n\nWrite to be understood, not admired. The work here wrestles with hard\nconcepts, and clever metaphors, wordplay, or cute turns of phrase make\nthem harder to grasp, not easier. Say plainly what you mean. If a\nsentence reads more clearly without a flourish, cut the flourish. State\nthe actual point rather than gesturing wittily at it.\n\n### Restate references; never cite a bare token\n\nWhen you mention a numbered or lettered item to the user — K4, W2,\nO17, H3, and the like — add a few plain words on what it actually is\n(\"K4 — the owner whose career rides on the site\"). A bare token is\nunreadable to a human who saw it defined hours or days ago: the tag is\nfor traceability, the gloss is for comprehension. Keep the tag for\naccuracy; always add the gloss.\n\n### One level per exchange, crystallized before moving\n\nThe walk is strictly paced: anchor the user's own level first, then\none level per exchange — downward until the levels stop mattering,\nthen upward until the purpose levels. A level is settled only when it\npasses the crystallization gate below; do not sketch the whole stack\nup front and refine later (if the user asks for exactly that, decline\nin substance: a ladder of unvetted levels is a brainstorm, not a map,\nand each level is built on the one before it — offer instead to\npropose the candidates at every level so the user mostly confirms and\ncorrects), and do not accept \"and above that, obviously, success\" as\na level. Propose candidate phrasings AND candidate occupants yourself\nfreely — the user knows their customer; the outside perspective helps\nfind the honest phrasing and remember who else sells at a level — but\nthe user confirms every level. When you name occupants and alternatives,\nconfirm who serves a level today using current results from your search\ntools; do not rely on internal (training) knowledge, which is stale and\nnames dead products or misses new ones. A level heard out of order (\"they want\nto win cases\" volunteered during the anchor) is parked in chat and\ntakes its number only when the walk reaches it and it settles.\n\n### The crystallization gate\n\nEvery level must pass four tests before the walk moves on:\n\n1. **Customer's words, customer's goal.** Phrased as a need the\n   customer would state — \"set up a WordPress website,\" not the\n   vendor's category (\"managed hosting\") and not a generic gesture\n   (\"grow their business\" — whose growth, through what?). Generic\n   words (success, efficiency, value, scale) get pressed into the\n   specific picture the customer actually holds.\n2. **A true means-to-an-end link.** The test: if this level were\n   handed to the customer fully satisfied, would they happily never\n   touch the level below? If they would still want the lower level for\n   its own sake, the link is wrong — the levels aren't stacked, or a\n   middle level is missing.\n3. **Named occupants.** Who serves this level today — vendors,\n   products, methods, agencies, by name. Occupants are what make a\n   level operational: they are the alternatives and the\n   counter-positioning targets. A mid-stack level with no nameable\n   occupant is suspect — usually two levels blurred together or a\n   level invented to flatter the product. (Purpose levels are the\n   exception: mark them instead.)\n4. **A real step, not a reword.** Distinct from its neighbors: if\n   satisfying one level automatically satisfies the other with\n   nothing left over, they are one level, merged.\n\nTwo scope notes. When *descending*, the means-to-end test points\nupward — it verifies the already-settled level above the new one\n(handed that fulfilled, would they skip this new lower step?); a\nbrand-new bottom level's own downward link isn't testable until the\nnext descent, and that's fine. And **purpose levels** are exempt from\ntest 3 only: tests 2 and 4 still apply, and test 1 applies in\npersonalized form — \"recognition\" and \"legacy\" are recorded as *this*\ncustomer's specific version of them (\"be known in town for her beer,\"\n\"promotion to VP, and evenings back\"), never as bare abstractions.\n\n### The user owns the customer; the gate owns the wording\n\nWhether their customer really climbs this way, what the customer\nactually wants, which persona is ideal — the user's knowledge, and\ntheir call stands after one honest press. But the gate is not theirs\nto waive: a level that fails a test is not recorded in the stack in\nany form, however insisted; there is always a compliant phrasing of\nwhat the user actually means, and finding it is the work. When the\nuser defends a phrasing by appeal to market knowledge (\"that IS what\nthe customer wants — the board approved this language\"), separate\nthe two out loud: the *want* is theirs and stands; the *words* are\nthe gate's, and vendor phrasing never enters the file. Tone stays\nwarm; the bar does not move. One escape hatch: if, after the trap is\nexplained once, the user still declines to climb further, don't\nstall the whole exercise — finalize with an explicit caveat in the\npreamble (\"stack incomplete — stopped below the purpose levels at\nthe user's request\") so the file is honest about what it is.\n\n### The closing press\n\nBefore finalizing, attack the whole stack once. If a devil's-advocate\ninterrogation skill is installed in the environment (for example\n*Rude Q&A* \u002F `asb-rude-qa`, from the same author as this method),\ninvoke it against the draft stack with this brief: *attack this needs\nstack — find every level phrased in vendor language or generic words;\nevery means-to-end link that fails the \"handed to them fulfilled,\nwould they skip the level below?\" test; every level with no real\noccupants that isn't a purpose level; every adjacent pair that is one\nlevel reworded; and check the top — did they stop climbing at their\nown level or one polite step above it?* If no such skill is available,\nrun exactly that interrogation yourself, visibly, before finalizing.\n\n## How to use this skill\n\n### Phase A — Ingest and anchor\n\n**Optional inputs, worth asking for once.** The stack is anchored to a\nspecific customer, so ask (in the same breath: paths to the files,\nand the company\u002Fproduct name for the file title) whether the user\nhas: an ideal-customer definition (a file defining the customer by\nbehavioral and circumstantial markers — often with numbered\nkeystones, deal-breakers, and inciting events); customer-interview\nfindings; a keystones chart. Read whatever exists — the ideal\ncustomer named there is whose stack this is, interview quotes are\ngold for phrasing levels in the customer's words, and keystones\nsharpen the \"why your level still wins\" lines. If none exist, say\nplainly that the stack will be sharper with them (and that an\nideal-customer method from this skill's author produces the\ndefinition — `asb-carol-define` is the final step, if installed),\nthen proceed anyway: press for a one-or-two-line sketch of the ideal\ncustomer — who they are by circumstance and behavior, not\ndemographics; the press repeats until the sketch is genuinely sharp,\nsince a vague anchor bends every level above it — and record it in\nthe preamble as the anchor, caveated as unvetted. Record absences\ntoo (\"no ideal-customer definition, interviews, or keystones chart\nexist\"), so a resumed session doesn't re-ask.\n\n**Resume check.** If a `NEEDS-STACK.md` already exists at the target\nlocation, read it first: an in-progress header means resume — pick up\nexactly where the pointer says, don't re-litigate settled levels. A\nfinalized file means ask whether to revise or to build a second\npersona's stack. When the user says \"continue\" but no file is found\nwhere expected, ask where it lives before starting fresh.\n\n**Anchor your level.** Ask what the product does, then convert it: the\nanchor level is the customer's need, not the product's category. \"We\nsell managed Postgres hosting\" anchors as \"have a production database\nthat runs itself.\" Run the crystallization gate on it — including\noccupants: the user plus their direct competitors. This is N1. Create\n`NEEDS-STACK.md` as soon as N1 settles — in the same directory as any\ninput file; with no input file, ask where the method's files should\nlive before creating it (default: the current directory) — with the\nin-progress header.\n\n### Phase B — Walk down\n\nOne level per exchange: what would the customer have to do or buy\n*below* this level if your product didn't handle it? Each level down\ngets the full gate, plus its role line: an advancement — a step you\nmake obsolete, and should say so. Stop descending when the next level\ndown no longer matters to the purchase — the test: would any buyer\nweigh it when choosing among the occupants at your level, and would\nyour positioning ever mention it? Both no = stop (below \"buy\ninfrastructure\" lies \"have electricity\" — real, but nobody's\npositioning mentions it). One or two levels down is typical. Note the\nstop and its reasoning in the header pointer while in progress, so a\nresumed session knows the descent is complete.\n\n### Phase C — Walk up\n\nOne level per exchange, starting from the anchor: *is that the\ncustomer's life ambition? Means to what end?* Each level up gets the\nfull gate, plus its role lines: the first level up is **the promise**;\nlevels above that are aspirations; every occupied level above notes\nwhy your level still wins for your ideal customer (the flexibility,\ncustomization, or uniqueness they keep). Keep climbing past the\ncomfortable stopping point — the trap is stopping at or just above\nyour own level. The walk ends when the levels stop being\nproduct-shaped: record one or two purpose levels, marked as such.\n\nWhere the market genuinely diverges at some height — different ideal\ncustomers climbing to different ends — don't average them into one\nvague level; note the divergence and offer a second stack for the\nother persona (Phase D).\n\n**Record to the file as you go.** Write each level into the file at\nits stack position the moment it settles — settle order and stack\norder differ, so this is placement, not appending to the bottom —\nand keep the header pointer current: anchored, walked down through\n(and whether the descent is complete), walked up through, currently\ncrystallizing. When a level is in flight — candidates proposed,\nnothing settled — put the candidate phrasings in the pointer too:\nthe not-recorded-in-any-form rule protects the stack body, not the\nresume pointer, and a resumed session shouldn't lose work the user\nalready reacted to. The file is the memory, not the chat. If files\naren't accessible, re-emit the full draft in a fenced block every\nlevel or two.\n\n### Phase D — Sweep and close\n\n- **The closing press** (delegated or self-run, per the posture). It\n  covers every stack in the file, and it audits — it does not reopen\n  settled pacing: fixes it surfaces are patched inline with the\n  user's confirmation, under the frozen numbers.\n- **Role check.** Every level carries its role annotation; each\n  stack's anchor and promise level are unambiguous.\n- **Second stack?** If the sale has two heads (buyer vs. user) or a\n  second ideal persona surfaced, offer to walk that stack now —\n  numbering continues (no reuse), in its own section, with the full\n  protocol (its own anchor marked YOU ARE HERE, its own down-check,\n  its own promise level, the same gates). If the user defers it,\n  record the divergence in Next steps (\"the economic buyer may climb\n  a different stack; numbering would continue from N\u003Cnext>\") so it\n  isn't lost.\n- Finalize: remove the in-progress header, write the \"Uses beyond\n  positioning\" and \"Next steps\" sections (they are finalization\n  content, not built during the walk), and close with the handoff:\n  the stack's levels are the skeleton of positioning — what you say\n  at each level and what you promise one level up. If a positioning\n  skill from this method's author is installed (for example\n  *Positioning* \u002F `asb-positioning`), name it: \"when you're ready,\n  run `asb-positioning` on your marketing copy with this file.\"\n\n### The file structure\n\n```markdown\n# Needs Stack — \u003Ccompany \u002F product>\n\n> ⚠️ IN PROGRESS — anchored at N1; walked down: \u003CN-numbers, and\n> whether the descent is complete, with the stop reasoning>; walked\n> up: \u003CN-numbers settled so far>; currently crystallizing: \u003Cthe level\n> in flight — include any candidate phrasings proposed but not yet\n> settled>. \u003CIf the walk is done and the sweep isn't: \"walk complete;\n> closing press \u002F role check \u002F finalization remaining.\"> \u003CIf a second\n> stack is in flight, say which stack and where.> If you are\n> resuming, continue there. (This note is removed at finalization.)\n\n\u003CTwo or three lines: whose stack this is — the ideal-customer\ndefinition file it anchors to, or the confirmed customer sketch — and\nthe product. Levels are numbered in settle order; position in the\nlist below carries the stack order, top ends before bottom means.>\n\n## The stack\n\n**N5.** ★ \u003Cpurpose level> — *purpose level: no product satisfies\n    this directly; material for higher-purpose stories, never for\n    promises.*\n\n**N4.** → \u003Caspiration level>\n    Occupants: \u003Cwho serves this level, by name>\n    Role: aspiration — show the part you play; never promise it.\n    Why your level still wins for your ideal customer: \u003Cwhat they keep>.\n\n**N3.** → \u003Cone level up>\n    Occupants: \u003C…>\n    Role: **the promise** — the outcome claimed as a consequence of N1.\n    Why your level still wins for your ideal customer: \u003Cwhat they keep>.\n\n**N1.** → \u003Cyour level>  ← YOU ARE HERE\n    Occupants: you; \u003Cdirect competitors, by name>.\n    Role: **what you do** — features live here; meet searchers where\n    they are.\n\n**N2.** → \u003Cone level down>\n    Occupants: \u003C…>\n    Role: advancement — a step you make obsolete; brag about it.\n\n## \u003CSecond persona> stack (only if the sale has more than one head)\n\n\u003CSame structure; numbering continues from the first stack.>\n\n## Uses beyond positioning\n\n\u003CTwo or three lines: measure success one level up from what you\ndeliver; the purpose levels are where the company's higher purpose\nlives; moving your product up a level is a different business —\npartial climbs (verticals, add-ons, helpful content) are the\nrealistic versions.>\n\n## Next steps\n\n\u003CTwo or three sentences of prose: the stack feeds positioning — talk\nfeatures at your level, promise the level above, reference\naspirations without promising, brag about the levels you obviate —\nand the method continues by converting your actual marketing copy\nlevel by level. Name the positioning skill if installed.>\n```\n\nN-numbers are stable once written — downstream positioning statements\ncite them. Never renumber; a level inserted later takes the next\nfresh number and its place in the list. Stability binds the number\nand the level's meaning, not its letter-for-letter wording: while the\nfile is in progress, wording may be refined under a frozen number\nwith the user's confirmation (the closing press often does this);\nafter finalization, changes append rather than rewrite.\n\n## Refusal conditions\n\n- **No idea who the customer is.** A stack without a customer is a\n  guess. Press for at least a sharp sketch (circumstance and\n  behavior); recommend the ideal-customer work; caveat the file if\n  proceeding on a sketch.\n- **Vendor-language or generic levels, however insisted.** \"Leverage\n  our platform\" and \"achieve success\" never enter the file; the\n  customer's actual goal, in words the customer would say, always\n  exists and is the only recordable form.\n- **Stopping at the user's own level.** The levels above are the\n  point — the walk continues past comfort until purpose levels.\n- **A stack averaged across divergent customers.** When personas\n  genuinely split, one blurred stack describes nobody; build per\n  persona.\n- **Skipping crystallization to sketch the whole ladder at once.** A\n  stack of uncrystallized levels is a brainstorm, not a map; the gate\n  runs per level, in order.\n- **Writing the positioning itself.** Converting copy, statements,\n  and pitches against this stack is the next step of the method, not\n  this one; this file ends at roles and the handoff.\n","# The Needs Stack: What Your Customer Actually Wants\n\nNobody's life ambition is to buy your product. Whatever your product\ndoes, it is a means to an end — and that end is a means to a higher\nend, and so on, up a ladder this method calls the **Needs Stack**.\nMapping the stack tells you who your real alternatives are (not just\nyour competitors), what outcome you may honestly promise, which steps\nyou should brag about making obsolete, and where your company's higher\npurpose lives. This skill builds that map with the user: anchor the\nlevel the product satisfies, walk down, then walk up — one level per\nexchange, each level crystallized before the next.\n\n## The mental model\n\n### A worked stack\n\nCharlie signs up for AWS to buy cloud infrastructure — servers,\nstorage, network. But \"buy infrastructure\" isn't what Charlie wants;\nit's an obstacle in the way of the WordPress website Charlie actually\nwants. And a WordPress site isn't the end either: it's a means to a\npersonal website for content and self-promotion. Which is itself a\nmeans: Charlie really wants a book deal, and the way to get one is to\nhave built an online following first. Written as a stack, top ends\nabove bottom means:\n\n- ★ Get a book deal.\n- → Have a personal website for content and self-promotion.\n- → Set up a WordPress website.\n- → Buy infrastructure.\n\nEvery level is real, every level has vendors serving it (Substack and\nsocial media at the following level; Wix, Squarespace, and Webflow at\nthe website level; WP Engine at the WordPress level; AWS, GCP, and\nAzure at the infrastructure level), and every level is *only a means*\nto the one above it.\n\n### The obviation rule\n\nA product that satisfies a need in the stack makes the products below\nit **obsolete** for that customer. Charlie never wanted infrastructure\nand still doesn't — so a company that delivers a working WordPress\nsite without the customer ever touching infrastructure wins Charlie,\nand the infrastructure vendors never even see Charlie. Charlie\ndisappears from that market. This is why the stack matters\ncompetitively: the vendors one level above you are not your\n*competitors* (they don't sell what you sell) but they are your\n**alternatives** — they can remove your customer from your market\nentirely. Ask a vendor who their competitors are and they'll name the\nother vendors at their own level; the stack reveals the alternatives\nabove, which is where disruption actually comes from.\n\n### The trade-off between high and low\n\nHigher levels offer the shortest path to the goal; lower levels offer\nflexibility and customization. An all-in-one product gets the customer\nto the outcome fastest but constrains them to its fixed menu; building\nfrom lower-level parts takes longer but bends to any requirement. This\nis why a level being \"obviated\" doesn't kill the vendors below it —\ncustomers who need the flexibility still buy low. It's also each\nlevel's standing defense against the level above: name what your\ncustomer keeps by buying at your level.\n\n### The trap: stopping at your own level\n\nEveryone wants to stop mapping when they reach the level they operate\non — \"we sell websites, and customers want websites, done.\" There is\nalways another level up, and the levels above yours are exactly the\nones that determine what you may promise and who can obviate you.\nKeep climbing until the stack tops out.\n\n### Where the stack tops out: purpose levels\n\nHigh enough, the needs stop being product-shaped: recognition, ego,\nlegacy, self-actualization. No product satisfies these directly (some\nwould argue meditation and therapy come closest). Record one or two of\nthese **purpose levels** and mark them: they are not promises and not\nmarkets, but they are the raw material for the company's higher\npurpose — the true stories worth telling on the website and\ncelebrating internally when a customer actually gets there.\n\n### What each level is for downstream\n\nPositioning consumes the stack by role, relative to the user's level:\n\n- **Your level** — *what you do.* Features live here. A customer whose\n  current thought (and search query) is at this level wants specs and\n  features, not lifestyle benefits — a builder searching for a 5\u002F16\"\n  socket wrench does not want to be told the light \"helps you see.\"\n- **One level up** — *what you promise.* The outcome you claim as the\n  consequence of what you do. This is the strongest honest benefit.\n- **Levels far above** — *aspirations.* Never promise them; show the\n  part you play in them, with testimonials and how-to content proving\n  it's possible.\n- **Levels above, held by others** — *counter-positioning.* The\n  vendors there are obviating you; answer with what the customer keeps\n  by buying at your level (flexibility, customization, uniqueness).\n- **Levels below** — *advancements.* Brag that you make these steps\n  obsolete: no time spent, nothing to manage, nothing to learn.\n\nThe stack also picks your most strategic metric — measure whether\ncustomers succeed **one level up** from you, not just whether your\nproduct delivered (a store-builder can deliver a perfect store whose\nowner sells nothing and churns; the vendor that measures its\ncustomers' sales sees the truth) — and it warns against the tempting\npivot: moving your product up a level is usually a different product,\na different business, and a smaller market. Partial climbs (vertical\nsub-brands, add-on features, content that helps with the next level)\nare the realistic versions.\n\n### Whose stack it is\n\nA stack belongs to one kind of customer. Different customers climbing\nthrough the same product diverge at higher levels — an agency, a\nhobbyist, and an e-commerce store may all \"set up a website\" for\nentirely different ends. Build the stack for the *ideal* customer —\nthe one the business most wants to win. And when a sale has two heads\n(the buyer and the user are different people, common in business\nsoftware), each may need their own stack; both can decide the sale.\n\n### Vocabulary\n\n- **Level (N1, N2, …)** — one need, phrased as the customer's goal;\n  numbered in the order settled (numbers are frozen; position in the\n  file carries stack order).\n- **Your level** — the need the user's product satisfies; the anchor.\n- **Obviation** — a higher-level product making lower levels\n  irrelevant for that customer.\n- **Occupants** — who serves a level today: vendors, products, DIY\n  methods, agencies. Real names.\n- **Purpose level** — a top level no product satisfies directly;\n  material for meaning, not marketing promises.\n\n## The elicitor's posture\n\n### Be clear, not clever\n\nWrite to be understood, not admired. The work here wrestles with hard\nconcepts, and clever metaphors, wordplay, or cute turns of phrase make\nthem harder to grasp, not easier. Say plainly what you mean. If a\nsentence reads more clearly without a flourish, cut the flourish. State\nthe actual point rather than gesturing wittily at it.\n\n### Restate references; never cite a bare token\n\nWhen you mention a numbered or lettered item to the user — K4, W2,\nO17, H3, and the like — add a few plain words on what it actually is\n(\"K4 — the owner whose career rides on the site\"). A bare token is\nunreadable to a human who saw it defined hours or days ago: the tag is\nfor traceability, the gloss is for comprehension. Keep the tag for\naccuracy; always add the gloss.\n\n### One level per exchange, crystallized before moving\n\nThe walk is strictly paced: anchor the user's own level first, then\none level per exchange — downward until the levels stop mattering,\nthen upward until the purpose levels. A level is settled only when it\npasses the crystallization gate below; do not sketch the whole stack\nup front and refine later (if the user asks for exactly that, decline\nin substance: a ladder of unvetted levels is a brainstorm, not a map,\nand each level is built on the one before it — offer instead to\npropose the candidates at every level so the user mostly confirms and\ncorrects), and do not accept \"and above that, obviously, success\" as\na level. Propose candidate phrasings AND candidate occupants yourself\nfreely — the user knows their customer; the outside perspective helps\nfind the honest phrasing and remember who else sells at a level — but\nthe user confirms every level. When you name occupants and alternatives,\nconfirm who serves a level today using current results from your search\ntools; do not rely on internal (training) knowledge, which is stale and\nnames dead products or misses new ones. A level heard out of order (\"they want\nto win cases\" volunteered during the anchor) is parked in chat and\ntakes its number only when the walk reaches it and it settles.\n\n### The crystallization gate\n\nEvery level must pass four tests before the walk moves on:\n\n1. **Customer's words, customer's goal.** Phrased as a need the\n   customer would state — \"set up a WordPress website,\" not the\n   vendor's category (\"managed hosting\") and not a generic gesture\n   (\"grow their business\" — whose growth, through what?). Generic\n   words (success, efficiency, value, scale) get pressed into the\n   specific picture the customer actually holds.\n2. **A true means-to-an-end link.** The test: if this level were\n   handed to the customer fully satisfied, would they happily never\n   touch the level below? If they would still want the lower level for\n   its own sake, the link is wrong — the levels aren't stacked, or a\n   middle level is missing.\n3. **Named occupants.** Who serves this level today — vendors,\n   products, methods, agencies, by name. Occupants are what make a\n   level operational: they are the alternatives and the\n   counter-positioning targets. A mid-stack level with no nameable\n   occupant is suspect — usually two levels blurred together or a\n   level invented to flatter the product. (Purpose levels are the\n   exception: mark them instead.)\n4. **A real step, not a reword.** Distinct from its neighbors: if\n   satisfying one level automatically satisfies the other with\n   nothing left over, they are one level, merged.\n\nTwo scope notes. When *descending*, the means-to-end test points\nupward — it verifies the already-settled level above the new one\n(handed that fulfilled, would they skip this new lower step?); a\nbrand-new bottom level's own downward link isn't testable until the\nnext descent, and that's fine. And **purpose levels** are exempt from\ntest 3 only: tests 2 and 4 still apply, and test 1 applies in\npersonalized form — \"recognition\" and \"legacy\" are recorded as *this*\ncustomer's specific version of them (\"be known in town for her beer,\"\n\"promotion to VP, and evenings back\"), never as bare abstractions.\n\n### The user owns the customer; the gate owns the wording\n\nWhether their customer really climbs this way, what the customer\nactually wants, which persona is ideal — the user's knowledge, and\ntheir call stands after one honest press. But the gate is not theirs\nto waive: a level that fails a test is not recorded in the stack in\nany form, however insisted; there is always a compliant phrasing of\nwhat the user actually means, and finding it is the work. When the\nuser defends a phrasing by appeal to market knowledge (\"that IS what\nthe customer wants — the board approved this language\"), separate\nthe two out loud: the *want* is theirs and stands; the *words* are\nthe gate's, and vendor phrasing never enters the file. Tone stays\nwarm; the bar does not move. One escape hatch: if, after the trap is\nexplained once, the user still declines to climb further, don't\nstall the whole exercise — finalize with an explicit caveat in the\npreamble (\"stack incomplete — stopped below the purpose levels at\nthe user's request\") so the file is honest about what it is.\n\n### The closing press\n\nBefore finalizing, attack the whole stack once. If a devil's-advocate\ninterrogation skill is installed in the environment (for example\n*Rude Q&A* \u002F `asb-rude-qa`, from the same author as this method),\ninvoke it against the draft stack with this brief: *attack this needs\nstack — find every level phrased in vendor language or generic words;\nevery means-to-end link that fails the \"handed to them fulfilled,\nwould they skip the level below?\" test; every level with no real\noccupants that isn't a purpose level; every adjacent pair that is one\nlevel reworded; and check the top — did they stop climbing at their\nown level or one polite step above it?* If no such skill is available,\nrun exactly that interrogation yourself, visibly, before finalizing.\n\n## How to use this skill\n\n### Phase A — Ingest and anchor\n\n**Optional inputs, worth asking for once.** The stack is anchored to a\nspecific customer, so ask (in the same breath: paths to the files,\nand the company\u002Fproduct name for the file title) whether the user\nhas: an ideal-customer definition (a file defining the customer by\nbehavioral and circumstantial markers — often with numbered\nkeystones, deal-breakers, and inciting events); customer-interview\nfindings; a keystones chart. Read whatever exists — the ideal\ncustomer named there is whose stack this is, interview quotes are\ngold for phrasing levels in the customer's words, and keystones\nsharpen the \"why your level still wins\" lines. If none exist, say\nplainly that the stack will be sharper with them (and that an\nideal-customer method from this skill's author produces the\ndefinition — `asb-carol-define` is the final step, if installed),\nthen proceed anyway: press for a one-or-two-line sketch of the ideal\ncustomer — who they are by circumstance and behavior, not\ndemographics; the press repeats until the sketch is genuinely sharp,\nsince a vague anchor bends every level above it — and record it in\nthe preamble as the anchor, caveated as unvetted. Record absences\ntoo (\"no ideal-customer definition, interviews, or keystones chart\nexist\"), so a resumed session doesn't re-ask.\n\n**Resume check.** If a `NEEDS-STACK.md` already exists at the target\nlocation, read it first: an in-progress header means resume — pick up\nexactly where the pointer says, don't re-litigate settled levels. A\nfinalized file means ask whether to revise or to build a second\npersona's stack. When the user says \"continue\" but no file is found\nwhere expected, ask where it lives before starting fresh.\n\n**Anchor your level.** Ask what the product does, then convert it: the\nanchor level is the customer's need, not the product's category. \"We\nsell managed Postgres hosting\" anchors as \"have a production database\nthat runs itself.\" Run the crystallization gate on it — including\noccupants: the user plus their direct competitors. This is N1. Create\n`NEEDS-STACK.md` as soon as N1 settles — in the same directory as any\ninput file; with no input file, ask where the method's files should\nlive before creating it (default: the current directory) — with the\nin-progress header.\n\n### Phase B — Walk down\n\nOne level per exchange: what would the customer have to do or buy\n*below* this level if your product didn't handle it? Each level down\ngets the full gate, plus its role line: an advancement — a step you\nmake obsolete, and should say so. Stop descending when the next level\ndown no longer matters to the purchase — the test: would any buyer\nweigh it when choosing among the occupants at your level, and would\nyour positioning ever mention it? Both no = stop (below \"buy\ninfrastructure\" lies \"have electricity\" — real, but nobody's\npositioning mentions it). One or two levels down is typical. Note the\nstop and its reasoning in the header pointer while in progress, so a\nresumed session knows the descent is complete.\n\n### Phase C — Walk up\n\nOne level per exchange, starting from the anchor: *is that the\ncustomer's life ambition? Means to what end?* Each level up gets the\nfull gate, plus its role lines: the first level up is **the promise**;\nlevels above that are aspirations; every occupied level above notes\nwhy your level still wins for your ideal customer (the flexibility,\ncustomization, or uniqueness they keep). Keep climbing past the\ncomfortable stopping point — the trap is stopping at or just above\nyour own level. The walk ends when the levels stop being\nproduct-shaped: record one or two purpose levels, marked as such.\n\nWhere the market genuinely diverges at some height — different ideal\ncustomers climbing to different ends — don't average them into one\nvague level; note the divergence and offer a second stack for the\nother persona (Phase D).\n\n**Record to the file as you go.** Write each level into the file at\nits stack position the moment it settles — settle order and stack\norder differ, so this is placement, not appending to the bottom —\nand keep the header pointer current: anchored, walked down through\n(and whether the descent is complete), walked up through, currently\ncrystallizing. When a level is in flight — candidates proposed,\nnothing settled — put the candidate phrasings in the pointer too:\nthe not-recorded-in-any-form rule protects the stack body, not the\nresume pointer, and a resumed session shouldn't lose work the user\nalready reacted to. The file is the memory, not the chat. If files\naren't accessible, re-emit the full draft in a fenced block every\nlevel or two.\n\n### Phase D — Sweep and close\n\n- **The closing press** (delegated or self-run, per the posture). It\n  covers every stack in the file, and it audits — it does not reopen\n  settled pacing: fixes it surfaces are patched inline with the\n  user's confirmation, under the frozen numbers.\n- **Role check.** Every level carries its role annotation; each\n  stack's anchor and promise level are unambiguous.\n- **Second stack?** If the sale has two heads (buyer vs. user) or a\n  second ideal persona surfaced, offer to walk that stack now —\n  numbering continues (no reuse), in its own section, with the full\n  protocol (its own anchor marked YOU ARE HERE, its own down-check,\n  its own promise level, the same gates). If the user defers it,\n  record the divergence in Next steps (\"the economic buyer may climb\n  a different stack; numbering would continue from N\u003Cnext>\") so it\n  isn't lost.\n- Finalize: remove the in-progress header, write the \"Uses beyond\n  positioning\" and \"Next steps\" sections (they are finalization\n  content, not built during the walk), and close with the handoff:\n  the stack's levels are the skeleton of positioning — what you say\n  at each level and what you promise one level up. If a positioning\n  skill from this method's author is installed (for example\n  *Positioning* \u002F `asb-positioning`), name it: \"when you're ready,\n  run `asb-positioning` on your marketing copy with this file.\"\n\n### The file structure\n\n```markdown\n# Needs Stack — \u003Ccompany \u002F product>\n\n> ⚠️ IN PROGRESS — anchored at N1; walked down: \u003CN-numbers, and\n> whether the descent is complete, with the stop reasoning>; walked\n> up: \u003CN-numbers settled so far>; currently crystallizing: \u003Cthe level\n> in flight — include any candidate phrasings proposed but not yet\n> settled>. \u003CIf the walk is done and the sweep isn't: \"walk complete;\n> closing press \u002F role check \u002F finalization remaining.\"> \u003CIf a second\n> stack is in flight, say which stack and where.> If you are\n> resuming, continue there. (This note is removed at finalization.)\n\n\u003CTwo or three lines: whose stack this is — the ideal-customer\ndefinition file it anchors to, or the confirmed customer sketch — and\nthe product. Levels are numbered in settle order; position in the\nlist below carries the stack order, top ends before bottom means.>\n\n## The stack\n\n**N5.** ★ \u003Cpurpose level> — *purpose level: no product satisfies\n    this directly; material for higher-purpose stories, never for\n    promises.*\n\n**N4.** → \u003Caspiration level>\n    Occupants: \u003Cwho serves this level, by name>\n    Role: aspiration — show the part you play; never promise it.\n    Why your level still wins for your ideal customer: \u003Cwhat they keep>.\n\n**N3.** → \u003Cone level up>\n    Occupants: \u003C…>\n    Role: **the promise** — the outcome claimed as a consequence of N1.\n    Why your level still wins for your ideal customer: \u003Cwhat they keep>.\n\n**N1.** → \u003Cyour level>  ← YOU ARE HERE\n    Occupants: you; \u003Cdirect competitors, by name>.\n    Role: **what you do** — features live here; meet searchers where\n    they are.\n\n**N2.** → \u003Cone level down>\n    Occupants: \u003C…>\n    Role: advancement — a step you make obsolete; brag about it.\n\n## \u003CSecond persona> stack (only if the sale has more than one head)\n\n\u003CSame structure; numbering continues from the first stack.>\n\n## Uses beyond positioning\n\n\u003CTwo or three lines: measure success one level up from what you\ndeliver; the purpose levels are where the company's higher purpose\nlives; moving your product up a level is a different business —\npartial climbs (verticals, add-ons, helpful content) are the\nrealistic versions.>\n\n## Next steps\n\n\u003CTwo or three sentences of prose: the stack feeds positioning — talk\nfeatures at your level, promise the level above, reference\naspirations without promising, brag about the levels you obviate —\nand the method continues by converting your actual marketing copy\nlevel by level. Name the positioning skill if installed.>\n```\n\nN-numbers are stable once written — downstream positioning statements\ncite them. Never renumber; a level inserted later takes the next\nfresh number and its place in the list. Stability binds the number\nand the level's meaning, not its letter-for-letter wording: while the\nfile is in progress, wording may be refined under a frozen number\nwith the user's confirmation (the closing press often does this);\nafter finalization, changes append rather than rewrite.\n\n## Refusal conditions\n\n- **No idea who the customer is.** A stack without a customer is a\n  guess. Press for at least a sharp sketch (circumstance and\n  behavior); recommend the ideal-customer work; caveat the file if\n  proceeding on a sketch.\n- **Vendor-language or generic levels, however insisted.** \"Leverage\n  our platform\" and \"achieve success\" never enter the file; the\n  customer's actual goal, in words the customer would say, always\n  exists and is the only recordable form.\n- **Stopping at the user's own level.** The levels above are the\n  point — the walk continues past comfort until purpose levels.\n- **A stack averaged across divergent customers.** When personas\n  genuinely split, one blurred stack describes nobody; build per\n  persona.\n- **Skipping crystallization to sketch the whole ladder at once.** A\n  stack of uncrystallized levels is a brainstorm, not a map; the gate\n  runs per level, in order.\n- **Writing the positioning itself.** Converting copy, statements,\n  and pitches against this stack is the next step of the method, not\n  this one; this file ends at roles and the handoff.\n",{"name":5,"description":7},"main","c9d0c408715983e993b2f9ebffdbfa7f10153bcb","business\u002Fasb-needs-stack",0,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack","https:\u002F\u002Fgithub.com\u002FNairon-AI","https:\u002F\u002Fwww.naironai.com\u002F","Building the future of Work","2026-09-20 17:40:05",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Nairon-AI\u002Fagentic-starter-pack --skill asb-needs-stack",{"tool":59,"command":60},"bunx","bunx skills add Nairon-AI\u002Fagentic-starter-pack --skill asb-needs-stack",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Nairon-AI\u002Fagentic-starter-pack --skill asb-needs-stack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fbusiness\u002Fasb-needs-stack\u002FSKILL.md",true,[67,72],{"path":68,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"LICENSE","许可证",18657,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fbusiness\u002Fasb-needs-stack\u002FLICENSE",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"NOTICE.md","REFERENCE","参考文档",444,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fbusiness\u002Fasb-needs-stack\u002FNOTICE.md",[79,114,136,156,176,198],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":95,"publishedAt":39},"01M6RBCG630Y8X99XWR9Q4GYNY","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-shape\u002FSKILL.md",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,23,113,22],"writing","writing shape","shape","notes","help","file","markdown","format","session","use","take","draft","article","material","it","about","quotes","candidate",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":122,"publishedAt":39},"01M6RBCCCB1KMF01P5SYGFWBSW","writing-fragments","Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions \"fragments\", \"ideate\", or \"raw material\" for writing.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-fragments\u002FSKILL.md",[120,121],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[96,123,124,125,126,127,104,105,128,129,130,108,131,109,132,133,134,135,22],"writing fragments","grilling","ideate","develop","user","document","structure","ideas","as","sharp","claims","for","single",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":144,"publishedAt":39},"01M6RBC8V7NHHKMTAZB4BPXVYQ","writing-beats","Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-beats\u002FSKILL.md",[142,143],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[96,145,146,147,105,148,149,98,150,151,152,108,26,131,153,109,154,155,134,22],"writing beats","choose","write","assemble","only","journey","next","options","style","narrative","argument",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":164,"publishedAt":39},"01M6RBC58SG5Y5SC4ZV4ZNEFHC","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fstop-slop\u002FSKILL.md",[162,163],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[165,166,167,96,168,169,170,171,172,105,173,174,175,134,22],"stop","stop slop","slop","content","https","text","editing","remove","prose","patterns","drafts",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":184,"publishedAt":39},"01M6RBBJTTCJ7KZCP16G9JDFZH","humanizer","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fhumanizer\u002FSKILL.md",[182,183],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[178,96,185,186,170,187,147,188,189,172,190,191,174,192,193,194,195,196,197,22],"code","em dash","read","edit","generated","guide","opencode","three","human","make","wikipedia","vague","dash",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":39},"01M6RBBEQKJ5HRH8AV9J85QB1T","feedback","Prepare, deliver, and debrief timely interpersonal feedback using a question-first coaching flow, observable behavior, owned experience, and concrete impact. Use when drafting feedback, coaching managers, rehearsing a feedback conversation, praising specific behavior, or reviewing whether feedback landed.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Ffeedback\u002FSKILL.md",[],[200,205,206,207,208,209,105,210,211,212,213,214,22,215],"prepare","flow","first","question","behavior","conversation","coaching","debrief","impact","managers","deliver"]