Manage Local Studio automations — scheduled prompts the app re-runs on its own — when the user asks to schedule, pause, resume, edit, inspect or delete recurring work, or asks what a scheduled job has been doing.
GitHub through the gh CLI that is already installed and signed in on this machine — issues, pull requests, diffs, reviews, Actions runs, code search, and the REST API. Load when the user asks about a repo, an issue, a PR, a review, red CI, or anything on github.com.
The user's Obsidian vault — searching, reading, creating and appending to their markdown notes, with wikilinks, frontmatter and tags handled the way Obsidian means them. Load when the user mentions their notes, their vault, Obsidian, a daily note, a note by name, or asks you to write something down for them.
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, or editing any .md or .mdx file in the project, and before any mcpopen-knowledge tool call (exec, search, write, edit, and the rest). Installed…
Deep autoscaling diagnostics and tuning for three scaling paths: 1) Horizontal Pod Autoscaler (HPA), 2) Vertical Pod Autoscaler (VPA), 3) Karpenter node provisioning.
Ejecución de Terminal Puedes ejecutar comandos en la terminal del servidor para obtener información del sistema, leer archivos, buscar datos, etc. :::terminal COMANDO::.
Generate and edit Draw.io-first diagrams for formal documents, reports, proposals, design documents, and implementation plans. Use Draw.io for flowcharts, sequence diagrams, class diagrams, Entity-Relationship (ER) diagrams, mind maps, architecture diagrams, UI wireframes, module dependency diagrams, and network…
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?".
Your Chief of Staff. Run /debrief gm for a morning briefing, /debrief triage for prioritized messages, or /debrief to run any of the bundled skills below.
File a bug report or feature request against the zordon project (github.com/piotrkowalczuk/zordon) from a short description. Distills a generic, reproducible essence and strips anything specific to the user's local setup — absolute paths, usernames, hostnames, internal service/company names, concrete ports, secrets …
Use in a repo that has an Alphasfile, or inside a zordon workspace copy, when a task touches the local dev stack — bringing services up or down, checking status or ports, or running a declared provision (migration, seeding, teardown). Prefer the zordon MCP tools over running the zordon/alpha binaries in Bash, and…