excel-debug-extraction
Iteratively debug Excel structure with exploratory scripts before writing extraction logic
55
61%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./benchmarks/gdpval/skills/excel-debug-extraction/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow suggests running debug Python scripts that load a user-provided Excel file at runtime (`load_workbook('file.xlsx')`) and then print cell values/row contents into the logs/LLM-readable output (e.g., first 10 rows, header mappings, sampled row values), which for “files received from external sources” would be outsider-authored free text.
- Repository
- HKUDS/OpenSpace
- Commit
c5a9c4b
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.