claris-filemaker-prolisted

REFERENCE skill — FileMaker Pro script steps, calculation functions, and field types. Use for: syntax lookups, function parameters and return types, per-step platform support across FileMaker Pro, Go, WebDirect, Server, Cloud, Data API and Custom Web Publishing, field type capabilities, usage examples, and live doc fetches. Covers all 368 built-in functions (If, Case, Let, While, ExecuteSQL, JSON, AI/embedding, Persistent Data), all 216 script steps (including the FM 26 PDF Files and Persistent Data categories), plus the Data API, OData, WebDirect, FileMaker Go, SQL/ExecuteSQL, error codes, and custom functions. Not a platform administration guide. Out of scope: FileMaker Server admin, Claris Connect, Claris Studio, ODBC/JDBC configuration. Trigger on any FileMaker function or script step name — even inside code, a calc field, or a script. Local reference files are verified against source and are authoritative; fetch live docs when the topic is volatile or the user signals recency.
CadenceUX/claris-filemaker-pro-skill · ★ 9 · Data & Documents · score 67

Install: claude install-skill CadenceUX/claris-filemaker-pro-skill

# Claris FileMaker Pro — Skill v2.0.0 ## What this skill is A **reference skill for FileMaker Pro** — script steps, calculation functions, field types, and the client platforms a solution runs on. It is deliberately scoped to FileMaker Pro rather than the wider Claris platform, and it goes deep on that one surface: verified call signatures and return types, per-step platform support, worked usage examples, error codes, and the API surfaces a Pro developer actually reaches for. It is **not** a minimal name-and-signature vocabulary list, and **not** a link index that defers every real answer to a web fetch. The local reference files carry verified content and are designed to answer most questions without a network round-trip. It does not cover FileMaker Server administration, Claris Connect, Claris Studio, or deep ODBC/JDBC configuration. The Claris Help Centre at **https://help.claris.com** remains the authoritative upstream source. Every local file records how and when it was verified against it. --- ## Local-first: when to answer locally, when to fetch **Default: answer from the local reference files.** They were re-derived from the live Claris documentation on **2026-07-25** — every function signature, return type, and originated-in version, and every script step's full seven-product compatibility matrix. Treat them as correct. This matters for generation speed and accuracy: composing a script, or a set of field definitions, should not require a network fetch per st