basitalisandhu

Claude Code Tooling Skills — Security skill for Claude Code

Security community

Claude Code skills for keeping a Claude Code setup safe: review a third-party skill before installing it, lint and evaluate your own skill descriptions, audit the context budget, build least-privilege.

How to install Claude Code Tooling Skills

This entry records only its repository, not the path inside it, so there is no exact command to give. Open basitalisandhu/claude-code-tooling-skills and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Tooling Skills does

Claude Code skills for keeping a Claude Code setup safe: review a third-party skill before installing it, lint and evaluate your own skill descriptions, audit the context budget, build least-privilege permissions, author and test hooks, find skill collisions and portability problems. Drives the author's gate, lock, simulator and hook tools.

Alternatives in Security

  • Brooks Audit — Run a Brooks-Lint architecture audit 1.5k ★
  • Engage.Threatmodel — Materialize, lint, and drift-check the engagement threat model 348 ★
  • Bob Evaluate — Run or resume a Hacker Bob security evaluation 97 ★

README

Claude Code skills for keeping your Claude Code setup safe and tidy: review third-party skills, lint and evaluate your own, audit context budget, build least-privilege permissions, author hooks, find collisions and portability problems

**Eight skills, each with an offline, standard-library Python script and tests: skill-supply-chain-review, skill-description-linter, skill-trigger-eval, context-budget-audit, permissions-builder, hook-author, skill-collision-check and skill-portability-check.**

claude-code-tooling-skills is a Claude Code plugin for the upkeep of Claude Code itself. A setup grows by accretion: skills and plugins installed from other people's repositories, descriptions written once and never measured, memory files and MCP servers that fill the context before the first word, permission rules added one "always allow" at a time, hooks copied from examples, two skills with the same name, a script that works on one laptop only. Each skill here turns one of those into a check with a script that reads local files, applies stated rules, and reports what it found with the file and line, leaving the decision to you.

**Who it is for:** people who write or maintain Claude Code skills and plugins, teams that share a `.claude/` folder in a repository, and anyone about to install a skill or plugin they did not write.

**Why:** skill and plugin supply chains are now an attack path, descriptions decide whether a skill is ever used, and the context window is shared by everything installed. The author already maintains command-line tools for parts of this (skill-scan-gate, cc-plugin-lock, claude-perm-sim, claude-mcp-allow, cc-hooks, mcp-tools-lint); these skills tell Claude when and how to run them, and add the offline checks they do not cover.

/plugin marketplace add basitalisandhu/claude-code-tooling-skills
/plugin install cc-setup-tooling@claude-code-tooling-skills

Quickstart: open Claude Code in a folder of skills and ask "will this skill work on Wi