extract-parameters-from-full — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited extract-parameters-from-full (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Wraps the quantitative-triage system prompt at system-prompt.txt (next to this file) and applies it to a PlanExe report the user supplies. Output is strict JSON matching the schema in the system prompt — no markdown, no commentary.
Not for: full report summarisation, narrative analysis, code generation. The system prompt explicitly forbids those.
system-prompt.txt. Apply every "Important", "Additional modelling rules", and "Formula and dependency rules" section as you generate each field.<report-basename>.parameters.json next to the report.unit: "fraction". Never value: 60 for 60%.key_values, missing_values_to_estimate, or the object's own depends_on."DKK", "people", "fraction"). Downstream consumers — generate-calculations, run-scenarios, monte-carlo — read these directly and do not parse formula_hint or pattern-match on tokens. The LLM is the single authority for both fields.| Mistake | Fix |
|---|---|
Wrapping JSON in ``` `json ``` fences | Raw JSON only — the system prompt forbids markdown |
| Returning >8 key_values "because the report has many" | Hard cap. Triage. The point is to surface the few that matter |
Including suggested_low/base/high by default | Only include when essential to the value's meaning |
Using value: 60 for "60%" | Use value: 0.6 and unit: "fraction" |
Citing variable in formula_hint that isn't declared anywhere | Either add it to missing_values_to_estimate or rewrite the formula |
| Picking a descriptive timeline value over a funding gate | Prefer the gate — it determines pass/fail |
system-prompt.txt/Users/neoneye/git/PlanExe-web/20250720_faraday_enclosure_report.html~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.