marketplace
Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/aiskillstore/marketplace with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/aiskillstore/marketplace'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/aiskillstore-marketplace)HTML
<a href="/listings/aiskillstore-marketplace"><img src="/api/listings/aiskillstore-marketplace/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
The recommended way to install any skill is the **`skillstore` CLI** — one command works for both **Claude Code** and **Codex**:
npx skillstore add author/skill-name
For example:
npx skillstore add aiskillstore/code-review
It downloads the skill and drops it into the right `skills/` directory for your tool. Claude Code auto-discovers it; for Codex, restart the session.
Prefer to do it by hand, or installing via Claude Web? See the full **[Installation Guides](https://skillstore.io/docs/install-guides)** for every method (CLI, manual, and ZIP upload) and the scope directories (`~/.agents/skills/`, `.claude/skills/`, `~/.claude/skills/`, `.codex/skills/`, …).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 90 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # Skill Store — Marketplace Repository
- This is the open-source content repository behind
- **[Skill Store](https://skillstore.io)**. It stores every approved
- [Agent Skill](https://agentskills.io/specification), the records that go with
- it, and the automated security audits published with each skill.
- > **This repo is a companion to the Skill Store platform, not the place to submit skills.**
- > Skills are added through [skillstore.io](https://skillstore.io) — its review pipeline writes to this repo automatically. Please **do not open a pull request here to add a skill**; PRs adding skills will be closed. See [Contributing a skill](#contributing-a-skill) below.
- ## Installing a skill
- The recommended way to install any skill is the **`skillstore` CLI** — one command works for both **Claude Code** and **Codex**:
- ```sh
- npx skillstore add author/skill-name
- ```
- For example:
- ```sh
- npx skillstore add aiskillstore/code-review
- ```
- It downloads the skill and drops it into the right `skills/` directory for your tool. Claude Code auto-discovers it; for Codex, restart the session.
- Prefer to do it by hand, or installing via Claude Web? See the full **[Installation Guides](https://skillstore.io/docs/install-guides)** for every method (CLI, manual, and ZIP upload) and the scope directories (`~/.agents/skills/`, `.claude/skills/`, `~/.claude/skills/`, `.codex/skills/`, …).
- ## Contributing a skill
- Submit through the platform — not through a pull request:
- 1. Go to **[skillstore.io/submit](https://skillstore.io/submit)**.
- 2. Enter the GitHub repository URL that contains your `SKILL.md`.
- 3. Your submission runs through automated security analysis.
- 4. A maintainer reviews and approves it.
- 5. On approval, the skill is published here and appears on [skillstore.io](https://skillstore.io).
- ### What makes a valid skill
- - `SKILL.md` — the skill definition (**required**, per the [Agent Skills spec](https://agentskills.io/specification))
- - Supporting files the skill references (optional)
- - `LICENSE` (recommended)
- ### Security audit
- Every submission is scanned automatically before it can be published. The audit flags things like:
- - Dangerous code patterns (`eval`, `exec`, raw system commands)
- - File access outside the project scope
- - Network calls to external hosts
- - Obfuscated or minified code
- - Credential / secret handling
- Security analysis is report-only: findings inform maintainers and users, but a
- risk result does not automatically block an otherwise approved skill from being
- published. See our [Security Trust Center](https://skillstore.io/security) for
- the methodology, limitations, and risk-level definitions.
- Live Security Passport example:
- [](https://skillstore.io/skills/consiliency-research?utm_source=security_passport_badge)
- ## Repository layout
- ```
- .
- ├── skills/ # Approved, published skills (one folder each, with SKILL.md)
- ├── pending/ # Submissions awaiting review
- ├── packages/
- │ ├── cli/ # The `skillstore` CLI (npx skillstore add …)
- │ └── skillstore/
- ├── schemas/ # JSON schemas for skill records
- ├── scripts/ # Maintenance & scoring scripts
- └── .github/workflows/ # Submission, audit, and sync automation
- ```
- The contents of this repo are maintained by Skill Store's automated pipeline. Manual changes are limited to maintainers.
- ## Links
- - **Website**: [skillstore.io](https://skillstore.io)
- - **Submit a skill**: [skillstore.io/submit](https://skillstore.io/submit)
- - **Install guides**: [skillstore.io/docs/install-guides](https://skillstore.io/docs/install-guides)
- - **Docs**: [skillstore.io/docs](https://skillstore.io/docs)
- - **Agent Skills spec**: [agentskills.io/specification](https://agentskills.io/specification)
- ## License
- The marketplace catalog is MIT-licensed. Individual skills carry their own licenses — check each skill's `LICENSE` file.
skills/0xdarkmatter/claude-code-templates/assets/hook-script.sh · Bundled script · 85 lines · 1 finding marked
- #!/bin/bash
- #
- # Claude Code Hook: [Description]
- #
- # Event: [PreToolUse|PostToolUse|SessionStart|etc]
- # Matcher: [Tool name or * for all]
- #
- # Security: Validates input, quotes variables, prevents path traversal
- #
- set -euo pipefail
- # Error handling
- trap 'echo "Error at line $LINENO" >&2; exit 1' ERR
- # Check dependencies
- command -v jq >/dev/null 2>&1 || {
- echo "jq is required but not installed" >&2
- exit 1
- }
- # Read input from stdin
- INPUT=$(cat)
- # Validate JSON
- if ! echo "$INPUT" | jq -e '.' > /dev/null 2>&1; then
- echo "Invalid JSON input" >&2
- exit 2
- fi
- # Parse common fields
- TOOL=$(echo "$INPUT" | jq -r '.tool_name // empty')
- SESSION=$(echo "$INPUT" | jq -r '.session_id // empty')
- # -------------------------------------------------------------------
- # Your hook logic here
- # -------------------------------------------------------------------
- # Example: Log tool usage
- LOG_FILE="${CLAUDE_PROJECT_DIR:-.}/.claude/hook.log"
- mkdir -p "$(dirname "$LOG_FILE")"
- echo "$(date -u +"%Y-%m-%dT%H:%M:%SZ") | $TOOL | $SESSION" >> "$LOG_FILE"
- # Example: Block dangerous operations
- # if [[ "$TOOL" == "Bash" ]]; then
- # CMD=$(echo "$INPUT" | jq -r '.tool_input.command // empty')
- # if [[ "$CMD" == *"rm -rf /"* ]]; then
- Note: Quoted as data in code: Runs `rm -rf` against a root or home-directory path
- Line 47 on GitHub
- # echo "Blocked dangerous command" >&2
- # exit 2 # Exit 2 = blocking error
- # fi
- # fi
- # Example: Validate file paths
- # if [[ "$TOOL" == "Write" ]]; then
- # FILE=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty')
- # if [[ "$FILE" == *".."* ]]; then
- # echo "Path traversal blocked" >&2
- # exit 2
- # fi
- # fi
- # -------------------------------------------------------------------
- # Exit codes:
- # 0 = Success (continue execution)
- # 2 = Blocking error (stderr shown to Claude)
- # Other = Non-blocking error (logged, continues)
- # -------------------------------------------------------------------
- exit 0
- # CONFIGURATION EXAMPLE:
- # Add to ~/.claude/settings.json or .claude/settings.local.json:
- #
- # {
- # "hooks": {
- # "PreToolUse": [{
- # "matcher": "*",
- # "hooks": [{
- # "type": "command",
- # "command": "$CLAUDE_PROJECT_DIR/.claude/hooks/this-script.sh",
- # "timeout": 5000
- # }]
- # }]
- # }
- # }
skills/92bilal26/code-validation-sandbox/scripts/setup-sandbox.sh · Bundled script · 91 lines · 1 finding marked
- #!/bin/bash
- # setup-sandbox.sh - Create persistent validation container
- # Part of code-validation-sandbox v3.0 (Reasoning-Activated)
- set -euo pipefail
- CONTAINER_NAME="code-validation-sandbox"
- BASE_IMAGE="${1:-python:3.14-slim}"
- echo "=== Code Validation Sandbox Setup ===" >&2
- echo >&2
- # Check if container already exists
- if docker ps -a --format '{{.Names}}' | grep -q "^${CONTAINER_NAME}$"; then
- echo "Container '$CONTAINER_NAME' already exists" >&2
- # Check if running
- if docker ps --format '{{.Names}}' | grep -q "^${CONTAINER_NAME}$"; then
- echo "✅ Container is running" >&2
- container_id=$(docker ps --filter "name=$CONTAINER_NAME" --format '{{.ID}}')
- echo "Container ID: $container_id" >&2
- exit 0
- else
- echo "Container exists but is stopped. Starting..." >&2
- docker start "$CONTAINER_NAME" >&2
- echo "✅ Container started" >&2
- exit 0
- fi
- fi
- echo "Creating new container with base image: $BASE_IMAGE" >&2
- echo >&2
- # Create persistent container
- container_id=$(docker run -d \
- --name "$CONTAINER_NAME" \
- --mount type=bind,src="$(pwd)",dst=/workspace \
- "$BASE_IMAGE" \
- tail -f /dev/null)
- echo "Container created: $container_id" >&2
- echo >&2
- # Install base tools
- echo "Installing base tools..." >&2
- docker exec "$CONTAINER_NAME" bash -c "
- set -e
- apt-get update -qq
- apt-get install -y -qq curl git build-essential > /dev/null 2>&1
- echo '✓ Base tools installed'
- "
- # Install Python tools (if Python base image)
- if [[ $BASE_IMAGE == python:* ]]; then
- echo "Installing Python tools..." >&2
- docker exec "$CONTAINER_NAME" bash -c "
- set -e
- # Install UV package manager
- curl -LsSf https://astral.sh/uv/install.sh | sh > /dev/null 2>&1
- export PATH=\"\$HOME/.cargo/bin:\$PATH\"
- # Install common Python tools
- pip install --quiet pytest mypy ruff 2>/dev/null
- echo '✓ Python tools installed (UV, pytest, mypy, ruff)'
- "
- fi
- # Install Node.js (for multi-language support)
- echo "Installing Node.js..." >&2
- docker exec "$CONTAINER_NAME" bash -c "
- set -e
- curl -fsSL https://deb.nodesource.com/setup_20.x | bash - > /dev/null 2>&1
- Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
- Line 75 on GitHub
- apt-get install -y -qq nodejs > /dev/null 2>&1
- npm install -g pnpm > /dev/null 2>&1
- echo '✓ Node.js 20 + pnpm installed'
- "
- echo >&2
- echo "=== Setup Complete ===" >&2
- echo "Container: $CONTAINER_NAME" >&2
- echo "ID: $container_id" >&2
- echo >&2
- echo "Installed:" >&2
- echo " - Python 3.14 + UV + pytest + mypy + ruff" >&2
- echo " - Node.js 20 + pnpm" >&2
- echo " - Base tools (curl, git, build-essential)" >&2
- echo >&2
- echo "✅ Sandbox ready for validation" >&2
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.