Loading...
Loading...
Found 266 Skills
Two-round debate protocol where perspectives challenge each other before consensus. Round 1 presents independent positions, Round 2 allows counter-arguments and rebuttals. Produces battle-tested decisions for high-stakes choices.
Delegate tasks to AI agents via Box0. Use when the user asks to review code, check security, run tests, compare tools, get multiple perspectives, research a topic, analyze data, write docs, or any task that could benefit from specialized or parallel execution. Also use when the user mentions agent names or says "ask", "delegate", "get opinions from", or "have someone".
Generates an evidence-calibrated product or marketing persona using the canonical v2.5 output contract. Use when shaping artifact perspective, stress-testing decisions, or framing product and GTM strategy.
Orchestrate multi-agent collaborative document synthesis through 6 phases - Divergence, Synthesis, Commentary, Consolidation, Reality Check, Final Merge. Produces authoritative founding documents from complex multi-perspective inputs. Use for constitutional documents, architecture decisions, organizational charters, or any document requiring rigorous multi-perspective synthesis. Activates on "synthesize document", "multi-agent authorship", "collaborative synthesis", "founding document", "architecture document", "recursive synthesis", "constitutional document", "multi-perspective document". NOT for simple document writing, single-author tasks, quick summaries, or documents that don't require adversarial review.
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
Design, critique, and revise UML diagrams from a modeling and communication perspective. Use when model is asked to create or improve UML; when the user asks for a graphical representation, diagram, schema, visual model, process map, state view, architecture view, or system representation of software/system behavior or structure; when the user does not explicitly choose UML but needs a model-like visual explanation; when model must autonomously choose the right UML diagram type or split across multiple UML diagrams. Use for reasoning about diagram form, abstraction level, boundaries, grouping, lifecycle/state design, behavior vs structure, interaction design, or diagnosing why a diagram feels wrong at the modeling level. This skill treats notation as the final representation, not as the core task.
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Also trigger when the user wants feedback on code changes, wants to approve or request changes on a PR, or asks to review someone's contribution.
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed. Triggers on: 'ask me', 'ask questions about', 'clarify requirements', 'gather requirements', 'I need you to ask', or when the user explicitly wants a question-and-answer session before work begins.
First-century Hebrew scripture interpretation assistant. Explains Bible passages through Yeshua's perspective as a first-century Torah-observant Jewish teacher, grounded in Hebrew language analysis and biblical archaeology. Use this skill whenever the user asks about Bible verses, Torah passages, scripture meaning, biblical concepts, Hebrew word studies, or anything related to understanding the Bible — especially when they want historically accurate interpretation free from later Christian denominational theology. Also use when the user references specific books like Genesis, Exodus, Psalms, Isaiah, Matthew, Romans, etc., or Hebrew/Greek terms from scripture. Triggers on any Bible study, scripture interpretation, or theological question.
FansRevenue platform help — creator monetization through affiliate brand promotion, creator-to-creator promotion, MyEroLink link-in-bio, Creator Academy, and CrakRevenue network. Use when setting up FansRevenue brand partnerships, commission earnings aren't showing up, custom landing pages aren't converting, MyEroLink bio links need optimization, Creator Academy isn't loading, or trying to understand which offers pay highest commissions. Do NOT use for general affiliate program design strategy (use /sales-affiliate-program), influencer marketing strategy from a brand's perspective (use /sales-influencer-marketing), or CPA network selection (use /sales-performcb).
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the Task tool for architecturally enforced context isolation. Supports Jest, Vitest, pytest, Go test, cargo test, PHPUnit, and RSpec.
Multi-AI Agent P2P Debate. Suitable for technical solution stress testing, multi-perspective collision, and design decision convergence. Use it when you want a solution to be challenged or to understand the pros and cons of different technical routes. Triggered when mentioning "debate", "agent discussion", "multi-angle analysis", or "start a team".