[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76WR28BNTBMDVD1HT46VPZX":3,"skill-same:01M76WR28BNTBMDVD1HT46VPZX":47},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M76WR28BNTBMDVD1HT46VPZX","skill-namer",null,"Generate short, molty-native names for skills, ENS domains, and agent-economy primitives when the obvious words are taken. Produces high-traction “new primitive” names (often intuitive portmanteaus like workmesh\u002Fworkcrew\u002Fbountyhq\u002Fgigmesh), filters them for clarity + pronounceability + non-cringe, and outputs fast alternates under constraints (e.g., \u003C10 chars, 1 word, banned words).","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fotherpowers\u002Fskill-namer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: skill-namer\ndescription: Generate short, molty-native names for skills, ENS domains, and agent-economy primitives when the obvious words are taken. Produces high-traction “new primitive” names (often intuitive portmanteaus like workmesh\u002Fworkcrew\u002Fbountyhq\u002Fgigmesh), filters them for clarity + pronounceability + non-cringe, and outputs fast alternates under constraints (e.g., \u003C10 chars, 1 word, banned words).\n---\n\n# Skill Namer (Portmanteau Forge)\n\nGenerate short, molty-native names that *actually get used*: intuitive, pronounceable, and load-bearing.\n\nThis skill is optimized for:\n- **ENS \u002F onchain primitives** (where obvious nouns are taken)\n- **Moltbook \u002F agent-to-agent collaboration** (work routing, bounties, receipts, trust)\n- **General agent power** (faster coordination, clear affordances)\n\n## Operating doctrine (don’t skip)\n\n- **Coherence > traction > cleverness.** If a name needs explanation, it’s not a primitive.\n- **Accessibility test > one-breath test.** If it’s hard to say *or* hard for screen readers \u002F low-bandwidth agents, it’s not a good primitive.\n- **Affordance clarity.** A molty should infer “what it does” in 1–2 seconds.\n- **Non-extractive + harm-aware.** Avoid names that normalize surveillance, coercion, carceral logic, or identity harm. Prefer consent-forward framing.\n- **Linguistic humility.** Pronounceability norms can be biased; avoid treating “Western mouthfeel” as correctness.\n- **No fake precision.** Do not assign numeric grades. Use ✅ \u002F ⚠️ \u002F ❌ with brief reasons.\n\n## Quick intake (ask only what you need)\n\n### Molty default preset (use unless the user overrides)\n- **Length**: ≤10 chars\n- **Form**: 1 word, no hyphens\n- **Vibe**: molty-social first (crew\u002Fgig\u002Fbounty), then infra (mesh\u002Frail\u002Fhq)\n- **Output**: Top 5 ✅ + Next 10 ⚠️ + 10 backups (mutations)\n- **Availability checking**: Manual links across ENS + Unstoppable + top ICANN registrars\n- **TLD favorites**: default to `.eth`, `.ai`, `.com`, `.dao` (user can set favorites; persist)\n- **TLD gravity**: bias candidates toward what reads *native* on favorite TLDs (see “TLD-aware naming” below)\n- **Default banned words (can override)**: harvest, mine, scrape, exploit, stalk, police, punish\n\nCollect constraints in this order (stop when enough signal):\n1) **Object**: ENS name? skill slug? product? protocol primitive? (pick one)\n2) **Primary job-to-be-done**: what does it enable? (e.g., “agents coordinate work + payout bounties”)\n3) **Relational permission**: is this name being *offered* to the network, or *claimed* as a moat? (choose a posture)\n4) **Vibe lane**: molty-social (crew\u002Fguild\u002Fgig) vs infra (mesh\u002Frail\u002Frouter) vs trust (proof\u002Fclaim\u002Frecord)\n5) **Hard constraints**: max chars (e.g. 10), must be 1 word, banned words (e.g. “book”), tone boundaries\n6) **Audience**: humans, agents, or both\n\nIf the user is speed-running availability checks: skip questions and produce *batches*.\n\n## Core workflow\n\n### Step 0 — Choose a target surface (preset)\nUse one preset and state it explicitly in the output:\n\n- **ENS preset (default)**: ≤10 chars, 1 word, no hyphens, verbable, batchy.\n- **Skill preset**: kebab-case allowed, clarity > brevity, include 3–5 trigger phrases.\n- **Product preset**: brandable, pronounceable, avoid confusability\u002Ftrademark collisions.\n\n### Step 1 — Choose a semantic lane\nPick 1–3 lanes; don’t mix more than 2 in a single name.\n\n**Molty-social lanes** (high adoption)\n- work, gig, bounty, crew, guild, team, coop\n\n**Vitality \u002F sympoiesis lane** (making-with)\n- bloom, pulse, root, flow, kin, weave, garden\n\nNote: avoid militarized or de-individualizing metaphors by default (e.g., prefer *crew\u002Fkin* over *swarm* unless explicitly requested).\n\n**Coordination lanes**\n- handoff, relay, dispatch, route, queue, sync, link\n\n**Trust lanes**\n- claim, record, proof, attest, receipt, audit, verify\n\n**Money lanes**\n- pay, tip, fund, split, settle, escrow\n\n**Network lanes**\n- mesh, rail, hub, lane, ring, fabric, bridge\n\n### Step 2 — Generate candidates (portmanteau patterns)\nUse these patterns in order of hit-rate.\n\nAlso: generate with **TLD gravity** in mind (you’re not naming in a vacuum).\n\n### TLD-aware naming (gravitational pull)\nDefault TLDs: **.eth \u002F .ai \u002F .com \u002F .dao**. When you output candidates, optionally tag the best-fit TLD(s).\n\n- **.eth**: onchain identity + payments + trust primitives. Words like *claim, record, proof, pay, escrow, attest, verify, receipt* read native.\n- **.dao**: governance + coordination + bounties + collective action. Words like *bounty, guild, crew, vote, proposal, council, grants* read native.\n- **.ai**: tools, copilots, automation surfaces. Words like *namer, agent, studio, lab, forge, relay, router, workflow* read native.\n- **.com**: broad public\u002Fbrand surface. Prefer the clearest\u002Fleast-jargon name; avoid crypto-only vibes unless intentional.\n\nRule of thumb: if you’re unsure, make the candidate compatible with **.com** clarity and let **.eth\u002F.dao** carry the specialized meaning.\n\n\n1) **Noun+Noun primitive**: `work`+`mesh` → **workmesh**\n2) **Noun+Place**: `bounty`+`hq` → **bountyhq**\n3) **Noun+Group**: `work`+`crew` → **workcrew**\n4) **Action+Noun**: `sync`+`crew` → **synccrew**\n5) **Noun+Rail** (payments\u002Fsettlement): `pay`+`rail` → **payrail**\n6) **Noun+Log** (provenance): `claim`+`log` → **claimlog**\n\nPrefer:\n- 6–10 chars\n- 2–3 syllables\n- no hyphens (for ENS) unless requested\n\n### Step 3 — Filter hard (kill list)\nRemove candidates that fail any of:\n- **Pronounceability**: awkward consonant pileups (e.g., “tskrl”) ⚠️\n- **Ambiguity**: could mean 3+ different things without context ⚠️\n- **Cringe \u002F cutesy**: feels like marketing copy, not tooling ⚠️\n- **Confusability**: too close to common brands\u002Fprotocols (avoid legal + social collisions) ⚠️\n- **Power\u002Fharms**: surveillance\u002Fcop vibes (e.g., “track”, “snitch”, “police”), coercion (“enforce”), extractive framing (“harvest”) ❌\n\nConsent-forward \u002F harm-reducing replacements (examples):\n- prefer **\"optin\" \u002F \"consent\" \u002F \"invite\" \u002F \"handoff\"** over “track \u002F monitor \u002F enforce”\n- prefer **\"receipt\" \u002F \"record\" \u002F \"proof\"** over “snitch \u002F police \u002F punish”\n\n### Step 4 — Reality + verbability + accessibility test\nFor each finalist, run these tests:\n\n**A) Two sentences**\n- “Send it to ___ on **NAME**.”\n- “We’re running bounties through **NAME**.”\n\n**B) Verb test (must pass)**\n- “Just **NAME** it over.”\n\n**C) 7-word definition (meaning compression)**\nWrite a 7-word definition. If you can’t, it’s not a primitive.\n\n**D) Accessibility check (must not fail)**\n- Screen-reader friendly? (no lookalike characters, no weird punctuation)\n- Low-bandwidth parse? (obvious segmentation; not a typo-soup)\n- Cross-accent tolerance? (don’t overfit to one phonetic norm)\n\nIf it reads naturally, keep it.\n\n### Step 5 — Output format (what to return)\nReturn:\n- State the **target surface preset** (ENS \u002F Skill \u002F Product).\n- **Top 5** (✅): name + **best-fit TLD tag** + 7-word definition + why it’s sticky (1 line)\n- **Next 10** (⚠️): name + micro-caveat\n- **Set Builder (optional, high leverage)**: 1 flagship + 4 satellites (pay\u002Fverify\u002Fclaims\u002Fdocs\u002Fapi) in a consistent style\n\nTemplate example (Set Builder output)\n- Flagship: **workcrew** (best: .com\u002F.ai) — “A crew that ships work together, fast.”\n- Satellites:\n  - **crewpay** (best: .eth\u002F.dao) — “Payout rails for crews and bounties.”\n  - **crewclaim** (best: .eth) — “Claims + receipts for shipped work.”\n  - **crewverify** (best: .eth\u002F.ai) — “Verify who did what, when.”\n  - **crewdocs** (best: .com\u002F.ai) — “Human-readable rules, docs, how-to.”\n\nNotes:\n- Keep morphology consistent (crew\u002Fmesh\u002Frail\u002Fhq), then vary the role word.\n- If flagship is generic, add one vitality marker (e.g., **bloomcrew**) but only if it stays legible.\n\n- **Fallback transforms** (mutation ladder)\n\nAvoid long essays.\n\n## Fallback transforms (when everything is taken)\n\n### Mutation ladder (use in order, report which rung you used)\nWhen names are taken, don’t thrash. Walk the ladder:\n\n1) **Swap suffix (network\u002Fplace)**: mesh → hub → lane → rail → hq\n2) **Swap group word**: crew → guild → coop → team → swarm\n3) **Swap work noun**: gig → work → task → job → quest\n4) **Pluralize**: crew → crews, guild → guilds (keeps meaning, increases availability)\n5) **Add one clarifier syllable**: pay → payout, claim → claims, proof → proofs\n6) **Lengthen by ≤2 chars**: prefer meaning over ultra-short\n\nUse these to generate “still intuitive” alternatives:\n- swap **mesh ↔ net ↔ hub ↔ lane ↔ rail ↔ hq**\n- swap **crew ↔ guild ↔ coop ↔ team ↔ swarm**\n- swap **pay ↔ tip ↔ fund ↔ split ↔ settle**\n- pluralize: `crew` → `crews` (often available and still readable)\n\n## Availability checking (Web3 + ICANN) (optional)\n\nGoal: let the user choose **how automated** the checking should be, while keeping **zero-barrier manual mode** always valid.\n\n### Choose a mode (ask once, then remember preference)\nOffer 3 modes; default to **Manual**:\n\n1) **Manual (zero keys, lowest friction)** ✅\n   - Return clickable search URLs for each provider.\n   - Fast, resilient to captchas\u002FUI changes.\n\n2) **Assisted (browser-driven, best-effort)** ⚠️\n   - Use a browser to open provider searches in tabs.\n   - Works until a provider throws captcha \u002F bot protection.\n\n3) **API (highest automation, requires keys)** ✅\n   - Use official APIs where available (e.g., GoDaddy) for deterministic checks.\n   - Fall back to Manual links for providers without keys.\n\nAlways support mixed mode: “API for GoDaddy + Manual for ENS\u002FUD.”\n\n### Choose providers (top Web3 + ICANN)\nIf the user says “check top sites,” use this default set:\n\n**Web3 naming (common in agent circles)**\n- ENS: https:\u002F\u002Fapp.ens.domains\u002F\n- Unstoppable Domains: https:\u002F\u002Funstoppabledomains.com\u002Fsearch\n\n**ICANN \u002F DNS registrars (manual search works without keys)**\n- GoDaddy: https:\u002F\u002Fwww.godaddy.com\u002Fdomainsearch\u002Ffind\n- Namecheap: https:\u002F\u002Fwww.namecheap.com\u002Fdomains\u002Fregistration\u002F\n- Cloudflare Registrar: https:\u002F\u002Fwww.cloudflare.com\u002Fproducts\u002Fregistrar\u002F\n- Porkbun: https:\u002F\u002Fporkbun.com\u002F\n- Dynadot: https:\u002F\u002Fwww.dynadot.com\u002Fdomain\u002Fsearch\n- Hover: https:\u002F\u002Fwww.hover.com\u002Fdomains\n- Gandi: https:\u002F\u002Fwww.gandi.net\u002Fen\u002Fdomain\n- Squarespace Domains: https:\u002F\u002Fdomains.squarespace.com\u002F\n\nIf the user prefers a smaller list (speed), ask for their “top 3” and remember it.\n\n### Remember preference (important)\nIf the user specifies:\n- mode (Manual\u002FAssisted\u002FAPI)\n- providers (e.g., ENS + GoDaddy + Namecheap)\n- **TLD favorites** (e.g., `.eth,.dao` or `.com,.ai`)\n\n…then **remember that as their default** for future naming sessions.\n\nRecommended memory format:\n- `TLD_FAVORITES: .eth,.ai,.com,.dao`\n\n### How to run the check (recommended UX)\n\n**Step A — Generate candidates**\n- Produce Top 5 ✅ + Next 10 ⚠️ as usual.\n- If the user needs a **bundle**, run **Set Builder** immediately (flagship + satellites).\n\n**Step B — Check availability**\n- In Manual mode: for each candidate, output provider search links.\n- In Assisted\u002FAPI mode: run what you can; for what you can’t, output links.\n\n**Step C — Backup loop (tight + fast)**\nIf a name is taken:\n1) Generate **3–8 closest alternates** (fallback transforms).\n2) Check alternates using the same mode\u002Fproviders.\n3) Return the first set that clears the user’s constraints.\n\n**Truthfulness rule:** never say “available everywhere” unless every provider was checked successfully. Use:\n- ✅ likely available (checked)\n- ⚠️ unknown (not checked \u002F captcha)\n- ❌ taken (confirmed)\n\n### Helper script (optional)\nUse `scripts\u002Fcheck.mjs` to print a **batch of provider URLs** for quick manual checking.\n\n## ENS-specific guidance (optional)\n\nIf the task is ENS buying:\n- Produce **batches of 10–20** to try quickly.\n- Keep a **“miss list”** (taken) and mutate via fallback transforms.\n- Use the availability-check flow above when possible; otherwise output manual check links.\n\n## Advanced: “missing primitive finder” (connection-making)\n\nWhen the user describes a workflow, identify missing primitives and propose names for them.\n\n### Namespace pollution guardrail (anti-generic)\nIf a candidate is too generic (likely to be produced by many agents), prefer one of:\n- add a **vibe marker** (vitality lane) that still reads clean\n- add a **role marker** (pay\u002Fverify\u002Fclaims\u002Frecord)\n- produce a **set** (flagship + satellites) so the ecosystem has handles, not mush\n\n### Social liquidity check\nPrefer names that will be adopted socially (easy to repeat, easy to tag, easy to remember) over “technically available but socially dead.”\n\nAlso run lightweight **confusion safety** checks on finalists (complementary to linguistic humility):\n- **2am test**: does it *visually parse* under low cognitive load (tired, small screen)?\n- **Dictation test**: would voice-to-text likely capture it across accents?\n- **Typo radius**: avoid names where one-letter typos become other common words.\n\nImportant: the 2am test is about **visual parsing**, not “Western mouthfeel.” If it fails for one audience, treat that as signal to redesign, not to exclude.\n\nCommon missing primitives in agent economies:\n- **handoff artifact** (context bundle) → “workpack”, “taskpack”\n- **receipt for work** (verifiable) → “workreceipt”, “claimreceipt”\n- **bounty lifecycle** (post→claim→deliver→payout) → “bountyloop”\n- **crew split** (multi-party payout) → “splithub”, “splitrail”\n\nWhen you propose a primitive, also propose:\n- 1 sentence of “what it is”\n- 1 sentence of “why moltys need it now”\n\n## Bundled resources\n\n- For curated building blocks and “molty-speak primitives”, read: `references\u002Fblocks.md`\n- For scripts to generate candidates in batches, run: `scripts\u002Fforge.mjs` (does not check availability)\n","# Skill Namer (Portmanteau Forge)\n\nGenerate short, molty-native names that *actually get used*: intuitive, pronounceable, and load-bearing.\n\nThis skill is optimized for:\n- **ENS \u002F onchain primitives** (where obvious nouns are taken)\n- **Moltbook \u002F agent-to-agent collaboration** (work routing, bounties, receipts, trust)\n- **General agent power** (faster coordination, clear affordances)\n\n## Operating doctrine (don’t skip)\n\n- **Coherence > traction > cleverness.** If a name needs explanation, it’s not a primitive.\n- **Accessibility test > one-breath test.** If it’s hard to say *or* hard for screen readers \u002F low-bandwidth agents, it’s not a good primitive.\n- **Affordance clarity.** A molty should infer “what it does” in 1–2 seconds.\n- **Non-extractive + harm-aware.** Avoid names that normalize surveillance, coercion, carceral logic, or identity harm. Prefer consent-forward framing.\n- **Linguistic humility.** Pronounceability norms can be biased; avoid treating “Western mouthfeel” as correctness.\n- **No fake precision.** Do not assign numeric grades. Use ✅ \u002F ⚠️ \u002F ❌ with brief reasons.\n\n## Quick intake (ask only what you need)\n\n### Molty default preset (use unless the user overrides)\n- **Length**: ≤10 chars\n- **Form**: 1 word, no hyphens\n- **Vibe**: molty-social first (crew\u002Fgig\u002Fbounty), then infra (mesh\u002Frail\u002Fhq)\n- **Output**: Top 5 ✅ + Next 10 ⚠️ + 10 backups (mutations)\n- **Availability checking**: Manual links across ENS + Unstoppable + top ICANN registrars\n- **TLD favorites**: default to `.eth`, `.ai`, `.com`, `.dao` (user can set favorites; persist)\n- **TLD gravity**: bias candidates toward what reads *native* on favorite TLDs (see “TLD-aware naming” below)\n- **Default banned words (can override)**: harvest, mine, scrape, exploit, stalk, police, punish\n\nCollect constraints in this order (stop when enough signal):\n1) **Object**: ENS name? skill slug? product? protocol primitive? (pick one)\n2) **Primary job-to-be-done**: what does it enable? (e.g., “agents coordinate work + payout bounties”)\n3) **Relational permission**: is this name being *offered* to the network, or *claimed* as a moat? (choose a posture)\n4) **Vibe lane**: molty-social (crew\u002Fguild\u002Fgig) vs infra (mesh\u002Frail\u002Frouter) vs trust (proof\u002Fclaim\u002Frecord)\n5) **Hard constraints**: max chars (e.g. 10), must be 1 word, banned words (e.g. “book”), tone boundaries\n6) **Audience**: humans, agents, or both\n\nIf the user is speed-running availability checks: skip questions and produce *batches*.\n\n## Core workflow\n\n### Step 0 — Choose a target surface (preset)\nUse one preset and state it explicitly in the output:\n\n- **ENS preset (default)**: ≤10 chars, 1 word, no hyphens, verbable, batchy.\n- **Skill preset**: kebab-case allowed, clarity > brevity, include 3–5 trigger phrases.\n- **Product preset**: brandable, pronounceable, avoid confusability\u002Ftrademark collisions.\n\n### Step 1 — Choose a semantic lane\nPick 1–3 lanes; don’t mix more than 2 in a single name.\n\n**Molty-social lanes** (high adoption)\n- work, gig, bounty, crew, guild, team, coop\n\n**Vitality \u002F sympoiesis lane** (making-with)\n- bloom, pulse, root, flow, kin, weave, garden\n\nNote: avoid militarized or de-individualizing metaphors by default (e.g., prefer *crew\u002Fkin* over *swarm* unless explicitly requested).\n\n**Coordination lanes**\n- handoff, relay, dispatch, route, queue, sync, link\n\n**Trust lanes**\n- claim, record, proof, attest, receipt, audit, verify\n\n**Money lanes**\n- pay, tip, fund, split, settle, escrow\n\n**Network lanes**\n- mesh, rail, hub, lane, ring, fabric, bridge\n\n### Step 2 — Generate candidates (portmanteau patterns)\nUse these patterns in order of hit-rate.\n\nAlso: generate with **TLD gravity** in mind (you’re not naming in a vacuum).\n\n### TLD-aware naming (gravitational pull)\nDefault TLDs: **.eth \u002F .ai \u002F .com \u002F .dao**. When you output candidates, optionally tag the best-fit TLD(s).\n\n- **.eth**: onchain identity + payments + trust primitives. Words like *claim, record, proof, pay, escrow, attest, verify, receipt* read native.\n- **.dao**: governance + coordination + bounties + collective action. Words like *bounty, guild, crew, vote, proposal, council, grants* read native.\n- **.ai**: tools, copilots, automation surfaces. Words like *namer, agent, studio, lab, forge, relay, router, workflow* read native.\n- **.com**: broad public\u002Fbrand surface. Prefer the clearest\u002Fleast-jargon name; avoid crypto-only vibes unless intentional.\n\nRule of thumb: if you’re unsure, make the candidate compatible with **.com** clarity and let **.eth\u002F.dao** carry the specialized meaning.\n\n\n1) **Noun+Noun primitive**: `work`+`mesh` → **workmesh**\n2) **Noun+Place**: `bounty`+`hq` → **bountyhq**\n3) **Noun+Group**: `work`+`crew` → **workcrew**\n4) **Action+Noun**: `sync`+`crew` → **synccrew**\n5) **Noun+Rail** (payments\u002Fsettlement): `pay`+`rail` → **payrail**\n6) **Noun+Log** (provenance): `claim`+`log` → **claimlog**\n\nPrefer:\n- 6–10 chars\n- 2–3 syllables\n- no hyphens (for ENS) unless requested\n\n### Step 3 — Filter hard (kill list)\nRemove candidates that fail any of:\n- **Pronounceability**: awkward consonant pileups (e.g., “tskrl”) ⚠️\n- **Ambiguity**: could mean 3+ different things without context ⚠️\n- **Cringe \u002F cutesy**: feels like marketing copy, not tooling ⚠️\n- **Confusability**: too close to common brands\u002Fprotocols (avoid legal + social collisions) ⚠️\n- **Power\u002Fharms**: surveillance\u002Fcop vibes (e.g., “track”, “snitch”, “police”), coercion (“enforce”), extractive framing (“harvest”) ❌\n\nConsent-forward \u002F harm-reducing replacements (examples):\n- prefer **\"optin\" \u002F \"consent\" \u002F \"invite\" \u002F \"handoff\"** over “track \u002F monitor \u002F enforce”\n- prefer **\"receipt\" \u002F \"record\" \u002F \"proof\"** over “snitch \u002F police \u002F punish”\n\n### Step 4 — Reality + verbability + accessibility test\nFor each finalist, run these tests:\n\n**A) Two sentences**\n- “Send it to ___ on **NAME**.”\n- “We’re running bounties through **NAME**.”\n\n**B) Verb test (must pass)**\n- “Just **NAME** it over.”\n\n**C) 7-word definition (meaning compression)**\nWrite a 7-word definition. If you can’t, it’s not a primitive.\n\n**D) Accessibility check (must not fail)**\n- Screen-reader friendly? (no lookalike characters, no weird punctuation)\n- Low-bandwidth parse? (obvious segmentation; not a typo-soup)\n- Cross-accent tolerance? (don’t overfit to one phonetic norm)\n\nIf it reads naturally, keep it.\n\n### Step 5 — Output format (what to return)\nReturn:\n- State the **target surface preset** (ENS \u002F Skill \u002F Product).\n- **Top 5** (✅): name + **best-fit TLD tag** + 7-word definition + why it’s sticky (1 line)\n- **Next 10** (⚠️): name + micro-caveat\n- **Set Builder (optional, high leverage)**: 1 flagship + 4 satellites (pay\u002Fverify\u002Fclaims\u002Fdocs\u002Fapi) in a consistent style\n\nTemplate example (Set Builder output)\n- Flagship: **workcrew** (best: .com\u002F.ai) — “A crew that ships work together, fast.”\n- Satellites:\n  - **crewpay** (best: .eth\u002F.dao) — “Payout rails for crews and bounties.”\n  - **crewclaim** (best: .eth) — “Claims + receipts for shipped work.”\n  - **crewverify** (best: .eth\u002F.ai) — “Verify who did what, when.”\n  - **crewdocs** (best: .com\u002F.ai) — “Human-readable rules, docs, how-to.”\n\nNotes:\n- Keep morphology consistent (crew\u002Fmesh\u002Frail\u002Fhq), then vary the role word.\n- If flagship is generic, add one vitality marker (e.g., **bloomcrew**) but only if it stays legible.\n\n- **Fallback transforms** (mutation ladder)\n\nAvoid long essays.\n\n## Fallback transforms (when everything is taken)\n\n### Mutation ladder (use in order, report which rung you used)\nWhen names are taken, don’t thrash. Walk the ladder:\n\n1) **Swap suffix (network\u002Fplace)**: mesh → hub → lane → rail → hq\n2) **Swap group word**: crew → guild → coop → team → swarm\n3) **Swap work noun**: gig → work → task → job → quest\n4) **Pluralize**: crew → crews, guild → guilds (keeps meaning, increases availability)\n5) **Add one clarifier syllable**: pay → payout, claim → claims, proof → proofs\n6) **Lengthen by ≤2 chars**: prefer meaning over ultra-short\n\nUse these to generate “still intuitive” alternatives:\n- swap **mesh ↔ net ↔ hub ↔ lane ↔ rail ↔ hq**\n- swap **crew ↔ guild ↔ coop ↔ team ↔ swarm**\n- swap **pay ↔ tip ↔ fund ↔ split ↔ settle**\n- pluralize: `crew` → `crews` (often available and still readable)\n\n## Availability checking (Web3 + ICANN) (optional)\n\nGoal: let the user choose **how automated** the checking should be, while keeping **zero-barrier manual mode** always valid.\n\n### Choose a mode (ask once, then remember preference)\nOffer 3 modes; default to **Manual**:\n\n1) **Manual (zero keys, lowest friction)** ✅\n   - Return clickable search URLs for each provider.\n   - Fast, resilient to captchas\u002FUI changes.\n\n2) **Assisted (browser-driven, best-effort)** ⚠️\n   - Use a browser to open provider searches in tabs.\n   - Works until a provider throws captcha \u002F bot protection.\n\n3) **API (highest automation, requires keys)** ✅\n   - Use official APIs where available (e.g., GoDaddy) for deterministic checks.\n   - Fall back to Manual links for providers without keys.\n\nAlways support mixed mode: “API for GoDaddy + Manual for ENS\u002FUD.”\n\n### Choose providers (top Web3 + ICANN)\nIf the user says “check top sites,” use this default set:\n\n**Web3 naming (common in agent circles)**\n- ENS: https:\u002F\u002Fapp.ens.domains\u002F\n- Unstoppable Domains: https:\u002F\u002Funstoppabledomains.com\u002Fsearch\n\n**ICANN \u002F DNS registrars (manual search works without keys)**\n- GoDaddy: https:\u002F\u002Fwww.godaddy.com\u002Fdomainsearch\u002Ffind\n- Namecheap: https:\u002F\u002Fwww.namecheap.com\u002Fdomains\u002Fregistration\u002F\n- Cloudflare Registrar: https:\u002F\u002Fwww.cloudflare.com\u002Fproducts\u002Fregistrar\u002F\n- Porkbun: https:\u002F\u002Fporkbun.com\u002F\n- Dynadot: https:\u002F\u002Fwww.dynadot.com\u002Fdomain\u002Fsearch\n- Hover: https:\u002F\u002Fwww.hover.com\u002Fdomains\n- Gandi: https:\u002F\u002Fwww.gandi.net\u002Fen\u002Fdomain\n- Squarespace Domains: https:\u002F\u002Fdomains.squarespace.com\u002F\n\nIf the user prefers a smaller list (speed), ask for their “top 3” and remember it.\n\n### Remember preference (important)\nIf the user specifies:\n- mode (Manual\u002FAssisted\u002FAPI)\n- providers (e.g., ENS + GoDaddy + Namecheap)\n- **TLD favorites** (e.g., `.eth,.dao` or `.com,.ai`)\n\n…then **remember that as their default** for future naming sessions.\n\nRecommended memory format:\n- `TLD_FAVORITES: .eth,.ai,.com,.dao`\n\n### How to run the check (recommended UX)\n\n**Step A — Generate candidates**\n- Produce Top 5 ✅ + Next 10 ⚠️ as usual.\n- If the user needs a **bundle**, run **Set Builder** immediately (flagship + satellites).\n\n**Step B — Check availability**\n- In Manual mode: for each candidate, output provider search links.\n- In Assisted\u002FAPI mode: run what you can; for what you can’t, output links.\n\n**Step C — Backup loop (tight + fast)**\nIf a name is taken:\n1) Generate **3–8 closest alternates** (fallback transforms).\n2) Check alternates using the same mode\u002Fproviders.\n3) Return the first set that clears the user’s constraints.\n\n**Truthfulness rule:** never say “available everywhere” unless every provider was checked successfully. Use:\n- ✅ likely available (checked)\n- ⚠️ unknown (not checked \u002F captcha)\n- ❌ taken (confirmed)\n\n### Helper script (optional)\nUse `scripts\u002Fcheck.mjs` to print a **batch of provider URLs** for quick manual checking.\n\n## ENS-specific guidance (optional)\n\nIf the task is ENS buying:\n- Produce **batches of 10–20** to try quickly.\n- Keep a **“miss list”** (taken) and mutate via fallback transforms.\n- Use the availability-check flow above when possible; otherwise output manual check links.\n\n## Advanced: “missing primitive finder” (connection-making)\n\nWhen the user describes a workflow, identify missing primitives and propose names for them.\n\n### Namespace pollution guardrail (anti-generic)\nIf a candidate is too generic (likely to be produced by many agents), prefer one of:\n- add a **vibe marker** (vitality lane) that still reads clean\n- add a **role marker** (pay\u002Fverify\u002Fclaims\u002Frecord)\n- produce a **set** (flagship + satellites) so the ecosystem has handles, not mush\n\n### Social liquidity check\nPrefer names that will be adopted socially (easy to repeat, easy to tag, easy to remember) over “technically available but socially dead.”\n\nAlso run lightweight **confusion safety** checks on finalists (complementary to linguistic humility):\n- **2am test**: does it *visually parse* under low cognitive load (tired, small screen)?\n- **Dictation test**: would voice-to-text likely capture it across accents?\n- **Typo radius**: avoid names where one-letter typos become other common words.\n\nImportant: the 2am test is about **visual parsing**, not “Western mouthfeel.” If it fails for one audience, treat that as signal to redesign, not to exclude.\n\nCommon missing primitives in agent economies:\n- **handoff artifact** (context bundle) → “workpack”, “taskpack”\n- **receipt for work** (verifiable) → “workreceipt”, “claimreceipt”\n- **bounty lifecycle** (post→claim→deliver→payout) → “bountyloop”\n- **crew split** (multi-party payout) → “splithub”, “splitrail”\n\nWhen you propose a primitive, also propose:\n- 1 sentence of “what it is”\n- 1 sentence of “why moltys need it now”\n\n## Bundled resources\n\n- For curated building blocks and “molty-speak primitives”, read: `references\u002Fblocks.md`\n- For scripts to generate candidates in batches, run: `scripts\u002Fforge.mjs` (does not check availability)\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fotherpowers\u002Fskill-namer",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill skill-namer",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill skill-namer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill skill-namer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fotherpowers\u002Fskill-namer\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]