antithesis-setup
Scaffold the Antithesis harness: initialize the working directory, write Dockerfiles and docker-compose.yaml with build directives, and prepare to submit your first Antithesis test run.
57
65%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./antithesis-setup/SKILL.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
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
Third-party content exposure detected (high risk: 0.80). The skill explicitly requires loading and interpreting public web resources as part of its required workflow—see the language refs that say to "load https://api.github.com/repos/antithesishq/antithesis-sdk-cpp/tags", "https://proxy.golang.org/…", "https://pypi.org/pypi/antithesis/json", and to use the antithesis-documentation skill to fetch docs (https://antithesis.com/docs/…)—which the agent must read to choose SDK versions, flags, and build steps that materially affect tool use and next actions, exposing it to untrusted third‑party content.
- Repository
- antithesishq/antithesis-skills
- Commit
f837248
- 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.