All Skills

HASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Design tools that agents can use effectively, including when to reduce tool complexity. Use when creating, optimizing, or reducing agent tool sets.

Develop custom Tekton Tasks and reusable pipeline components. Use when creating Tasks for Tekton Hub, building ClusterTasks, designing parameterized Task libraries, or packaging Tekton components for distribution.

Bidirectional conversion between Clojure and Scala. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Clojure↔Scala specific patterns. Use when migrating Clojure projects to Scala, translating Clojure patterns to idiomatic Scala, or refactoring Clojure codebases. Extends meta-convert-dev with Clojure-to-Scala specific patterns.

Bidirectional conversion between Elixir and Erlang. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Elixir↔Erlang specific patterns. Use when migrating Elixir projects to Erlang, translating Elixir patterns to Erlang idioms, or refactoring Elixir codebases to Erlang. Both run on the BEAM VM with the same OTP framework, making this conversion primarily syntactic with semantic preservation. Extends meta-convert-dev with Elixir-to-Erlang specific patterns.

Bidirectional conversion between Haskell and Scala. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Haskell↔Scala specific patterns. Use when migrating Haskell projects to Scala, translating Haskell patterns to idiomatic Scala, or refactoring Haskell codebases. Extends meta-convert-dev with Haskell-to-Scala specific patterns.

Manage, inventory, standardize, migrate, and test reusable Codex skills for the MetaSkill repository. Use when Codex needs to inspect local skills, convert a personal workflow into a public skill candidate, normalize skill folder shape, plan skill promotion, or decide whether a skill belongs in skill-management, publication-review, or skill-examples.

Review MetaSkill skills before publication for privacy, public-safe examples, frontmatter and folder standards, truthful capability claims, and resource consistency.

Use after the user has authorized GPT Pro help; manage a prompt-plus-sources workspace, route through ChatGPT Projects when available, and audit returned reasoning.

Synthesize source-indexed proof-material items into the final proof-usage playbook. Use when Codex needs to cluster proof items by proof shape, de-duplicate across sources, design reusable taxonomy entries, update proof-usage indexes and source maps, or preserve material-ID links from cooked proof entries.

Mine proof-heavy papers, notes, PDFs, Markdown, or LaTeX sources into source-indexed proof-material files. Use when the user wants to extract technically nontrivial lemmas, estimates, definitions, dependencies, reductions, constructions, or proof strategies, preserve paper locations and stable material IDs, run DeepSeek screening/backtests, and update the proof-material index rather than writing directly to proof-usage.

Turn a theory-first research idea into a proof-oriented research plan. Use after idea-creator-analysis, or when the user asks for theorem targets, assumptions, proof obligations, impossibility routes, analysis validation, or a non-experimental plan.

Verify research idea novelty against recent literature. Use when user says "查新", "novelty check", "有没有人做过", "check novelty", or wants to verify a research idea is novel before implementing.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.

Install or update Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path, then surface any per-skill install.md guidance. Use when a user asks to list installable skills, install a curated skill, update an installed skill, or install a skill from another repo (including private repos).

Independent DeepSeek-backed adversarial proof-audit step for existing theorem, lemma, proposition, or proof artifacts in Markdown, LaTeX, or proof logs. Use when asked to check, audit, verify, red-team, or adversarially review a proof; when a completed proof task needs a correctness pass; or when a broader proof workflow dispatches an independent reviewer to find gaps, hidden assumptions, counterexamples, or unjustified steps.

Generate and rank theory-first or proof-oriented research ideas. Use when the user wants non-experimental research ideas, theoretical methods, proof programs, theorem candidates, impossibility results, convergence/sample-complexity analyses, or "analysis" variants of idea creation.

Orchestrate a full theory-first idea discovery pipeline. Use when the user wants the analysis counterpart of idea-discovery: literature context, proof-oriented idea generation, novelty checking, DeepSeek critique, and an analysis plan instead of an experiment-first workflow.

Chrome-dependent academic literature scouting and idea planning. Use when the user gives a research idea, topic, question, or draft direction and wants Codex to browse Google, Google Scholar, and academic sources through the Codex Chrome plugin, identify relevant papers, explain what can be borrowed from them, and write a planNN.md before collecting PDFs or BibTeX.

Protocol-level two-agent paper writing workflow. Use when the user wants Codex to plan and review from global context while DeepSeek writes or revises the manuscript through the global deepseek-agent skill, with muxing-style-review used for explicit prose style checks.

Developer Role Session

Compare Local vs Remote State

Pull Remote State

Push to Remote Environment

Public-recording safety overrides

Build a New PBIR Report (preview)

Power BI Report (PBIR) Deploy Only

Send Structured Feedback to the Framework Maintainers

Incremental page addition to existing PBIR report

Execute Databricks Notebooks / Jobs

Extract Lineage from Fabric Artifacts

Databricks → Fabric migration assessment + execute

Ad-Hoc Raw Upload to Databricks