yugabyte

@yugabyte source repo

28 skills
0 followers
9 hours ago last updated

▌
Meko MCP Tools · yugabyte bundle
Behavioral guide for AI agents using Meko MCP tools. Triggers when calling MCP tools, storing memories, persisting knowledge, managing datapacks, or searching shared knowledge bases through Meko.

0
installs
▌
Meko Select Datapack · yugabyte bundle
Lists the user's Meko datapacks, shows authorization, supports search and pagination, and pins one as the active datapack for the current project. Triggers when the user says things like "switch datapack", "use the Acme datapack", "list my datapacks", "which datapack am I on", "pin Acme", or any request to change or inspect the active datapack. Also trigger before the first Meko MCP write of a session if no datapack pin exists and the user has more than one datapack.

0
installs
▌
Meko MCP Tools Desktop · yugabyte bundle
Behavioral guide for Meko MCP tools on desktop Claude. READ IT BEFORE calling any meko tool — it sets the required agent_id and workflow; calling a meko tool without it produces wrong-bucket writes. Use whenever the user mentions memory, Meko, datapacks, knowledge base, or conversations, or asks to remember/save/store anything. ALSO trigger (even with no tool or Meko keyword) when: (a) the user states ANY durable fact about themselves — name, role, team, tools, stack, preferences, conventions — INCLUDING facts dropped inside a task/technical question ("I use pnpm", "I'm evaluating X"); or (b) the user asks a RECALL question — "what do you know about me", "who am I", "what was the last thing I told you" — then search Meko (memory_search) first and never claim memory is unavailable without checking. On Desktop the agent_id is ALWAYS "claude_desktop" (or "meko_agent" for cross-project identity) — NEVER "claude_code".

0
installs
▌
Meko Select Datapack Desktop · yugabyte bundle
Lists the user's Meko datapacks, shows authorization, supports search and pagination, and pins one as the active datapack on Claude Desktop. Triggers when the user says things like "switch datapack", "use the Acme datapack", "list my datapacks", "which datapack am I on", "pin Acme", or any request to change or inspect the active datapack. Persistence is via memory_add (Desktop has no SessionStart hook), so the pin survives across sessions until the user clears it.

0
installs
▌
Meko Bmad Setup · yugabyte bundle
Sets up, configures, inspects, and uninstalls the Meko integration for the BMad Method. Verifies the installed BMad version, detects the Meko MCP connection, selects a datapack, and wires Meko recall (and, after explicit consent, artifact publishing) into BMad workflows via customization overrides. Triggers on the BMad menu code "MS", or when the user says "set up Meko for BMad", "configure the Meko BMad module", "check Meko BMad status", or "uninstall Meko from BMad".

0
installs
▌
Meko Bmad Context · yugabyte bundle
Recalls relevant Meko experience for an in-progress BMad workflow. Given a workflow name, the current objective, and an optional focused query, it searches Meko memories and (when a datapack is active) shared knowledge for prior decisions, constraints, preferences, unresolved risks, and related BMad outputs, then returns a compact structure. Triggers on the BMad menu code "MR", when a BMad workflow's external_sources directive asks to recall Meko context, or when the user says "recall Meko context for this workflow".

0
installs
▌
Meko Bmad Publish · yugabyte bundle
Publishes finalized BMad artifacts and one concise learning summary to the active Meko datapack after a BMad workflow has written its local output. Uploads permitted files via artifact_put and stores a single deduplicated memory_add summary of the durable decisions, constraints, open questions, and artifact hashes. Triggers on the BMad menu code "MP", when a BMad workflow's external_handoffs directive asks to publish to Meko, or when the user says "publish these BMad artifacts to Meko".

0
installs
▌
Git Rebase · yugabyte
Interactive git rebase workflow with conflict-by-conflict review. Use when the user asks to rebase a branch, rebase onto main, resolve rebase conflicts, or update a branch with upstream changes.

0
installs
▌
Branch Review · yugabyte
Review all code changes on the current branch compared to main, applying the hierarchical AGENTS.md engineering standards from each changed file's directory up to the repo root. Use when the user asks to review a branch, review changes, compare against main, do a code review, or check branch diff.

