⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
appa-guide
Set up and tune OpenAPPA on Claude Code, OpenCode, or a kagent cluster. Checks tool coverage, includes matching batteries, writes remaining rules, and explains blocked calls. Use for initial setup or policy changes.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
appa-guide
The canonical OpenAPPA configuration skill. SKILL.md owns host detection
and the modes. references/core.md owns the policy-writing, proposal and
approval rules every host shares; it names operations, not host tools. The
router sends each host to the core rules and then to one host reference:
references/claude-code.md— Claude Code tool discovery, installed batteries, local runtime reload, and the commands for each core operation.references/kagent.md— kagent CR discovery, and policy changes through the runtime-ownedappa_update_policyandappa_include_batterytools, which validate, publish and reload.
PARITY.md defines the behavior both hosts must preserve
and the limited platform-specific differences they may expose.
kagent attaches this directory directly through skills.gitRefs.
The appa binary exposes the core rules as appa_runtime::guide::CORE and
compiles SKILL.md with the core rules and the Claude reference appended, in
that order. appa plugin install claude-code writes that text to the user's
Claude Code skills directory beside the policy-review guide. Claude
therefore needs no gated Read call to bootstrap the guide. The runtime
chart mounts a ConfigMap copy of SKILL.md, references/core.md and
references/kagent.md from charts/appa-runtime/files/skill/ over the git
checkout;
appa-runtime/tests/guide_skill.rs keeps that copy byte-identical to this
directory.
The appa-runtime chart installs a pre-configured kagent Agent around the skill.
The Agent supplies the kagent tool server's Kubernetes and Helm tools and sets
APPA_ENABLED=true beside APPA_RUNTIME_URL. That pair puts it behind
the shared runtime. The skill itself remains usable from any kagent
Agent that has those tools and permissions and sets the same pair. An
Agent that leaves APPA_ENABLED unset runs ungated: the image ignores
APPA_RUNTIME_URL, and its own k8s_apply_manifest call raises no
Approve card.
// HOW IT'S BUILT
KEY FILES