install-ooe-fm

Clone and synchronize the ooe-fm FileMaker reference repository via git.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of cloning, tracking, and updating the ooe-fm (One Of Everything) FileMaker reference repository, ensuring your test environment is always synchronized with the latest XML test cases.

Core Features & Use Cases

  • Automated Version Control: Automatically compares local commits against the remote repository to detect updates.
  • Safe Installation: Provides a robust workflow for cloning or updating test data with built-in safety checks to prevent accidental directory deletion.
  • Use Case: When you need to run validation tests against the latest FileMaker XML structure, this skill ensures your local reference data is current without requiring manual git commands.

Quick Start

Ask the assistant to install the ooe-fm test data to automatically clone or update the repository in your local documentation folder.

Frequently Asked Questions about install-ooe-fm

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

FAQPage Schema
How do I automate FileMaker XML test data setup from a git repository?

Automating FileMaker XML test data setup involves cloning and synchronizing a version-controlled reference repository via git to ensure your local test environment matches the latest XML test cases.

Do I need git installed to sync FileMaker test data repositories?

Yes, git must be installed and accessible in your environment to perform the repository operations required for cloning and updating the FileMaker XML test data.

How does version control synchronization work for FileMaker test environments?

Version control synchronization compares local commits against the remote repository to detect updates, then applies those changes to maintain consistent FileMaker testing environments.

What is the best way to update local FileMaker XML test data safely?

The safest way to update local FileMaker XML test data is using an automated workflow with built-in safety checks that prevent accidental directory deletion during repository synchronization.

Can I track version markers for FileMaker XML test cases locally?

Yes, you can track version markers for FileMaker XML test cases locally by comparing your local commit state against the remote repository to determine if updates are required.