Agent skill
manage-plugins
Add or remove inline plugins from the ccdev function in dotfiles .zshrc
Install this agent skill to your Project
npx add-skill https://github.com/nathanvale/side-quest-marketplace/tree/main/TO_AUDIT/skills/manage-plugins
SKILL.md
Manage ccdev Inline Plugins
Add or remove --plugin-dir entries from the ccdev() function in ~/code/dotfiles/.zshrc.
Arguments
$0— Action:addorremove$1— Plugin directory path (e.g.~/code/side-quest-plugins/plugins/my-plugin)
Steps
- Read
~/code/dotfiles/.zshrcand find theccdev()function (look forfunction ccdev()) - Validate the plugin path exists on disk (use Bash
lsto check) - Check for duplicates — if adding, confirm the
--plugin-dirline doesn't already exist; if removing, confirm it does exist - Edit the file:
- add: Insert a new
--plugin-dirline in alphabetical order within the existing list. The lines are sorted alphabetically by full path. Maintain the existing indentation (4 spaces +--plugin-dir). - remove: Delete the
--plugin-dirline for that path.
- add: Insert a new
- Show the user the updated
ccdev()function so they can verify - Remind the user:
Done! To activate the change:
1. Run: sz (reloads .zshrc)
2. Restart Claude Code with ccdev
Important Rules
- NEVER modify anything outside the
ccdev()function - NEVER reorder existing lines — only insert/remove the single target line
- Keep
"$@"as the last argument on its own line - Use
~/code/prefix (not full/Users/nathanvale/code/) to match existing style
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
cli-mcp-decision
Decide whether a workflow should use CLI skills, MCP, or a hybrid approach. Use when planning agentic tooling, writing ADRs, or evaluating migrations between CLI and MCP.
agent-cli
Patterns for building CLIs that serve both humans and AI agents. Covers tri-modal output (JSON/JSONL/human), typed exit codes, structured error contracts, zero-dependency arg parsing, topic-based help, service discovery, field projection, and auto agent-mode detection. Reference implementation: @side-quest/observability CLI. Use when: building a CLI, adding a command, CLI output format, agent-friendly CLI, machine-readable output, JSON CLI contract, exit codes, --json flag, NDJSON streaming, how should my CLI work with agents, CLI design patterns.
explain-codebase
Generate an engaging, deep-dive explanation document (FOR_[NAME].md) that explains a codebase or domain in plain language with analogies, lessons learned, and practical wisdom.
vscode-bookmarks
Create and manage VS Code Bookmarks extension labeled bookmarks in .vscode/bookmarks.json. Use when the user wants to add navigation bookmarks to a codebase, trace data flows through code, mark important code locations, or set up labeled waypoints for code walkthroughs. Also use when user says "bookmark", "label this code", "mark this flow", or "add waypoints".
observability
Start, stop, or check status of the Side Quest observability event server. Use when asked to start the server, stop the server, check server status, or manage the observability dashboard lifecycle.
node-cert
Fix Node.js certificate trust issues behind corporate SSL-inspecting proxies. Use when discussing: VPN, corporate VPN, corporate proxy, SSL inspection, MITM proxy, TLS interception, NODE_EXTRA_CA_CERTS, self-signed certificate error, UNABLE_TO_VERIFY_LEAF_SIGNATURE, certificate chain, proxy CA, corporate network, Claude Code on VPN, Gemini CLI on VPN, npm behind proxy, Node.js certificate error, CAFile.pem, proxy-on, proxy-off, HTTPS_PROXY, HTTP_PROXY, openssl s_client, certificate extraction, corporate root CA, forward trust CA, trust store gap.
Didn't find tool you were looking for?