CC project-investment-analysis
Evaluates a discrete investment, project or acquisition from its cash flow stream — NPV, IRR with every root reported when the stream has more than one, MIRR, profitability index and project selection under a capital budget, equivalent annuities and replication for unequal lives, payback and discounted payback, project return on capital and EVA, synergy value with the ceiling price it supports, the value of control and its expected value, the four-number acid test for a deal, and control premiums and minority discounts. Use when deciding whether to take a project, ranking competing projects, comparing projects with different lives, sizing a capital budget, testing whether a stream is truly incremental, valuing synergy or control, pricing a majority or minority stake, or setting the maximum price for an acquisition.
Evaluates a discrete investment, project or acquisition from its cash flow stream — NPV, IRR with every root reported when the stream has more than one, MIRR…
As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6485 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Execution cost. Instruction body is 6485 tokens
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 826: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 17 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.