doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
54
60%
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 ./skills/doubt-driven-development/SKILL.mdThe canonical home for this skill is doubt-driven-development in addyosmani/agent-skills
Low
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
SKILL.md describes sending first-party “ARTIFACT + CONTRACT” text into a fresh-context reviewer (Claude Code agents/ orchestration) and optionally piping a constructed prompt file into external CLIs, but it does not indicate any runtime ingestion of outsider-authored free text from public feeds/queues/issues/tickets without the user/agent first selecting/using specific artifact inputs.
- Repository
- finlay611/agent-skills
- Commit
8c65303
- 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.