skills/claude-code/SKILL.md
Set up APort guardrails for Claude Code. Creates a passport and activates the PreToolUse hook that enforces policy on every tool call. Local evaluation by default, zero network calls.
npx skillsauth add aporthq/aport-agent-guardrails claude-codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are setting up APort Agent Guardrails for Claude Code. Follow these steps in order.
Run these checks. If either fails, tell the user what to install and stop.
bash --version | head -1
Expected: GNU bash, version 4 or higher.
jq --version
Expected: jq-1.x. If missing, tell the user: brew install jq (macOS) or apt install jq (Linux).
${CLAUDE_PLUGIN_ROOT}/bin/aport-status.sh 2>/dev/null
If this prints passport info, guardrails are already active. Ask the user if they want to reconfigure. If they say no, stop here.
If it prints nothing or errors, continue to Step 3.
APORT_FRAMEWORK=claude-code ${CLAUDE_PLUGIN_ROOT}/bin/aport-create-passport.sh --framework=claude-code
This is an interactive wizard. It will prompt the user for:
Let the user interact with the wizard directly. Do not answer the prompts for them.
Expected outcome: A passport file is created at ~/.claude/aport/passport.json.
${CLAUDE_PLUGIN_ROOT}/bin/aport-status.sh
Expected: Shows passport location, agent ID, and evaluation mode. If this succeeds, tell the user guardrails are active.
The PreToolUse hook is registered automatically by the plugin system. No settings.json editing is needed.
If the wizard fails or status shows no passport:
~/.claude/aport/ directory exists~/.claude/DEBUG_APORT=1 prefix for verbose outputdevelopment
Check APort guardrail status — passport validity, evaluation mode, and recent audit log entries. Works for all frameworks.
tools
Set up APort guardrails for OpenClaw. Local-first policy enforcement that checks tool calls against your passport before execution. Zero network calls by default. Open-source (Apache 2.0).
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------