Skill Claude CodeCodex
Maintain the Wax memory store used by the Hermes wax-memory provider.
Skill Claude CodeCodex
Maintain the Wax memory store used by the Hermes wax-memory provider.
Skill Codex
Operator install and diagnose playbook for waxmcp hosts (HTTP vs stdio, LaunchAgent, Hermes plugin, doctor, vector-health). Use only when installing, repairing, or rewiring a host. Do not use at session start. Do not use when MCP remember/recall/stats are already available — follow the live server instructions instead…
Skill Codex
Benchmarking and performance auditing for the Wax repo. Use when running or interpreting Wax benchmarks, diagnosing CPU, memory, or I/O bottlenecks, or investigating Swift 6.2 concurrency issues such as Sendable, actor isolation, @unchecked Sendable, task-group fan-out, and data races.
Skill Codex
Swift client guidance for Wax's public Memory, PhotoMemory, and VideoMemory APIs. Use only when writing or changing Swift app code that imports Wax. Do not use at session start. Do not use for MCP remember/recall/stats — those follow the live MCP server instructions. Do not use for waxmcp install or doctor (that is…
Plugin Claude Code
Bundles 5 skills · 0 tokens together
ryk safety hooks and skills for Claude Code.
Skill Claude CodeCodex needs its repo
Check ryk installation, policy status, host integration status, and plugin readiness.
Skill Claude CodeCodex
Create or repair an ryk policy for the current repository.
Skill Claude CodeCodex
Explain how to run the current Codex workflow under ryk protection.
Skill Claude CodeCodex
Run ryk red-team fixtures and summarize results.
Skill Claude CodeCodex
Show and explain the latest ryk session replay.
Skill Claude CodeCodex
Skill "openclaw-plugin" from christopherkarani/ryk, covering ryk, when to use ryk, how it works, prerequisites and example policy behavior.
Skill Claude CodeCodex
Use when Pi tool calls are protected by ryk runtime guardrails or when a secret was captured from a Pi prompt.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: