Loading...
Loading...
Found 702 Skills
Rust project implementation guide for multi-crate workspace projects. Covers workspace config, toolchain (nightly + rustfmt + clippy + cranky + cargo-deny), strict lint rules (no unsafe/unwrap/expect/panic), error handling (thiserror + anyhow), async runtime (Tokio), TLS (rustls + aws-lc-rs), CI/CD (GitHub Actions with test/build/docker/SBOM), and coding conventions. Use when scaffolding, developing, or reviewing Rust applications.
Load this skill for any up-fetch task: `up(fetch, getDefaultOptions?)`, `upfetch(url, options?)`. Covers dynamic defaults, auth, request shaping, validation, error handling, lifecycle timing, and runtime caveats.
JavaScript runtime performance patterns for hot paths, loops, DOM operations, caching, and data structures. Framework-agnostic.
Breaks natural-language problem descriptions into sub-tasks suitable for DAG nodes. The entry point of the meta-DAG. Identifies phases, dependencies, parallelization opportunities, and vague/pluripotent nodes that can't yet be specified. Uses domain meta-skills when available. Activate on "decompose task", "break down problem", "plan workflow", "what are the steps", "sub-tasks", "task breakdown". NOT for executing the decomposed tasks (use dag-runtime), building the DAG structure (use dag-planner), or matching skills to nodes (use dag-skills-matcher).
Switch JDK, Kotlin, Gradle, Maven, or any SDKMAN-managed candidate when the user or runtime explicitly demands a different version. Use when the user says "switch to Java 17", "run with JDK 21", "use Gradle 8.x", asks about JAVA_HOME, a build fails with UnsupportedClassVersionError or "class file has wrong version", or the repo contains a `.sdkmanrc`. Operates on machines configured with SDKMAN (`$SDKMAN_DIR`, default `~/.sdkman`).
MUST be used whenever fixing correctness and error handling issues in a Flows app. This skill finds AND fixes bugs, missing error states, unhandled rejections, and edge-case failures — it does not just report them. Triggers: correctness, error handling, bug fix, edge case, crash, unhandled, null, undefined, empty state, loading state, error boundary, try catch, async error, useEffect cleanup, type guard, runtime error, robustness.
Layering and boundaries, web vs public API, app layout (clients, routes, logging), ports/adapters, runtime-portable domain/shared/utils code, multi-tenancy, DDD layout, or anti-patterns.
Interact with the Cargo platform via CLI. Use when the user wants to execute an action, run a workflow, trigger a batch, message an AI agent, query orchestration runtime tables (runs/batches/spans/records) with SQL, fetch segment records, or inspect a model schema.
Use the local `5dive` CLI on a 5dive runtime VM to spawn, inspect, send to, and tear down sibling agents. Trigger this skill whenever the user asks for a worker, sub-agent, side task, parallel run, "another agent", "fan out", "delegate", or anything that needs more than one Claude/Codex/Gemini process running at once on the host. Also trigger when the user asks to inspect, restart, or pair an existing agent, when they mention `/var/lib/5dive/`, or when they need a machine-readable health check (`5dive doctor --json`). Always prefer `5dive` over running coding CLIs by hand — it is the only sanctioned way to keep agents under systemd.
Performance review and testing: evaluate Core Web Vitals, page load times, bundle sizes, runtime performance, resource optimization, and rendering efficiency with browser-based measurement and benchmarking.
Data Cloud 360° view of a single Agentforce session. Pulls 24 STDM + GenAI DMO rows via the DC Query REST API, assembles a hierarchical session tree (Interaction → Step → Generation → GatewayRequest), renders a human-readable summary with transcript + per-turn topic/action invocations + LLM generations + tool calls + audit chain. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use investigating-agentforce-architecture instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud.
Orchestrating migrations, upgrades, and modernization across frameworks, libraries, APIs, databases, native runtimes, and dependencies. Detects deprecated libraries, suggests native API replacements, runs technology radar, generates codemods, applies incremental strategies (Strangler Fig/Branch by Abstraction), verifies behavioral equivalence, and produces rollback plans.