Total 50,523 skills, AI & Machine Learning has 8481 skills
Showing 12 of 8481 skills
Assemble a panel of experts to assess a problem from multiple professional perspectives, surface agreement and disagreement, and deliver a chaired recommendation with clear tradeoffs. Use when the user wants multi-expert judgment, a second opinion, design critique, option comparison, or a recommendation backed by distinct expert viewpoints.
Enforces spec-before-code workflow for AI-driven development. Automatically selects Spec-Kit or OpenSpec mode, triages complexity (quick/standard/thorough), recovers session context, and applies quality gates (G0-G4) with automated review loops at every stage. Use this skill whenever the user says "/super-spec", "spec first", "规范先行", or starts any feature, bugfix, or refactor — especially in projects with .spec-mode, .specify/, or openspec/ directories. Even if the user doesn't explicitly ask for spec-driven workflow, activate this skill for any non-trivial code change to prevent skipping the design phase. Orchestrates: Spec-Kit/OpenSpec (OPSX) + planning-with-files + ui-ux-pro-max (v2.0, 67 styles, 161 palettes, 13 stacks) + Superpowers (TDD, code review, verification, debugging, spec/plan review loops, subagent model selection).
A self-evolution engine for AI agents. Analyzes runtime history to identify improvements and applies protocol-constrained evolution.
This skill should be used when the user asks to "run a tracking cycle", "measure AI visibility", "check share of voice", "run Morphiq Track", "track citations", "check GEO score", "generate prompts", "run content creation workflow", or mentions monitoring LLM mentions, running content creation workflows, measuring brand visibility, or generating query fanout content. Queries multiple LLM providers, produces delta reports, and maintains MORPHIQ-TRACKER.md as the persistent state file for the entire pipeline.
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin
Patterns for parallel subagent execution using Task tool with run_in_background. Use when coordinating multiple independent tasks, spawning dynamic subagents, or implementing features that can be parallelized.
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Solve competition math problems (IMO, Putnam, USAMO, AIME) with adversarial verification that catches the errors self-verification misses. Activates when asked to 'solve this IMO problem', 'prove this olympiad inequality', 'verify this competition proof', 'find a counterexample', 'is this proof correct', or for any problem with 'IMO', 'Putnam', 'USAMO', 'olympiad', or 'competition math' in it. Uses pure reasoning (no tools) — then a fresh-context adversarial verifier attacks the proof using specific failure patterns, not generic 'check logic'. Outputs calibrated confidence — will say 'no confident solution' rather than bluff. If LaTeX is available, produces a clean PDF after verification passes.
Build and deploy autonomous AI agents in-process using Open Agent SDK, an open-source alternative to @anthropic-ai/claude-agent-sdk that works anywhere without CLI dependencies.
Generate high-quality images from text prompts using Volcano Engine Seedream models. Supports multiple artistic styles and aspect ratios. Use this skill when users want to create images from text descriptions, generate artwork in various styles, create visual content for creative projects, or need AI-powered image generation capabilities.
AI-powered user research through natural language. Use the Cookiy CLI and hosted API for study creation, AI interviews, discussion guide editing, participant recruitment, report generation, and optional quantitative questionnaires.
Use when creating a new beo skill, editing an existing beo skill, or pressure-testing a beo skill before deployment. This skill should win whenever the task is to make a beo skill robust against rationalization, misuse, or failure under pressure. Do not use it for project-specific AGENTS.md conventions, one-off solutions, or ordinary feature planning.