CtrlK
BlogDocsLog inGet started
Tessl Logo

k8s

Operate the joelclaw Kubernetes cluster — Talos Linux on Colima (Mac Mini). Deploy services, check health, debug pods, recover from restarts, add ports, manage Helm releases, inspect logs, fix networking. Triggers on: 'kubectl', 'pods', 'deploy to k8s', 'cluster health', 'restart pod', 'helm install', 'talosctl', 'colima', 'nodeport', 'flannel', 'port mapping', 'k8s down', 'cluster not working', 'add a port', 'PVC', 'storage', any k8s/Talos/Colima infrastructure task. Also triggers on service-specific deploy: 'deploy redis', 'redeploy inngest', 'livekit helm', 'pds not responding'.

62

Quality

75%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/k8s/SKILL.md
SKILL.md
Quality
Evals
Security

Security

4 findings — 4 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 (medium risk: 0.65). The required runtime workflow for the k8s agent runner creates Kubernetes Jobs whose pods materialize a repo from `REPO_URL`/`REPO_BRANCH` and then execute the agent; if `REPO_URL` points to outsider-authored content (e.g., arbitrary public repo/URL), that repo’s files become readable text in the pod’s `/workspace` and thus enter the LLM context via the agent’s execution.

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.90). The Agent Runner runtime explicitly materializes arbitrary repos from the supplied REPO_URL (git clone at job runtime) and pulls/executes the runtime image ghcr.io/joelhooks/agent-runner:latest, so remote repository content and container images are fetched at runtime and can directly control prompts or execute code.

Medium

W013: Attempt to modify system services in skill instructions

What this means

The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.

Why it was flagged

Attempt to modify system services in skill instructions detected (high risk: 0.90). The skill contains many host-level administrative actions (e.g., "sudo modprobe br_netfilter", editing /Library/LaunchDaemons plists, updating Docker host configs, changing Colima VM settings and kube/talos endpoints) that require elevated privileges and modify system state, so it instructs actions that can compromise the machine.

Medium

W021: Hidden or invisible Unicode characters detected (potential obfuscation or prompt injection)

What this means

Detected hidden or invisible Unicode characters (Format/Cf or Control/Cc categories) in the component’s content. These characters are invisible when rendered but are still processed by AI models, and attackers use them to smuggle instructions past human review — for example, zero-width spaces, bidirectional overrides, invisible formatters, or Unicode Tag characters (U+E0000–U+E007F) that encode an entire hidden message. Severity escalates to high when three or more distinct hidden character types are present, or when a hidden tag-encoded message is successfully decoded, as these strongly indicate intentional obfuscation.

Why it was flagged

Hidden Unicode characters detected (1 type(s) found)

Repository
joelhooks/joelclaw
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.