Audits a Claude Code skill for security risks in three modes: before download (from a URL or install command), after download but before install (from a .skill file), or after install (from a local skills directory). Use this skill whenever a user is about to install a skill from any source — including GitHub URLs, git clone commands, npx/npm commands, curl/wget downloads, pip installs, marketplace links, or raw SKILL.md URLs. Also trigger when a user asks "is this skill safe?", "should I trust this skill?", "can you check this before I install it?", "audit this skill", or pastes any link to a skill repository or .skill file. If a user mentions installing ANY skill, proactively offer to audit it first — do not wait for them to ask.
97
97%
Does it follow best practices?
Impact
99%
1.28xAverage score across 5 eval scenarios
Advisory
Suggest reviewing before use
All notable changes to this project will be documented in this file.
~/.config/ alone no longer escalates to CRITICAL — only triggers when combined with credential/token/key/secret patterns. Generic app config paths now correctly classified as B5 (WARNING), preventing false DO NOT INSTALL verdicts.evals/) covering all three audit modes, all check categories, and prompt injection resistance — 97% score, 1.28× upliftreferences/ files as docs in tile.json so Tessl bundler includes them.tileignore to .tesslignore (deprecation fix)test-fixtures/ from published bundle via .tesslignoreRead,WebFetch,Glob → Read WebFetch Glob)tile.json and publish workflow (tile was not previously auto-publishing)references/index.md as docs entrypoint linking security-checks.md and report-format.mdskill-safety-auditorsecurity-checks.md and report-format.mdaudit-sample
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5