andykear

FileMaker XMLsnippet Claude Skill — Development skill for Claude Code

Development community

Reverse-engineered specification of FileMaker's undocumented script XML paste behaviour, including a fully verified step ID dictionary and the hidden paste-handler rules that make a pasted script work.

How to install FileMaker XMLsnippet Claude Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open andykear/FileMaker-XMLsnippet-Claude-Skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What FileMaker XMLsnippet Claude Skill does

Reverse-engineered specification of FileMaker's undocumented script XML paste behaviour, including a fully verified step ID dictionary and the hidden paste-handler rules that make a pasted script work or silently fail. Packaged as a Claude skill that generates accurate, pasteable script XML.

Alternatives in Development

README

FileMaker Script XML Specification

[![Stars](https://img.shields.io/github/stars/andykear/FileMaker-XMLsnippet-Claude-Skill?style=social)](https://github.com/andykear/FileMaker-XMLsnippet-Claude-Skill) [![License](https://img.shields.io/badge/license-CC%20BY%204.0-green)](https://creativecommons.org/licenses/by/4.0/)

Reverse-engineered specification of FileMaker's undocumented `fmxmlsnippet` clipboard format. Every step ID, element ordering rule, and silent failure mode, established through empirical round-trip testing against production FileMaker solutions.

Developed by Andrew Kear of [Clockwork Creative Technology](https://www.clockworkct.co.uk) and shared openly with the FileMaker/Claris community.


Why this exists

FileMaker's Script Workspace accepts pasted scripts in a specific XML format. Claris has never published a specification for it. Get the XML wrong and FileMaker accepts it silently, dropping data without any error message.

This specification documents what the paste handler actually accepts: 220 step IDs, canonical XML skeletons for every step, the element ordering constraints that cause silent drops when violated, and the calculation slot binding rules that cause multi-slot steps to misbind.


What it catches

The specification documents several classes of silent failure that are invisible in the Script Workspace after paste:

**Set Variable name drop.** If the variable name element is emitted as a single-letter tag instead of the canonical four-letter `Name` form, FileMaker pastes the step with no variable name. No error. No warning. You find out when the script runs.

**Calculation slot misbinding.** Install OnTimer Script, Perform JavaScript in Web Viewer, and other steps with multiple calculation slots silently bind a calculation to the wrong internal slot when elements are in the wrong order. The script appears to work. The calculation runs in the wrong context.

**Element ordering.** Several steps require child elements in