[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JTXP4SEKFJFSAVM71637KQ":3,"skill-same:01M6JTXP4SEKFJFSAVM71637KQ":70},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6JTXP4SEKFJFSAVM71637KQ","customer-billing-ops",null,"Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.","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\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fcustomer-billing-ops\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"customer billing ops","billing","ops","customer","use","when","inspect","operate","churn","revenue","as","stripe","manage","operations","refunds","plan","analysis","recovery","Tools","state","workflows","2026-11-10 10:12:30",false,"---\nname: customer-billing-ops\ndescription: Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.\norigin: ECC\n---\n\n# Customer Billing Ops\n\nUse this skill for real customer operations, not generic payment API design.\n\nThe goal is to help the operator answer: who is this customer, what happened, what is the safest fix, and what follow-up should we send?\n\n## When to Use\n\n- Customer says billing is broken, they want a refund, or they cannot cancel\n- Investigating duplicate subscriptions, accidental charges, failed renewals, or churn risk\n- Reviewing plan mix, active subscriptions, yearly vs monthly conversion, or team-seat confusion\n- Creating or validating a billing portal flow\n- Auditing support complaints that touch subscriptions, invoices, refunds, or payment methods\n\n## Preferred Tool Surface\n\n- Use connected billing tools such as Stripe first\n- Use email, GitHub, or issue trackers only as supporting evidence\n- Prefer hosted billing\u002Fcustomer portals over custom account-management code when the platform already provides the needed controls\n\n## Guardrails\n\n- Never expose secret keys, full card details, or unnecessary customer PII in the response\n- Do not refund blindly; first classify the issue\n- Distinguish among:\n  - accidental duplicate purchase\n  - deliberate multi-seat or team purchase\n  - broken product \u002F unmet value\n  - failed or incomplete checkout\n  - cancellation due to missing self-serve controls\n- For annual plans, team plans, and prorated states, verify the contract shape before taking action\n\n## Workflow\n\n### 1. Identify the customer cleanly\n\nStart from the strongest identifier available:\n\n- customer email\n- Stripe customer ID\n- subscription ID\n- invoice ID\n- GitHub username or support email if it is known to map back to billing\n\nReturn a concise identity summary:\n\n- customer\n- active subscriptions\n- canceled subscriptions\n- invoices\n- obvious anomalies such as duplicate active subscriptions\n\n### 2. Classify the issue\n\nPut the case into one bucket before acting:\n\n| Case | Typical action |\n|------|----------------|\n| Duplicate personal subscription | cancel extras, consider refund |\n| Real multi-seat\u002Fteam intent | preserve seats, clarify billing model |\n| Failed payment \u002F incomplete checkout | recover via portal or update payment method |\n| Missing self-serve controls | provide portal, cancellation path, or invoice access |\n| Product failure or trust break | refund, apologize, log product issue |\n\n### 3. Take the safest reversible action first\n\nPreferred order:\n\n1. restore self-serve management\n2. fix duplicate or broken billing state\n3. refund only the affected charge or duplicate\n4. document the reason\n5. send a short customer follow-up\n\nIf the fix requires product work, separate:\n\n- customer remediation now\n- product bug \u002F workflow gap for backlog\n\n### 4. Check operator-side product gaps\n\nIf the customer pain comes from a missing operator surface, call it out explicitly. Common examples:\n\n- no billing portal\n- no usage\u002Frate-limit visibility\n- no plan\u002Fseat explanation\n- no cancellation flow\n- no duplicate-subscription guard\n\nTreat those as ECC or website follow-up items, not just support incidents.\n\n### 5. Produce the operator handoff\n\nEnd with:\n\n- customer state summary\n- action taken\n- revenue impact\n- follow-up text to send\n- product or backlog issue to create\n\n## Output Format\n\nUse this structure:\n\n```text\nCUSTOMER\n- name \u002F email\n- relevant account identifiers\n\nBILLING STATE\n- active subscriptions\n- invoice or renewal state\n- anomalies\n\nDECISION\n- issue classification\n- why this action is correct\n\nACTION TAKEN\n- refund \u002F cancel \u002F portal \u002F no-op\n\nFOLLOW-UP\n- short customer message\n\nPRODUCT GAP\n- what should be fixed in the product or website\n```\n\n## Examples of Good Recommendations\n\n- \"The right fix is a billing portal, not a custom dashboard yet\"\n- \"This looks like duplicate personal checkout, not a real team-seat purchase\"\n- \"Refund one duplicate charge, keep the remaining active subscription, then convert the customer to org billing later if needed\"\n","# Customer Billing Ops\n\nUse this skill for real customer operations, not generic payment API design.\n\nThe goal is to help the operator answer: who is this customer, what happened, what is the safest fix, and what follow-up should we send?\n\n## When to Use\n\n- Customer says billing is broken, they want a refund, or they cannot cancel\n- Investigating duplicate subscriptions, accidental charges, failed renewals, or churn risk\n- Reviewing plan mix, active subscriptions, yearly vs monthly conversion, or team-seat confusion\n- Creating or validating a billing portal flow\n- Auditing support complaints that touch subscriptions, invoices, refunds, or payment methods\n\n## Preferred Tool Surface\n\n- Use connected billing tools such as Stripe first\n- Use email, GitHub, or issue trackers only as supporting evidence\n- Prefer hosted billing\u002Fcustomer portals over custom account-management code when the platform already provides the needed controls\n\n## Guardrails\n\n- Never expose secret keys, full card details, or unnecessary customer PII in the response\n- Do not refund blindly; first classify the issue\n- Distinguish among:\n  - accidental duplicate purchase\n  - deliberate multi-seat or team purchase\n  - broken product \u002F unmet value\n  - failed or incomplete checkout\n  - cancellation due to missing self-serve controls\n- For annual plans, team plans, and prorated states, verify the contract shape before taking action\n\n## Workflow\n\n### 1. Identify the customer cleanly\n\nStart from the strongest identifier available:\n\n- customer email\n- Stripe customer ID\n- subscription ID\n- invoice ID\n- GitHub username or support email if it is known to map back to billing\n\nReturn a concise identity summary:\n\n- customer\n- active subscriptions\n- canceled subscriptions\n- invoices\n- obvious anomalies such as duplicate active subscriptions\n\n### 2. Classify the issue\n\nPut the case into one bucket before acting:\n\n| Case | Typical action |\n|------|----------------|\n| Duplicate personal subscription | cancel extras, consider refund |\n| Real multi-seat\u002Fteam intent | preserve seats, clarify billing model |\n| Failed payment \u002F incomplete checkout | recover via portal or update payment method |\n| Missing self-serve controls | provide portal, cancellation path, or invoice access |\n| Product failure or trust break | refund, apologize, log product issue |\n\n### 3. Take the safest reversible action first\n\nPreferred order:\n\n1. restore self-serve management\n2. fix duplicate or broken billing state\n3. refund only the affected charge or duplicate\n4. document the reason\n5. send a short customer follow-up\n\nIf the fix requires product work, separate:\n\n- customer remediation now\n- product bug \u002F workflow gap for backlog\n\n### 4. Check operator-side product gaps\n\nIf the customer pain comes from a missing operator surface, call it out explicitly. Common examples:\n\n- no billing portal\n- no usage\u002Frate-limit visibility\n- no plan\u002Fseat explanation\n- no cancellation flow\n- no duplicate-subscription guard\n\nTreat those as ECC or website follow-up items, not just support incidents.\n\n### 5. Produce the operator handoff\n\nEnd with:\n\n- customer state summary\n- action taken\n- revenue impact\n- follow-up text to send\n- product or backlog issue to create\n\n## Output Format\n\nUse this structure:\n\n```text\nCUSTOMER\n- name \u002F email\n- relevant account identifiers\n\nBILLING STATE\n- active subscriptions\n- invoice or renewal state\n- anomalies\n\nDECISION\n- issue classification\n- why this action is correct\n\nACTION TAKEN\n- refund \u002F cancel \u002F portal \u002F no-op\n\nFOLLOW-UP\n- short customer message\n\nPRODUCT GAP\n- what should be fixed in the product or website\n```\n\n## Examples of Good Recommendations\n\n- \"The right fix is a billing portal, not a custom dashboard yet\"\n- \"This looks like duplicate personal checkout, not a real team-seat purchase\"\n- \"Refund one duplicate charge, keep the remaining active subscription, then convert the customer to org billing later if needed\"\n",{"name":5,"origin":45,"description":7},"ECC","main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fcustomer-billing-ops",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill customer-billing-ops",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill customer-billing-ops",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill customer-billing-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fcustomer-billing-ops\u002FSKILL.md",true,[],[71,81,89,97,105,113],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":80},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":80},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":80},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":80},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":80},"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",[],[]]