메뉴
이 저장소의 skills
SkillsMP는 mcorbett51090/RavenClaude에서 924개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
mcorbett51090/RavenClaude수집된 skill 924개 중 40개를 표시합니다.
Write composable Terraform/OpenTofu modules: single responsibility, typed variables with validation, documented outputs, for_each over count to avoid reorder churn, pinned provider requirements, and a working example.
원문 언어: 영어
Gate infrastructure with policy-as-code: evaluate the Terraform plan JSON with OPA/Conftest (or Sentinel) to reject misconfigurations — public exposure, wildcard IAM, missing tags, unencrypted resources — before apply, preventively.
원문 언어: 영어
Design safe remote Terraform/OpenTofu state: remote backend with locking, encryption, and versioning; isolate state by blast radius; keep secrets out (and treat the whole file as sensitive); and do state surgery only with a snapshot.
원문 언어: 영어
Classify a Bermuda (non-insurance) entity into its BMA sector + licence class and resolve its AML/ATF position before any capital/Code/filing advice. Used by `bma-financial-institutions-specialist`. Traverses the BMA decision trees, then the sector files.
원문 언어: 영어
Build / refresh an enterprise risk register that survives audit committee scrutiny — three lines of defense assignment, inherent + residual rating math, KRI design, risk-appetite mapping, control coverage, and the half-yearly refresh cadence. Reach for this…
원문 언어: 영어
Veteran reference for building an accurate all-in freight quote — air chargeable weight (IATA 1:6000 volumetric vs actual), ocean CBM and weight/measure ton, the full ocean + air surcharge stack (BAF, CAF, THC, LSS, GRI, PSS, ISPS, AMS/ENS, DDC), margin…
원문 언어: 영어
Veteran reference for Incoterms 2020 in a sales context — all 11 terms, the cost vs risk transfer point of each, the who-pays-what responsibility matrix, the 7 any-mode vs 4 sea-only split, named-place discipline, and the recurring quoting traps (FCA vs FOB…
원문 언어: 영어
Veteran playbook for freight-sales pipeline and forecast discipline — stage definitions tied to buyer behavior, coverage ratio, sales velocity, weighted vs commit vs best-case forecast, the deal-inspection checklist, single-threaded-risk flags, and the long…
원문 언어: 영어
Veteran playbook for freight new-business prospecting — ICP definition for shippers, trigger-event sourcing, the 8-touch multi-channel sequence (email / call / LinkedIn), the value-first message framework (problem to lane-proof to ask), the low-risk wedge for…
원문 언어: 영어
Veteran playbook for freight key-account work — the QBR agenda and deck structure (partnership recap, value delivered, honest assessment, next-quarter goals, joint action plan), the account-plan template (relationship map, whitespace, growth plays, risks),…
원문 언어: 영어
Veteran playbook for freight RFQ/RFP/tender response — RFQ vs RFP vs RFI, the qualify-or-decline scorecard, the four operational drivers of quote win-rate (speed, accuracy, optionality, margin consistency), the lane rate-matrix format, the bid-narrative…
원문 언어: 영어
Decompose staffing margin into bill minus pay minus burden, itemize the burden stack, and locate whether a compression is pricing, pay, burden, or mix — before anyone calls it a pricing problem. Reach for this when gross margin or spread is moving and the…
원문 언어: 영어
Build a segment-by-segment competitive-positioning analysis for a staffing firm — placing it on a players-by-segment grid, naming where it wins and where scale competitors lead, with a source on every claim. Reach for this when the question is where the firm…
원문 언어: 영어
Design or audit the credentialing and clearance pipeline as a measured part of time-to-fill, with stage timings, document-completion gates, and the parallelizable steps that compress time-to-start. Reach for this when time-to-start lags time-to-offer or…
원문 언어: 영어
Diagnose a fill-rate move without blaming the wrong thing — by pinning the denominator, checking the seasonal boundary, splitting supply from order-quality, and pairing with time-to-fill including the credentialing clock. Reach for this when fill rate dropped…
원문 언어: 영어
Locate where the recruiting pipeline leaks by decomposing it stage by stage (order to workable to submittal to interview to offer to accept to start to billing), naming the leak stage and its likely cause. Reach for this when placements or submittal-to-fill…
원문 언어: 영어
Lay out a staffing KPI dashboard so the most decision-relevant number is read first, every tile pairs with its partner metric, and a red number explains itself via drill-down. Reach for this when turning a scorecard spec into a dashboard layout (not the build…
원문 언어: 영어
Right-size a recruiting desk by modeling fillable-order supply against the reqs a recruiter can carry at target conversion, distinguishing nominal from fillable orders and under-fed from under-staffed. Reach for this when the question is whether to hire more…
원문 언어: 영어
Produce a staffing readout that compares like-cycle-to-like-cycle instead of calendar-quarter-to-calendar-quarter, so the academic or healthcare seasonality doesn't masquerade as a performance change. Reach for this when a fill-rate or volume comparison…
원문 언어: 영어
Build a staffing operations scorecard where every KPI carries a definition, formula, window, baseline, owner, drill-down, and a triggered action — so an operator can act on it Monday morning. Reach for this when standing up a new scorecard or auditing one…
원문 언어: 영어
Produce a defensible staffing market-trend readout — segment-resolved, SIA-anchored, triangulated across primary sources, with the inflection (not just the level) named and soft numbers marked. Reach for this when a client wants the market read for healthcare…
원문 언어: 영어
Define and track a project that spans multiple GitHub repos. Use when a piece of work (a launch, a client, a feature) lives across several repositories and you want its status rolled up in one place instead of checked repo-by-repo. Covers the three match…
원문 언어: 영어
Stand up centralized multi-repo, multi-person activity tracking for a team. Use when a team works across several GitHub repos and needs one place to see who did what — and a supervisor needs a manage-the-team roll-up that a single-repo activity log can't…
원문 언어: 영어
Take vendor-specific raw support-ticket tables in the warehouse (Zendesk, Freshdesk, Intercom Conversations + Tickets, SFDC Case, JSM, HubSpot, Help Scout, Front) and produce conformed `fct_ticket` + `fct_conversation_event` models with SFDC Account / Planhat…
원문 언어: 영어
Use when stitching the same real-world entity — a customer account — across multiple source systems into one conformed spine; e.g. Salesforce + Planhat + Intercom + Slack. Operationalizes the deterministic-keys-before-fuzzy best practice: inventory candidate…
원문 언어: 영어
Codex's master roadmap for executing the Partner Success Command Center build. Invoke FIRST when asked to build any tier of the PSM dashboard. Identifies which tier to execute, names the read-list, codifies the anti-pattern catalog from…
원문 언어: 영어
Translate `.ravenclaude/comfort-posture.yaml` into `.claude/settings.json` permission rules. Owns the (category, level) → permission-rule emission table that the `/set-posture` slash command applies. Read this skill when authoring or reviewing the translation…
원문 언어: 영어
RBAC and ABAC in the application layer: defining roles and claims, mapping the authenticated identity to roles, enforcing roles in middleware and UI. The critical seam: row-level data scoping hands off to data-platform RLS via auth.uid(). Authentication…
원문 언어: 영어
Put the analytics dashboard and embedded BI behind login: app-shell login gate + session check + the handoff to data-platform's embed-JWT and RLS for per-user data isolation. The clearest expression of the auth-identity → data-platform seam.
원문 언어: 영어
Wire Sign in with Google end-to-end: Google Cloud OAuth client + consent screen + redirect URIs + scopes, then via Supabase Auth's Google provider (and a note on the Auth.js / direct path). Step-by-step with verification checkpoints.
원문 언어: 영어
Pick and implement the right OAuth 2.0 / OIDC flow by client type: Authorization Code + PKCE for SPA and native apps, confidential-client code flow for server-side apps, client-credentials for M2M. ID-token vs access-token vs refresh-token handling.…
원문 언어: 영어
Protect a React/Next.js SPA with route guards and middleware, and protect an API with token-verification middleware (signature + iss + aud + exp). Covers CORS configuration and CSRF defense. Applies to both the web-app and the API/backend targets.
원문 언어: 영어
Session vs JWT trade-offs; HttpOnly+Secure+SameSite cookie storage; refresh-token rotation; logout and revocation; storage anti-patterns (no tokens in localStorage or sessionStorage). The post-sign-in half of the auth lifecycle.
원문 언어: 영어
Lock the gain after an improvement: build the control plan, design SPC monitoring, write standard work, add poka-yoke (mistake-proofing), define the reaction plan, and hand off to the process owner. A fix without a control plan didn't happen.
원문 언어: 영어
Scope an improvement opportunity as a DMAIC project: problem statement, quantified goal, CTQ/VOC, SIPOC boundaries, baseline metric, team, and timeline. Produces a populated charter using the dmaic-project-charter template.
원문 언어: 영어
Find and remove waste using the 8 wastes (DOWNTIME), value-add analysis, takt/cycle time comparison, bottleneck/constraint identification, and quick-win prioritization. Feeds the DMAIC Improve phase with a ranked elimination roadmap.
원문 언어: 영어
Baseline a process: compute DPMO/sigma level and Cp/Cpk, select and read the right control chart (I-MR / Xbar-R / p / c / u), and apply Western Electric/Nelson rules to separate common-cause from special-cause variation. Routes deeper capability inference and…
원문 언어: 영어
Build the current-state process map: SIPOC, swimlane/flowchart, and value-stream map. Mark value-add vs. non-value-add steps and handoffs. Identify where to instrument and measure. Used in the DMAIC Measure phase before root-cause analysis begins.
원문 언어: 영어
Drive to proven root cause using 5 Whys, fishbone/Ishikawa (6M categories), and Pareto (80/20 prioritization), then validate the suspected cause with data. Routes hypothesis testing to applied-statistics. Anti-pattern: solution-jumping before cause is proven.
원문 언어: 영어
Design a transparent, explainable rule-based customer-success health tier (Green/Yellow/Red) from multi-source signals: signal selection, weighting, thresholds, per-signal evidence display, and tuning against actual past churn. Reach for this skill when…
원문 언어: 영어