Loading...
Loading...
Found 5 Skills
Agent Infrastructure: Bridge any skill or directory of skill collections to Claude Code (~/.claude/skills) and Codex (~/.codex/skills). Supports skills in the dbskill repository as well as absolute paths to external skills. Connect source directories via symlinks, with both ends synchronized when the source directory is modified. Supports batch bridging by skill name, relative path, absolute path, or skills directory, as well as unbridging and checking bridge status. Triggers: /dbs-bridge, /bridge, "bridge this skill", "bridge this skills directory", "connect this skill to Claude Code and Codex", "make this skill callable by both Claude and Codex", "unbridge", "check bridge status" Bridge any skill folder or directory of skill folders to Claude Code and Codex using symlinks. Supports dbskill skills and external skill directories. Use when the user wants one or many skills callable from both agents, or wants to unlink/check bridge status. Trigger: /dbs-bridge, /bridge, "bridge this skill", "bridge this skills directory", "make this skill available to Claude Code and Codex", "unlink this skill", "check bridge status"
Install behavioral skills from trousse. Use FIRST when onboarding a new machine or after fresh Claude Code install. Creates symlinks for session lifecycle, utilities, and optionally offers tool repos (todoist-gtd, garde-manger). Triggers on 'help me set up', 'install skills', '/setup'. (user)
Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills.
Audit and maintain the joelclaw skill inventory. Use when checking skill health, fixing broken symlinks, finding stale skills, or running the skill garden. Triggers: 'skill audit', 'check skills', 'stale skills', 'skill health', 'skill garden', 'broken skill', 'skill review', 'fix skills', 'garden skills', or any task involving skill inventory maintenance.
Consolidate Claude Code memory across git worktrees so all branches of the same repo share a single memory directory. Use when memory is isolated per worktree, when switching branches loses context, or when setting up a new machine with worktree-based workflows.