[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79NRYPVRQSWJVEEZSH4RM3A":3,"skill-same:01M79NRYPVRQSWJVEEZSH4RM3A":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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79NRYPVRQSWJVEEZSH4RM3A","finance-billing-ops",null,"Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-billing-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: finance-billing-ops\ndescription: Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.\nmetadata:\n  origin: ECC\n---\n\n# Finance Billing Ops\n\nUse this when the user wants to understand money, pricing, refunds, team-seat logic, or whether the product actually behaves the way the website and sales copy imply.\n\nThis is broader than `customer-billing-ops`. That skill is for customer remediation. This skill is for operator truth: revenue state, pricing decisions, team billing, and code-backed billing behavior.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `customer-billing-ops` for customer-specific remediation and follow-up\n- `research-ops` when competitor pricing or current market evidence matters\n- `market-research` when the answer should end in a pricing recommendation\n- `github-ops` when the billing truth depends on code, backlog, or release state in sibling repos\n- `verification-loop` when the answer depends on proving checkout, seat handling, or entitlement behavior\n\n## When to Use\n\n- user asks for Stripe sales, refunds, MRR, or recent customer activity\n- user asks whether team billing, per-seat billing, or quota stacking is real in code\n- user wants competitor pricing comparisons or pricing-model benchmarks\n- the question mixes revenue facts with product implementation truth\n\n## Guardrails\n\n- distinguish live data from saved snapshots\n- separate:\n  - revenue fact\n  - customer impact\n  - code-backed product truth\n  - recommendation\n- do not say \"per seat\" unless the actual entitlement path enforces it\n- do not assume duplicate subscriptions imply duplicate value\n\n## Workflow\n\n### 1. Start from the freshest billing evidence\n\nPrefer live billing data. If the data is not live, state the snapshot timestamp explicitly.\n\nNormalize the picture:\n\n- paid sales\n- active subscriptions\n- failed or incomplete checkouts\n- refunds\n- disputes\n- duplicate subscriptions\n\n### 2. Separate customer incidents from product truth\n\nIf the question is customer-specific, classify first:\n\n- duplicate checkout\n- real team intent\n- broken self-serve controls\n- unmet product value\n- failed payment or incomplete setup\n\nThen separate that from the broader product question:\n\n- does team billing really exist?\n- are seats actually counted?\n- does checkout quantity change entitlement?\n- does the site overstate current behavior?\n\n### 3. Inspect code-backed billing behavior\n\nIf the answer depends on implementation truth, inspect the code path:\n\n- checkout\n- pricing page\n- entitlement calculation\n- seat or quota handling\n- installation vs user usage logic\n- billing portal or self-serve management support\n\n### 4. End with a decision and product gap\n\nReport:\n\n- sales snapshot\n- issue diagnosis\n- product truth\n- recommended operator action\n- product or backlog gap\n\n## Output Format\n\n```text\nSNAPSHOT\n- timestamp\n- revenue \u002F subscriptions \u002F anomalies\n\nCUSTOMER IMPACT\n- who is affected\n- what happened\n\nPRODUCT TRUTH\n- what the code actually does\n- what the website or sales copy claims\n\nDECISION\n- refund \u002F preserve \u002F convert \u002F no-op\n\nPRODUCT GAP\n- exact follow-up item to build or fix\n```\n\n## Pitfalls\n\n- do not conflate failed attempts with net revenue\n- do not infer team billing from marketing language alone\n- do not compare competitor pricing from memory when current evidence is available\n- do not jump from diagnosis straight to refund without classifying the issue\n\n## Verification\n\n- the answer includes a live-data statement or snapshot timestamp\n- product-truth claims are code-backed\n- customer-impact and broader pricing\u002Fproduct conclusions are separated cleanly\n","# Finance Billing Ops\n\nUse this when the user wants to understand money, pricing, refunds, team-seat logic, or whether the product actually behaves the way the website and sales copy imply.\n\nThis is broader than `customer-billing-ops`. That skill is for customer remediation. This skill is for operator truth: revenue state, pricing decisions, team billing, and code-backed billing behavior.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `customer-billing-ops` for customer-specific remediation and follow-up\n- `research-ops` when competitor pricing or current market evidence matters\n- `market-research` when the answer should end in a pricing recommendation\n- `github-ops` when the billing truth depends on code, backlog, or release state in sibling repos\n- `verification-loop` when the answer depends on proving checkout, seat handling, or entitlement behavior\n\n## When to Use\n\n- user asks for Stripe sales, refunds, MRR, or recent customer activity\n- user asks whether team billing, per-seat billing, or quota stacking is real in code\n- user wants competitor pricing comparisons or pricing-model benchmarks\n- the question mixes revenue facts with product implementation truth\n\n## Guardrails\n\n- distinguish live data from saved snapshots\n- separate:\n  - revenue fact\n  - customer impact\n  - code-backed product truth\n  - recommendation\n- do not say \"per seat\" unless the actual entitlement path enforces it\n- do not assume duplicate subscriptions imply duplicate value\n\n## Workflow\n\n### 1. Start from the freshest billing evidence\n\nPrefer live billing data. If the data is not live, state the snapshot timestamp explicitly.\n\nNormalize the picture:\n\n- paid sales\n- active subscriptions\n- failed or incomplete checkouts\n- refunds\n- disputes\n- duplicate subscriptions\n\n### 2. Separate customer incidents from product truth\n\nIf the question is customer-specific, classify first:\n\n- duplicate checkout\n- real team intent\n- broken self-serve controls\n- unmet product value\n- failed payment or incomplete setup\n\nThen separate that from the broader product question:\n\n- does team billing really exist?\n- are seats actually counted?\n- does checkout quantity change entitlement?\n- does the site overstate current behavior?\n\n### 3. Inspect code-backed billing behavior\n\nIf the answer depends on implementation truth, inspect the code path:\n\n- checkout\n- pricing page\n- entitlement calculation\n- seat or quota handling\n- installation vs user usage logic\n- billing portal or self-serve management support\n\n### 4. End with a decision and product gap\n\nReport:\n\n- sales snapshot\n- issue diagnosis\n- product truth\n- recommended operator action\n- product or backlog gap\n\n## Output Format\n\n```text\nSNAPSHOT\n- timestamp\n- revenue \u002F subscriptions \u002F anomalies\n\nCUSTOMER IMPACT\n- who is affected\n- what happened\n\nPRODUCT TRUTH\n- what the code actually does\n- what the website or sales copy claims\n\nDECISION\n- refund \u002F preserve \u002F convert \u002F no-op\n\nPRODUCT GAP\n- exact follow-up item to build or fix\n```\n\n## Pitfalls\n\n- do not conflate failed attempts with net revenue\n- do not infer team billing from marketing language alone\n- do not compare competitor pricing from memory when current evidence is available\n- do not jump from diagnosis straight to refund without classifying the issue\n\n## Verification\n\n- the answer includes a live-data statement or snapshot timestamp\n- product-truth claims are code-backed\n- customer-impact and broader pricing\u002Fproduct conclusions are separated cleanly\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Ffinance-billing-ops","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill finance-billing-ops",{"tool":39,"command":40},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill finance-billing-ops",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill finance-billing-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-billing-ops\u002FSKILL.md",true,[],[48,54,60,66,72,78],{"skillNo":49,"name":50,"nameZh":6,"description":6,"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},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":6,"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":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]