- Home
- Skills
- Data & Databases
- FileMaker Pro Development Reference
More screenshots
Works with the AI Agents you already use
FileMaker Pro Development Reference
AI reference for Claris FileMaker development: 368 functions, 216 script steps, 292 error codes, compatibility guidance, ExecuteSQL, Data API, and script reviews.
$14.99
FileMaker Pro Development Reference
Example session with this skill installed
Write a script to create a new record in a 'Logs' table and set a 'Timestamp' field, ensuring it works on FileMaker Server. Use a transaction if possible.
- Read your context and instructions
- Compiled the filemaker pro development
Claris FileMaker Pro — AI Development Reference
Build, troubleshoot, and improve Claris FileMaker solutions with a specialized AI agent skill designed for professional developers.
This skill provides structured technical references, practical development guidance, and version-aware information to help AI coding assistants work more accurately with FileMaker's native scripting language, calculations, database architecture, and integration APIs.
What's Included
- 368 Native Functions: Reference signatures, parameters, return types, and version information.
- 216 Script Steps: Explore scripting capabilities, execution contexts, and platform compatibility.
- 292 Error Codes: Identify errors and understand relevant troubleshooting approaches.
Platform Compatibility: Guidance for FileMaker Pro, Go, WebDirect, Server, and other supported execution environments.
- Database Development: Tables, relationships, table occurrences, layouts, field types, and indexing.
- Advanced Calculations: JSON processing, text manipulation, date/time operations, and ExecuteSQL.
- API Integration: FileMaker Data API, OData, HTTP integrations, and interoperability patterns.
Professional Development Patterns: Transactions, validation, error handling, modular scripts, and maintainable database design.
What Can You Do With It?
Ask your AI agent to
- Review FileMaker scripts and identify potential errors or compatibility issues.
- Develop calculations and explain their behavior.
- Check whether specific functions or script steps are supported in your FileMaker version.
- Troubleshoot database relationships, finds, and ExecuteSQL queries.
- Design integrations using JSON and the FileMaker Data API.
- Improve script organization, error handling, and maintainability.
Built for AI-Assisted Development
Designed for use with AI coding assistants that support Agent Skills, including ChatGPT, Codex, and other compatible environments.
The skill includes structured references and optional read-only Python lookup utilities. Execution of those utilities depends on the capabilities of the agent environment.
Important Limitations
This skill provides technical references and development assistance. It does not include FileMaker software, connect automatically to your databases, or execute scripts inside the FileMaker engine.
Catalog information reflects documented reference snapshots. Generated calculations and scripts should be validated against your target FileMaker version and environment.
Licensing & Attribution
Independent adaptation of work originally developed by Darrin Southern / CadenceUX under Creative Commons Attribution 4.0 (CC BY 4.0).
Includes rewritten examples, original utilities, enhanced compatibility guidance, additional documentation, and automated validation.
Applicable CC BY 4.0 rights remain in effect for the corresponding licensed material.
Source code, documentation, and attribution:
https://github.com/Marbin891/filemaker-pro-agent-skills
Independent project. Not affiliated with or endorsed by Claris, CadenceUX, or third-party plugin vendors.
Connects securely to your tools. The creator never sees your data.
About this skill
Managing Claris FileMaker development often involves navigating inconsistent behavior across Pro, Go, WebDirect, and Server. This skill provides precise, version-aware assistance for building calculations, scripts, and integrations using a local catalog of over 360 functions and 200 script steps.
What it does
- Version-aware logic validates whether specific functions or script steps are supported in your target FileMaker version, including patch levels like 19.6.1.
- Platform validation identifies partial or missing support for script steps across WebDirect, FileMaker Go, Server-side scripting, and Data API.
- Formula construction builds syntactically correct calculations for JSON handling, ExecuteSQL, and complex logical operations.
- API integration generates structured requests and handles responses for the FileMaker Data API and OData endpoints.
- Schema analysis provides guidance on table occurrences, relationship graphs, and layout contexts to ensure context-correct scripting.
How it works
- Define your environment by providing the FileMaker version, host type, and client product (e.g., FileMaker Go 2024 on iOS).
- Input your requirement, such as fixing a broken transaction script or building a dynamic find request.
- The skill checks local catalogs for function signatures and step options to ensure compatibility with your specific environment.
- It outputs readable Script Workspace steps or calculations along with error handling logic and verification steps.
Frameworks & tools
This skill focuses on native Claris FileMaker Pro, Server, Go, and WebDirect development. It supports integration with the FileMaker Data API, OData, and ExecuteSQL.
Why this beats prompting it yourself
Generic LLMs frequently hallucinate script steps or mix up function parameters between versions. This skill uses a local, versioned catalog to ensure that suggested script steps actually exist in your specific FileMaker release and work on your target platform.
Use cases
- Debugging scripts that fail only on FileMaker Server or WebDirect.
- Writing complex
JSONSetElementcalculations with proper escaping and types. - Drafting ExecuteSQL queries that respect FileMaker's specific SQL syntax limits.
- Mapping Data API or OData calls for external web integrations.
Known limitations
Does not support third-party plug-ins like BaseElements or MBS unless explicitly paired with their respective skills. Performance claims are not verified by a live FileMaker engine.
Reference catalogs are based on a FileMaker 26 (2026) snapshot. Historical version and platform compatibility information may be incomplete for specific options or releases.
Generated scripts and calculations are not automatically executed or validated by the FileMaker engine. Developers must test solutions in their target environment.
The skill does not directly access or modify FileMaker databases. Optional offline catalog lookup tools require Python 3.10+ and an agent environment supporting local file access and script execution.
Third-party plugin function catalogs (BaseElements, MBS, and bBox) are provided through separate companion skills. No plugin binaries or licenses are included.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 10 days ago
Requires
Permissions
This skill operates in read-only reference mode by default. It reads bundled JSON and Markdown documentation to provide FileMaker development guidance, function signatures, script step compatibility, and error diagnostics. An optional Python 3.10+ command-line utility performs offline, read-only catalog lookups. No network access, credentials, environment variables, telemetry, automatic downloads, or file modifications are required for normal operation. Live FileMaker integrations require separately configured tools and explicit user authorization.