Menu
Skills in this repository
SkillsMP has collected 924 skills from mcorbett51090/RavenClaude. Open a skill to review its source and details.
mcorbett51090/RavenClaudeShowing 40 of 924 collected skills.
Playbook for shaping OneLake gold Delta tables to serve a Direct Lake semantic model efficiently — covers framing prerequisites, column naming rules, fallback prevention, and the on-OneLake vs on-SQL mode selection.
Design a CLI's command/subcommand surface, flags vs positionals, and config precedence (flags > env > file > default), then pick the idiomatic parser for the language. Use when starting a CLI or reworking a messy one.
Plan how a CLI ships and updates — single static binary vs runtime package, cross-compilation, install channels (Homebrew/Scoop/winget/npm/pipx), a build-stamped --version, and a safe installer. Use when making a tool installable and keeping it current.
Define a CLI's output contract — human by default, --json on demand, data to stdout, diagnostics to stderr — and an exit-code map treated as a public API. Use when a tool must serve both humans and scripts, or CI keeps passing on real failures.
Generate shell completions (bash/zsh/fish/PowerShell) from the parser and design config-file discovery + env-var conventions (XDG, TOOL_* prefixes). Use when adding tab completion or a config/env layer to a CLI.
Decide whether a full-screen TUI is warranted (vs a scriptable CLI), pick the framework (Ink / Bubble Tea / Textual / ratatui), and design the render-loop + non-TTY fallback. Use for interactive terminal dashboards, pickers, and wizards.
Pick the right data-pipeline orchestrator for a described workload by traversing the orchestrator-selection decision tree (workload shape → latency → asset-centric vs task-centric → team/ops capacity → cloud lock-in → engine), then return the recommended…
Design a correct, minimal DAG or software-defined-asset graph for a pipeline — derive the real upstream→downstream edges, pick the partition grain, choose the scheduling/triggering model (cron / sensor-deferrable / data-aware-asset), and decide catchup…
Make pipeline tasks safe to re-run and plan backfills that don't corrupt state — prove idempotency (deterministic partition keys, overwrite-by-partition), then add bounded retries with exponential backoff + jitter, and run a controlled backfill (partition…
Pick the right monorepo/build tool and package manager for a described repo by traversing the monorepo-tooling decision tree (language mix → scale → hermeticity need → tool), then return the recommended tool, the package-manager pick, the tradeoffs, and an…
Set and enforce dependency & package management across a monorepo: version policy (single-version vs independent), lockfile hygiene (commit + freeze in CI), automated batched upgrades (renovate/dependabot), supply-chain hygiene (SBOM, provenance/SLSA, digest…
Diagnose and fix a slow build by measuring the task graph and cache-hit rate, auditing cache CORRECTNESS (input-hash completeness, hermeticity leaks) before any speed tuning, then applying the highest-leverage fix (affected-only, remote cache, parallelism,…
Build a tiered, stage-fit investor pipeline and a warm-intro-first outreach sequence for a founder running a round. Produces a target list scored by stage-fit + thesis-fit + check-size, a warm-path map for each target, and a sequenced outreach plan that…
Model a startup cap table and the dilution a round causes — including option-pool shuffle, pro-rata, and post-money SAFE conversion — with worked arithmetic. Produces a post-round ownership table and surfaces the post-money-cap dilution gotcha. Reach for this…
Assemble a founder's fundraising data room — the structured set of documents investors expect in diligence — so a "send me the data" request never stalls the round. Produces a stage-appropriate checklist organized by section (corporate, financials, cap table,…
End-to-end workflow to build a Manifest V3 browser extension: decide which context owns each piece of logic (content script vs MV3 service worker vs injected page script vs popup/options), wire messaging between contexts, request the narrowest permissions…
Diagnose why mail is landing in spam (or pre-flight a domain before a big send) by traversing the deliverability triage tree — authentication, DMARC alignment, reputation/warm-up, list hygiene, content, and bulk-sender compliance — then return the specific…
Build a minute-by-minute run-of-show / show-flow: a timed table with a row per segment — time, duration, what happens, the cue, and a named owner/role — plus the contingency plan-Bs for the day-of.
Design the event plan and budget: goal/KPIs, format (in-person/virtual/hybrid), audience, a budget with a named contingency line, the break-even point in registrations/sponsorship, and the dated go/no-go gate.
Post-event measurement: compute ROI against the goal/KPIs set up front (revenue/pipeline, cost per attendee, sponsor renewal, NPS) — not vanity attendance — and run the debrief while it is fresh so lessons feed the next event.
Registration and attendee operations: model the funnel (reach -> visit -> register -> confirm -> attend) not a headcount, then run check-in as a throughput operation — lanes, staffing, badge/QR flow sized for peak arrival with a system-down fallback.
Sponsorship and revenue: define tiers by delivered value, build the prospectus, sell against value not logos, and fulfill every promise (placement, leads, speaking slot) with a checklist and proof of delivery so sponsors renew.
Keep spatial data trustworthy: geometry validity (ST_IsValid / ST_MakeValid, self-intersections, ring order), topology, declared-vs-actual SRID checks, coordinate-order (lon/lat) sanity, and validating geometry at load time so bad data never lands. Reach for…
Run content as a system — brief against search intent, build topic clusters around pillar pages, plan distribution, and measure leading vs lagging signals. Reach for this on a content-strategy or SEO-content question.
Run the computer-vision MLOps lane end to end: data/annotation -> CV task -> architecture choice -> training (transfer-learn first) -> eval by task (mAP/IoU/CER/OKS) -> serving/edge placement. CV-specific leakage (scene-aware split, augment-after-split).…
Manage a grant AFTER the award — set up, spend only on allowable/allocable/reasonable costs, track budget-vs-actual monthly, report on cadence, stay audit-ready through close-out. Reach for this once a grant is won (the post-award/compliance side; the…
Run the eye-care claims loop: verify both medical and vision eligibility before the visit, manage payor mix, and triage denials by cause (eligibility, coding/medical-necessity, wrong-payor-routed, timely-filing). Payor specifics are verify-at-use.
Engineer the exam lane: pretesting/workup done by a tech before the doctor enters, a workup-to-doctor handoff that protects chair time, and a tech-to-doctor ratio that lets one doctor run multiple lanes. Protect the scarcest resource — the doctor's chair.
Route an eye-care visit to medical insurance vs the vision plan deliberately, on the chief complaint and what the visit addressed. Code to the encounter, document medical necessity for medical claims, and flag every payor/coding specific verify-at-use.
Run the optical for profit: track and lift the capture rate (eyes examined -> Rx written -> Rx filled in your optical), run the frame board on inventory turns, manage the lab pipeline, and dispense within managed-vision-care formularies knowingly.
Build the eye-care schedule off recall: set recall/recare intervals by exam type, template exam-length to exam-type, and read capacity as lanes x exam length x fill rate. Recall, not walk-ins, is the primary schedule-filler.
Write and review defensible PT/rehab daily notes and evaluations — establishing medical necessity every visit, documenting skilled care as skilled, tying each note to a plan-of-care goal, and avoiding boilerplate that invites a denial or audit finding.
Prevent PT/rehab claim denials at the front end (eligibility, authorization, units, modifiers, documentation) and triage the ones that slip through to their root cause, then write a documentation-grounded appeal — confirming each payor's edits before billing.
Manage the PT/rehab plan of care end to end — goals, frequency/duration, certification, and the recertification clock — so the POC stays signed and current, visits trace to goals, and a lapsing certification is re-booked before it invalidates visits.
Plan outpatient PT/rehab clinic capacity and the schedule template against committed plan-of-care visit cadence, provider hours, patient flow, and the measured no-show/cancellation rate — so provider hours become completed, billable visits.
Calculate PT/rehab billable units correctly: separate timed (time-based, 15-min) from untimed (service-based) CPT codes, apply the 8-minute rule to total timed units, and place GP/KX/59 modifiers — confirming the payor's rule variant before billing.
Build Gutenberg blocks (block.json, the edit/save split, dynamic render_callback, attributes, supports) and themes (classic templates or block/FSE with theme.json), enqueuing assets with versioned handles the supported way.
Decide how to build a WordPress site: classic vs block/FSE theme, plugin vs theme vs must-use plugin for custom code, headless/decoupled vs traditional, and single vs multisite — matched to the editing model, not fashion.
Extend WordPress through actions and filters at the right hook and priority, register custom post types/taxonomies and REST routes, and query with WP_Query (or a $wpdb->prepare'd query) — keeping logic in a plugin, never editing core.
Secure WordPress: sanitize-in/escape-out, $wpdb->prepare for all dynamic SQL, nonce + capability checks on every action, least-privilege roles, disable file editing, force HTTPS, secure wp-config, and keep core/plugins/themes current.