filemaker-field-xml — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited filemaker-field-xml (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill gives Claude a deterministic, empirically verified foundation for generating FileMaker field definition XML — the fmxmlsnippet type="FMObjectList" clipboard format containing <Field> elements, accepted by FileMaker's Manage Database paste handler.
Created by Andrew Kear of Clockwork Creative Technology and shared openly with the FileMaker/Claris community.
When this skill is active, Claude will:
id values across all fields in a single paste. Duplicate IDs cause silent drops when calculation auto-enter fields reference each other.<ValueList> child element is only preserved when the referenced value list ID exists in the target file at paste time. When the target file is unknown, omit the value list and tell the user to assign it manually after pasting.<Furigana> element on paste when the field's <ValueList> reference does not resolve. Ensure the value list ID is real if Furigana is required.<!-- --> comments (unlike the script paste handler, which tolerates them). Generated field XML must be comment-free. Document intent with descriptive field names and <Comment> elements instead.<Annotation> (a <Text> child holding plain text, read by FieldAnnotation()) and <DisplayNames enable="..."> (when enabled, a <Calculation> returning JSON keyed by fm_common/fm_export/fm_sort/fm_table_view plus optional custom keys, read by FieldDisplayNames()). Both are round-trip confirmed on Normal, Calculation, and Summary fields (see §14). Omit both for 2025 or mixed targets; emit both for 2026. Note that annotating any field narrows that table's generated DDL to annotated fields only. The 2026 calculation-controlled field entry (read-only via calculation) is a layout object property, not a field definition, and is out of scope here.The full specification is in references/filemaker_xmfd_spec.md (v1.0), covering:
Claude reads this automatically when handling field definition XML tasks. You do not need to reference it in your prompts.
Generate field definitions:
"Generate XML for a Contacts table: UUID primary key, first name, last name, email with validation, and creation/modification audit stamps"
Review existing XML:
Paste your fmxmlsnippet and ask: "Check this field XML for paste-handler errors"
With a DDR:
Attach your DDR export and Claude will use real value list IDs and existing field names from your solution.
Requires MBS Plugin to be installed in FileMaker Pro. No MBS scripting is needed — the plugin simply needs to be present.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.