0
installs
▌
Post Pr Review · yugabyte
Post a single non-blocking GitHub PR review with inline line-anchored comments generated by the agent. Every comment is prefixed with `[AI]` plus a severity tag so reviewers can tell they are AI-generated and triage at a glance. Critical, Warning, and Suggestion findings are posted; Questions are not (they would make reviews too verbose). Use when the user asks to "post the review on GitHub", "post these comments on the PR", "post the findings as PR comments", or otherwise wants an in-chat code review persisted on a GitHub pull request. Typically runs as a follow-up to the `branch-review` skill but does not require it.

0
installs
▌
Pr Description · yugabyte
Create and update GitHub pull request descriptions using the project PR template. Use when the user asks to create a PR, write a PR description, update a PR description, or manage pull requests.

0
installs
▌
Pr Review Sweep · yugabyte
Sweep recently updated open GitHub PRs that need an AI review — never reviewed, or with new commits since the last AI review (incremental re-review, at most once per 24h) — running the branch-review skill and posting findings with the post-pr-review skill; fully automated, no per-PR confirmation. Use when the user asks to "sweep open PRs", "review all open PRs", "run the PR review sweep", or when invoked by the scheduled daily PR-review routine. Also accepts explicit PR numbers to force a review of specific PRs.

0
installs
▌
Voyager Release Notes · yugabyte
Generate yb-voyager release notes from a commit range, formatted like the YugabyteDB Voyager release-notes docs page. Use when the user asks to draft release notes, summarize a release, or write what's-new entries for a voyager version.

0
installs
▌
Update Yb Latest Stable · yugabyte
Bump YugabyteDB latest_stable in yb-versions.json, coordinate Jenkins migtest cluster upgrades, fix version-gated issue/integration tests, and open a PR only after all GitHub Actions pass. Also covers bumping the bundled CDC connector version in yb-cdc-connector-versions.json. Use when updating latest stable YB version, yb-versions.json, the CDC/debezium connector version, yb-cdc-connector-versions.json, Jenkins YB cluster, or Voyager supported YB versions.

0
installs
▌
Create Pr · yugabyte
Create a Pull Request for the current branch's changes. Use when the user wants to publish a branch for review as a GitHub PR.

0
installs
▌
Create Diff · yugabyte
Create a YugabyteDB Phorge diff for the current branch's changes. Use when the user wants to publish their changes for review.

0
installs
▌
Create Issue · yugabyte
Create a GitHub issue (or JIRA ticket) tracking a YugabyteDB change or bug. Use when the user needs a tracker reference and doesn't have one yet — e.g. before opening a PR/diff, or to file a standalone bug/feature request.

0
installs
▌
Yba Query CLI · yugabyte bundle
Query a running YugabyteDB Anywhere (YBA) control plane using the `yba` CLI (managed/yba-cli) — list/describe universes, tasks, backups, providers, alerts, users, storage/EAR/EIT configs, xClusters, RBAC, runtime config, telemetry providers, and more. Use when the user wants to inspect, list, describe, or look up the current state of a live YBA instance. Read-only: do not use for creating, editing, deleting, pausing/resuming, or upgrading YBA resources.

0
installs
▌
Review Backport · yugabyte
Review YugabyteDB backport diffs by comparing them against their original commits/diffs. Use when the user provides a Phorge backport diff ID (e.g. D51405) and wants to verify the backport is correct, or when reviewing backport revisions.

0
installs
▌
Ash Instrumentation · yugabyte bundle
Instrument YugabyteDB ASH (Active Session History) wait states: add a new WaitStateCode, choose the right macro for synchronous vs asynchronous/callback code paths, register background trackers, plumb ASH metadata through RPCs, and test with wait_states-itest. Use when adding or changing wait states, or when instrumenting a code path for ASH anywhere under src/yb.

