Agent skill

Finance Billing Ops

by affaan-m in affaan-m/ECC

Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC.

MITAuto-check passed

Install Finance Billing Ops

skills CLI
$ npx skills add affaan-m/ECC --skill finance-billing-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC finance-billing-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/finance-billing-ops .claude/skills/finance-billing-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
finance-billing-ops
GitHub stars
277k
Used in
1 other repo
Token cost
~958 tokens
SKILL.md length
422 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC.

  • Works in 4 steps: Start from the freshest billing evidence → Separate customer incidents from product… → Inspect code-backed billing behavior → …
  • The user wants a sales snapshot
  • SKILL.md covers Skill Stack, When to Use, Guardrails and Workflow, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Finance Billing Ops is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • The user wants a sales snapshot
  • Pricing comparison
  • Duplicate-charge diagnosis
  • Code-backed billing reality instead of generic payments advice

Example prompts

  • “/finance-billing-ops”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Start from the freshest billing evidence
  2. Separate customer incidents from product truth
  3. Inspect code-backed billing behavior
  4. End with a decision and product gap

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Finance Billing Ops loads about 958 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 422 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~958

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 2d515e4, republished under its MIT licence (© affaan-m). 422 words, ~958 tokens.

Download SKILL.mdSave it as .claude/skills/finance-billing-ops/SKILL.md (or your agent's skills folder).
name
finance-billing-ops
description
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.
metadata.origin
ECC

Finance Billing Ops

Use 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.

This 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.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

  • customer-billing-ops for customer-specific remediation and follow-up
  • research-ops when competitor pricing or current market evidence matters
  • market-research when the answer should end in a pricing recommendation
  • github-ops when the billing truth depends on code, backlog, or release state in sibling repos
  • verification-loop when the answer depends on proving checkout, seat handling, or entitlement behavior

When to Use

  • user asks for Stripe sales, refunds, MRR, or recent customer activity
  • user asks whether team billing, per-seat billing, or quota stacking is real in code
  • user wants competitor pricing comparisons or pricing-model benchmarks
  • the question mixes revenue facts with product implementation truth

Guardrails

  • distinguish live data from saved snapshots
  • separate:
    • revenue fact
    • customer impact
    • code-backed product truth
    • recommendation
  • do not say "per seat" unless the actual entitlement path enforces it
  • do not assume duplicate subscriptions imply duplicate value

Workflow

1. Start from the freshest billing evidence

Prefer live billing data. If the data is not live, state the snapshot timestamp explicitly.

Normalize the picture:

  • paid sales
  • active subscriptions
  • failed or incomplete checkouts
  • refunds
  • disputes
  • duplicate subscriptions
Show full SKILL.md (182 more words)Show less
2. Separate customer incidents from product truth

If the question is customer-specific, classify first:

  • duplicate checkout
  • real team intent
  • broken self-serve controls
  • unmet product value
  • failed payment or incomplete setup

Then separate that from the broader product question:

  • does team billing really exist?
  • are seats actually counted?
  • does checkout quantity change entitlement?
  • does the site overstate current behavior?
3. Inspect code-backed billing behavior

If the answer depends on implementation truth, inspect the code path:

  • checkout
  • pricing page
  • entitlement calculation
  • seat or quota handling
  • installation vs user usage logic
  • billing portal or self-serve management support
4. End with a decision and product gap

Report:

  • sales snapshot
  • issue diagnosis
  • product truth
  • recommended operator action
  • product or backlog gap

Output Format

text
SNAPSHOT
- timestamp
- revenue / subscriptions / anomalies

CUSTOMER IMPACT
- who is affected
- what happened

PRODUCT TRUTH
- what the code actually does
- what the website or sales copy claims

DECISION
- refund / preserve / convert / no-op

PRODUCT GAP
- exact follow-up item to build or fix

Pitfalls

  • do not conflate failed attempts with net revenue
  • do not infer team billing from marketing language alone
  • do not compare competitor pricing from memory when current evidence is available
  • do not jump from diagnosis straight to refund without classifying the issue

Verification

  • the answer includes a live-data statement or snapshot timestamp
  • product-truth claims are code-backed
  • customer-impact and broader pricing/product conclusions are separated cleanly

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/finance-billing-ops of affaan-m/ECC.

Open the folder on GitHubat commit 2d515e4

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Finance Billing Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Finance Billing Ops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Finance Billing Ops this skillaffaan-m/ECC277k1 repos~958Automated safety check: PassMIT
Pricingsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
Ops Revenuedavepoon/buildwithclaude3.6k—~1.6kAutomated safety check: NotesMIT
Pricing Strategyphuryn/pm-skills27k—~913Automated safety check: PassMIT
Pricing Strategyalirezarezvani/claude-skills28k1 repos~3.5kAutomated safety check: PassMIT
Billing Automationwshobson/agents40k13 repos~473Automated safety check: PassMIT

Similar skills

  • Pricing

    sickn33/agentic-awesome-skills

    When the user wants help with pricing decisions, packaging, or monetization strategy.

    47k GitHub starsUsed in 1 repo~1.9k tokens
    Sales & SupportAuto-check passed
  • Ops Revenue

    davepoon/buildwithclaude

    Revenue and costs tracker. An agent skill from davepoon/buildwithclaude.

    3.6k GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check: notes
  • Pricing Strategy

    phuryn/pm-skills

    Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity.

    27k GitHub stars~913 tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Pricing Strategy

    alirezarezvani/claude-skills

    Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

    28k GitHub starsUsed in 1 repo~3.5k tokens
    Sales & SupportAuto-check passed
  • Billing Automation

    wshobson/agents

    Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.

    40k GitHub starsUsed in 13 repos~473 tokens
    Backend & APIsAuto-check passed
  • Pricing Strategist

    alirezarezvani/claude-skills

    A skill your agent uses when designing or revisiting product pricing — selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid), running Van Westendorp…

    28k GitHub stars~2.3k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

