[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7331C7Y062NXWYXY7RBTHDA":3,"skill-same:01M7331C7Y062NXWYXY7RBTHDA":49},{"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":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7331C7Y062NXWYXY7RBTHDA","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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffinance-billing-ops\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Ffinance-billing-ops",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill finance-billing-ops",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill finance-billing-ops",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill finance-billing-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffinance-billing-ops\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]