All authors
Claude Skills by mcorbett51090
github.com/mcorbett51090964 skills6 installs216 views
- Benefits Plan DesignDesign 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) sized to the group, with the ACA/ERISA obligations named — educational scaffolding, not advice.Votes: 0GitHub stars: 7
- Enrollment And ComplianceRun 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, ACA 1095-C/1094-C, ERISA Form 5500 + SPD/SBC) — educational scaffolding, not legal advice.Votes: 0GitHub stars: 7
- Underwriting And RatingExplain 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, experience, pooling, demographics, plan change) — educational scaffolding, not actuarial advice.Votes: 0GitHub stars: 7
- Decompose The Combined RatioSplit the combined ratio into loss and expense, then attritional and catastrophe, so a deteriorating result is diagnosed correctly. Reach for this on any result question.Votes: 0GitHub stars: 7
- Price To Rate AdequacyPrice risk to expected loss plus expense plus profit load against loss trend, not to the competitor, so growth doesn't grow a loss. Reach for this on any pricing question.Votes: 0GitHub stars: 7
- Read The Portfolio ResultRead the underwriting result by line of business, attritional-vs-cat and net-of-reinsurance, so the mix story is visible. Reach for this on a portfolio review.Votes: 0GitHub stars: 7
- Review Claims LeakageRead indemnity leakage, LAE, and cycle time as managed metrics, not minimized payout, to find the controllable gap. Reach for this on a claims-cost question.Votes: 0GitHub stars: 7
- Separate Frequency And SeverityDecompose a loss-ratio move into frequency and severity, since they have opposite responses, before prescribing. Reach for this when the loss ratio moves.Votes: 0GitHub stars: 7
- Build Risk Based Audit PlanBuild a risk-based internal-audit universe and annual plan by traversing the internal-audit decision tree (assurance-vs-advisory → risk-ranking the universe → coverage/cycle → resourcing), then return the scored audit universe, the resource-balanced annual plan (assurance/advisory mix, cycle coverage), the IIA-Standards/Three-Lines positioning, and the audit-committee residual-risk narrative. Reach for this when the user asks 'how do we rank our audit universe?', 'what should be on this year'...Votes: 0GitHub stars: 7
- Plan And Execute Audit EngagementPlan and execute a single internal-audit engagement by traversing the internal-audit decision tree (assurance-vs-advisory → scope & criteria → sampling approach → evidence), then return the planning memo, the risk & control matrix (risk → control → type → tests), the walkthrough, the test of design + test of operating effectiveness with an attribute-sampling plan and sample size, and review-ready workpapers. Reach for this when the user asks 'draft the planning memo and RCM', 'how do we test ...Votes: 0GitHub stars: 7
- Rate And Report Audit FindingsTurn tested control gaps into well-formed internal-audit findings and report them by traversing the issue-rating branch of the internal-audit decision tree, then return each finding on the 5 C's (Criteria/Condition/Cause/Consequence/Corrective action), an impact×likelihood rating (high/medium/low), the agreed management action plan (owner + date), the audit-committee summary, and the follow-up / remediation-validation plan. Reach for this when the user asks 'write this control gap as a findin...Votes: 0GitHub stars: 7
- Build The CmdbStand up a maintainable CMDB — configuration items scoped to what earns its place, automated discovery, the relationships needed for impact analysis, and a drift-audit discipline. Reach for this when you need a configuration/asset source of truth.Votes: 0GitHub stars: 7
- Design Slas And CatalogDefine an SLA backed by the OLAs and underpinning contracts that make it deliverable, and a service catalog of standard requests. Reach for this when designing service targets or a request catalog.Votes: 0GitHub stars: 7
- Run Change EnablementClassify a change (standard/normal/emergency), assess its risk, and route it — pre-authorizing repeatable changes and reserving the CAB for genuine risk. Reach for this on any 'does this need approval / a CAB?' question.Votes: 0GitHub stars: 7
- Select Itil PracticesPick the lightest set of ITIL 4 practices that delivers value, grounded in the service value system and guiding principles — adopt what earns its keep, skip the ceremony. Reach for this when standing up or right-sizing ITSM.Votes: 0GitHub stars: 7
- Triage Incident Vs ProblemClassify an issue as an incident (restore service now), a problem (remove the recurring cause), or a major incident (declare command), and open the right record. Reach for this when something is broken or keeps breaking.Votes: 0GitHub stars: 7
- Allocate Per PupilAllocate per-pupil dollars to need and impact, not last year's distribution. Reach for this on a budget-allocation question.Votes: 0GitHub stars: 7
- Fit Staffing To BudgetModel a student:teacher ratio into FTE and salary cost and check it against the budget envelope. Reach for this on a staffing question.Votes: 0GitHub stars: 7
- Flag Chronic AbsenteeismCompute the chronic-absentee rate, flag it early, and size the attendance-recovery funding upside. Reach for this on an attendance question.Votes: 0GitHub stars: 7
- Model Enrollment FundingTranslate enrollment and ADA into funding and quantify the dollar value of each attendance point. Reach for this on a funding question.Votes: 0GitHub stars: 7
- Read Outcomes SegmentedRead proficiency and growth disaggregated by subgroup and link to attendance — never the school average. Reach for this on an outcomes question.Votes: 0GitHub stars: 7
- Assess Legacy EstateAssess a legacy system and choose a modernization strategy with the 6 R's (retain/rehost/replatform/refactor/rearchitect/replace). Reach for this when the question is 'rewrite or refactor?' or 'is this worth modernizing?'.Votes: 0GitHub stars: 7
- Characterization TestingPin a legacy system's current behavior with characterization / golden-master / approval tests before changing it, so a refactor that changes behavior fails loudly. Reach for this before any edit to untested legacy code.Votes: 0GitHub stars: 7
- Data Migration And CutoverMigrate data off a legacy store with dual-write / parallel-run / reconciliation, then cut over with go/no-go gates and a tested rollback. Reach for this for any zero-downtime move or final switch-over.Votes: 0GitHub stars: 7
- Dependency And Framework UpgradeUpgrade a stuck dependency, framework, or language version incrementally — one major at a time, on green tests, deprecations resolved between each — instead of a single risky leap. Reach for this when a system is several versions behind.Votes: 0GitHub stars: 7
- Strangler Fig MigrationPlan an incremental strangler-fig migration off a legacy system — a facade routing one capability at a time to a new implementation behind an anti-corruption layer. Reach for this instead of a big-bang rewrite.Votes: 0GitHub stars: 7
- Contract Review And RedlineBuild 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 support, not legal advice.Votes: 0GitHub stars: 7
- Legal Intake And PlaybooksDesign 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 support, not legal advice.Votes: 0GitHub stars: 7
- Obligations And RenewalsExtract 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.Votes: 0GitHub stars: 7
- Build Practice ScorecardBuild a realization-led practice scorecard with utilization, collected revenue, and A/R, each defined and baselined. Reach for this to instrument the practice.Votes: 0GitHub stars: 7
- Read RealizationRead realization and the billed-vs-collected gap, locating write-downs, write-offs, and A/R, so the practice's real economics are visible. Reach for this on any 'busy but broke' question.Votes: 0GitHub stars: 7
- Run Conflict Checked IntakeRun intake as risk management — conflict check and fit/viability screen before the engagement — to prevent the matters that destroy realization. Reach for this at every new matter.Votes: 0GitHub stars: 7
- Scope The MatterScope a matter and choose the fee structure deliberately, since an open-ended hourly with no budget breeds write-offs. Reach for this before engaging.Votes: 0GitHub stars: 7
- Support DraftingDraft and review documents from clause libraries with issue flags, as attorney-reviewed work product, never legal advice. Reach for this on a drafting or review task.Votes: 0GitHub stars: 7
- Build Llm JudgeDesign, calibrate, and bias-audit an LLM-as-judge so its scores track human judgment: named criteria with anchored levels (not 'rate 1-10'), a structured verdict + reason, a pinned judge model/version, a human-agreement calibration on a sample, and checks for position / verbosity / self-preference / leniency bias. Reach for it whenever a judge grades outputs. Used by `eval-harness-engineer` (primary).Votes: 0GitHub stars: 7
- Design Eval SuiteTurn a fuzzy 'is the AI good enough?' into a concrete measurement plan: task spec, the eval method from the decision tree (exact / rule-based / model-graded / human), the metric + what it misses, the offline-vs-online split, a power-adequate sample size, and a numeric ship-gate decided before the run. Reach for it at the START of any LLM-feature eval. Used by `eval-strategy-lead` (primary).Votes: 0GitHub stars: 7
- Gate Releases With EvalsWire an offline eval suite into a CI ship-gate so a prompt/model change is scored against a frozen baseline and blocked on a regression past a preset threshold, with guardrail/red-team checks as a zero-tolerance blocker and cost/latency tracked alongside quality. Reach for it to make evals a merge gate instead of a report. Used by both agents.Votes: 0GitHub stars: 7
- I18n Foundations And IcuCore 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 planning.Votes: 0GitHub stars: 7
- L10n Pipeline And TmsDesign 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 branching strategies for in-flight translations.Votes: 0GitHub stars: 7
- Localization Qa And Pseudo LocLocalization 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 matrix, and false-positive triage for l10n lint.Votes: 0GitHub stars: 7
- Capa And SpcHold 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 over detection over scrap.Votes: 0GitHub stars: 7
- Mrp And Production PlanningTurn 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 infinite-capacity planning.Votes: 0GitHub stars: 7
- Oee And ThroughputDiagnose 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 non-bottleneck.Votes: 0GitHub stars: 7
- Audit Attribution DataAudit data hygiene, dedup, and UTM/tracking integrity before trusting any funnel or ROI number. Reach for this first on any new dataset.Votes: 0GitHub stars: 7
- Content EngineRun 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.Votes: 0GitHub stars: 7
- Diagnose FunnelDiagnose MQL→SQL→opp→win conversion stage-by-stage — find the leaking stage before adding lead volume. Reach for this on a funnel question.Votes: 0GitHub stars: 7
- Evaluate Channel MixEvaluate channels on contribution and marginal ROI under a stated attribution model — not average ROI or lead count. Reach for this on a channel or budget question.Votes: 0GitHub stars: 7
- Read Cac LtvRead LTV:CAC and CAC-payback to gate acquisition spend on unit economics, not lead count. Reach for this on a CAC or sustainability question.Votes: 0GitHub stars: 7
- Size DemandBack-solve the lead volume a win target requires through each stage conversion. Reach for this on a 'how many leads' question.Votes: 0GitHub stars: 7
- Choose Cdp And Collection ArchitecturePick the right CDP and event-collection architecture for a described workload by traversing the CDP/collection decision tree (source of truth & activation → packaged CDP vs warehouse-first/reverse-ETL vs Snowplow self-hosted; accuracy vs UI-richness → client-side vs server-side vs hybrid), then return the recommendation, the trade-offs, and the conditions that would flip it. Reach for this when the user asks "Segment vs RudderStack vs Snowplow?", "packaged CDP or warehouse-first?", or "client...Votes: 0GitHub stars: 7