instinct-import

Import instincts from external exports with merge strategies and provenance tags.

Updated Aug 27, 2026

Search Tags:#cli #provenance #merge #export #import #instincts

Ready to run

npx skills add https://github.com/ItsMattG/property-tracker --skill instinct-import-itsmattg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: instinct-import
Source: https://github.com/ItsMattG/property-tracker/tree/main/.claude/skills/instinct-import
Command: npx skills add https://github.com/ItsMattG/property-tracker --skill instinct-import-itsmattg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import instincts from external exports into the current project, enabling reuse and consolidation of AI-driven patterns across repositories.

Core Features & Use Cases

Import instincts from exported files to extend the current project's capabilities.
Merge duplicates deterministically using a defined strategy and preserve provenance metadata.
Apply changes with a dry-run preview or an apply mode to ensure safe integration, with audit trails.

Quick Start

Run the instinct CLI to import instincts from an export file into your project.

Frequently Asked Questions about instinct-import

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

FAQPage Schema

How do I import instincts from an export file into my project?▼

You can import instincts by running the instinct CLI against an export file. This enables reuse and migration of AI-driven patterns across repositories by applying a defined merge strategy.

What is the best way to merge duplicate instincts during an import?▼

The best way to merge duplicates during an import is to use the defined merge strategy. This deterministically consolidates instincts while preserving provenance metadata like imported_from and imported_at.

Can I preview an instinct import before applying changes to my repository?▼

Yes, you can preview an instinct import using dry-run mode. This shows the changes before they are committed, allowing for auditable integration before you switch to apply mode.

How does provenance tracking work when importing instincts across repositories?▼

Provenance tracking works by preserving imported_from and imported_at tags during the import. This creates an auditable trail of where and when AI-driven patterns were integrated into the project.

Why use a CLI to migrate AI patterns instead of copying files manually?▼

Using a CLI to migrate AI patterns ensures deterministic duplicate merging and preserved provenance metadata, unlike manual copies. It provides dry-run previews and audit trails for safe integration.