[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CFPNP370Y4JR9SZH3WPWVR":3,"skill-same:01M7CFPNP370Y4JR9SZH3WPWVR":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CFPNP370Y4JR9SZH3WPWVR","subscription-billing-reconciliation",null,"Reconcile what a subscription contract says should have been billed for a period against what invoices actually billed. Covers proration, billing terms, invoice exports with revisions, credit notes, merged and churned accounts, parent\u002Fchild billing, currency conversion and rounding. Use for contract-vs-invoice, revenue assurance, or billing-leakage checks.","getedgehq\u002Fskills","getedgehq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F327350993?v=4","01M7CEH5YJQYF1PB3MDG9PA5HX","01M7CEH5ZAPY8TX4H3E04KM875",5,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fsubscription-billing-reconciliation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fsubscription-billing-reconciliation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: subscription-billing-reconciliation\ndescription: Reconcile what a subscription contract says should have been billed for a period against what invoices actually billed. Covers proration, billing terms, invoice exports with revisions, credit notes, merged and churned accounts, parent\u002Fchild billing, currency conversion and rounding. Use for contract-vs-invoice, revenue assurance, or billing-leakage checks.\n---\n\n# Subscription billing reconciliation\n\nGoal: for each customer, compute EXPECTED (from the contract schedule) and BILLED (from invoices) for one period in one reporting currency, then classify the gap. Write the rules down before coding; most errors are rule mistakes, not arithmetic.\n\n## 1. Read every rule source first\nSpecs rarely sit in one place. Read all prose (memos, chat logs, READMEs) end to end, in time order. Later messages override earlier ones. Note every definition (period length, tolerance, rate choice, who is in scope) and every exception. Re-read the rules after your first output and check each one against the data, not just the first mention.\n\n## 2. Expected amount (from the contract)\n- Schedule amounts are per billing term (monthly, quarterly, annual). Normalise to the period: monthly x1, quarterly \u002F3, annual \u002F12, unless the spec says otherwise.\n- Contract changes (upgrade, downgrade, price change, pause) take effect on their effective date. Build a per-day timeline and sum per day, rather than assuming one price for the whole period.\n- Proration is by calendar days in the period (use the actual day count of the period, not a flat 30, unless told).\n- Status rules: trials bill zero; the churn\u002Ftermination date is normally the last day of service, inclusive; days after it earn nothing. Check which date convention the spec uses.\n- Dates arrive in mixed formats; parse each explicitly and validate that none failed.\n\n## 3. Billed amount (from invoices)\n- An invoice export is often an event log: the same invoice id can appear many times. Keep only the latest snapshot per id (by export timestamp), then apply status filters. Draft and void never count; paid and open do. A later snapshot can cancel an invoice that an earlier one showed as paid.\n- An invoice covering a multi-period service window contributes only the share of days that fall inside the reporting period: overlap days \u002F total window days. Do not count by issue date alone.\n- Credit notes reduce billed revenue. A credit note belongs wherever the invoice it corrects belongs: attribute it to the same customer AND the same service period as the original, regardless of its own issue date or its own (often blank or wrong) customer field. If the original is outside the period, the credit note is outside it too. If the original does not count (void, draft, cancelled), the credit note is moot and is ignored.\n- Never infer a credit note's customer from its own text when it carries a link to the invoice it corrects.\n\n## 4. Entity resolution\n- Customer names come as free text from several systems. Normalise case, punctuation, whitespace, accents, `&` vs `and`, and legal-form suffixes (Inc, Ltd, GmbH, AG, PLC, BV, LLC...). Prefer authoritative keys in this order: account id, then domain, then normalised name.\n- Merged duplicates: invoices of a merged-away account belong to the surviving account. Follow chains (A merged into B merged into C) to the final survivor. Decide explicitly how the survivor's status and contract timeline interact with the duplicate's; if a surviving record is churned, its own churn rule applies to the merged entity.\n- Parent\u002Fchild accounts (a child billed through a billing parent): children roll up to the parent. If the parent is churned or otherwise no longer a valid billing target, children are reported on their own lines. Follow chains and watch for cycles.\n- Anything that cannot be tied to an account becomes its own unmatched line, grouped by its cleaned-up name, if the spec asks for it. Do not silently drop it and do not force-match it to the nearest account.\n\n## 5. Currency and rounding\n- Convert each side at the rate the spec names for that side: for example schedule at a period average or period-end rate, invoices at the rate on their own issue date. Use the same table for both and the spec's definition of average (simple mean over published days).\n- Rate tables skip weekends and holidays: use the last published rate on or before the date.\n- Keep full precision (use Fraction\u002FDecimal) through the whole computation and round only once at output, half up, to 2 decimals. Do not round per day or per invoice.\n- Convert after prorating or before it consistently; the result is identical, but mixing them with per-step rounding is not.\n\n## 6. Classification\n- Tolerance is usually max(absolute floor, percentage of expected). Apply it to the absolute delta.\n- Typical classes: within tolerance; nothing billed although something was due; billed less than due beyond tolerance; billed more than due beyond tolerance; billed with no account. Use the exact labels the spec gives.\n- Delta = billed - expected, sign preserved. Omit rows where both sides are zero unless the spec says to list every account.\n- Output exactly the columns, order, sort and number formats the spec states.\n\n## 7. Self-checks before finishing\n1. Row count and set of ids plausible; no id appears twice; every merged-away id is absent as its own line.\n2. Pick 5 accounts with unusual features (multi-period invoice, credit note, merged, bill-to, mid-period change, churn) and recompute them by hand from the raw rows.\n3. Sum of credit-note effects: confirm each counted credit note's original also counted.\n4. Totals by class look sane (most accounts match; a few percent off).\n5. Output parses with a strict reader; no trailing spaces; consistent decimals.\n","# Subscription billing reconciliation\n\nGoal: for each customer, compute EXPECTED (from the contract schedule) and BILLED (from invoices) for one period in one reporting currency, then classify the gap. Write the rules down before coding; most errors are rule mistakes, not arithmetic.\n\n## 1. Read every rule source first\nSpecs rarely sit in one place. Read all prose (memos, chat logs, READMEs) end to end, in time order. Later messages override earlier ones. Note every definition (period length, tolerance, rate choice, who is in scope) and every exception. Re-read the rules after your first output and check each one against the data, not just the first mention.\n\n## 2. Expected amount (from the contract)\n- Schedule amounts are per billing term (monthly, quarterly, annual). Normalise to the period: monthly x1, quarterly \u002F3, annual \u002F12, unless the spec says otherwise.\n- Contract changes (upgrade, downgrade, price change, pause) take effect on their effective date. Build a per-day timeline and sum per day, rather than assuming one price for the whole period.\n- Proration is by calendar days in the period (use the actual day count of the period, not a flat 30, unless told).\n- Status rules: trials bill zero; the churn\u002Ftermination date is normally the last day of service, inclusive; days after it earn nothing. Check which date convention the spec uses.\n- Dates arrive in mixed formats; parse each explicitly and validate that none failed.\n\n## 3. Billed amount (from invoices)\n- An invoice export is often an event log: the same invoice id can appear many times. Keep only the latest snapshot per id (by export timestamp), then apply status filters. Draft and void never count; paid and open do. A later snapshot can cancel an invoice that an earlier one showed as paid.\n- An invoice covering a multi-period service window contributes only the share of days that fall inside the reporting period: overlap days \u002F total window days. Do not count by issue date alone.\n- Credit notes reduce billed revenue. A credit note belongs wherever the invoice it corrects belongs: attribute it to the same customer AND the same service period as the original, regardless of its own issue date or its own (often blank or wrong) customer field. If the original is outside the period, the credit note is outside it too. If the original does not count (void, draft, cancelled), the credit note is moot and is ignored.\n- Never infer a credit note's customer from its own text when it carries a link to the invoice it corrects.\n\n## 4. Entity resolution\n- Customer names come as free text from several systems. Normalise case, punctuation, whitespace, accents, `&` vs `and`, and legal-form suffixes (Inc, Ltd, GmbH, AG, PLC, BV, LLC...). Prefer authoritative keys in this order: account id, then domain, then normalised name.\n- Merged duplicates: invoices of a merged-away account belong to the surviving account. Follow chains (A merged into B merged into C) to the final survivor. Decide explicitly how the survivor's status and contract timeline interact with the duplicate's; if a surviving record is churned, its own churn rule applies to the merged entity.\n- Parent\u002Fchild accounts (a child billed through a billing parent): children roll up to the parent. If the parent is churned or otherwise no longer a valid billing target, children are reported on their own lines. Follow chains and watch for cycles.\n- Anything that cannot be tied to an account becomes its own unmatched line, grouped by its cleaned-up name, if the spec asks for it. Do not silently drop it and do not force-match it to the nearest account.\n\n## 5. Currency and rounding\n- Convert each side at the rate the spec names for that side: for example schedule at a period average or period-end rate, invoices at the rate on their own issue date. Use the same table for both and the spec's definition of average (simple mean over published days).\n- Rate tables skip weekends and holidays: use the last published rate on or before the date.\n- Keep full precision (use Fraction\u002FDecimal) through the whole computation and round only once at output, half up, to 2 decimals. Do not round per day or per invoice.\n- Convert after prorating or before it consistently; the result is identical, but mixing them with per-step rounding is not.\n\n## 6. Classification\n- Tolerance is usually max(absolute floor, percentage of expected). Apply it to the absolute delta.\n- Typical classes: within tolerance; nothing billed although something was due; billed less than due beyond tolerance; billed more than due beyond tolerance; billed with no account. Use the exact labels the spec gives.\n- Delta = billed - expected, sign preserved. Omit rows where both sides are zero unless the spec says to list every account.\n- Output exactly the columns, order, sort and number formats the spec states.\n\n## 7. Self-checks before finishing\n1. Row count and set of ids plausible; no id appears twice; every merged-away id is absent as its own line.\n2. Pick 5 accounts with unusual features (multi-period invoice, credit note, merged, bill-to, mid-period change, churn) and recompute them by hand from the raw rows.\n3. Sum of credit-note effects: confirm each counted credit note's original also counted.\n4. Totals by class look sane (most accounts match; a few percent off).\n5. Output parses with a strict reader; no trailing spaces; consistent decimals.\n",{"name":5,"description":7},"main","01960aeb08909dbd0c1a2d4f219cdb300099b8b9",0,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills","https:\u002F\u002Fgetedge.cc","https:\u002F\u002Fgithub.com\u002Fgetedgehq","2026-11-12 10:05:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add getedgehq\u002Fskills --skill subscription-billing-reconciliation",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill subscription-billing-reconciliation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill subscription-billing-reconciliation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fsubscription-billing-reconciliation\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"DERIVATION.json","REFERENCE","参考文档",1594,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fsubscription-billing-reconciliation\u002FDERIVATION.json",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"EVALS.md",1141,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fsubscription-billing-reconciliation\u002FEVALS.md",{"path":56,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":15},"LICENSE","许可证",10756,[60,68,76,83,90,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CFVPC1P7JN60J5AN9AZZ5G","zero-downtime-cloud-move","Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CFVH8VN6G2KE8PBFD1CRMN","zayats-ceo-branding","Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CFV9BB7G8K8CX9RKZ3GECX","yc-app-roast","YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks \"what would a YC partner think\", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-roast\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CFV11Z1HB9EEWFQ6PCJ98X","yc-app-review","YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press \"Send my notes\" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-review\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CFTSVJV7XCSW62W39MX8CZ","x-growth-playbook","X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says \"analyse my X posts\", \"what works on my Twitter\", \"how do I grow on X\", \"what should I post next on X\", \"audit my X account\", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CFTK101S3P00MQ129G5YNH","workplan","Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: \"workplan\", \"work plan\", \"create a plan\", \"what's the plan\", \"where was I\", or when Claude detects a multi-step task that needs tracking.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FSKILL.md",[],[]]