scylladb
- 27 skills
- 0 followers
- 13 hours ago last updated
- ▌ Managing Argus Release Plans · scylladb bundleUse when creating or updating an Argus release test plan (argus planner create/update), building a plan from a Confluence test-plan/strategy page, mapping Confluence-named tests/categories to real Argus tests via argus search, resolving people named in a doc to Argus usernames via argus users search/get, or setting up label-based test triggering (argus test execute --plan-id --label) for a release. Also covers reading an existing plan as a template (argus planner get) and the confirmation checklist before writing anything.
- ▌ Benchmarks · scylladbGuide for running and writing coodie vs cqlengine performance benchmarks. Use when asked to run benchmarks, add new benchmarks, investigate performance, or debug benchmark failures.
- ▌ Modern Python · scylladb bundleConfigures Python projects with modern tooling (uv, ruff, ty). Use when creating projects, writing standalone scripts, or migrating from pip/Poetry/mypy/black.
- ▌ Test Refactoring · scylladb bundleGuides refactoring of Python test suites to reduce duplication using pytest.mark.parametrize, split large monolithic test files into focused modules, and deduplicate mirrored sync/async test classes. Use when test files exceed 400 lines, when multiple test functions share identical structure with different inputs, or when sync and async test classes are copy-pasted mirrors of each other.
- ▌ Designing Workflow Skills · scylladb bundleGuides the design and structuring of workflow-based Claude Code skills with multi-step phases, decision trees, subagent delegation, and progressive disclosure. Use when creating skills that involve sequential pipelines, routing patterns, safety gates, task tracking, phased execution, or any multi-step workflow. Also applies when reviewing or refactoring existing workflow skills for quality.
- ▌ Scylladb Cloud MCP · scylladbHelp users set up and use the ScyllaDB Cloud MCP server to manage ScyllaDB Cloud clusters via AI agents. Use this skill when a user wants to manage ScyllaDB Cloud programmatically through an AI agent, configure the MCP server, create or monitor clusters via MCP, or integrate ScyllaDB Cloud management into an agentic workflow. Triggers on "ScyllaDB Cloud MCP", "MCP server ScyllaDB", "manage ScyllaDB with AI agent", "ScyllaDB MCP setup".
- ▌ Scylladb Alternator · scylladb bundleGuide users building against ScyllaDB's DynamoDB-compatible API (Alternator). Use this skill when a user is porting a DynamoDB application to ScyllaDB, using boto3/AWS SDK clients against ScyllaDB, or asking about Alternator setup, write isolation, or load balancing. Triggers on "Alternator", "DynamoDB API", "DynamoDB compatible", "boto3 with ScyllaDB", "migrate from DynamoDB", "aws-sdk against ScyllaDB", "alternator_port", "alternator_write_isolation".
- ▌ Scylladb Kubernetes · scylladb bundleGuide users deploying and operating ScyllaDB on Kubernetes via the official ScyllaDB Operator. Use this skill when a user is setting up a ScyllaCluster, configuring node storage/CPU pinning for ScyllaDB pods, installing the Operator, or troubleshooting a Kubernetes-based ScyllaDB deployment. Triggers on "ScyllaDB Operator", "ScyllaCluster", "scylla-operator", "ScyllaDB on Kubernetes", "ScyllaDB Helm chart", "NodeConfig", "ScyllaDB EKS", "ScyllaDB GKE", "ScyllaDB OKE", "ScyllaDB kubernetes deployment", "exposeOptions", "ScyllaCluster TLS/mTLS", "ScyllaDB Manager backup/restore on Kubernetes", "multi-datacenter ScyllaDB", "externalSeeds".
- ▌ Scylladb Cloud Setup · scylladb bundleGuide users through connecting to a ScyllaDB Cloud cluster, choosing the correct driver and version, and configuring authentication. Use this skill when a user needs to connect to ScyllaDB Cloud, pick a CQL driver, check a driver version, configure credentials, or troubleshoot connection issues. Triggers on "connect to ScyllaDB Cloud", "ScyllaDB connection", "ScyllaDB driver setup", "which driver", "driver version", "Java driver", "Python driver", "CQL connection", "DC-aware load balancing", "ScyllaDB credentials", "connection bundle".
- ▌ Scylladb Data Modeling · scylladb bundleScyllaDB CQL data modeling patterns and anti-patterns. Use when designing tables, reviewing schemas, migrating from SQL or MongoDB, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "ScyllaDB data model", "partition key", "clustering column", "primary key", "CQL table design", "ALLOW FILTERING", "large partitions", "hot partitions", "query-first design", "secondary index", "materialized view", "schema review", "wide partition", "tombstones", "time series", "BATCH", "paging", "fetch size".
- ▌ Scylladb Vector Search · scylladb bundleGuides ScyllaDB Cloud users through implementing and optimizing Vector Search for semantic similarity, RAG, and similar use cases. Use this skill when users need to store and query embeddings, build vector indexes (HNSW), run approximate nearest neighbour (ANN) queries, apply filtering (global/local secondary indexes), configure quantization, or integrate with LLM frameworks (e.g. LangChain). Also use when users mention "vector", "embeddings", "similarity search", "ANN", "nearest neighbor", "RAG", "semantic search", or "recommendation system" in the context of ScyllaDB.
- ▌ Stack Sync · scylladbManage stacked PRs in scylla-cluster-tests using the gh-stack CLI extension (GitHub's native stacked PR support, public preview since 2026-07-31). Use when asked to split a large change into a chain of small reviewable PRs, check stack status, add/push/sync/rebase/merge stack layers, or navigate between stack branches. Covers the fork-vs-upstream remote nuance specific to SCT's contribution model. Adapted from the official github/gh-stack agent skill.
- ▌ Code Review · scylladb bundleGuides AI-assisted code review of SCT pull requests. Use when reviewing a PR, checking a diff for correctness, evaluating method signature changes across class hierarchies, verifying override compatibility, checking import conventions, error handling patterns, backend impact, test coverage, or provision label requirements. Covers inheritance safety, polymorphic method audits, and SCT-specific review criteria.
- ▌ Writing Plans · scylladb bundleWrite, review, or restructure an implementation plan for the SCT repository. Triggers: "create a plan", "write a plan", "draft a plan", "save a plan", "make a plan for", "generate an implementation plan", "planning document", "design doc", "implementation roadmap", "feature rollout", "mini-plan", "break this into phases", "plan before implementing", or reviewing and shortening an existing plan. Supports two formats: full 7-section plans for multi-phase work (1K+ LOC, tracked in MASTER.md) and lightweight mini-plans for single-PR changes (under 1K LOC, in docs/plans/mini-plans/). Routes automatically based on PR plans label, user input, or task size estimate.
- ▌ Commit Summary · scylladb bundleGenerate weekly commit summary reports for SCT repository. Use when asked to create a commit summary, weekly report, changelog, or "last week in SCT" issue. Applies to summarizing git commits from scylla-cluster-tests master branch for developer audiences. Covers running sct_commits_summary.py, filtering commits by importance, and writing prose summaries with embedded GitHub links.
- ▌ Writing Nemesis · scylladbGuides writing new nemesis (chaos engineering disruptions) for the SCT framework. Use when creating a new NemesisBaseClass subclass, adding disruption logic, setting nemesis flags, or configuring target node pools. Covers the sdcm/nemesis/ package structure, auto-discovery, flag filtering, CI configuration, and unit testing patterns.
- ▌ Designing Skills · scylladb bundleGuides the design and structuring of AI agent skills for the SCT repository with multi-step phases, progressive disclosure, and dual-platform compatibility (GitHub Copilot and Claude Code). Use when creating new skills, reviewing existing skills, restructuring AI guidance into modular skill directories, editing SKILL.md files, or improving agent instructions.
- ▌ Migrate To Sizing · scylladb bundleMigrate SCT test configs and pipeline jobs from literal instance_type params to constraint-based sizing_db/sizing_loader/sizing_monitor. Use when converting instance_type_db, gce_instance_type_db, azure_instance_type_db, instance_type_loader, instance_type_monitor to sizing constraints. Covers identifying instance specs, choosing vcpu/memory/arch/disk constraints, running sizing preview, and handling multi-DC or special params like nemesis_grow_shrink_instance_type.
- ▌ Labeling Pipelines · scylladb bundleGuides labeling and linting test-case YAML files in SCT with test_metadata sections. Use when bulk-adding test_metadata to multiple test cases, running lint-test-docs to find coverage gaps, or auditing label accuracy across a directory. Triggers: "label pipelines", "add metadata to test cases", "bulk document tests", "find missing test_metadata", "lint test docs".
- ▌ Profiling Sct Code · scylladb bundleProfile Python code in SCT to find CPU, memory, and concurrency bottlenecks using cProfile, scalene, memray, and py-spy. Use when a test or framework operation is unexpectedly slow, memory usage grows unbounded, you need to find which functions dominate CPU time, or you want to verify that an optimization actually improved performance. Covers profiling unit tests and full SCT test runs.
- ▌ Writing Unit Tests · scylladb bundleGuides writing and debugging unit tests for the SCT framework using pytest conventions. Use when creating new test files in unit_tests/, adding test cases, mocking external services, setting up fixtures, or reviewing test coverage. Covers network-blocking patterns, FakeRemoter, moto for AWS mocking, monkeypatch, and common pitfalls.
- ▌ Package Installation · scylladbGuides writing remote package installation commands (apt-get, yum, dnf, zypper) in SCT code. Use when adding apt-get install/update, yum install, dnf install, or zypper install calls via remoter.run/remoter.sudo. Ensures timeouts, retries, and non-interactive flags are always present to prevent hangs in CI.
- ▌ Fix Backport Conflicts · scylladbFix inline merge conflict markers in backport PRs by resolving conflicts and recommitting cleanly with original metadata preserved. Use when a backport PR has unresolved conflict markers, a cherry-pick produced merge conflicts, or a PR has the 'conflicts' label and needs to be made ready for review. Supports bulk mode for multiple PRs.
- ▌ Reviewing Pipeline Docs · scylladb bundleGuides reviewing and generating test_metadata sections for SCT test-case YAML files. Use when adding or auditing test_metadata to a test-case YAML, checking that description, tier, test_type, stress_tools, nemesis_labels, and features are accurate and complete. Triggers: "add test_metadata", "audit test YAML", "fill in pipeline labels", "document test case", "run lint-test-docs", "review test_metadata". Covers the TestMetadata pydantic model, taxonomy values, cross-reference rules, and validation.
- ▌ Perf Weekly Status Report · scylladb bundleGenerate Gmail-compatible HTML performance weekly status reports from Argus CLI data. Use when asked to produce a weekly perf summary, create a performance status email, aggregate latency and throughput results across enterprise perf tests, or generate an HTML report for stakeholders. Covers predefined-throughput-steps, latency-650gb-with-nemesis, rolling-upgrade, and microbenchmark tests using argus run list and argus run results commands.
- ▌ Writing Integration Tests · scylladb bundleGuides writing and debugging integration tests for the SCT framework that interact with real external services. Use when creating tests requiring Docker, AWS, GCE, Azure, OCI, or Kubernetes backends. Covers service labeling, credential skip patterns, Docker Scylla fixtures, resource cleanup, and common pitfalls.
- ▌ Test Run Comparison Reports · scylladb bundleGenerate Confluence-compatible HTML comparison pages from multiple SCT test runs. Use when comparing performance or elasticity test results across runs with different parameters (instance types, configurations, versions). Covers fetching run metadata and latency results from Argus API and S3 logs, extracting hdr_summary P99/P90 and throughput metrics per phase, building styled HTML tables with pass/fail color coding, and linking to Argus run pages. Applies to perf-regression, elasticity, and latency tests that use the latency_calculator_decorator.