qtpass-linting
QtPass CI/CD workflow - run GitHub Actions locally with act, linters, formatters
52
57%
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 ./.opencode/skills/qtpass-linting/SKILL.mdLow
Low-risk findings.
2 low severity findings. 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 workflow described in SKILL.md runs GitHub Actions super-linter as part of PR/CI and therefore ingests repository/PR markdown/YAML/etc files authored by outsiders (contributors) without preselecting a specific trusted item.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The SKILL runs the remote Docker image ghcr.io/super-linter/super-linter:v8.6.0 via docker run (lines showing that image), which pulls and executes external code at runtime and is used as a required linter dependency.
- Repository
- IJHack/QtPass
- Commit
04899e4
- 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.