---
name: linkedin-import
description: "Import a LinkedIn Basic Data Export into the Maxy Neo4j graph. Skill-only plugin owned by the librarian specialist. Opt-in per brand — not enabled by default."
tools: []
always: false
embed: false
specialist: librarian
metadata: {"platform":{"optional":true,"pluginKey":"linkedin-import"}}
---

# LinkedIn Import

Ingests a LinkedIn Basic Data Export (unzipped directory of CSVs + subdirectories) into the Maxy Neo4j graph. Skill-only plugin — no MCP server, no admin tools added. The skill runs under the `specialists:librarian` specialist, which owns foreground archive and document ingestion.

## When this applies

The admin agent delegates to `specialists:librarian` when the operator drops a `Basic_LinkedInDataExport_*` directory (or references one by path) into chat. The specialist runs the skill's archive-owner confirmation flow before any CSV is read, then ingests the CSVs the skill has references for.

## Intra-plugin growth

A LinkedIn export contains ~20 CSVs. The skill ships references for `Profile.csv` and `Connections.csv` today — additional CSVs (Messages, Positions, Skills, Endorsements, Recommendations, Articles, Education, Certifications, Invitations, etc.) land as **new reference files inside this same plugin** under `skills/linkedin-import/references/` as each is authored. They do not become new plugins.

## Relationship to other plugins

- **contacts** — CRM surface. LinkedIn-imported `:Person` nodes are visible via `contact-list`, but ingestion does not go through contact tools.
- **memory** — the underlying Cypher-write surface used by the skill (`memory-write`, `memory-update`). The skill is parameterised so all writes carry `source='linkedin'` + `createdByAgent='linkedin-import'` for provenance.
- **librarian specialist** — owns execution. See [admin/IDENTITY.md](../../../platform/templates/agents/admin/IDENTITY.md) delegation clause.
