mikefullerton/setup-and-install-scripts
skills/setup-and-install-scripts/SKILL.md
Use when authoring or modifying install/uninstall scripts, or when creating a /setup directory for a repo that requires developer setup steps. Enforces the /setup layout, install/uninstall naming, and supporting-files location.
development
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add mikefullerton/catherding setup-and-install-scriptsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 2:49 AM145.4s1 file scanned
SKILL.md
- name:
- setup-and-install-scripts
- description:
- Use when authoring or modifying install/uninstall scripts, or when creating a /setup directory for a repo that requires developer setup steps. Enforces the /setup layout, install/uninstall naming, and supporting-files location.
Setup & Install Scripts — MANDATORY
When a /setup directory is required
If a repo requires steps a developer must take to use it — automated scripts, tools, or installers — those go in a /setup directory.
Naming
- Setup scripts are named
install(regardless of file extension):install.sh,install.py, etc. - Every
installmust have a correspondinguninstallthat reverses what it did. - The uninstall counterpart is not required for prerequisite software managed externally (e.g. installing
brewitself — that's the developer's responsibility).
Supporting files
- Config files, assets, themes, and anything else the scripts need →
/setup/files/.
Shell exception reminder
install.sh, uninstall.sh, and setup.sh are the only .sh exceptions to the "Python for scripts" rule. See ~/.claude/CLAUDE.md → "Scripting Language — MANDATORY".
Reference
Full rationale in ~/projects/active/catherding/policies/setup/repo-organization/setup-scripts.md. See INDEX.md for related policies.
Related Skills
mikefullerton/general-principles
development
VerifiedTrustedCommunity
Use whenever writing, modifying, refactoring, or reviewing code, or when making any design decision — including small ones. Loads the 21 cookbook principles (simplicity, yagni, fail-fast, explicit-over-implicit, separation-of-concerns, design-for-deletion, etc.) as heuristics for judgment calls about code shape, module boundaries, and what to build. Applies across all languages and project types.
SKILL.mdUpdated Apr 22, 2026
mikefullerton/yolo
tools
VerifiedTrustedCommunity
Toggle per-session YOLO mode (auto-approve permissions with configurable deny list). Use when --dangerously-skip-permissions is broken. /yolo on, /yolo off, /yolo install, /yolo uninstall, /yolo configure, /yolo status
SKILL.mdUpdated Apr 21, 2026
mikefullerton/new-repo-scaffold
testing
VerifiedTrustedCommunity
Use when creating a new repo (git init, gh repo create, scaffolding a new project) or when a repo is missing README/LICENSE/.gitignore/.claude/CLAUDE.md. Enforces the "every repo must have" checklist and documentation layout.
SKILL.mdUpdated Apr 21, 2026
mikefullerton/llm-integration-policies
development
VerifiedTrustedCommunity
Use when a file imports an LLM SDK (anthropic, openai, langchain, etc.), when scaffolding LLM features, or when placing Claude-specific files in a repo. Enforces the "do not assume Claude" rule, the /claude directory convention, Graphify opt-in, and the rules-vs-behavioral-instructions split.
SKILL.mdUpdated Apr 21, 2026