health-insuranceCompare health insurance plans, estimate total yearly costs, and choose coverage that fits medical usage, prescriptions, and financial risk.
Install via ClawdBot CLI:
clawdbot install ivangdavila/health-insuranceGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawic.com/skills/health-insuranceAudited Apr 16, 2026 · audit v1.0
Generated Mar 21, 2026
A self-employed freelancer needs to choose a health insurance plan from the public marketplace during open enrollment. They have moderate prescription needs and want to balance monthly premiums with predictable out-of-pocket costs for routine care, while ensuring their current doctors are in-network.
A family of four is renewing their employer-sponsored health insurance plan. They must compare PPO and HMO options, factoring in their children's frequent pediatric visits and one family member's ongoing specialist treatments, to minimize total yearly expenses without compromising access.
An individual with chronic conditions requiring expensive medications needs to select a plan that covers their specific prescriptions on the formulary without high copays. They must assess drug tiers, step-therapy rules, and annual out-of-pocket maximums to avoid cost spikes.
A young, healthy professional considers an HDHP paired with a Health Savings Account (HSA) to lower premiums. They need to model worst-case scenarios for unexpected emergencies, evaluate network coverage for urgent care, and ensure the deductible aligns with their financial risk tolerance.
A retiree approaching Medicare eligibility must compare Medicare Advantage plans versus traditional Medicare with supplements. They focus on prescription coverage, provider networks for existing specialists, and additional benefits like dental or vision to optimize long-term healthcare costs.
Offer basic plan comparison tools for free to attract users, then charge for premium features like personalized cost modeling, enrollment assistance, or integration with broker services. Revenue comes from subscription fees or commission on referred insurance purchases.
License this skill to employers or HR platforms to help employees make informed insurance decisions during open enrollment. Revenue is generated through annual licensing fees per employee or enterprise contracts based on company size.
Provide personalized consulting services using this skill's framework to guide individuals or small businesses through health insurance selection. Revenue comes from hourly rates or fixed-fee packages for plan analysis, enrollment support, and ongoing renewal management.
💬 Integration Tip
Integrate with budgeting tools to align insurance costs with financial plans, and ensure user data is stored locally with explicit permissions to maintain privacy.
Scored Jun 17, 2026
Manages free AI models from OpenRouter for OpenClaw. Automatically ranks models by quality, configures fallbacks for rate-limit handling, and updates openclaw.json. Use when the user mentions free AI, OpenRouter, model switching, rate limits, or wants to reduce AI costs.
Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
Reduce OpenClaw AI costs by 97%. Haiku model routing, free Ollama heartbeats, prompt caching, and budget controls. Go from $1,500/month to $50/month in 5 min...
Generate and edit images with Gemini API using pure Python stdlib. Zero dependencies - works on locked-down environments where pip/uv aren't available.
Manage and use local Ollama models. Use for model management (list/pull/remove), chat/completions, embeddings, and tool-use with local LLMs. Covers OpenClaw sub-agent integration and model selection guidance.
Auto-route tasks to the cheapest Claude model that works correctly. Three-tier progression: Haiku → Sonnet → Opus. Classify before responding. HAIKU (default): factual Q&A, greetings, reminders, status checks, lookups, simple file ops, heartbeats, casual chat, 1-2 sentence tasks. ESCALATE TO SONNET: code >10 lines, analysis, comparisons, planning, reports, multi-step reasoning, tables, long writing >3 paragraphs, summarization, research synthesis, most user conversations. ESCALATE TO OPUS: architecture decisions, complex debugging, multi-file refactoring, strategic planning, nuanced judgment, deep research, critical production decisions. Rule: If a human needs >30 seconds of focused thinking, escalate. If Sonnet struggles with complexity, go to Opus. Save 50-90% on API costs by starting cheap and escalating only when needed.