More from affaan-m/ECC

All 682 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    277k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed
  • Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    277k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    277k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    277k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    277k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Set an ECC-specific frontend design direction for production UI work.

    277k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

Questions about Finance Billing Ops

What does Finance Billing Ops do?

Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Finance Billing Ops is an agent skill from affaan-m/ECC. Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC.

When should I use Finance Billing Ops?

Finance Billing Ops fits situations like: the user wants a sales snapshot; pricing comparison; duplicate-charge diagnosis; code-backed billing reality instead of generic payments advice.

How do I install Finance Billing Ops in Claude Code?

Run `npx skills add affaan-m/ECC --skill finance-billing-ops -a claude-code`. Or copy the skill folder (skills/finance-billing-ops in affaan-m/ECC) into .claude/skills/finance-billing-ops in your project. Claude Code loads it when a task matches its description.

How do I install Finance Billing Ops in Codex?

Run `npx skills add affaan-m/ECC --skill finance-billing-ops -a codex`. Or copy the skill folder (skills/finance-billing-ops in affaan-m/ECC) into .agents/skills/finance-billing-ops in your project. Codex loads it when a task matches its description.

Can I use Finance Billing Ops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill finance-billing-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finance-billing-ops, .gemini/skills/finance-billing-ops, .github/skills/finance-billing-ops and .opencode/skills/finance-billing-ops in your project.

What does Finance Billing Ops need to run?

SKILL.md names no scripts, command-line tools or credentials: Finance Billing Ops is instructions for the agent only.

Does Finance Billing Ops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Finance Billing Ops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Finance Billing Ops use?

Finance Billing Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Finance Billing Ops use?

About 958 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Finance Billing Ops?

Skills that share tags, products or a category with Finance Billing Ops: Pricing (sickn33/agentic-awesome-skills, 47k stars), Ops Revenue (davepoon/buildwithclaude, 3.6k stars), Pricing Strategy (phuryn/pm-skills, 27k stars) and Pricing Strategy (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Finance Billing Ops?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.