[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FS051ZXC7DB1SM9KYA80N":3,"skill-same:01M70FS051ZXC7DB1SM9KYA80N":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70FS051ZXC7DB1SM9KYA80N","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcustomer-billing-ops\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"customer","customer billing ops","ops","billing","recovery","state","use","manage","as","refunds","Tools","stripe","revenue","plan","analysis","when","workflows","churn","inspect","operate","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.\nmetadata:\n  origin: 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,"metadata":49,"description":7},{"origin":50},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fcustomer-billing-ops",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill customer-billing-ops",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill customer-billing-ops",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill customer-billing-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcustomer-billing-ops\u002FSKILL.md",true,[],[74,82,90,97,104,111],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":89},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":89},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\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":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":89},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":89},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":89},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]