Install
$ agentstack add skill-krillinai-growee-skills-growth-budget-allocation ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Growth Budget Allocation
Turn one bounded resource envelope into a traceable allocation or reallocation proposal. Reconcile what is authorized and movable, protect customer and operating obligations, compare commitments on compatible incremental evidence, and stage decisions by maturity, marginal return, capacity, risk, and reversibility. Allocation is a governed portfolio decision, not equal division, target backsolving, historical credit, or permission to spend.
Read [budget-allocation-contract.md](references/budget-allocation-contract.md) before accepting the envelope, resource states, allocation units, periods, currencies, owners, approvals, or current version. Read [portfolio-economics-and-evidence.md](references/portfolio-economics-and-evidence.md) before comparing customer value, attribution, incrementality, costs, cash, capacity, overlap, marginal returns, or protected obligations. Read [allocation-scenarios-and-decision-gates.md](references/allocation-scenarios-and-decision-gates.md) before creating scenarios, allocation bands, reserves, gates, or a change proposal. Read [governance-market-transfer-and-actions.md](references/governance-market-transfer-and-actions.md) before versioning, transferring across markets, using personal data, assigning decision rights, or proposing external actions. Read [output-contract.md](references/output-contract.md) before delivery. Use [playbook-sources.md](references/playbook-sources.md) for the pinned Growth Playbook basis.
Select One Mode
| Mode | Use | | --- | --- | | audit | Inspect a current budget or resource portfolio for false availability, incompatible bases, omissions, duplicate value, weak evidence, concentration, hidden obligations, or governance failure | | design | Build an evidence-bounded allocation proposal from a declared envelope, strategy, constraints, candidate commitments, and decision horizon | | reallocate | Preserve the current approved version and propose bounded source-to-destination changes after material evidence, cost, cash, capacity, risk, obligation, or strategy changes |
Name one primary mode and state draft, reconciling, decision-ready, approval-pending, approved-record, superseded, or expired. State does not prove availability, transfer, execution, spend, or results.
Use growth-strategy for arenas, portfolio thesis, commitment classes, and exclusions; growth-operations for one proposed commitment; growth-model-design for one opportunity; acquisition-strategy for channel strategy and channel-only allocation; monetization for detailed economics; growth-measurement for calibrated outlooks; and growth-operations for cycle-wide budget, capacity, and calendar reconciliation. This Skill owns the cross-functional comparable ledger, protected and discretionary pools, allocation bands, reallocation record, and approval-ready resource change.
Freeze The Allocation Contract
Record allocation ID and version, mode and state, decision and accountable owner, contributors, finance and specialist reviewers, required approvers, strategy and planning-cycle versions, scope and exclusions, products and business models, customers and participant roles, markets and locales, fiscal and calendar periods, decision horizon, evidence cutoff, review and expiry, currencies and exchange-rate conventions, accounting and cash bases, resource units, current allocation version, superseded version, privacy boundary, and external-action boundary.
Define the total envelope and every sub-envelope. Use exactly verified, inferred, unavailable, or not applicable for evidence-bearing claims. Keep reported signal, request, recommendation, approval, authorization, commitment, encumbrance, availability, transfer, spend, accrual, verification, and result separate. Do not invent resources, approvals, customers, returns, conversion, retention, LTV, costs, cash, capacity, timing, probabilities, risks, or outcomes.
Reconcile Resource States
Reconcile requested, recommended, approved, authorized, committed, encumbered, spent, accrued, prepaid, recoverable, available, protected, discretionary, contingent, reserved, and unavailable resources. A department request, accounting allocation, target, prior-year budget, executive preference, or open role is not available capacity.
Separate cash, accountable people, specialist time, management attention, product and engineering capacity, data and creative supply, partner bandwidth, inventory, customer exposure, and operational risk. Record period, owner, funding source, restrictions, notice, lead time, ramp, utilization, transferability, expiry, and proof. Do not double-book a person, team, vendor commitment, customer population, or dollar.
Separate sunk, fixed, variable, step, allocated, shared, committed, avoidable, recoverable, salvage, exit, decommissioning, opportunity, and residual cost. Sunk cost, work completed, publicity, or sponsorship does not justify future allocation. Compare continuation with stage, narrow, preserve, defer, pause, stop, salvage, and responsible exit from the current decision point.
Gate Numeric Allocation
Produce recommended amounts, percentages, weights, ceilings, floors, reserves, source-to-destination deltas, or dated release bands only when the envelope and prior spend share a verified basis; restrictions, commitments, encumbrances, recoveries, protected obligations, and discretionary availability reconcile; allocation units have compatible evidence or explicit separate views; capacity and dependencies are feasible; and accountable owners and required approvers are attributable. A reported total, list of requests, verbal approval, executive demand, or arithmetic remainder does not pass this gate.
If any decision-critical condition is unavailable, keep the state draft or reconciling. Preserve user-supplied numbers as reported states and show valid arithmetic only for diagnosis; do not turn them into a recommended allocation. Return a nonnumeric portfolio structure, unresolved resource ledger, first limiting gate, evidence requests, and conditions for a later numeric version. Do not invent allocation ratios, normalized scores, protected floors, uncertainty reserves, approval roles, deadlines, phases, ordering, return thresholds, or release criteria to make the proposal look complete.
Build The Portfolio Ledger
For each allocation unit record stable ID and version, portfolio class, owner and decision rights, customer and problem, strategic choice, mechanism, customer value, retained outcome, incremental business effect, evidence and counterevidence, current resource, requested band, resource type and period, maturity, full and marginal economics, cash, capacity, dependencies, overlap, opportunity cost, concentration, risk, guardrails, obligations, earliest decision-changing evidence, and scale, cap, stop, rollback, exit, expiry, and review rules.
Do not allocate equally by initiative count or apply a universal ratio. Do not backsolve assumptions or budget to make a target true. Separate target, baseline, opportunity, scenario, forecast, plan, budget, approval, actual, attribution, association, causal estimate, and recommendation.
Reconcile customers, accounts, lifecycle states, products, markets, and economic effects before comparing. Expose overlap, interaction, halo, cannibalization, displacement, substitution, and unknown residual. Do not add attribution, experiment lift, forecast upside, opportunity headroom, cost savings, and realized outcomes or give every contributor credit for the same value.
Compare Incremental Economics, Cash, And Capacity
Attributed revenue or ROAS is not automatically incremental retained contribution. Historical average CAC, ROI, LTV, payback, conversion, or retention describes a past population and does not establish the next resource band's marginal return. Define identity, eligibility, source, cohort, window, maturity, attribution model, counterfactual evidence, and reconciliation. Route detailed work to the owning analytical Skill.
Include relevant product, engineering, design, data, creative, sales, channel, partner, support, success, incentives, refunds, chargebacks, payment, fraud, infrastructure, security, privacy, compliance, finance, procurement, implementation, migration, training, maintenance, decommissioning, working-capital, and opportunity costs. Separate bookings, billings, revenue, gross profit, contribution, accounting profit, cash, and valuation.
Time-phase implementation outflow, hiring and onboarding, ramp, adoption, benefit maturity, billing, collections, refunds, inventory, incentives, renewal, useful life, replacement, exit, and residual obligations. A high annual ROI can still fail a cash, payback, capacity, or customer-protection gate.
Protect Required Pools
Protect explicitly evidenced floors for existing-customer value, support, maintenance, reliability, security, privacy, compliance, accessibility, fraud prevention, measurement integrity, contractual service, documentation, incident readiness, responsible transition, and decommissioning. Record owner, standard, resource floor, evidence, exception authority, risk, escalation, review, and exit condition.
Do not call protected work nongrowth or offset noncompensable harm with financial upside. Expose the residual discretionary envelope only after approved restrictions, commitments, reserves, and protected obligations reconcile.
Design Scenarios And Allocation Bands
Build conditional scenarios only for uncertainties that change an allocation decision. Keep assumptions, sources, ranges, contradictions, lags, maturity, cash, capacity, risk, trigger, and response explicit. Do not invent probabilities, average incompatible scenarios into an expected return, show unsupported decimal precision, or guarantee performance.
Identify robust commitments, protected reserves, contingent commitments, hedges, options, and irreversible commitments. Use sensitivity to name the threshold where a decision changes. Allocate in evidence-gated bands with prerequisites, amount or resource range, maturity, owner, positive, negative, harmful, invalid, and inconclusive rules, cap, stop, rollback, expiry, and next review.
When the numeric gate does not pass, describe only the role of possible pools, bands, reserves, options, and gates. Do not assign a value, percentage, order, date, or owner that the supplied evidence and authority do not support.
Decide And Reallocate
Use preserve, fund, stage, cap, reduce, pause, stop, reserve, reject, or unresolved. For each decision state the current approved amount, proposed amount or band, source pool, destination, timing, evidence and contradiction, customer and strategic effect, incremental economics, cash, capacity, overlap, opportunity cost, dependencies, protected obligations, risks, conditions, required approvers, effective date, expiry, and review.
In reallocate, preserve the prior version and create an explicit bridge. Immature, selected, incompatible, underpowered, invalid, or guardrail-harming evidence cannot become a conclusive winner or immediate transfer. Keep the current allocation, narrow exposure, or request decision-changing evidence as warranted. Never imply that a proposed change was approved or executed.
Govern Markets, People, And Actions
Treat every market as a new customer, product, channel, platform, metric, economic, cash, capacity, risk, operating, evidence, owner, and approval boundary. Translation and currency conversion do not validate transfer. For China, require current direct sources and locally accountable expertise while avoiding legal, tax, accounting, regulatory, provider-availability, approval, causal, or performance conclusions.
Use aggregate, redacted, pseudonymous, minimum-necessary evidence. Do not expose credentials, payment details, private messages, health or financial data, protected traits, precise locations, employee reviews, compensation, ratings, raw identities, or complete histories. Do not rank individuals for budget, pricing, targeting, service, credit, or employment decisions.
Deliver In Order
Follow [output-contract.md](references/output-contract.md). Deliver the contract; resource reconciliation; protected pools; portfolio and evidence ledger; compatible economic, cash, capacity, overlap, and risk views; scenarios and sensitivity; allocation and change register; gates, governance, handoffs, pinned sources, approval-ready external actions, and completion record.
External-Action Boundary
Create and read local artifacts only. Do not access authenticated finance, banking, planning, procurement, HR, payroll, advertising, analytics, warehouse, CRM, billing, product, cloud, partner, or communication systems; export or join personal data; approve or transfer funds, budgets, headcount, capacity, permissions, or customer exposure; purchase; sign; hire; fire; reorganize; change bids, campaigns, prices, products, contracts, records, or systems; launch; pause; contact; publish; send; spend; procure; deploy; or claim execution or results without separate task-level authorization and controls.
Keep One Output Language
Use the requested output language consistently across headings, prose, tables, labels, and actions. When no language is explicit, match the user's dominant language; market, locale, platform, and source language do not override it.
For Simplified Chinese, write natural Simplified Chinese and translate ordinary business or analytical jargon instead of embedding English words such as owner, brief, listing, cohort, baseline, benchmark, guardrail, gate, finding, roadmap, workflow, and handoff. Keep only proper names, standard acronyms after a Chinese first-use definition, machine tokens or IDs, code, formulas, filenames, URLs, and exact quotations where necessary.
For English, use idiomatic English and do not add Chinese glosses except for proper nouns or quoted source text. Use multiple languages only when explicitly requested, and keep each version in a separate labeled section rather than mixing languages within sentences or tables. Do not alternate languages for emphasis or perceived expertise.
Completion Gate
Confirm the output passes [output-contract.md](references/output-contract.md); the envelope and resource states reconcile; protected obligations remain funded; units and bases are compatible or separate; customers and effects are deduplicated; target, attribution, average history, and sunk cost did not become future return; full costs, cash, capacity, risk, and opportunity cost remain visible; scenarios preserve uncertainty; every change has gates and approvers; market and privacy boundaries hold; specialist work is routed; recommendation is not authorization; and no external action occurred.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: krillinai
- Source: krillinai/growee-skills
- License: MIT
- Homepage: www.clawee.ai/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.