script-lookup

Locate FileMaker scripts in parsed XML by ID or name.

89|29|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/petrowsky/agentic-fm --skill script-lookup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: script-lookup
Source: https://github.com/petrowsky/agentic-fm/tree/main/.cursor/skills/script-lookup
Command: npx skills add https://github.com/petrowsky/agentic-fm --skill script-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fd, and includes scripts (resource) components.

What problem does it solve?

This Skill helps developers quickly locate specific FileMaker scripts within a project's parsed XML exports, whether by ID or name, and provides easy access to their different versions for review or refactoring.

Core Features & Use Cases

  • Script Identification: Pinpoints scripts using script IDs or names (exact, contains, fuzzy matching).
  • Version Access: Provides paths to human-readable sanitized versions, original Save-As-XML references, and editable fmxmlsnippet versions.
  • Use Case: When a developer needs to refactor a script named "Update Customer Record," this Skill finds the correct script, shows its different file representations, and prompts for confirmation before proceeding.

Quick Start

Use the script-lookup skill to find and review the script with ID 123.

Frequently Asked Questions about script-lookup

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

FAQPage Schema
How do I find a specific FileMaker script within parsed XML data?

You can find a specific FileMaker script by locating it within parsed XML data using exact script ID or name matching, which supports multi-solution structures and returns paths to various XML versions.

Can I search for FileMaker scripts using partial names instead of exact matches?

Yes, FileMaker script lookup supports exact, contains, and fuzzy name matching to pinpoint scripts, allowing you to identify scripts even when you only have partial names rather than exact IDs.

What's the best way to access different XML versions of a FileMaker script for refactoring?

The best way to access script versions for refactoring is to locate the script by ID or name, which provides direct paths to human-readable sanitized versions, original Save-As-XML references, and editable fmxmlsnippet versions.

Does this FileMaker script lookup approach work with multi-solution structures?

Yes, the script lookup mechanism fully supports multi-solution structures, enabling you to locate and review specific scripts across different FileMaker solution files within the parsed XML data exports.

Do I need the fd dependency to locate FileMaker scripts in XML exports?

Yes, you need the fd dependency installed, as the script lookup component relies on it to parse the XML data and locate the specific FileMaker scripts by ID or name matching.

How does the script lookup process handle confirmation before proceeding with refactoring?

The script lookup process presents clear file paths for the sanitized, Save-As-XML, and fmxmlsnippet versions, and then explicitly prompts you for confirmation before proceeding with any script review or refactoring workflow.