本文へ移動
cccskills
無料GitHub で公開

cost-accounting

Establishes what something actually costs — fixed, variable and mixed cost behavior, absorption versus variable costing, job-order, process and activity-based methods, breakeven and operating leverage, and price/volume/mix decomposition. Use this to set a price floor, explain why revenue or margin moved, decide make versus buy, judge whether a product line earns its place, or work out how an allocation basis is distorting a reported margin.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md4.4 KB
  • references/sources.md1.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Cost accounting

Most bad pricing decisions, bad product-line decisions, and bad margin arguments come from the same place: nobody agrees what the thing costs.

Classify cost behavior before you allocate anything

  • Fixed costs do not move with volume — within a relevant range. Outside that range they step, and the step is usually large: another shift, another facility, another tier of licensing.
  • Variable costs move with each unit: materials, payment processing, per-unit fulfillment, usage-based infrastructure.
  • Mixed costs have both, and most real accounts are mixed. Split them with high-low or a regression on historical volume rather than guessing the proportion.

The split is not academic. Variable cost sets the floor for one more incremental order. Fully loaded cost sets the floor for the business as a whole. Confusing the two is how companies price themselves into volume that loses money.

Know which costing basis you are looking at

Absorption costing puts fixed production overhead into inventory and releases it when the unit sells. Variable costing expenses that overhead as incurred.

Absorption is what external reporting requires. Variable is what decisions want. The consequence worth carrying: under absorption, producing more than you sell moves fixed cost onto the balance sheet and raises reported profit without a single additional sale. When margin improves and inventory grows in the same period, check whether that is what happened.

Match the costing method to how the work actually runs

  • Job-order — distinct, identifiable jobs. Construction, custom manufacture, print runs, agency engagements. Cost accumulates per job.
  • Process — continuous, homogeneous output. Chemicals, food, high-volume components. Cost accumulates per period and divides across equivalent units.
  • Activity-based — worth the overhead when indirect cost is large and consumed unevenly. Its value is rarely precision; it is discovering that a low-volume product consumes a disproportionate share of support, setup, or handling.

Choose an allocation driver that causes the cost. Allocating overhead on revenue is not costing, it is redistribution — it guarantees the largest product looks worst and tells you nothing.

Breakeven, margin of safety, and operating leverage

Contribution margin is revenue less variable cost. Breakeven volume is fixed cost divided by contribution per unit; margin of safety is how far current volume sits above it.

Operating leverage follows from the mix: a high fixed-cost structure amplifies profit on the way up and losses on the way down. It is a deliberate choice about how much volatility the business can absorb, and it should be made deliberately rather than accumulated.

Decompose price, volume and mix

Revenue moved for three reasons and you cannot manage any of them until they are separated.

  • Price — the change in realized price applied at actual volume.
  • Volume — the change in units applied at the original price.
  • Mix — the shift in what sold, toward or away from higher-margin items.

This is the single most useful technique here and the one most often skipped. Without it, a mix shift toward an expensive product gets reported as a pricing win, and a discount gets buried under volume growth.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Allocate overhead on revenue and present the result as a product margin.
  • Quote a long-term price off variable cost. It covers the incremental order and nothing else.
  • Compare absorbed unit cost across periods without checking whether production volume changed.
  • Attribute a revenue change to price without separating volume and mix.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する