dot-opencode

Work inside a running marimo notebook's kernel — execute code, create cells, and build a notebook as an artifact. Use when the user wants to start a marimo notebook or work in an active marimo session.

Working on config and plugins for opencode

Hypothesis-driven debugging methodology: systematic investigation, binary search isolation, escalation criteria. Load when debugging complex, elusive, or multi-system bugs.

Systematic code refactoring methodology using ast-grep, comby, and manual transformations. Load when performing large-scale code restructuring or systematic transformations.

Deep research methodology: recursive exploration, branch-and-synthesize pattern, documentation structure. Load when conducting broad, open-ended research on technical or scientific topics.

Code review framework: 5-category evaluation, structured output format, severity levels. Load when performing thorough code reviews of changes, diffs, or pull requests.

Software development workflow patterns: exploration, implementation, testing, review cycles. Load this skill when coordinating multi-step development tasks or delegating software work.

Check if a marimo notebook is compatible with WebAssembly (WASM) and report any issues.

Query and explore the opencode session database using `opencode db` CLI. Use when: (1) Searching session history by title, directory, or date, (2) Inspecting conversation messages and parts within sessions, (3) Analyzing project or workspace data, (4) Reviewing todo lists across sessions, (5) Any task requiring structured queries against opencode's persisted state — sessions, messages, parts, projects, workspaces, todos, events, permissions, accounts. Trigger keywords: "session db", "opencode db", "session history", "conversation data", "past sessions", "session search".

Search and explore locally-generated cargo doc documentation for Rust projects and their dependencies. Use when: (1) looking up types, traits, functions, or modules in a Rust crate, (2) exploring the API surface of a local workspace crate or dependency, (3) browsing locally-built rustdoc output in target/doc/, (4) searching docs without an internet connection, (5) user mentions cargo doc, rustdoc, rust docs, or asks about Rust API documentation.

Extract text, tables, and structured data from PDFs. Use when processing any PDF for text extraction, table extraction, search, metadata, or conversion to markdown. Supports text-based and scanned/image PDFs with OCR.

Repository understanding and hierarchical codemap generation

Vendor external dependencies into a monorepo using git subtree. Use when adding, updating, or managing vendored third-party code, soft forks (pull-only), or push-pull subtrees for self-owned repos. Covers interaction with jujutsu (jj) colocated workflows.

Extract data from electronics/component datasheets (PDF). Use when processing datasheets for pin tables, electrical characteristics, timing specs, absolute maximum ratings, or ordering information. Combine with pdf-extraction skill.

Extract content from academic and scientific papers (PDF). Use when processing research papers for equations, algorithms, figures, references, or structured sections. Combine with pdf-extraction skill.

Use when you need to explore, search, or understand codebases using structural AST patterns. Ideal for finding specific code patterns, understanding code architecture, discovering API usage, or locating code smells across multiple files.

Use when you need to perform code refactoring, semantic transformations, or structural rewrites across multiple files. Ideal for API migrations, code modernization, breaking change adoption, or systematic code transformations.

Combine the best parts of multiple skills into one. Searches ClawHub, GitHub, skills.sh, skillsmp.com and other AI skill repos. Analyzes each safely, compares features, and builds a combined 'Frankenstein' skill with the best of each. Uses skill-auditor for security scanning and sandwrap for safe analysis. Use when: (1) Multiple skills exist for same purpose, (2) Want best-of-breed combination, (3) Building a comprehensive skill from fragments.

Guide to Jujutsu (jj) version control system. Use when working with commits, branches, pull requests, PRs, version control, rebasing, pushing, or when the user mentions jj, git, or version control operations.

Use when you need help with Neovim configuration, plugin development, Lua scripting, creating custom plugins, or troubleshooting Neovim setups. Also use for configuring LSP, treesitter, completion engines, keybindings, or Neovim-based workflows.