Design, rationalize, and optimize truck-stock for field-service technicians — tier the parts list by usage frequency and service-level impact, set reorder points, model the first-time-fix ↔ carrying-cost tradeoff, and analyze parts-delay failures and returns.
Skills in this repository
mcorbett51090/RavenClaude - Page 12
SkillsMP has collected 924 skills from mcorbett51090/RavenClaude. Open a skill to review its source and details.
mcorbett51090/RavenClaudeShowing 40 of 924 collected skills.
Core internationalization foundations: string externalization strategy, ICU MessageFormat for plurals and gender selects, CLDR plural rules, locale-aware formatting via ECMA-402/Intl APIs, RTL/bidi layout design, Unicode encoding, and text expansion budget…
Design and operate the localization pipeline: string extraction configuration, TMS (Phrase, Lokalise, Crowdin, Transifex) integration and handoff, XLIFF/ARB/PO/JSON format conversion, translation memory management, continuous localization in a CD cycle, and…
Localization quality assurance methodology: pseudo-localization CI gate design (accent, expansion, bidi variants), l10n linting rules (missing keys, empty values, placeholder consistency, ICU syntax), visual and overflow QA techniques, locale-coverage test…
Design an accessible-by-default component pattern, semantic HTML first and ARIA only where needed. Reach for this on a design-system or component question.
Rank audit issues by user-impact and effort into a sequenced remediation plan with owners. Reach for this when there are more fixes than time.
Audit a page set against a named WCAG version and level, classify issues by severity/level, and compute a weighted conformance score. Reach for this on a conformance question.
Verify keyboard operability and screen-reader parity hands-on with the assistive technology real users use. Reach for this on a parity question.
Compute the WCAG contrast ratio from hex foreground/background values and check AA/AAA for normal and large text. Reach for this on any color question.
Audit segregation of duties and chart-of-accounts hygiene before trusting the books. Reach for this on a controls or data-quality question.
Estimate bad-debt from AR aging buckets weighted by loss rate. Reach for this on a receivables-risk question.
Read the cash conversion cycle (DSO + DIO − DPO) and locate trapped or surrendered cash. Reach for this on a cash question.
Reconcile bank and balance-sheet accounts to source before any statement ships. Reach for this first on any reporting question.
Run the period-end close on a cadence: critical-path checklist, days-to-close, bottleneck. Reach for this on a close question.
Compute cost per request and right-size the context to fewest-high-precision chunks. Reach for this on a cost/context question.
Build a judgment set and measure recall@k, precision@k, faithfulness, and answer-relevance with a baseline. Reach for this before shipping any change.
Separate retrieval failure from generation failure by measuring recall@k before touching the model. Reach for this first on wrong answers.
Add citations, refuse-on-empty-retrieval, and context-constraint to cut hallucination. Reach for this on a faithfulness question.
Tune chunk size, overlap, and structure-awareness against the eval and the context budget. Reach for this on a chunking question.
Compute the service absorption rate against total fixed overhead — the survival metric. Reach for this on a fixed-ops question.
Compute total gross per unit as front plus F&I back, with penetration. Reach for this on a deal-profitability question.
Diagnose the lead-to-sold funnel by conversion step — a volume gap is usually a conversion gap. Reach for this on a sales-volume question.
Frame F&I product penetration and PVR back-end gross inside the compliance boundary. Reach for this on an F&I question.
Read inventory days-supply against a target and quantify floorplan carrying cost. Reach for this on an inventory question.
Read note timeliness and medical-necessity completeness as one revenue-and-compliance control — operationally, never as a clinical judgment. Reach for this on a denial or audit-readiness question.
Quantify no-show/late-cancel as a flow — lost slots, lost revenue, and the recovery a reminder program delivers. Reach for this on a no-show question.
Read reimbursement net of variable cost by payer, compute blended margin, and model a mix shift — flagging parity for counsel. Reach for this on a payer or margin question.
Read intake-to-first-appointment access time as the conversion lever and find where the delay loses referrals. Reach for this on an access or conversion question.
Size clinician caseload capacity against measured demand and the no-show-adjusted fill rate, not a guessed ratio. Reach for this on a staffing or utilization question.
Gate deploy on a security audit and invariant tests across the top vuln classes — deploy is irreversible. Reach for this before any mainnet go-live.
Model an illustrative net staking APR and annual reward — clearly NOT financial advice. Reach for this on a yield or reward question.
Profile gas and cut the dominant costs — storage writes and loops — then estimate the user-facing cost. Reach for this on a cost or UX-cost question.
Decide deliberately what lives on-chain vs off-chain on cost and privacy grounds. Reach for this on any data-placement question.
Build the threat model beyond code — oracle, flash-loan, and MEV economic surface. Reach for this on a 'can we be drained?' question.
Design a statistically meaningful QA sampling program and a tier/escalation model. Reach for this on a quality or routing question.
Model self-service/KB deflection and the cost avoided before sizing headcount. Reach for this first on a cost-to-serve question.
Read SLA and backlog as arrivals against resolution capacity — project the days-to-clear. Reach for this on a backlog question.
Read CSAT/NPS segmented by channel/tier/issue-type and tie it to FCR — never a blended score. Reach for this on a satisfaction question.
Size agents from workload and a target occupancy band — not a fixed agent:ticket ratio. Reach for this on a staffing question.
Track flash and RAM (image, static, worst-case stack/heap) against the part's limits. Reach for this on any memory or footprint question.