
Claude Skills by infometa
github.com/infometa出游需求澄清 · 只问 3 件事(目的地/日期/人数),其余靠 agent 思考-调工具-给选项-必要追问。绝不一次问 10 个问题,绝不静默用默认值。老用户从 user_profile 默认沿用。
⭐ 行程运筹核心壁垒 · 把 Top N POI 池转成"地理顺路 + 体力分配 + 时间窗匹配"的可执行行程。三步走:K-Means 地理聚类分天 → TSP 贪心+2-opt 排顺路 → 体力/营业/用时窗适配。这是通用 AI 完全做不好的事。
POI 多维加权打分 · 基于美团/online-search的 POI 详情 + 小红书评论 + 用户偏好画像,按 scoring_rules.json 多维度打分,输出每天可塞入的 Top N POI 清单。是 itinerary-optimize 的输入。
用户偏好画像加载与增量学习 · 加载 user_profile.json / 首次走 BOOTSTRAP 极简 3 题问卷 / 每次对话后从对话内容自动抽取增量 / 顺便做数据源体检。这是 agent 跨次复用的护城河。
⭐ HTML 行程书生成 · 把上游所有 JSON(itinerary/transport/hotel/budget/risk)渲染成单文件 HTML,含 Leaflet 地图(每天分色路线)+ 时间轴 + POI 卡片 + 预算饼图 + 风险面板 + 行前清单。写到 output/,preview_url 打开。
出行风险体检 · 天气预警 / 限行 / 节假日人流 / 当地骗局 / 应急联系。结合 risk_knowledge.json 静态知识 + online-search 实时天气 + xhs-explore skill"避雷"搜索。按置信度绿/黄/灰输出。
搜索编排底座 · 把"江西附近游玩"这类模糊地理意图转成结构化查询矩阵,调度online-search / 美团连接器 / xhs-explore skill 做 fan-out → fan-in 多源混合检索,输出带置信度的候选地点 + 内容证据池。是 03/04/06/09 的共用底座。
交通方案规划 · 大交通(高铁/飞机推荐+备选)+ 市内交通(地铁/打车/公交)。美团连接器 + online-search(火车票查询) 双源校验高铁,机票走 WebSearch 兜底。永远标注"参考价 + 查询时间"。
Practice-profile interview that recommends and installs a starter pack of community legal skills. This IS the cold start for the whole ecosystem — it asks what kind of lawyer you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.
Guided customization of your Legal Builder Hub profile — change one thing without re-running the whole cold-start interview. Adjust practice profile, installed starter pack, watched registries, update preferences, or QA strictness. Use when the user says "change my [thing]", "add a registry", "update my profile", "edit my config", or "customize".
Suggest community skills based on recent activity in other plugins. Checks whether the community has built something relevant to a task and mentions it once, non-intrusively. Use when the user says "is there a community skill for this", "what else is out there", or asks for skill recommendations; also runs passively as part of other plugins' workflows.
Evaluate a skill against the Legal Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three legal failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as p...
Consolidated workflow layer copied and merged from legal-builder-hub. Use this skill as the exposed entry point while preserving detailed source workflows under references/source-workflows.
Help a clinic supervisor author a practice-area guide that configures how student-facing skills behave — intake questions, pedagogy posture (assist / guide / teach), review gates, cross-plugin checks, and local rules. Use when a supervising attorney wants to build or revise a per-practice-area guide, tune how the clinic skills behave for their clinic type, or set their teaching philosophy as plugin configuration.
Log a client communication — call, email, text, letter, in-person, voicemail. Append-only per-case record with dated entries, direction, medium, summary, action items. Works alongside /client-letter and /status client. Use when logging a call or client email, reviewing a communication log, or asking "what did we tell [client] last time".
Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new client's situation.
Routine client correspondence from templates — appointment confirmations, document requests, brief "we filed it" updates. Plain language, required elements, supervision routing. NOT substantive advice. Use when a student needs to send routine correspondence, an appointment confirmation, a document request letter, or a brief status note to a client.
Professor's one-time clinic setup — practice areas, jurisdiction, supervision style (formal review queue / configurable flags / lighter-touch), and handbook/rules upload. Writes practice-profile.md so every other skill and every student who runs /ramp reads from the same clinic context. Use on fresh install, when practice-profile.md has placeholders, when re-doing setup with --redo, or when re-checking integrations with --check-integrations.
Guided customization of your legal clinic profile — change one thing without re-running the whole cold-start interview. Adjust clinic profile, jurisdiction, supervision style, practice-area templates, semester configuration, or output safeguards. Use when the user says "change my [thing]", "new semester", "add a practice area", "update my config", or "customize".
Track case deadlines — add, cross-case rollup report, update, complete, close. Warns at configurable thresholds (default 14/7/3/1 days); overdue items stay flagged until resolved. The operational record for a clinic workload. Use when a student or supervisor needs to add a deadline, ask what's due this week, get a deadline report, or update a case deadline.
First draft of a common clinic document — practice-area templates (asylum applications, eviction answers, protective order petitions, demand letters), jurisdiction-aware formatting, explicitly a starting point requiring student analysis and attorney review. Use when a student needs a first draft of a motion, letter, petition, declaration, or other clinic document.
IRAC-scaffolded case analysis memo with research gaps flagged — the scaffold, not the analysis. Rule blocks are RESEARCH NEEDED, Application is STUDENT ANALYSIS prompts, Conclusion is blank. Use when a student needs to scaffold a case analysis memo, write up their analysis, or build an IRAC memo for a case.
Reference: DEPRECATED — use `/client-letter` for routine correspondence or `/status client` for substantive updates. Split into two more focused skills during the v2 rebuild. Kept as a redirect for migration.
Student semester onboarding — clinic procedures, tool walkthrough, practice exercises before real cases. Reads the handbook the professor uploaded at setup and teaches it interactively. Use when a new clinic student says "onboard me", "I'm new to the clinic", "getting started", or at the start of each semester; pass --card for the one-page reference.
Research roadmap for a legal issue — statutes to check, case law areas to investigate, regulatory frameworks, research platform search terms. Leads and frameworks, NOT authoritative citations; students verify and develop everything. Use when a student asks where to start researching, wants a research roadmap for an issue, or needs gaps identified in existing research.
End-of-semester case handoff memos — the mirror of /ramp. Produces per-case transition memos and a cohort summary so the departing cohort hands work to the incoming cohort cleanly. Reads deadlines, client-comms, and case history. Use when the professor or departing students need to wrap up the semester, build transition memos, or offboard a graduating/withdrawing student.
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Professor's review queue — student output waits here for professor approval before going to clients or courts. Only active if "formal review queue" supervision style was chosen at setup; otherwise dormant. Use when the professor wants to see what's waiting for review, approve, edit-then-approve, or return an item.
Consolidated workflow layer copied and merged from legal-clinic. Use this skill as the exposed entry point while preserving detailed source workflows under references/source-workflows.
统一的 IMA OpenAPI 技能,支持笔记管理和知识库操作。 当用户提到知识库、资料库、笔记、备忘录、记事,或者想要上传文件、添加网页到知识库、 搜索知识库内容、搜索/浏览/创建/编辑笔记时,使用此 skill。 即使用户没有明确说"知识库"或"笔记",只要意图涉及文件上传到知识库、网页收藏、 知识搜索、个人文档存取(如"帮我记一下"、"搜一下知识库里有没有XX"),也应触发此 skill。
API base path: `openapi/wiki/v1` — 完整数据结构和接口参数详见 `references/api.md`。
> ⛔ Before ANY write (`import_doc`/`append_doc`): validate ALL string fields (`content`, `title`) are legal UTF-8. > Non-UTF-8 content causes irreversible garbled text in IMA. See root SKILL.md § MANDATORY RULES for platform-specific validation methods. API base path: `openapi/note/v1` 通过 IMA OpenAPI 管理用户个人笔记,支持读取(搜索、列表、获取内容)和写入(新建、追加)。 完整的数据结构和接口参数详见 `references/api.md`。 > **隐私规则:** 笔记内容属于用户隐私,在群聊场景中只展示标题和摘要,禁止展示笔记正文。
Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose ...
腾讯文档(docs.qq.com)-在线云文档平台,是创建、编辑、管理文档的首选 skill。涉及"新建/创建/编辑/读取/查看/搜索文档"、"保存文件"、"云文档"、"腾讯文档"、"docs.qq.com"等操作,请优先使用本 skill。支持能力:(1) 创建各类在线文档(文档/Word/Excel/幻灯片/思维导图/流程图/智能表格/收集表)(2) 管理知识库空间(创建空间、查询空间列表)(3)
当用户需要查找与当前法律问题相关的类似案例、相关判决、裁判规则时触发。典型场景:查找类似案例或判例、通过裁判支撑法律论点、案件预判、分析司法实践趋势、对比不同法院/时期的裁判立场。关键词包括:类似案例、相关判决、判例检索、裁判规则、同类案件、指导性案例、典型案例、司法观点、裁判要旨等。
Format legal-retrieval results into the output shape required by the routed scenario. Use after retrieval to draft the final answer text and citation style. If the task sheet says 核验工作台=必用 or 输出档位=重量, this skill is NOT the final step: it must hand off to legal-verification-workbench for scripted HTML generation and must not create HTML itself.
Identify the user's true legal-search intent and route it to the correct retrieval scenario. Use this skill FIRST for every legal-search request to determine scenario type, depth, required material types, and the binding output standard before any actual search happens.
Execute the multi-layer legal retrieval pipeline once a scenario is identified - extract legal facts, locate the legal issue, judge source effectiveness hierarchy, generate dynamic search strategy with statutory hierarchy scanning and comprehensive retrieval methodology, then filter and rank results with effectiveness verification and applicability validation in a feedback loop. Use this skill to perform actual statute retrieval through available legal databases, MCP/skills, official sources,...
法律检索核验工作台。任务单出现【核验工作台:必用】、【输出档位:重量】或输出形态属于全面合规检索、文书引用素材、诉讼仲裁支撑、非诉文书检索、企业合规体检、案例专题分析、刑事量刑参考、行政复议证据时必须使用。本 skill 执行脚本化动作:保存 answer/sources/claims,运行 legal-verify all/html/repair-* 生成模板 HTML;禁止手写 HTML。
Darwin Skill (达尔文.skill): autonomous skill optimizer inspired by Karpathy's autoresearch. Evaluates SKILL.md files using an 8-dimension rubric (structure + effectiveness), runs hill-climbing with git version control, validates improvements through test prompts, and generates visual result cards. Use when user mentions \"优化skill\", \"skill评分\", \"自动优化\", \"auto optimize\", \"skill质量检查\", \"达尔文\", \"darwin\", \"帮我改改skill\", \"skill怎么样\", \"提升skill质量\", \"skill review\", \"skill打分\".
Multi search engine integration with 16 engines (7 CN + 9 Global). Supports advanced search operators, time filters, site search, privacy engines, and WolframAlpha knowledge queries. No API
Draft a brief section in house style, consistent with the case theory — every fact cited, every case checked, every argument tied to the theory. Use when the user says "draft the [section]", "write the statement of facts", "argument section on [issue]", or needs a first draft of a brief section.
Build or update a chronology from declared document sources and uploads — dated events extracted, de-duped, and tagged by significance per the matter theory. Use when the user asks to build a chronology or timeline from a production or matter file, says "chron from the production" or "what happened when", or needs a working, statement-of-facts, or witness-specific timeline.
Build or review an element chart — a patent claim chart (infringement, invalidity, or review) or a civil element chart for any cause of action or defense — with every cell pin-cited and gap detection as the priority output. Use when the user asks for a claim chart, element chart, proof chart, infringement or invalidity contention, element-by-element mapping, or asks "what are we missing to prove [claim]".
House cold-start for the litigation plugin — branches by role (in-house, firm associate, solo) and side (plaintiff, defense, both), captures risk calibration, landscape, and house style, and writes the practice profile practice-profile.md. Use on a fresh install, when the user wants to set up or redo the practice profile, or to re-check available integrations.
Guided customization of your litigation practice profile — change one thing without re-running the whole cold-start interview. Adjust practice role, side (plaintiff / defense / mixed), risk calibration, landscape, house style, escalation contacts, severity vocabulary, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", or "customize".
Draft a demand letter from a completed intake, gated on a privilege / settlement-communication rule / waiver / admission checklist, with a .docx output, post-send checklist, and an offer to create a matter. Use when the user says "draft the demand", "write the [type] letter", or has a finished demand intake ready to turn into a sendable draft.
Pre-drafting context gathering for a demand letter — parties, facts, basis, leverage, BATNA, and privilege filters — written to a structured intake.md the demand-draft skill reads. Use when the user wants to prep a demand letter, run intake before drafting, or capture context for a payment demand, breach/cure notice, cease-and-desist, employment separation, or preservation demand.
Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted. Use when the user says "we got a demand letter", "triage this demand", or shares an incoming demand to evaluate.
Deep briefing on one matter — current posture, what's changed, next deadline, open questions, and a risk re-assessment check, ready before a GC update or outside counsel call. Use when the user says "brief me on [matter]", "where are we on [matter]", or needs a read on a specific matter.