Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

davidB

@davidb source repo

3 published skills

  1. ▌
    Tda · davidb bundle
    Work tasks from the tda task manager as an AI agent — find a claimable task (globally or for the current repo), claim it, pull ancestor context, refine into subtasks, log progress notes, and complete it. Use when asked to "work on the next task", "pick a task", or to create/update tasks in tda.
    0
    installs
  2. ▌
    Comonteur · davidb bundle
    Build and edit video scenes, shots, animations and timelines inside Blender through the comonteur helper library, in a project that has `timeline.blend`, `timeline.toml` or `.comonteur/`, or starting one from scratch. Use for: scaffolding a new video project, creating or changing a shot (`shots/*.blend`), title cards and kinetic text, keyframes and GSAP-named eases, staggered reveals, linking components from `lib/*.blend`, rendering review frames, assembling the VSE timeline from `timeline.toml`, and importing an existing HyperFrames project. Read this before writing any `bpy` code against such a project — raw `bpy` bypasses the ownership and journal system that lets a human edit the same `.blend` at the same time.
    0
    installs
  3. ▌
    Kubectl View Allocations · davidb bundle
    Use when inspecting Kubernetes resource allocation with kubectl view-allocations. For allocation questions, use kubectl view-allocations first and do not replace it with native kubectl get/describe/top/jsonpath queries. Covers cluster/node/namespace/pod requests, limits, allocatable, free capacity, ALL resources including GPU and custom resources (not just CPU/memory), taint-filtered node views, tree-view grouping via -g, multi-column sort via --sort, CSV exports, metrics-server utilization via kubectl view-allocations -u, kubeconfig/context access checks, and allocation-focused troubleshooting. Trigger for CPU, memory, GPU, pod capacity, overcommit, missing requests/limits, tainted nodes, or comparing requested/limit/utilization data in a Kubernetes cluster. WARNING: default output excludes tainted nodes — results may be empty or partial on clusters where all nodes have taints (e.g. control-plane-only, GPU, dedicated workload nodes).
    0
    installs