fm-debug

Capture FileMaker script runtime state, variable values, and error codes.

89|29|Updated Feb 19, 2026

Search Tags:#debugging #troubleshooting #scripting #runtime analysis #filemaker

Ready to run

npx skills add https://github.com/petrowsky/agentic-fm --skill fm-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fm-debug
Source: https://github.com/petrowsky/agentic-fm/tree/main/.cursor/skills/fm-debug
Command: npx skills add https://github.com/petrowsky/agentic-fm --skill fm-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve unexpected errors or incorrect behavior in FileMaker scripts when the root cause isn't apparent from the source code alone.

Core Features & Use Cases

Bridging the Opaque Gap: Provides methods for agents to gain insight into FileMaker script runtime state, which is normally inaccessible.
Two Debugging Methods: Supports both a preferred, machine-readable "Agentic-fm Debug Script" and a fallback method using a global variable ($$DEBUG).
Use Case: A FileMaker script is failing intermittently. You need to know the values of specific variables or the script's exit code at the point of failure to understand why.

Quick Start

Use the fm-debug skill to get runtime variable state from the script named "My Failing Script".

Frequently Asked Questions about fm-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I inspect FileMaker script variable values during runtime debugging?▼

FileMaker script debugging captures runtime variable values by executing the target script and retrieving debug output via a dedicated debug script or a global variable fallback. Developers manually trigger the script run to inspect variable state, script results, and error codes at the point of failure.

What is the best way to troubleshoot intermittent FileMaker script failures?▼

Troubleshooting intermittent FileMaker script failures requires capturing runtime state at the point of failure. This Skill inspects variable values and script error codes, bridging the opaque gap where the root cause isn't apparent from the source code alone, to help resolve unexpected behavior.

Can I debug FileMaker scripts without a dedicated debug script?▼

You can debug FileMaker scripts without a dedicated script by using a fallback method that writes runtime state to a global variable. This allows you to inspect variable values and error codes when the preferred machine-readable debug script is not available in your solution.

How do I retrieve FileMaker script error codes and exit states?▼

FileMaker script error codes and exit states are retrieved by manually triggering script execution and capturing runtime debug output. This Skill provides mechanisms to inspect script results and error codes, enabling developers to identify why a script is failing or producing incorrect behavior.

When do I need runtime analysis for FileMaker scripting issues?▼

Runtime analysis for FileMaker scripting is needed when unexpected errors or incorrect behavior occur and the root cause isn't visible in the source code. Capturing variable values and error codes at runtime provides the insight necessary to diagnose and resolve opaque script issues.

Does FileMaker runtime debugging require manual execution?▼

FileMaker runtime debugging requires manual execution by a developer to trigger script runs and retrieve debug output. This manual approach ensures you capture the exact runtime state, including variable values and error codes, at the specific point of script failure.