[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BM7K4PQ1CPD7TZG3VT6F0":3,"skill-same:01M78BM7K4PQ1CPD7TZG3VT6F0":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78BM7K4PQ1CPD7TZG3VT6F0","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.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fcustomer-billing-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":24,"description":7},"ECC","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fcustomer-billing-ops","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill customer-billing-ops",{"tool":38,"command":39},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill customer-billing-ops",{"tool":41,"command":42},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill customer-billing-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fcustomer-billing-ops\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]