Loading...
Loading...
Found 40 Skills
Deep architectural knowledge of AI Agent Harness design patterns, implementation strategies, and Claude Code internals for building production-grade AI agents
Deployable Flue agent harness lane for HTTP, CI, Node, Cloudflare, and sandbox-backed agents.
Expert guidance on AI Agent architecture, harness design patterns, and building production-grade Agent systems based on Claude Code analysis
Configure or diagnose the staged-only multi-model harness, including selectable implementation workers, review advisors, high-assurance packet policy, provider probes, and optional Claude model-matrix output style. Use when the user says "set up the agent harness", "configure multi-model reviewers", "choose worker models", "check harness setup", "skonfiguruj harness", or "sprawdź modele".
Transform Claude Code into a fully autonomous agent system with persistent memory, scheduled operations, computer use, and task queuing. Replaces standalone agent frameworks (Hermes, AutoGPT) by leveraging Claude Code's native crons, dispatch, MCP tools, and memory. Use when the user wants continuous autonomous operation, scheduled tasks, or a self-directing agent loop.
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
Shared internal runtime for configurable staged-only implementation workers, evidence-gated work packets, and multi-model review councils. Use indirectly through om-fix-issue, om-implement-feature, or om-setup-agent-harness; do not use it to publish, commit, push, or open a pull request.
Create the OpenSpec specs of behaviour that already exists in the code, so the next change can modify or remove it instead of only adding to it.
Create a plan for the specified task.
Create a git commit following the team's Conventional Commit conventions. Use when the user asks to commit changes or create a commit.
Create a plan for the specified task and store it as GitHub issues in the repository of the current working directory. Given the URL of a GitHub issue, it turns that issue into the parent "plan" issue (Goal, Context and a checklist of phases) and creates one child issue per phase, linking every phase as a native GitHub sub-issue of the parent. Stops for user approval before creating any issue. After creation, the plan is meant to be implemented with the codely-plan-phase-implement-github skill.
Create new documentation based on the current conversation context.