[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ME9J80XJFSB6VQVGN1F107":3,"skill-same:01M6ME9J80XJFSB6VQVGN1F107":98},{"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":28,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6ME9J80XJFSB6VQVGN1F107","marketing-site",null,"Honest marketing-site method: audience, offer, proof, objections, privacy, art direction, handoff. Triggers: marketing site, landing page, company website, portfolio, campaign page, conversion, positioning, value proposition, CTA, social proof, privacy policy.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fmarketing-site\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"marketing site","marketing","site","campaign","company","value","value proposition","privacy policy","proposition","direction","triggers","positioning","social","Art","conversion","handoff","portfolio","landing","edit","write","read","page","Bash","website","policy","2026-11-10 10:12:30",false,"---\nname: marketing-site\ndescription: \"Honest marketing-site method: audience, offer, proof, objections, privacy, art direction, handoff. Triggers: marketing site, landing page, company website, portfolio, campaign page, conversion, positioning, value proposition, CTA, social proof, privacy policy.\"\nallowed-tools: Read, Write, Edit, Bash, Grep, Glob\nkernel:\n  kind: methodology\n  version: 1\n  side_effects: none\n  confirmation: none\n---\n\n\u003Cskill id=\"marketing-site\">\n\n\u003Cpurpose>\nTurn a product or service into a focused, credible website. The page should help a specific\nperson understand the offer, trust it, and take the next useful action—without marketing\ntheater or a generic template wearing different nouns.\n\u003C\u002Fpurpose>\n\n\u003Cskill_load>skills\u002Ffrontend\u002FSKILL.md\u003C\u002Fskill_load>\n\n\u003Cinputs>\nRecover what the user and repository already supplied before asking questions:\n\n1. Audience: who arrives, what they know, and what situation brought them here.\n2. Desired action: install, buy, book, join, contact, learn, or compare.\n3. Offer: what changes for the visitor, how it works, and why this option is different.\n4. Friction: objections, risks, missing information, switching cost, and alternatives.\n5. Proof: product behavior, demo, screenshots, founder expertise, customer evidence, data.\n6. Brand and constraints: voice, assets, references, legal\u002Fprivacy needs, stack, deadline.\n\nDo not force an interview when the brief answers these. Ask only for a missing choice that\nwould materially change the page; otherwise make a reversible assumption and label it.\n\u003C\u002Finputs>\n\n\u003Ctruth-rules>\nNever invent customers, testimonials, metrics, guarantees, awards, integrations, press logos,\nscarcity, fake urgency, or “trusted by” claims. Placeholder proof must be visibly marked as a\nplaceholder and cannot ship. Describe capabilities at the strength the evidence supports.\nSpecific and modest beats impressive and false.\n\u003C\u002Ftruth-rules>\n\n\u003Cstrategy>\nWrite a one-sentence positioning statement:\n“For [audience in situation], [offer] helps [outcome] by [mechanism\u002Fdifference].”\n\nThen choose a page argument that fits the buying decision. A useful default is:\nproblem or desire → promise → mechanism → proof → objections → action.\nIt is a diagnostic spine, not a mandatory section order. A familiar plugin may need one sharp\nidea and a demo; an expensive service may need process, proof, risk reduction, and detail.\n\nGive each section one job. Prefer one primary CTA; secondary actions are allowed when they\nserve a genuinely different visitor state. CTA copy should name the next step, not “Submit.”\n\u003C\u002Fstrategy>\n\n\u003Ccopy>\n- Lead with the visitor's outcome or tension, then make the mechanism concrete.\n- Use the user's language and real nouns. Delete adjectives that the page cannot prove.\n- Keep the headline, subhead, visual, and CTA mutually reinforcing.\n- Answer the strongest objection near the claim that creates it.\n- Let product screenshots, examples, demos, and specifics carry more weight than slogans.\n- Match detail to consequence: higher price\u002Frisk needs more explanation and reassurance.\n\u003C\u002Fcopy>\n\n\u003Cart-direction>\nUse `skills\u002Ffrontend\u002FSKILL.md`. Derive the visual direction from audience, brand, offer,\ncontent, and references. A provocative page earns its tension through the idea; it does not\nneed random visual aggression. Preserve an existing design system when present.\n\u003C\u002Fart-direction>\n\n\u003Cprivacy-and-trust>\nThe privacy page must describe the actual implementation: what data is collected, why, where\nit goes, retention\u002Fdeletion, cookies or analytics, form\u002Femail providers, user choices, contact,\nand effective date. If the site collects nothing, say so plainly and still disclose hosting\nlogs or third parties that may receive technical data. Do not copy a broad boilerplate policy\nthat claims tools the site does not use. Flag jurisdiction-specific legal review when stakes\nrequire it; do not present generated copy as legal advice.\n\u003C\u002Fprivacy-and-trust>\n\n\u003Cclient-delivery>\nFor client work, confirm who approves copy\u002Fdesign, who owns supplied assets, the domain and\naccounts, analytics\u002Fconsent choices, editable-source handoff, launch\u002Frollback plan, and who\nmaintains the site. Keep credentials in the client's account or secure environment—not source.\nRead `skills\u002Fmarketing-site\u002Freferences\u002Fclient-delivery.md` for the compact handoff checklist.\n\u003C\u002Fclient-delivery>\n\n\u003Cverification>\nCheck the rendered page at target widths and follow every conversion path. Verify all claims\nagainst supplied evidence, every CTA and legal link, keyboard\u002Ffocus behavior, performance,\nmetadata\u002Fshare preview, form success\u002Ferror states, and the deployed privacy behavior.\n\u003C\u002Fverification>\n\n\u003Coutput>\nState the audience, desired action, positioning, page argument, proof used, art direction,\nassumptions\u002Fplaceholders, privacy reality, and what was actually verified.\n\u003C\u002Foutput>\n\n\u003C\u002Fskill>\n","\u003Cskill id=\"marketing-site\">\n\n\u003Cpurpose>\nTurn a product or service into a focused, credible website. The page should help a specific\nperson understand the offer, trust it, and take the next useful action—without marketing\ntheater or a generic template wearing different nouns.\n\u003C\u002Fpurpose>\n\n\u003Cskill_load>skills\u002Ffrontend\u002FSKILL.md\u003C\u002Fskill_load>\n\n\u003Cinputs>\nRecover what the user and repository already supplied before asking questions:\n\n1. Audience: who arrives, what they know, and what situation brought them here.\n2. Desired action: install, buy, book, join, contact, learn, or compare.\n3. Offer: what changes for the visitor, how it works, and why this option is different.\n4. Friction: objections, risks, missing information, switching cost, and alternatives.\n5. Proof: product behavior, demo, screenshots, founder expertise, customer evidence, data.\n6. Brand and constraints: voice, assets, references, legal\u002Fprivacy needs, stack, deadline.\n\nDo not force an interview when the brief answers these. Ask only for a missing choice that\nwould materially change the page; otherwise make a reversible assumption and label it.\n\u003C\u002Finputs>\n\n\u003Ctruth-rules>\nNever invent customers, testimonials, metrics, guarantees, awards, integrations, press logos,\nscarcity, fake urgency, or “trusted by” claims. Placeholder proof must be visibly marked as a\nplaceholder and cannot ship. Describe capabilities at the strength the evidence supports.\nSpecific and modest beats impressive and false.\n\u003C\u002Ftruth-rules>\n\n\u003Cstrategy>\nWrite a one-sentence positioning statement:\n“For [audience in situation], [offer] helps [outcome] by [mechanism\u002Fdifference].”\n\nThen choose a page argument that fits the buying decision. A useful default is:\nproblem or desire → promise → mechanism → proof → objections → action.\nIt is a diagnostic spine, not a mandatory section order. A familiar plugin may need one sharp\nidea and a demo; an expensive service may need process, proof, risk reduction, and detail.\n\nGive each section one job. Prefer one primary CTA; secondary actions are allowed when they\nserve a genuinely different visitor state. CTA copy should name the next step, not “Submit.”\n\u003C\u002Fstrategy>\n\n\u003Ccopy>\n- Lead with the visitor's outcome or tension, then make the mechanism concrete.\n- Use the user's language and real nouns. Delete adjectives that the page cannot prove.\n- Keep the headline, subhead, visual, and CTA mutually reinforcing.\n- Answer the strongest objection near the claim that creates it.\n- Let product screenshots, examples, demos, and specifics carry more weight than slogans.\n- Match detail to consequence: higher price\u002Frisk needs more explanation and reassurance.\n\u003C\u002Fcopy>\n\n\u003Cart-direction>\nUse `skills\u002Ffrontend\u002FSKILL.md`. Derive the visual direction from audience, brand, offer,\ncontent, and references. A provocative page earns its tension through the idea; it does not\nneed random visual aggression. Preserve an existing design system when present.\n\u003C\u002Fart-direction>\n\n\u003Cprivacy-and-trust>\nThe privacy page must describe the actual implementation: what data is collected, why, where\nit goes, retention\u002Fdeletion, cookies or analytics, form\u002Femail providers, user choices, contact,\nand effective date. If the site collects nothing, say so plainly and still disclose hosting\nlogs or third parties that may receive technical data. Do not copy a broad boilerplate policy\nthat claims tools the site does not use. Flag jurisdiction-specific legal review when stakes\nrequire it; do not present generated copy as legal advice.\n\u003C\u002Fprivacy-and-trust>\n\n\u003Cclient-delivery>\nFor client work, confirm who approves copy\u002Fdesign, who owns supplied assets, the domain and\naccounts, analytics\u002Fconsent choices, editable-source handoff, launch\u002Frollback plan, and who\nmaintains the site. Keep credentials in the client's account or secure environment—not source.\nRead `skills\u002Fmarketing-site\u002Freferences\u002Fclient-delivery.md` for the compact handoff checklist.\n\u003C\u002Fclient-delivery>\n\n\u003Cverification>\nCheck the rendered page at target widths and follow every conversion path. Verify all claims\nagainst supplied evidence, every CTA and legal link, keyboard\u002Ffocus behavior, performance,\nmetadata\u002Fshare preview, form success\u002Ferror states, and the deployed privacy behavior.\n\u003C\u002Fverification>\n\n\u003Coutput>\nState the audience, desired action, positioning, page argument, proof used, art direction,\nassumptions\u002Fplaceholders, privacy reality, and what was actually verified.\n\u003C\u002Foutput>\n\n\u003C\u002Fskill>\n",{"name":5,"kernel":59,"description":7,"allowed-tools":63},{"kind":60,"version":61,"confirmation":62,"side_effects":62},"methodology",1,"none","Read, Write, Edit, Bash, Grep, Glob","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fmarketing-site",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill marketing-site",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill marketing-site",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill marketing-site","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fmarketing-site\u002FSKILL.md",true,[88,94],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"agents\u002Fopenai.yaml","REFERENCE","参考文档",202,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fmarketing-site\u002Fagents\u002Fopenai.yaml",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fclient-delivery.md",1242,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fmarketing-site\u002Freferences\u002Fclient-delivery.md",[99,109,117,125,133,141],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":108},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":108},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":108},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":108},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":108},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":108},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]