consulting-proposal-advisor Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• Low GitHub adoption signal
• SKILL.md references multiple reference files (intake-questions.md, proposal-structure.md, ppt-template-usage.md, engagement-types.md, examples.md, quality-checklist.md) that are not present in the submitted skill directory. This makes the skill incomplete and potentially non-functional as described.
• Financial research output is not financial advice; require human review before any live investment decision
• The skill mentions local scripts for offline Codex use, but no scripts are included in the package; only a package.json with a dependency is present.