← ClaudeAtlas

filemaker-xmllisted

Use this skill whenever the user wants to work with FileMaker script XML or custom function XML. This includes: generating FileMaker XML from a description, pseudocode, or script steps; analysing or reviewing existing FileMaker XML for errors or silent-failure risks; converting scripts between formats; or any task where the output must be paste-ready XML for the FileMaker Script Workspace or Manage Custom Functions dialog. Trigger any time the user mentions FileMaker scripts, fmxmlsnippet, Set Variable XML, script step XML, custom function XML, or asks to produce XML that can be pasted into FileMaker. Always use this skill — do not attempt FileMaker XML tasks from memory alone, as the format has undocumented paste-handler rules that cause silent failures without this reference.
andykear/FileMaker-XMLsnippet-Claude-Skill · ★ 6 · Data & Documents · score 68
Install: claude install-skill andykear/FileMaker-XMLsnippet-Claude-Skill
# FileMaker Script & Custom Function XML Skill ## Overview This skill enables Claude to correctly **analyse** and **generate** FileMaker Script Workspace XML — the `fmxmlsnippet type="FMObjectList"` format that FileMaker accepts via clipboard paste. The format has a lenient XML parser but a strict paste handler. Structural deviations that look fine as XML can cause steps to paste with silently missing data (e.g. Set Variable pastes with no variable name). The reference files in this skill are the authoritative reverse-engineered spec for what the paste handler actually accepts. --- ## Mandatory reading — progressive loading The specification (v1.11) is split so a task loads only the sections it needs. The rules are: 1. **Always read `references/core.md` first.** Not optional. It contains the paste format requirements, common conventions, the Set Variable canonical structure, and the silent-failure modes that apply to every step. Skipping it reintroduces the from-memory failure mode this skill exists to prevent. 2. **Always read `references/steps-control.md`.** Control steps (If, Loop, Perform Script, Exit Script, Comment, transactions) appear in virtually every script. 3. **Then read only the step category files containing the steps the task needs**, using the routing index below. When reviewing XML someone else produced, route by the `name` attributes on the `<Step>` elements in the snippet. 4. Custom function tasks: read `references/custom-