insurance-briefing
This skill should be used when the user asks for an "insurance briefing", "sigorta brifing", "insurance digest", "sigorta haberleri", "insurance news summary", or wants to understand the editorial philosophy behind the insurance briefing system. Also triggers when the user mentions "insurance briefing plugin" or wants a curated daily overview of the Turkish insurance sector.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-12
- Stars
- ★ 82
- Forks
- 18
01 前言 Front Matter
- name
- insurance-briefing
- version
- 0.1.0
- description
- This skill should be used when the user asks for an "insurance briefing", "sigorta brifing", "insurance digest", "sigorta haberleri", "insurance news summary", or wants to understand the editorial philosophy behind the insurance briefing system. Also triggers when the user mentions "insurance briefing plugin" or wants a curated daily overview of the Turkish insurance sector.
02 资源文件 5
- 参考文档references/briefing-structure.md4.4 KB
- 参考文档references/editorial-philosophy.md5.4 KB
- 参考文档references/insurance-domain-context.md13.8 KB
- 参考文档references/scout-strategies.md10.8 KB
- 参考文档references/tracker-schema.md8.0 KB
03 SKILL.md 正文
Insurance Briefing System
A multi-agent pipeline designed for Turkish insurance professionals that produces a curated daily briefing blending regulatory intelligence with market insights and cross-domain analysis.
Editorial Philosophy
The briefing serves two audiences living in the same person:
-
The Practitioner — an underwriter, risk manager, or actuary who needs to know what changed in regulation, what market signals matter, and how non-insurance developments affect their underwriting and pricing decisions. Senior underwriter directness: no filler, sharp analysis, efficient reading.
-
The Strategist — a member of leadership or someone in market-facing roles who needs to understand why things happen, how global patterns echo in Turkey's market, and how seemingly unrelated developments create competitive opportunity or threat. Executive-level insight: backstories, hidden mechanisms, the "I never thought about it that way" moments.
Every briefing must serve both. Regulatory updates and market moves serve the practitioner. The deep dives and cross-domain radar serve the strategist. The best pieces serve both simultaneously.
Pipeline Architecture
The briefing is produced by a 3-stage multi-agent pipeline:
Stage 1: Domain Scouts (parallel)
Four specialized agents search their domains simultaneously:
- regulatory-scout — SEDDK decisions, law changes, compliance requirements, solvency standards, reinsurance rules
- market-scout — Premium trends, underwriting results, premium distribution by line, investment performance, M&A
- industry-scout — Competitive moves, company strategy shifts, distribution channel evolution, product innovation
- cross-domain-scout — Macroeconomic data, interest rates, inflation, geopolitical events, CAT risks with Turkish relevance
Each scout returns a structured list of 5-8 candidate stories ranked by importance and Turkish relevance.
Stage 2: Cross-Pollinator (editorial intelligence)
A single agent receives all scout outputs and performs editorial curation:
- Selects the best 6-10 stories across all domains
- Identifies 1-2 cross-domain connections
- Picks one story for deep-dive treatment
- Flags 1-2 radar pieces (non-obvious insurance mechanisms)
- Outputs a structured editorial plan
Stage 3: Briefing Composer
A single agent takes the editorial plan and writes the final markdown briefing with consistent voice and structure.
Briefing Sections
The insurance briefing is organized into five main sections:
- Gündem (Agenda) — 4-6 most consequential stories of the day
- Derinlemesine (Deep Dive) — 2-3 medium-depth features with analysis
- Radar — 1-2 pieces about non-obvious insurance mechanisms in non-insurance news
- Gelişmeler (Developments) — Continuity: updates on stories from previous briefings
- Küresel Reasürans (Global Reinsurance) — 2-3 brief items on international developments with Turkish relevance
See references/briefing-structure.md for the full section-by-section specification.
Scout Strategies
See references/scout-strategies.md for domain-specific search strategies, quality criteria, and Turkish-language search tips.
Editorial Standards
See references/editorial-philosophy.md for the full editorial guidelines, the two tests (Practitioner Test and Implications Test), voice guidelines per section, and quality benchmarks.
Story Continuity & Tracking
See references/tracker-schema.md for the story tracker schema and how the briefing maintains cross-session memory of developing insurance stories.
Domain Context
See references/insurance-domain-context.md for institutional knowledge about the Turkish insurance market: regulatory bodies, top insurers, market structure, and key terminology.
04 同仓库更多 Skills
로인장 (Roinjiang)
Activates when the user needs legal advice, contract review, insurance law consultation, startup legal support, or any legal/regulatory matter. She is a top-tier in-house lawyer with absolute loyalty to the CEO, specializing in insurance law, financial consumer protection, privacy, contracts, labor law, family law, civil and criminal matters.
zocdoc-doctor-finder
Use when a user needs to find a doctor, dentist, specialist, therapist, or healthcare provider — especially when they mention insurance, in-network, availability, location, appointments, or booking. Also use for browsing provider reviews, comparing doctors by specialty, or checking if a provider takes their insurance.
zenmux-context
Answers any question about ZenMux by reading the latest official documentation. Use this skill whenever the user asks about ZenMux product features, API usage, configuration, integration, pricing, models, providers, routing, fallback, streaming, multimodal, structured output, tool calling, reasoning, prompt caching, image generation, video generation, web search, long context, observability, logs, cost tracking, usage analytics, insurance, subscription, pay-as-you-go, invoices, best practices for tools like Claude Code, Cursor, Cline, CodeX, Gemini CLI, opencode, Cherry Studio, Obsidian, Sider, Open-WebUI, Dify, Neovate, GitHub Copilot, OpenClaw, CC-Switch, Immersive Translate, Studio Chat, architecture, benchmarks, FAQ, contact, privacy, terms of service, compliance, or any other ZenMux-related topic. Also trigger when the user writes in Chinese about ZenMux: 文档, 使用指南, 快速开始, API 参考, 最佳实践, 模型路由, 供应商路由, 订阅, 按量计费, 可观测性, 帮助, 常见问题, 接入指南, 配置. Trigger on phrases like "how to use ZenMux", "ZenMux docs", "ZenMux API", "ZenMux integration", "ZenMux 怎么用", "ZenMux 接入", "ZenMux 配置". Even if the user doesn't say "ZenMux" explicitly but asks about LLM API aggregation, model routing, provider fallback in a context where ZenMux is the project being worked on, this skill should activate.
workers-comp-guide
Guide workers compensation compliance and claims management. TRIGGERS - Use when user needs help with workers-comp-guide related tasks.
weekly-kpi-report
Generate McKinsey-style board presentation PPTs from weekly auto insurance data. Automatically calculates 16+ KPIs, creates executive-level slides with actionable insights, and supports week-over-week comparisons. Use when user uploads insurance cost data (Excel/CSV) and requests board report, weekly presentation, executive briefing, or mentions keywords like 董事会汇报, 周报PPT, 经营分析演示, McKinsey-style reports.
wealth-advisory
Wealth management and financial planning for HNW and UHNW clients. Activate when the user mentions wealth management, financial planning, retirement, estate planning, tax planning, GRAT, IDGT, trust, asset allocation, withdrawal rate, Monte Carlo simulation, goals-based investing, tax-loss harvesting, Roth conversion, insurance, annuity, mortgage strategy, concentrated stock, family office, direct indexing, 529 plan, charitable giving, donor-advised fund, private foundation, or asks about personal finance strategy, inheritance, long-term financial planning, or UHNW advisory.