CtrlK
BlogDocsLog inGet started
Tessl Logo

test-driven-development

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/test-driven-development/SKILL.md

The canonical home for this skill is test-driven-development in addyosmani/agent-skills

SKILL.md
Quality
Evals
Security

Low

Low-risk findings.

1 low severity finding. Worth noting, but not necessarily harmful.

Low

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 "Browser Testing with DevTools" section of SKILL.md instructs the agent to navigate to pages and read DOM, console, and network responses (i.e., arbitrary web page/browser content), which are untrusted third-party sources that the agent is expected to interpret as part of its debugging workflow and could materially influence its actions.

Report incorrect finding
Repository
finlay611/agent-skills
Audited
Security analysis
Snyk

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.