intelligence-transfer
Publish or fetch learned patterns across projects via IPFS (Pinata) -- the cross-project pattern transfer that hooks_transfer enables
Best for multi-project teamsWorks with GitHubLow risk
⌘source
- author
@ruvnet- repo
- ruvnet/ruflo
- language
- TypeScript
★46kstars
5.1kforks
May 5, 2026
✦overview.md
Key Features
- ·Cross-project pattern sharing via IPFS
- ·Publish learned patterns as deploy artifacts
- ·Fetch patterns from any peer using a CID
- ·Structured error on missing API config
Use Cases
- →Sharing agent-learned patterns across development teams
- →Transferring patterns from one machine to another
- →Versioning and distributing pattern knowledge as IPFS artifacts
Best for
- ✓multi-project teams
- ✓distributed development
Not ideal for
- !single-project workflows
- !offline environments
FAQs
name
intelligence-transfer
description
Publish or fetch learned patterns across projects via IPFS (Pinata) -- the cross-project pattern transfer that hooks_transfer enables
argument-hint:<store|load|from-project> [--cid <ipfs-cid>] [--source <project-path>]
allowed-tools:mcp__claude-flow__hooks_transfer mcp__claude-flow__hooks_intelligence_pattern-search mcp__claude-flow__hooks_intelligence_pattern-store mcp__claude-flow__neural_patterns mcp__claude-flow__neural_status Bash
Intelligence Transfer
Cross-project pattern sharing via IPFS. Lets a different project — or a different machine — fetch and apply patterns this project has already learned.
Why this exists
Most learning is project-local. hooks_transfer is the escape hatch: publish patterns to IPFS, share the CID, and any peer can ingest them. Equivalent to "a deploy artifact for what your agents have learned."
Prerequisite
# Required env var (or equivalent endpoint config)
echo $PINATA_API_JWT
If unset, hooks_transfer returns a structured success: false with error: "PINATA_API_JWT not configured". Configure before running this skill.
Workflows
Publish current project's patterns
# Inspect what's stored locally first
mcp tool call neural_patterns --json -- '{"list": true}'
# Publish to IPFS — returns a CID
mcp tool call hooks_transfer --json -- '{"action": "store"}'
The response includes the IPFS CID. Save it; share it with peers who need the patterns.
Fetch + apply a peer's patterns
# Pull a CID and apply locally
mcp tool call hooks_transfer --json -- '{"action": "load", "cid": "QmXyz..."}'
# Verify they landed
$install
1-click copynpx skills add ruvnet/ruflo --skill intelligence-transferSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.