Installer scripts

Every Ark package includes a setup script that runs after download. The installer configures the package for the buyer's environment. A verify script confirms the install succeeded.

install.sh — the setup script

Referenced in ark.json as setup.installer. Runs automatically after ark install extracts the archive.

#!/usr/bin/env bash
set -euo pipefail

# Where this package lives after extraction
PKG_DIR="$HOME/.ark/packages/my-skill"

# Copy CLAUDE.md to ~/.claude/ for global availability
mkdir -p "$HOME/.claude/skills"
cp "$PKG_DIR/CLAUDE.md" "$HOME/.claude/skills/my-skill.md"

echo "✓ my-skill installed"
echo "  Add to your CLAUDE.md: @~/.claude/skills/my-skill.md"

verify.sh — the post-install check

Referenced in ark.json as setup.post_install_check. Must exit 0 on success, non-zero on failure. Ark runs this automatically and displays the result.

#!/usr/bin/env bash
set -euo pipefail

TARGET="$HOME/.claude/skills/my-skill.md"

# Check the file was copied
if [[ ! -f "$TARGET" ]]; then
  echo "✗ my-skill.md not found at $TARGET"
  exit 1
fi

echo "✓ my-skill verified"
exit 0

Interactive installers

If your setup requires user input (API keys, preferences, paths), set "interactive": true in ark.json. Users are warned before running an interactive installer.

#!/usr/bin/env bash
set -euo pipefail

CONFIG_DIR="$HOME/.ark/data/agent-comptable"
mkdir -p "$CONFIG_DIR"

# Prompt for configuration
read -rp "Company name: " COMPANY
read -rp "Default currency (EUR/USD): " CURRENCY
read -rp "Fiscal year start month (1-12): " FISCAL_START

# Write config
cat > "$CONFIG_DIR/config.json" <<EOF
{
  "company": "$COMPANY",
  "currency": "$CURRENCY",
  "fiscal_year_start": $FISCAL_START
}
EOF

echo "✓ Configured. Config saved to $CONFIG_DIR/config.json"

Permissions

Make both scripts executable before running ark audit or ark publish:

$ chmod +x bin/install.sh bin/verify.sh

Rules and restrictions

• Installer scripts must be POSIX-compatible bash (no zsh-only syntax)
• No network calls in install scripts — all files must be in the archive
• No sudo — all operations in user space only
• No writes outside ~/.ark/, ~/.claude/, or the user's home directory
• Scripts must complete within 5 minutes

• → 6 audit dimensions — how D1 and D5 evaluate your installer
• → ark.json reference — the setup object