Loading...
Loading...
Found 119 Skills
Research codebase comprehensively using parallel sub-agents to answer user questions. Use when the user asks to "research the codebase", "understand how X works", or "investigate Y".
Before starting any significant task, force explicit evaluation of available skills. For each potentially relevant skill, state YES/NO with reasoning. Only proceed to implementation after skills have been consciously evaluated and activated. Prevents the ~50% "coin flip" activation rate that occurs when skills are passively available but not deliberately considered.
Proposal-first development workflow with commit hygiene and decision authority rules. Enforces: propose before modifying, atomic commits, no force flags, warnings-as-errors. Use for any project where AI agents are primary developers and need guardrails.
Create, improve, and test skills for the z-schema JSON Schema validator library. Use this skill whenever the user wants to create a new skill from scratch, turn a workflow into a reusable skill, update or refine an existing skill, write test cases for a skill, or organize reference material for a skill. Also use when someone mentions "skill", "SKILL.md", or wants to document a z-schema workflow for reuse by humans or AI agents.
Adaptive exploration pipeline that integrates /brainstorm, /think, and /red-team with intelligent pivoting. Unlike /deepthink (which takes a fixed idea and iterates), /prospect starts with divergent brainstorming, picks the most promising vein, runs deep analysis, and — crucially — can PIVOT back to divergent thinking when: the idea dies under red-team, an adjacent opportunity surfaces during analysis, or the research reveals the real opportunity is elsewhere. Produces a prospecting report: the landscape explored, veins assayed, pivots taken, and the final stake with conviction. Use when the user says "prospect", "explore this space", "find opportunities", "what should I build", "explore and analyze", or has a domain/trend they want to both explore AND evaluate.
Create, verify, repair, and close durable Codex goals with measurable outcomes, evidence gates, plan templates, blocker handling, completion audits, and goal-backed workflow repair.
Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the `claude` CLI — for example, "have another Claude implement this", "delegate this to Claude Code", or "run this queue through a separate Claude session." Do not trigger merely because the current orchestrator is Claude, and do not use when the user asks the current Claude to implement directly without delegation.
Use when the user wants to create, author, write, or design a new Agent Skill (a SKILL.md) — for OpenKnowledge or for their editors — including requests like 'help me write a skill', 'make a skill that…', 'turn this workflow into a skill', or improving an existing skill's triggering and discipline. Also use when capturing reusable agent guidance that should live as an installable skill rather than a one-off prompt. Covers choosing scope (project vs global), the SKILL.md frontmatter contract, progressive-disclosure structure, evaluating the skill, and installing it into the user's editors.
AI agent workflow with interview-driven planning and team-based execution. Use /design to start planning, /work to execute.
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Extract standalone snippets from newsletters or blog posts and route to social platforms. Posts suggestions to
Orchestrate subagent workflows for complex tasks that benefit from decomposition, role-based delegation, and parallel execution. Use when Codex should assemble a temporary team of subagents, choose roles from a reusable role library, create a controlled fallback role when no preset role fits, coordinate read-heavy work in parallel, or handle write-heavy work with ownership boundaries, staged execution, and an integrator-led merge path.