메뉴
이 저장소의 skills
SkillsMP는 mcorbett51090/RavenClaude에서 924개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
mcorbett51090/RavenClaude수집된 skill 924개 중 40개를 표시합니다.
Use when creating, deploying, or managing Dataverse web resources for model-driven apps. Covers JavaScript form scripts (OnLoad, OnSave, OnChange events), HTML dashboard pages, CSS styling, image resources, navigation/side panes, ribbon/command bar…
원문 언어: 영어
Design a demo that maps to the buyer's discovered pain instead of touring features — build a Great Demo!-style storyline (show the compelling result first, then peel back only the layers the buyer asked for), tie every moment to a discovered pain and its…
원문 언어: 영어
Decide if a POC is warranted and, if so, write measurable success + exit criteria a champion signs before kickoff, scope a time-boxed plan, and build the evaluation scorecard that converts a passed POC to a technical win. Reach for this when a prospect asks…
원문 언어: 영어
Respond to an RFP/RFI/RFQ — decide go/no-go before committing effort, then build a compliant, scannable requirement-by-requirement response matrix (comply / partial / roadmap / no-bid), thread the win themes, and run the compliance checklist so the bid isn't…
원문 언어: 영어
Answer a security / vendor-risk questionnaire (SIG, CAIQ, VSA, or a bespoke one) honestly and defensibly — map every answer to an actual control and its SOC 2 / ISO 27001 evidence, state shipped vs roadmap vs not-applicable plainly, flag any unverifiable…
원문 언어: 영어
Run value-based technical discovery before any demo or POC — frame the deal with MEDDPICC, surface the prospect's pain and its quantified business impact, identify the decision criteria/process/champion, and capture it all in the discovery-notes template so…
원문 언어: 영어
Discover great-but-low-visibility ideas — the fringe excellence mainstream search buries under popularity. Given a seed (a name, repo, post, or topic), traverse its citation/collaborator graph + the periphery sources, score each candidate on depth × novelty ×…
원문 언어: 영어
Decide whether to pay down a specific tech-debt by sizing its carrying cost and payback against the roadmap — not all-or-nothing. Reach for this before a 'we must stop and refactor' or 'we never have time' reflex.
원문 언어: 영어
Design a structured hiring loop — rubric, consistent questions, evidence-based scoring, a debrief that surfaces dissent — over a vibe-based one. Reach for this before scheduling interviews.
원문 언어: 영어
Diagnose why delivery is unpredictable using flow + DORA as system signals, find the constraint, and fix it — never by velocity-quota'ing people. Reach for this when dates keep slipping.
원문 언어: 영어
Run a 1:1 that serves the engineer — agenda from them, growth thread, blockers surfaced — not your status update. Reach for this before defaulting to a status read.
원문 언어: 영어
Draft a performance review from dated, observable behavior with impact — specific, bias-checked, growth-oriented. A draft for a human to own, never a verdict.
원문 언어: 영어
Use when an agent must PROGRAMMATICALLY UPDATE an existing model-driven Power Apps app (including its custom pages) in a real Power Platform environment — typically reusing a service principal (SPN). Owns the "there has to be a way" question: it splits the…
원문 언어: 영어
Design a Power BI report/visualization in the Kurt-Buhler / Bas-Dohmen mold — a checklist-driven method: decide the question first, structure the page with the 3-30-300 information-seeking hierarchy, choose the visual by question-type, design headline KPIs…
원문 언어: 영어
Set the control-testing cadence, build evidence collection and continuous control monitoring, decide Type I vs Type II readiness, run a gap assessment and manage the auditor PBC list, and own third-party risk — vendor tiering, SIG/CAIQ, shared-responsibility,…
원문 언어: 영어
Choose the right security-compliance framework for the org's size/risk/customer demand, scope the audit boundary, crosswalk controls across SOC 2 TSC / ISO 27001 Annex A / NIST CSF 2.0 / 800-53 so one evidenced control attests many, and author a Statement of…
원문 언어: 영어
Build a risk register (assets, threats, likelihood x impact scoring), drive control selection from risk rather than from a framework checklist, choose a treatment per risk (mitigate / accept / transfer / avoid), and track residual risk with a named owner — so…
원문 언어: 영어
Run a disciplined exploratory pass before anyone models: profile the data (shape, types, missingness, cardinality, distributions), make and document cleaning decisions, visualize distributions and relationships, spot leakage candidates and target-definition…
원문 언어: 영어
Engineer features and fit, select, and honestly evaluate classical models on tabular data: build leakage-aware features, set a baseline, choose between regression / trees / gradient boosting, build a leakage-safe cross-validation harness with every transform…
원문 언어: 영어
Make an analysis re-runnable by anyone: enforce notebook hygiene (top-to-bottom-clean, no out-of-order state), pin environments and dependencies in a lockfile, set and thread random seeds, version data and artifacts, track experiments (params + metrics +…
원문 언어: 영어
Draft the sustainability disclosure with its evidence trail, build the data controls, assess readiness for the target assurance level (limited vs reasonable), run a gap assessment against what an assurer will test, strip greenwashing, and prepare the…
원문 언어: 영어
Select the applicable sustainability-reporting framework(s) and scope the disclosure: determine which standards apply (CSRD/ESRS, ISSB IFRS S1/S2, GRI, SEC), run the right materiality test (double vs financial), fix the reporting boundary and governance, and…
원문 언어: 영어
Build a GHG Protocol inventory: Scopes 1/2/3 and the 15 Scope-3 categories, activity data and emission-factor sourcing with vintage, location-based vs market-based Scope 2, base-year setting and recalculation, the consolidation boundary, and data-quality…
원문 언어: 영어
Design a group employee-benefits package as a system: plan types per line (medical/dental/vision/life/disability), plan-type mechanics (HMO/PPO/HDHP+HSA, deductible/coinsurance/OOP-max), and the funding decision (fully-insured vs self-funded vs level-funded)…
원문 언어: 영어
Run open enrollment and keep a group benefits program operationally compliant: a backward-planned enrollment cycle (timeline, eligibility, QLE/special enrollment, communications, carrier/EDI coordination) and the recurring compliance calendar (COBRA, HIPAA,…
원문 언어: 영어
Explain and pressure-test group rating and renewals: rating factors, manual vs experience rating weighted by credibility, the underwriting loss ratio vs the ACA medical-loss-ratio (MLR) test, and decomposing/sanity-checking a renewal projection (trend,…
원문 언어: 영어
Build a clause library with standard / fallback / walk-away positions, run a redline review that flags only the material deviations by risk tier, extract key terms into a structured schema, and route approval by the highest-tier deviation — operational…
원문 언어: 영어
Design structured legal intake and triage, the request-to-resolution workflow, contract playbooks (self-serve vs. escalate with bright-line escalation triggers), matter management, and the legal-ops metrics that prove the function is healthy — operational…
원문 언어: 영어
Extract and track contract obligations as owned items, watch renewals / expiries / auto-renew with tiered notice-window alerts, and model the contract repository metadata so contracts are findable and reportable — operational support, not legal advice.
원문 언어: 영어
Hold quality in control and stop defects recurring: stand up SPC reading special vs common cause correctly, structure a nonconformance through containment into a real CAPA, build inspection/control plans and FMEA, and set the supplier-quality bar — prevention…
원문 언어: 영어
Turn demand into a buildable plan: run MPS/MRP and net through the BOM, reconcile the forecast against finite capacity in S&OP, choose lot sizes on an honest setup-vs-holding trade, and build a finite schedule that respects the bottleneck — never…
원문 언어: 영어
Diagnose why the line is slow: compute OEE (availability × performance × quality) with stated denominators, compare takt to cycle time, identify the binding constraint via Theory of Constraints, and Pareto MES/downtime loss — fix the constraint, not a…
원문 언어: 영어
Design the load/stress/soak/spike test from a modeled workload: pick the open- vs closed-model executor deliberately, design ramping and think time, generate realistic owned test data, avoid coordinated omission, and assert thresholds in-script — tool-neutral…
원문 언어: 영어
Set the performance strategy before testing: turn vague goals into falsifiable NFRs (percentile + threshold + load), model the real workload, link targets to the customer SLO, and choose the test type (load/stress/soak/spike) that answers the open question.
원문 언어: 영어
Localize the bottleneck and size the system: CPU/memory/IO profiling and flame graphs, USE/RED triage to name the constraining resource, capacity planning with headroom via Little's law and the measured saturation point, and regression detection against a…
원문 언어: 영어
Build and maintain a CPM schedule: activity list, durations, logic ties (FS/SS/FF), critical-path calculation, float analysis, baseline establishment, weekly updates, look-ahead schedules, delay analysis (as-planned vs. as-built, TIA), and recovery…
원문 언어: 영어
Run a complete GC estimate and bid assembly: quantity takeoff from drawings, unit pricing (labor/material/equipment), markup vs. margin conversion, subcontractor scope review, general conditions budget, overhead and profit, contingency, and bid-letter…
원문 언어: 영어
Manage the GC's submittal register (identify required submittals, set lead-time-driven due dates, track review status), draft and track RFIs (structured question format, response tracking, overdue escalation), and document change orders (CO pricing…
원문 언어: 영어
Design and optimize a field-service dispatch board — priority queue logic by SLA tier, skill-match routing, geographic density optimization, emergency vs. planned time-block allocation, and day-of-dispatch escalation protocols.
원문 언어: 영어
Diagnose and improve technician utilization, first-time-fix rate, MTTR, and callback rate — including root-cause segmentation by parts/skill/information/diagnosis, the utilization waterfall, and the coaching framework to address each failure category.
원문 언어: 영어