[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XF2F64WJ177YCD4JXYCVSF":3,"skill-same:01M6XF2F64WJ177YCD4JXYCVSF":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6XF2F64WJ177YCD4JXYCVSF","acroform-fill",null,"Inspect, schema, and fill true AcroForm PDFs using sciClaw's pdf_form_inspect, pdf_form_schema, and pdf_form_fill tools. Use when: (1) checking whether a PDF is a real fillable AcroForm, (2) listing form field names, types, and choices, (3) filling a supported form from structured values, (4) preparing reviewable insurance, legal, administrative, or clinical form drafts, (5) reporting skipped fields or unused input keys after a fill. Do not use for scanned PDFs, OCR tasks, or XFA-only forms.","FDU-INS\u002FInsurance-Skills","FDU-INS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167067594?v=4","01M6XEYMRS4CVJMZ834YWE66BV","FDU-Insurance","01M6XEYMXPDA34HFM0ZE6AY78G",82,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Facroform-fill\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"acroform fill","fill","types","insurance","listing","when","unused","for","inspect","true","PDF","form","clinical","do","only","schema","use","brew","ocr","tasks","2026-11-10 10:12:30",false,"---\nname: acroform-fill\ndescription: \"Inspect, schema, and fill true AcroForm PDFs using sciClaw's pdf_form_inspect, pdf_form_schema, and pdf_form_fill tools. Use when: (1) checking whether a PDF is a real fillable AcroForm, (2) listing form field names, types, and choices, (3) filling a supported form from structured values, (4) preparing reviewable insurance, legal, administrative, or clinical form drafts, (5) reporting skipped fields or unused input keys after a fill. Do not use for scanned PDFs, OCR tasks, or XFA-only forms.\"\nmetadata: {\"nanobot\":{\"requires\":{\"bins\":[\"pdf-form-filler\"]},\"install\":[{\"id\":\"brew\",\"kind\":\"brew\",\"formula\":\"pdf-form-filler\",\"bins\":[\"pdf-form-filler\"],\"label\":\"Install pdf-form-filler (brew)\"}]}}\n---\n\n# acroform-fill\n\nUse this skill for fillable PDF form workflows backed by sciClaw's dedicated PDF form tools.\n\n## Core workflow\n\n1. Run `pdf_form_inspect` first.\n2. If `isSupportedAcroForm` is `false`, stop and explain that sciClaw will not force-fill non-AcroForm, XFA-only, or scanned PDFs.\n3. Run `pdf_form_schema` to get the field inventory before preparing values.\n4. If values are not already in a JSON file, create one in the workspace with `write_file`.\n5. Run `pdf_form_fill` to a **new** output path.\n6. Keep `flatten=false` by default. Only flatten when the user explicitly wants final non-editable output.\n7. Report `skippedFields` and `unusedInputKeys` clearly. If either is non-empty, treat the output as review-needed.\n8. If you need to send the resulting PDF back to the user, use `message` with the output file as an attachment.\n\n## Rules\n\n- Never overwrite the source PDF.\n- Never skip `pdf_form_inspect`.\n- Do not use `read_file` on raw PDFs.\n- Prefer exact field names from `pdf_form_schema`; do not invent field names.\n- For choice fields, use the schema's `choices` exactly.\n- If the user only wants to know whether a PDF is fillable, stop after `pdf_form_inspect`.\n- If the user gives narrative text instead of structured values, convert that text into a JSON values file before calling `pdf_form_fill`.\n- For sensitive or regulated workflows, prefer reviewable output before flattening.\n\n## Minimal examples\n\n### 1. Check whether a PDF is a real AcroForm\n\nUse when the user asks: \"Is this PDF fillable?\"\n\n```json\n{\"pdf_path\":\"forms\u002Fprior-auth.pdf\"}\n```\n\nTool:\n\n- `pdf_form_inspect`\n\nGood outcome:\n\n- `isSupportedAcroForm = true` -> continue if needed\n- `isSupportedAcroForm = false` -> stop and explain why\n\n### 2. Get the field schema before filling\n\nUse when the user asks: \"What fields are on this form?\"\n\n```json\n{\"pdf_path\":\"forms\u002Fprior-auth.pdf\"}\n```\n\nTool:\n\n- `pdf_form_schema`\n\nThen summarize the important field names, types, and any `choices` the model must respect.\n\n### 3. Fill from an existing values JSON file\n\nFirst make sure the values file exists in the workspace, for example:\n\n```json\n{\n  \"PatientName\": \"Jane Doe\",\n  \"DOB\": \"1978-02-14\",\n  \"Urgent\": true\n}\n```\n\nThen call:\n\n```json\n{\n  \"pdf_path\":\"forms\u002Fprior-auth.pdf\",\n  \"values_path\":\"memory\u002Fprior-auth.values.json\",\n  \"output_path\":\"memory\u002Fprior-auth.filled.pdf\",\n  \"flatten\":false\n}\n```\n\nTool:\n\n- `pdf_form_fill`\n\n### 4. Fill from narrative text\n\nUse when the user gives a note, letter, or summary instead of a ready JSON file.\n\nWorkflow:\n\n1. `pdf_form_inspect`\n2. `pdf_form_schema`\n3. `write_file` a JSON values file in the workspace\n4. `pdf_form_fill`\n5. Report any skipped or unused fields\n\n## When not to use this skill\n\n- OCR or scanned-document extraction\n- Free-form PDF text extraction\n- XFA-only forms that are not true AcroForms\n- Cases where the user wants arbitrary PDF editing instead of form filling\n","# acroform-fill\n\nUse this skill for fillable PDF form workflows backed by sciClaw's dedicated PDF form tools.\n\n## Core workflow\n\n1. Run `pdf_form_inspect` first.\n2. If `isSupportedAcroForm` is `false`, stop and explain that sciClaw will not force-fill non-AcroForm, XFA-only, or scanned PDFs.\n3. Run `pdf_form_schema` to get the field inventory before preparing values.\n4. If values are not already in a JSON file, create one in the workspace with `write_file`.\n5. Run `pdf_form_fill` to a **new** output path.\n6. Keep `flatten=false` by default. Only flatten when the user explicitly wants final non-editable output.\n7. Report `skippedFields` and `unusedInputKeys` clearly. If either is non-empty, treat the output as review-needed.\n8. If you need to send the resulting PDF back to the user, use `message` with the output file as an attachment.\n\n## Rules\n\n- Never overwrite the source PDF.\n- Never skip `pdf_form_inspect`.\n- Do not use `read_file` on raw PDFs.\n- Prefer exact field names from `pdf_form_schema`; do not invent field names.\n- For choice fields, use the schema's `choices` exactly.\n- If the user only wants to know whether a PDF is fillable, stop after `pdf_form_inspect`.\n- If the user gives narrative text instead of structured values, convert that text into a JSON values file before calling `pdf_form_fill`.\n- For sensitive or regulated workflows, prefer reviewable output before flattening.\n\n## Minimal examples\n\n### 1. Check whether a PDF is a real AcroForm\n\nUse when the user asks: \"Is this PDF fillable?\"\n\n```json\n{\"pdf_path\":\"forms\u002Fprior-auth.pdf\"}\n```\n\nTool:\n\n- `pdf_form_inspect`\n\nGood outcome:\n\n- `isSupportedAcroForm = true` -> continue if needed\n- `isSupportedAcroForm = false` -> stop and explain why\n\n### 2. Get the field schema before filling\n\nUse when the user asks: \"What fields are on this form?\"\n\n```json\n{\"pdf_path\":\"forms\u002Fprior-auth.pdf\"}\n```\n\nTool:\n\n- `pdf_form_schema`\n\nThen summarize the important field names, types, and any `choices` the model must respect.\n\n### 3. Fill from an existing values JSON file\n\nFirst make sure the values file exists in the workspace, for example:\n\n```json\n{\n  \"PatientName\": \"Jane Doe\",\n  \"DOB\": \"1978-02-14\",\n  \"Urgent\": true\n}\n```\n\nThen call:\n\n```json\n{\n  \"pdf_path\":\"forms\u002Fprior-auth.pdf\",\n  \"values_path\":\"memory\u002Fprior-auth.values.json\",\n  \"output_path\":\"memory\u002Fprior-auth.filled.pdf\",\n  \"flatten\":false\n}\n```\n\nTool:\n\n- `pdf_form_fill`\n\n### 4. Fill from narrative text\n\nUse when the user gives a note, letter, or summary instead of a ready JSON file.\n\nWorkflow:\n\n1. `pdf_form_inspect`\n2. `pdf_form_schema`\n3. `write_file` a JSON values file in the workspace\n4. `pdf_form_fill`\n5. Report any skipped or unused fields\n\n## When not to use this skill\n\n- OCR or scanned-document extraction\n- Free-form PDF text extraction\n- XFA-only forms that are not true AcroForms\n- Cases where the user wants arbitrary PDF editing instead of form filling\n",{"name":5,"metadata":49,"description":7},{"nanobot":50},{"install":51,"requires":56},[52],{"id":41,"bins":53,"kind":41,"label":55,"formula":54},[54],"pdf-form-filler","Install pdf-form-filler (brew)",{"bins":57},[54],"main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Facroform-fill",18,"https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills","https:\u002F\u002Fgithub.com\u002FFDU-INS","Fudan University Department of Risk Management and Insurance","2026-07-12 12:54:34",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add FDU-INS\u002FInsurance-Skills --skill acroform-fill",{"tool":72,"command":73},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill acroform-fill",{"tool":75,"command":76},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill acroform-fill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Facroform-fill\u002FSKILL.md",true,[],[81,110,133,162,183,216],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":44},"01M713QW6EGEG0YAD75440GSD0","로인장 (Roinjiang)","Activates when the user needs legal advice, contract review, insurance law consultation, startup legal support, or any legal\u002Fregulatory 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.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002F로인장 (Roinjiang)\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[83,93,27,94,95,96,29,97,98,99,100,101,102,103,104,105,106,107,108,109],"insurance law","civil","contract","family","review","loyalty","with","top","contract review","ceo","support","advice","consultation","regulatory","privacy","protection","startup",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":44},"01M713QRN8VFMA9VKS6R4DJ2WS","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.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fzocdoc-doctor-finder\u002FSKILL.md",[],[117,118,119,120,27,121,122,29,123,124,125,126,127,128,129,31,130,131,40,132],"zocdoc doctor finder","doctor","healthcare","reviews","browser automation","access","browsing","browser","booking","network","therapist","computer","availability","provider","tool","automation",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":44},"01M713QKGV3FTX7EEYWKDM8ENZ","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.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fzenmux-context\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[143,144,145,146,27,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161],"context","zenmux context","Video","chinese","project","web search","translate","search","open","question","pay","image","you","activate","architecture","logs","streaming","cherry studio","how",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":44},"01M713QHWTBG634BCBV7NBJME1","workers-comp-guide","Guide workers compensation compliance and claims management.\nTRIGGERS - Use when user needs help with workers-comp-guide related tasks.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fworkers-comp-guide\u002FSKILL.md",[],[169,170,171,172,173,27,174,175,40,29,43,99,176,177,178,179,180,181,182],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","claims management","claims","compliance","help","compensation","management","user",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":198,"publishedAt":44},"01M713QF45VMV1685AFNF1GPMA","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\u002FCSV) and requests board report, weekly presentation, executive briefing, or mentions keywords like 董事会汇报, 周报PPT, 经营分析演示, McKinsey-style reports.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fweekly-kpi-report\u002FSKILL.md",[189,192,195],{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":196,"categoryName":197,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000034","行政与办公人员",[199,200,201,202,203,27,204,205,206,207,29,208,209,210,211,212,213,214,40,215],"weekly","weekly kpi report","kpi","report","xlsx","actionable","insights","briefing","auto","board report","reports","generate","演示","data","presentation","slides","uploads",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":225,"publishedAt":44},"01M713QA9WJDHMNVTTY1ENRKVB","wealth-advisory","Wealth management and financial planning for HNW and UHNW clients. Activate when the user\nmentions wealth management, financial planning, retirement, estate planning, tax planning,\nGRAT, IDGT, trust, asset allocation, withdrawal rate, Monte Carlo simulation, goals-based\ninvesting, tax-loss harvesting, Roth conversion, insurance, annuity, mortgage strategy,\nconcentrated stock, family office, direct indexing, 529 plan, charitable giving, donor-advised\nfund, private foundation, or asks about personal finance strategy, inheritance, long-term\nfinancial planning, or UHNW advisory.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fwealth-advisory\u002FSKILL.md",[222],{"categoryNo":223,"categoryName":224,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000040","财务",[226,227,27,228,229,29,156,230,231,232,233,234,235,236,237,238,239,240,241,242],"wealth advisory","advisory","stock","inheritance","conversion","indexing","plan","simulation","personal finance","rate","allocation","asset","direct","personal","investing","trust","planning"]