[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BFXW9RFHWW3HR8XFBT01RE":3,"skill-same:01M7BFXW9RFHWW3HR8XFBT01RE":48},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7BFXW9RFHWW3HR8XFBT01RE","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.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\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.\norigin: 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,"origin":24,"description":7},"ECC","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\u002Ffinance-billing-ops",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill finance-billing-ops",{"tool":40,"command":41},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill finance-billing-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill finance-billing-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\u002Ffinance-billing-ops\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"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},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]