jj
Jujutsu (jj) — the Git-compatible version control system. Activate ONLY when a .jj/ directory is present in the project or when jj/jujutsu is explicitly mentioned. Do NOT activate for plain git repos without .jj/. Use for any VCS operations in jj-managed projects: commit, push, pull, branch, bookmark, rebase, squash, merge, diff, log, status, working copy, change ID, revset, fileset, template, configuration, workspaces.
95
92%
Does it follow best practices?
Impact
100%
1.23xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
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
The skill's required workflows (SKILL.md, git.md, and references/bookmarks.md) explicitly instruct the agent to run network operations like `jj git clone` and `jj git fetch` against public remotes (e.g., GitHub/GitLab), which import user-generated repository data (commits, messages, README, bookmarks) that the agent is expected to read and that can change push/fetch/bookmark behavior—so untrusted third-party content could indirectly inject instructions.
- Repository
- joshuadavidthomas/agent-skills
- Path
jj/SKILL.md
- Commit
516dee7
- 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.