Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. Use this to build a cash forecast, extend runway, improve working capital, decide where cash should sit, or assess exposure to a bank, currency, or customer concentration.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Profitable companies fail on cash. Earnings are an opinion arrived at through accruals; cash is a balance you either have on the day or do not.
The indirect method — net income adjusted for non-cash items — is right for reporting and nearly useless for operating. Build a direct forecast of receipts and disbursements by week, from actual expected timing.
Thirteen weeks is the working horizon: long enough to act, short enough to be accurate. Roll it weekly and compare last week's forecast against what happened. A forecast never checked against outturn does not improve, and its errors are the most useful information it produces.
Model timing, not just amount. A receipt that arrives four days late is the same money and a different liquidity position.
Runway is cash divided by net burn, but the useful version is scenario-based: the plan, a downside where revenue underperforms, and the case where a large receivable slips.
Know your decision points in advance — the date by which a raise must start, the date a cost reduction must be committed to take effect in time. Decision dates always precede the cash-out date, often by more than people assume, and discovering that late removes the good options.
Cash is trapped in the cycle between paying for inputs and being paid for output:
operations:supply-chain-and-logistics.A week off the cycle is permanent working capital released, and it costs nothing in interest.
Concentration in one bank is a single point of failure, as depositors have periodically rediscovered. Spread operating balances against counterparty limits, and hold reserves in instruments whose maturity matches when the money is needed.
Do not reach for yield with money you have a date for. The return on operating cash is not worth the liquidity risk, and treasury losses of this kind are always described afterwards as conservative investments.
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.
Cash visibility and forecasting: Kyriba, Trovata, Tesorio, and similar. Bank portals plus a spreadsheet cover a single-bank, single-currency position honestly.
Payments and AP: Bill.com, Tipalti, Ramp, Brex, and similar.
The control that matters is not in the tool list — it is dual approval on payment release, by whatever means you get it.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。