Fde review value
Privacy-safe forward-deployed engineering skills for Claude Code, Codex, and AGENTS.md-compatible agents
npx -y skills add inbusiness23/fde-skill --skill fde-review-valueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Compare a workflow baseline with real test results, calculate whether the solution pays for itself within 30 days, and decide to expand, fix once, stop, or wait. Use after a controlled live test and when transferring ownership to the operating team.
SKILL.md
2.6 KB, 476 tokens by cl100k_base, as published. Nobody here has run it
Check the Value and Decide What Happens Next
Use plain language. Explain any necessary technical word immediately.
Facts needed
Get the baseline and live-test dates, number and mix of items handled, completed work, cases sent to a person, staff minutes, quality, mistakes, sales or successful results, customer problems, staff corrections, extra profit or prevented loss, software and connection costs, review and support costs, and the one-time project cost.
Calculate
Compare like periods or exposure units. Convert every recurring benefit and cost to the same 30-day basis before combining them. Normalize shorter periods only when their volume and work mix are comparable; otherwise return wait and name the additional evidence required.
Monthly value = monthly extra profit + monthly losses prevented + monthly useful work created from freed time − monthly software cost − monthly connection cost − monthly staff review cost − monthly ongoing support cost
Payback days = one-time project cost ÷ real monthly value × 30
Count freed time only when it reduces spending, avoids hiring, completes more valuable work, or creates another measured result. Do not count the same benefit twice.
If real monthly value is zero or negative, report no payback instead of calculating payback days. Do not expand; choose stop when the result is conclusive or wait when the test is too small or too short.
Decide
- Expand: Quality holds, real results show payback within 30 days, value safely beats ongoing cost, failures stay limited, and the owner accepts responsibility.
- Fix once: One small, understood repair can likely make it pass without making the project bigger.
- Stop: Payback is too slow, value or volume is too low, trusted information is missing, staff will not use it, review uses up the benefit, or risk cannot be contained.
- Wait: The test was too small or too short; name the exact extra group or time needed.
Read value-scorecard.md for the results sheet and ownership checklist.
Return
Return old versus new results, measurement periods and exposure, normalization method, assumptions, monthly value, payback days or no payback, quality and safety status, decision, next test size, owner, and next review date. Keep estimates separate from real results.
What ships with it: 2 files
1.5 KB alongside SKILL.md
agents/
- openai.yaml236 B
references/
- value-scorecard.md1.3 KB