CtrlK
BlogDocsLog inGet started
Tessl Logo

flox-sharing

Sharing and composing Flox environments. Use for environment composition, remote environments, FloxHub, and team collaboration patterns.

79

Quality

73%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./flox-plugin/skills/flox-sharing/SKILL.md
SKILL.md
Quality
Evals
Security

Security

2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.

Medium

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

Third-party content exposure detected (high risk: 0.90). The skill explicitly instructs fetching and activating remote environment definitions from FloxHub (e.g., "flox activate -r owner/environment-name", "flox pull owner/environment-name", and manifest [include] entries like { remote = "team/postgres" }), which are third‑party/.flox files (including hooks and services) that the agent must read and that can contain runnable instructions affecting behavior.

Report incorrect finding
Medium

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

Potentially malicious external URL detected (high risk: 0.80). The skill instructs runtime fetching/activation of remote FloxHub environments (e.g., via "flox activate -r owner/environment-name" and includes remote entries like "team/postgres"), and those fetched .flox definitions can contain hooks/services that execute commands on activation, so the external content can directly execute code.

Repository
flox/flox-agentic
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.