All authors
Claude Skills by mcorbett51090
github.com/mcorbett51090964 skills6 installs216 views
- Design A Tracking PlanTurn product and business questions into an event tracking plan — derive the event taxonomy (object-action naming), the properties, the naming convention, the identity model (anonymousId → userId stitching), and the per-event spec table, captured as the contract instrumentation builds to. Reach for this when the user asks "what events should we track?", "how should we name these?", or "how do we stitch anonymous to known users?". Used by `event-taxonomy-architect` (primary).Votes: 0GitHub stars: 7
- Implement Event Instrumentation And ConsentImplement a tracking plan as working event collection — typed client/server-side Track/Identify calls, a codegen'd tracking library, schema validation in CI, consent gating at the source (Google Consent Mode v2 / IAB TCF / GPC), destination + reverse-ETL wiring, then QA the live stream. Reach for this when the user asks "implement these events", "add schema validation to CI", "wire consent", or "why is this event missing/wrong?". Used by `instrumentation-engineer` (primary).Votes: 0GitHub stars: 7
- Consult To Treatment ConversionTurn aesthetic consults into booked treatments: read where conversion leaks (offer clarity, provider-set treatment plan, transparent pricing, financing, same-day booking, follow-up cadence) and fix the highest-leak step first — without making a clinical or pricing determination.Votes: 0GitHub stars: 7
- Scope Of Practice And SupervisionMap the med-spa compliance structure — scope of practice, good-faith exam / medical supervision, consent and adverse-event protocols, product handling — as operational structure, flagging every state-specific rule [verify-at-use] and routing the actual determination to the medical director and a licensed professional. Flag, never decide.Votes: 0GitHub stars: 7
- Service Mix Injectables Devices MembershipsTilt the med-spa service mix toward contribution: read revenue and margin per provider-hour and per room-hour across injectables, energy devices, skincare retail, and memberships; model capital-device payback on realistic volume; size memberships on redemption and the capacity they pre-commit.Votes: 0GitHub stars: 7
- Treatment Room And Injector UtilizationRead a med spa on its two scarce inventories — injector-hours and treatment-room-hours. Utilization = productive hours booked / available, read by provider and by room and by daypart; confirm the current capacity is full before adding an injector, a room, or a device.Votes: 0GitHub stars: 7
- Build Rcm ScorecardBuild a net-collection-led RCM scorecard with first-pass, denial-by-category, and days-in-A/R, each defined and baselined. Reach for this to instrument the cycle.Votes: 0GitHub stars: 7
- Prevent DenialsCategorize denials by root cause and owner and push fixes upstream to registration and authorization, instead of only appealing. Reach for this when the denial rate is high.Votes: 0GitHub stars: 7
- Read Coding DenialsTrace coding denials to documentation, code selection, or modifier use as decision-support, never to up-coding. Reach for this when coding denials rise.Votes: 0GitHub stars: 7
- Read The Cash CycleRead net collection rate, first-pass resolution, and days-in-A/R together, against benchmark, so a cash problem is diagnosed correctly. Reach for this on any collections question.Votes: 0GitHub stars: 7
- Work Down ArPrioritize an A/R work-down by aging bucket, payer, and recoverable dollars, with timely-filing risk first. Reach for this when A/R piles up.Votes: 0GitHub stars: 7
- Budget Memory CostsPut a defensible number on a memory system — break-even against a named baseline, growth and caps, cache-invalidation cost, and cost per correct answer. Reach for this on any pay-for-itself question.Votes: 0GitHub stars: 7
- Build Memory EvalProve a memory system earns its write path — golden set with provenance, judged failure modes, the runnable bake-off, and cost per correct answer. Reach for this before adopting, replacing or retiring any memory system.Votes: 0GitHub stars: 7
- Choose Memory ParadigmDecide whether to build a memory system at all, and if so which paradigm — raw context, flat retrieval, LLM-extraction or agentic — behind a mandatory baseline-first gate. Reach for this before any memory design work.Votes: 0GitHub stars: 7
- Design Forgetting PolicyDesign retention and erasure before the first write — TTL, caps, decay, consolidation timing, dedup, contradiction handling, and what a delete actually leaves behind. Reach for this on any durable store.Votes: 0GitHub stars: 7
- Map Memory SurfaceName the storage surface a write actually lands on — who holds the bytes, who executes the write, and what trust model comes with it. Reach for this before writing any memory design down.Votes: 0GitHub stars: 7
- Memory Poisoning ReviewAudit an agent's durable memory for poisoning risk and harden it against OWASP ASI06 — enumerate write paths reachable from untrusted input, classify read-only vs read-write, verify audit and rollback. Reach for this when a diff touches a memory store.Votes: 0GitHub stars: 7
- Api Plugin Openapi HygieneMake a REST API safe and correct to expose as a Microsoft 365 Copilot API plugin — lay out the four files (app manifest + plugin manifest + OpenAPI + adaptive cards), verify the plugin-manifest↔OpenAPI `operationId` mapping both ways, respect the OpenAPI-for-Copilot subset, write model-readable operation descriptions, budget responses to ~66% of the 25-item/~4096-token wall, and wire Entra OAuth2/API-key auth (with the GCC-High caveat). Use when building or reviewing a Copilot API plugin.Votes: 0GitHub stars: 7
- Copilot Agent Eval HarnessBuild the golden-prompt regression set + pre-publish evaluation gate for a Microsoft 365 Copilot agent — author representative + adversarial prompts, check grounding accuracy and citation correctness, stress the declarative-agent hard limits (50/25/4096/45s, no-loop), and gate publish on the results. Use before declaring any declarative or custom-engine agent done, and on every manifest/grounding change.Votes: 0GitHub stars: 7
- Copilot Connector Schema DesignDesign a Microsoft 365 Copilot (Graph) connector schema — choose synced vs federated (MCP), declare property attributes (searchable/queryable/retrievable), apply the mandatory semantic-label map (title/url/createdBy/...), ingest ACLs for per-user trimming, and plan crawl/refresh + semantic-index latency. Use when building a Copilot connector to ground Copilot on a line-of-business store.Votes: 0GitHub stars: 7
- Declarative Agent Manifest AuthoringAuthor and review a Microsoft 365 Copilot declarative-agent manifest — pin the schema version (v1.8), keep instructions within the ~8,000-char budget, declare only the needed capabilities, write scope-demonstrating conversation starters, wire API actions, and pass manifest + Responsible-AI validation against the 50/25/4096/45s hard-limit wall. Use when building or reviewing a declarative agent.Votes: 0GitHub stars: 7
- Oversharing Remediation PlaybookRemediate Microsoft 365 oversharing BEFORE enabling Copilot — assess the blast radius, then run the sequence (RCD/RSS reach-reduction → Purview sensitivity labels + DLP-for-Copilot → site/permission cleanup → enable), framing RSS/RCD as reach-reduction and NOT a security boundary, with owners, verification, comms, and rollback. Use when planning a Copilot rollout over a tenant with uncertain permissions.Votes: 0GitHub stars: 7
- Capacity Sizing And IsolationPlaybook for sizing Fabric capacity SKUs, isolating noisy workloads across capacities, configuring surge protection and smoothing, and diagnosing throttling — the FinOps and operations companion to the capacity-finops knowledge file.Votes: 0GitHub stars: 7
- Direct Lake Gold ShapingPlaybook 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.Votes: 0GitHub stars: 7
- Fabric Alm PromotionPlaybook for promoting Fabric workspace items from dev to test to prod using Git integration, deployment pipelines, and the Fabric CLI — covers branch strategy, metadata-only deploys, and the pre-promotion checklist.Votes: 0GitHub stars: 7
- Fabric Ingestion Method SelectionDecision playbook for choosing the right Fabric data ingestion method — Mirroring, Copy job, pipeline Copy activity, Dataflow Gen2, or Eventstream — based on source type, latency, cost, and CDC requirements.Votes: 0GitHub stars: 7
- Medallion Layer DesignPlaybook for designing bronze/silver/gold medallion layers on OneLake — per-layer V-Order, file-size targeting, partitioning vs Liquid Clustering, deletion vectors, and materialized lake view decisions.Votes: 0GitHub stars: 7
- Batch Request DesignPlaybook for consolidating multiple Microsoft Graph API calls into a single $batch request — request shaping, dependency ordering, error handling per-response, and the throttling interaction that makes batching both necessary and tricky. Owned by graph-api-engineer.Votes: 0GitHub stars: 7
- Delta Query And Change NotificationsPlaybook for tracking Microsoft Graph resource changes using delta queries (polling) and change notifications (webhooks/subscriptions) — choosing between them, bootstrapping delta tokens, handling subscription lifecycle, and the rich-notification decryption hand-off. Owned by graph-workloads-engineer.Votes: 0GitHub stars: 7
- Odata Query BuilderPlaybook for constructing well-shaped Microsoft Graph OData queries: $select, $filter, $expand, $search, $count, $orderby, $top, $skip, the ConsistencyLevel header for advanced queries, and the common 400-error patterns. Owned by graph-api-engineer.Votes: 0GitHub stars: 7
- Permission Least Privilege ReviewStep-by-step playbook for auditing a Microsoft Graph app's permission scope list: delegated vs application decision, narrowing over-broad scopes, finding resource-scoped alternatives, and the escalation criteria for ravenclaude-core/security-reviewer. Owned by graph-identity-engineer.Votes: 0GitHub stars: 7
- Throttling Backoff HandlerPlaybook for designing a correct Graph API throttling (HTTP 429) response handler: reading Retry-After, exponential backoff with jitter, per-resource throttle budgets, and the SDK built-in retry middleware that makes hand-rolling unnecessary for most cases. Owned by graph-api-engineer.Votes: 0GitHub stars: 7
- Computer Vision PipelineRun 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). Seams back to training/serving/monitoring agents.Votes: 0GitHub stars: 7
- Feature Store ConsistencyPrevent training-serving skew: compute features once via a feature store or shared transformation so training and serving use identical logic, with point-in-time correctness for temporal features and no leakage of future data.Votes: 0GitHub stars: 7
- Ml Experiment TrackingPlaybook for setting up and operating an experiment tracking system (MLflow or Weights and Biases) — what to log, run comparison workflow, promotion to the model registry, and avoiding the common leakage and cherry-picking pitfalls.Votes: 0GitHub stars: 7
- Model MonitoringKeep production models honest: monitor input/data drift, prediction/concept drift, and performance decay (when labels arrive); define the retraining trigger up front (schedule/threshold/drop); alert on model health; and close the loop to retraining.Votes: 0GitHub stars: 7
- Model ServingServe models reliably: choose online vs batch by the use case, deploy a versioned model from the registry, optimize latency to a budget (batching/quantization/distillation/hardware), and roll out safely with shadow -> canary -> full.Votes: 0GitHub stars: 7
- Reproducible TrainingBuild reproducible training: a versioned prep->train->evaluate->register pipeline (not a notebook), experiment tracking (params/metrics/code/data/env), a model registry as source of truth, and leakage-free time-aware validation.Votes: 0GitHub stars: 7
- Android CraftBuild native Android the platform way: state-driven Jetpack Compose (state hoisting, remember, list keys), coroutines/Flow with lifecycle-scoped structured concurrency, Keystore/EncryptedSharedPreferences, WorkManager background respecting Doze, and Material + accessibility.Votes: 0GitHub stars: 7
- App Store Release PipelineStep-by-step guide for automating the iOS App Store and Google Play release pipeline — code signing, build automation with Fastlane, TestFlight and internal track distribution, phased rollout, and the common pipeline failure modes.Votes: 0GitHub stars: 7
- Cross Platform MobileBuild React Native/Flutter well: maximize shared logic while honoring per-platform conventions, manage the bridge/platform-channel native boundary (and write native modules when needed), avoid framework-specific performance pitfalls, and handle push/deep-links/offline once with secrets in the secure store.Votes: 0GitHub stars: 7
- Ios CraftBuild native iOS the platform way: state-driven SwiftUI with correct property-wrapper ownership, Swift Concurrency (async/await, actors, @MainActor), Keychain secure storage, lifecycle/background-task handling, and Human Interface Guidelines + accessibility.Votes: 0GitHub stars: 7
- Mobile Platform ChoiceDecide native vs React Native vs Flutter by the app's real needs (platform-specific UX, performance, OS-feature access, team), and set the offline-first sync strategy (local source of truth, write queue, conflict resolution) and lifecycle-survival plan.Votes: 0GitHub stars: 7
- Diagnose PullthroughDiagnose application-to-funded fall-out stage-by-stage and name the worst fallout stage — fix it before buying more apps. Reach for this on a pull-through question.Votes: 0GitHub stars: 7
- Frame Pipeline RiskTie fallout assumptions to locked-pipeline exposure and frame the lock/pipeline risk — route the hedge to the risk authority. Reach for this on a lock or rate-risk question.Votes: 0GitHub stars: 7
- Model Cost To OriginateCompute cost-to-originate (fixed + variable per loan) and the breakeven volume that the rate swing must clear. Reach for this on a unit-economics question.Votes: 0GitHub stars: 7
- Route ComplianceFrame operational compliance workflow and QC/defect signals — and route every TRID/ECOA/HMDA/fair-lending determination to counsel. Reach for this on a compliance or audit-readiness question.Votes: 0GitHub stars: 7
- Size Cycle CapacityMeasure app-to-close cycle, find the bottleneck stage, and size processor/LO capacity as a function of cycle — staff to the cycle, not a ratio. Reach for this on a cycle or staffing question.Votes: 0GitHub stars: 7
- Grow Membership And Visitor RevenueDesign the museum's earned-and-contributed revenue engine — the admissions/pricing model (timed ticketing / dynamic / pay-what-you-wish / free-admission, with the access-vs-revenue trade-off modeled), a tiered membership program built for behavior with an acquisition-and-renewal/retention engine (first-year renewal focused), the development levers (patron cultivation, corporate sponsorship, galas), and a named earned-vs-contributed revenue-mix target with its levers. Reach for this when the u...Votes: 0GitHub stars: 7
- Manage Collections And ExhibitionsSteward a collection and build the exhibitions it feeds — run the accession/deaccession ethics gate (AAM/AAMD; deaccession proceeds fund collection care/acquisition only), cataloging, provenance & NAGPRA due diligence, condition reporting, loans in/out, insurance/valuation, storage & environmental controls, the collections-CMS fit (TMS/Axiell/PastPerfect/CollectionSpace), and the exhibition project lifecycle (concept → checklist & loans → interpretation → budget → schedule → install/condition...Votes: 0GitHub stars: 7