Skip to content
Development
Command

/instinct-import

Import instincts from file or URL into project/global scope

From plugin
ecc
239k109 skills72 agents109 commands7 hooks
+1
Install
> /plugin marketplace add affaan-m/everything-claude-code
> /plugin install ecc@ecc

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/instinct-import

Context preview

What this command does when you run it.

Import instincts from file or URL into project/global scope

Command definition

instinct-import.md
name: instinct-import
description: Import instincts from file or URL into project/global scope
command: true

Instinct Import Command

Implementation

Run the instinct CLI using the plugin root path:

python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" import <file-or-url> [--dry-run] [--force] [--min-confidence 0.7] [--scope project|global]

Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):

python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <file-or-url>

Import instincts from local file paths or HTTP(S) URLs.

Usage

/instinct-import team-instincts.yaml
/instinct-import https://github.com/org/repo/instincts.yaml
/instinct-import team-instincts.yaml --dry-run
/instinct-import team-instincts.yaml --scope global --force

What to Do

1. Fetch the instinct file (local path or URL) 2. Parse and validate the format 3. Check for duplicates with existing instincts 4. Merge or add new instincts 5. Save to inherited instincts directory:

  • Project scope: `~/.claude/homunculus/projects/<project-id>/instincts/inherited/`
  • Global scope: `~/.claude/homunculus/instincts/inherited/`

Import Process

 Importing instincts from: team-instincts.yaml
================================================

Found 12 instincts to import.

Analyzing conflicts...

## New Instincts (8)
These will be added:
  ✓ use-zod-validation (confidence: 0.7)
  ✓ prefer-named-exports (confidence: 0.65)
  ✓ test-async-functions (confidence: 0.8)
  ...

## Duplicate Instincts (3)
Already have similar instincts:
  WARNING: prefer-functional-style
     Local: 0.8 confidence, 12 observations
     Import: 0.7 confidence
     → Keep local (higher confidence)

  WARNING: test-first-workflow
     Local: 0.75 confidence
     Import: 0.9 confidence
     → Update to import (higher confidence)

Import 8 new, update 1?

Merge Behavior

When importing an instinct with an existing ID:

  • Higher-confidence import becomes an update candidate
  • Equal/lower-confidence import is skipped
  • User confirms unless `--force` is used

Source Tracking

Imported instincts are marked with:

source: inherited
scope: project
imported_from: "team-instincts.yaml"
project_id: "a1b2c3d4e5f6"
project_name: "my-project"

Flags

  • `--dry-run`: Preview without importing
  • `--force`: Skip confirmation prompt
  • `--min-confidence <n>`: Only import instincts above threshold
  • `--scope <project|global>`: Select target scope (default: `project`)

Output

After import:

PASS: Import complete!

Added: 8 instincts
Updated: 1 instinct
Skipped: 3 instincts (equal/higher confidence already exists)

New instincts saved to: ~/.claude/homunculus/instincts/inherited/

Run /instinct-status to see all instincts.
Read more
Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

Get the whole plugin