file-processing 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
• Description mentions 'visualization capabilities' but no visualization functions are provided in the skill or supporting scripts.
• High-risk permission hints: Shell or command execution
• The skill claims to work 'without requiring users to write code', but the instructions and examples are heavily code-based, which may be confusing.
• The skill relies on a Python environment and the `shell` tool; it does not specify how to ensure Python is available or handle missing dependencies.