fm-summarize

Generate structured technical documentation for FileMaker objects from DuckDB catalog data.

17|5|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/marcel-more/fm-lab --skill fm-summarize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fm-summarize
Source: https://github.com/marcel-more/fm-lab/tree/main/.claude/skills/fm-summarize
Command: npx skills add https://github.com/marcel-more/fm-lab --skill fm-summarize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FileMaker solutions are often complex and opaque, making it difficult for developers and AI agents to understand the structure, dependencies, and logic of specific objects like scripts, fields, or layouts. This skill bridges that gap by providing instant, context-aware technical documentation directly from the solution's metadata.

Core Features & Use Cases

  • Technical Deep-Dives: Automatically generates structured summaries including purpose, technical details, and flow for any FileMaker object.
  • Dependency Mapping: Clearly identifies what an object uses and what uses it, enabling safe refactoring and impact analysis.
  • Multi-Language Support: Provides summaries in 11 languages, ensuring accessibility for global development teams.
  • Use Case: When refactoring a complex script, use this skill to instantly see every field it modifies and every sub-script it calls, preventing unintended side effects.

Quick Start

Ask the AI to describe the script named MyProcess in the current FileMaker solution.

Frequently Asked Questions about fm-summarize

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

FAQPage Schema
How do I generate technical documentation for FileMaker scripts and fields?

You can generate technical documentation for FileMaker scripts by querying a DuckDB-based catalog of solution metadata, which produces structured summaries detailing purpose, flow, and dependencies for fields and scripts.

What is dependency mapping for FileMaker objects and how does it work?

Dependency mapping for FileMaker objects identifies what a script or field uses and what uses it. It works by querying solution metadata to enable safe refactoring and impact analysis.

Do I need a DuckDB catalog to analyze FileMaker solution structures?

Yes, you need a DuckDB-based catalog of solution metadata to analyze FileMaker solution structures. This catalog provides the structured data required to resolve dependencies and generate summaries.

Can I get FileMaker layout analysis and summaries in multiple languages?

Yes, you can get FileMaker layout analysis and summaries in multiple languages. The system supports generating structured technical documentation in 11 languages for global development teams.

What is the best way to understand complex FileMaker scripts for refactoring?

The best way to understand complex FileMaker scripts for refactoring is to generate automated technical summaries that map operational flow, modified fields, and called sub-scripts to prevent unintended side effects.

When should I not use automated summaries for FileMaker analysis?

You should not use automated summaries for FileMaker analysis when your solution metadata is not stored in a DuckDB catalog, as the tool requires this structured metadata to resolve dependencies and generate documentation.