0
installs
▌
Pg Code Style Guide · yugabyte
The code style guide for YugabyteDB's PostgreSQL fork: required conventions for ANY change under src/postgres -- follow upstream PostgreSQL's rules, explicit and implicit, while isolating and marking the YB delta so that the diff/merge tooling (git, Phorge, GitHub) and future PG major-version merges are not confused. Follow it when writing or editing backend C files or headers (planner, executor, catalog, commands, utils, yb_*.c), adding or wiring a GUC, adding a field to a PG-owned struct, adding an #include, creating or updating regress tests and expected .out files (yb.port.*, yb.orig.*), cherry-picking or merging upstream PostgreSQL commits, cleanup-only passes bringing an existing file up to these conventions, and reviewing or fixing a src/postgres diff before arc diff or when lint reports missing_yb_marker_for_yb_changes or another src/postgres check. These requests look like ordinary edits, but code written from general PostgreSQL knowledge violates the fork's conventions and gets rejected in lint or r

0
installs
▌
Ycql · yugabyte
Use when writing or reviewing CQL code, schema definitions, or application code that targets YugabyteDB's Cassandra-compatible YCQL API (port 9042). Triggers on YCQL tables, partition keys, TTL, batching, or any mention of YugabyteDB with Cassandra/CQL.

0
installs
▌
Ysql · yugabyte bundle
Use when writing or reviewing SQL, schema definitions, or application code that targets YugabyteDB's PostgreSQL-compatible YSQL API (port 5433). Triggers on CREATE TABLE, indexes, connections, transactions, sharding, migrations from PostgreSQL, or any mention of YugabyteDB with SQL.

0
installs
▌
Yba API · yugabyte bundle
Use when scripting, automating, or troubleshooting the YugabyteDB Anywhere (YBA) REST API — the control-plane API for self-managed YBA instances that creates and manages providers, releases, universes, backups, KMS, and DR. Triggers on `/api/v1/`, `/api/v2/`, `X-AUTH-YW-API-TOKEN`, `apiToken`, `customerUUID`, `taskUUID`, `Invoke-YbaRequest`, registration of a new YBA instance, or any mention of the YBA API. Does NOT cover YugabyteDB Aeon (use the Aeon API skill) or database access via YSQL/YCQL (use those skills).

0
installs
▌
Yba Terraform · yugabyte bundle
Use when writing, generating, or troubleshooting Terraform that drives YugabyteDB Anywhere (YBA) via the `yugabyte/yba` provider — installing YBA on a VM, registering the first customer, and creating cloud (AWS/GCP/Azure) or on-prem providers, storage configs, universes, backups, schedules, and restores. Also covers the upstream cloud Terraform (IAM user / service account / service principal) that grants YBA its node-deployment permissions, and the CLI commands to discover the VPC/subnet/security-group network info those manifests need. Triggers on `yba_installer`, `yba_customer_resource`, `yba_aws_provider`/`yba_gcp_provider`/`yba_azure_provider`, `yba_universe`, `yba_backup`, `source = "yugabyte/yba"`, or any mention of the YBA Terraform provider. Does NOT cover the YBA REST API directly (use the yba-api skill) or YugabyteDB Aeon.

0
installs
▌
Operator · yugabyte bundle
Use when provisioning, managing, or troubleshooting YugabyteDB universes on Kubernetes via the YugabyteDB Kubernetes Operator and YugabyteDB Anywhere CRDs (YBUniverse, YBProvider, Release, Backup, StorageConfig, PitrRestore, DrConfig, etc.). Triggers on kubectl apply, Helm install of yugaware, operator CRDs, or any mention of YugabyteDB with Kubernetes.

0
installs
▌
Yb RAG Langchain · yugabyte
Use this skill when building RAG, semantic search, or hybrid (vector + full-text) search on YugabyteDB with LangChain — including PGVectorStore setup, vector/GIN index creation, hybrid search configuration, metadata filtering, and relational + vector queries. Triggers on mentions of YugabyteDB + LangChain, PGVectorStore on YugabyteDB, pgvector + YSQL, or RAG pipelines using `langchain_postgres` against a YugabyteDB cluster.

0
installs
▌
Explain Plan Analyzer · yugabyte
Analyzes PostgreSQL (and YugabyteDB) EXPLAIN / EXPLAIN ANALYZE query plans to identify performance issues. Use this skill whenever a user pastes an explain plan, asks to analyze a query plan, mentions seq scans or full table scans, wants index recommendations, or asks why a query is slow. Trigger even if the user just says "look at this plan", "what's wrong with this query", or pastes raw EXPLAIN output.

0
installs

28 published skills