dependency-analysis
Analyze package, lockfile, import/module, build, runtime-service, and third-party dependency relationships, risks, upgrades, and supply-chain health. Use when dependencies themselves are the primary object. Do not use for a broad security audit or whole-architecture review.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/dependency-analysis/SKILL.mdW011: 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 dependency-analysis skill parses repository files, package manifests, and lockfiles, which can contain untrusted external data (such as third-year dependencies or PR text), leading to potential indirect prompt injection.
- Repository
Noorkhalel/saas-ai-skills
- Revision
d4299f1
- 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.