Results for “variant-calling”

Store, query, and export genomic variant data (VCF/BCF) using TileDB's sparse array technology for scalable population genomics workflows.

Start voice calls via the OpenClaw voice-call plugin.

Start voice calls via the Clawdbot voice-call plugin.

Version bump, generate changelog, tag, and prepare a release

Turn a cold dial into a conversation. A permission-based opener plus ready objection turns for "not interested," "no time," "just send me info," and "we already use X," tuned to one persona. Built for B2B SDRs and full-cycle reps, customizable to your persona, offer, and dialer. Trigger on "write a cold call opener", "give me objection responses", "handle 'not interested'", "cold call script for this persona", or any live-dial prep.

Designs and reviews Apex actions exposed to Flow via @InvocableMethod, focusing on wrapper DTOs, bulk-safe list contracts, and intentional error behavior.

Use CALL-E from Codex through the calle CLI. Use for CALL-E setup checks, authentication recovery, phone call planning, planned call execution, and call status checks.

Scan for viral app opportunities from trends, gaps, and user pain points

Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

Convene a four-voice council of advisors to surface structured disagreement and tradeoffs for ambiguous decisions, go/no-go calls, and multi-path choices.

Suggest better variable, function, and class names based on context and conventions.

Set price, IV rank, unusual activity, earnings, and VRP alerts with contextual notifications and management commands.

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.

Use when annotating VCF files with flanking sequence information (INFO/FS tag) or masking regions/variants in flanking sequences.

Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution

Refactors code by renaming variables, methods, classes, and types to improve clarity and intent, with automatic testing and commits after each rename.

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Manage version bumper operations. Auto-activating skill for DevOps Basics. Triggers on: version bumper, version bumper Part of the DevOps Basics skill category. Use when working with version bumper functionality. Trigger with phrases like "version bumper", "version bumper", "version".

Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. Standalone design exploration you can run anytime. Use when: "explore designs", "show me options", "design variants", "visual brainstorm", or "I don't like how this looks". Proactively suggest when the user describes a UI feature but hasn't seen what it could look like. (gstack)

Ask a local external advisor CLI (Claude or Gemini) and capture a reusable artifact

Alias for $plan --consensus

Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.