# Connect

> Discover hidden relationships between ideas in Obsidian vaults. Find how two topics bridge, trace an idea's evolution, or surface recurring themes. Use when the user senses connections but can't articulate them, or wants to find patterns in their notes.

- **Type:** Skill
- **Install:** `agentstack add skill-markfive-proto-obsidian-brain-vault-connect`
- **Verified:** Pending review
- **Seller:** [markfive-proto](https://agentstack.voostack.com/s/markfive-proto)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [markfive-proto](https://github.com/markfive-proto)
- **Source:** https://github.com/markfive-proto/obsidian-brain-vault/tree/main/skills/connect
- **Website:** https://supermarcus.ai/brain-os

## Install

```sh
agentstack add skill-markfive-proto-obsidian-brain-vault-connect
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Connect Pack — "I sense these relate but can't see how"

Tools for finding relationships, patterns, and evolution of ideas across your vault.

## Commands

### /connect — Find how two ideas bridge

When the user invokes `/connect  `:

1. Search for notes related to each topic:
   - `obs search content "" --json`
   - `obs search content "" --json`
2. Try direct graph path between related notes:
   - `obs links path "" ""` for the most relevant notes
3. If a direct path exists, explain each hop — read each note in the chain and summarize why it connects them
4. If no direct path exists:
   - Find notes that mention both topics: `obs search content "" --json`, then check those results for topicB
   - Look for shared tags: `obs tags all --json` and find tags used by both topic clusters
   - Check for shared backlinks
5. Present the connection:
   - The bridge notes or shared concepts
   - A narrative explanation of how A connects to B through the user's own thinking
   - Suggest creating a new "bridge note" that makes this connection explicit

### /trace — Track an idea's evolution over time

When the user invokes `/trace `:

1. Find all notes mentioning the topic:
   - `obs search content "" --json`
   - `obs search path "" --json`
2. For each match, get the file modification date and read a summary:
   - Sort by date (oldest first)
3. Check backlinks and outgoing links for each note to find the thread
4. Present a timeline:
   ```
   ## Evolution of ""

   ### First appearance — YYYY-MM-DD
   [file]: [what you said then]

   ### Development — YYYY-MM-DD
   [file]: [how the idea evolved]

   ### Current state — YYYY-MM-DD
   [file]: [where you are now]

   ## Trajectory
   [Summary of how thinking shifted]

   ## Open questions
   [Unresolved threads in the evolution]
   ```
5. Use `obs files list --since 1y --sort modified --json` to ensure you're capturing the full timeline

### /drift — Surface what you're circling around

When the user invokes `/drift`:

1. Gather recent activity:
   - `obs files list --since 2w --sort modified --json` — recent files
   - `obs tags all --json` — tag distribution
2. Read the recent files and analyze:
   - What topics come up repeatedly?
   - What tags cluster together?
   - What wikilinks appear across multiple recent notes?
3. Look for patterns:
   - `obs search content "" --json` to see depth
   - `obs links orphans --json` — are orphan notes related to the pattern?
4. Present findings:
   ```
   ## What you've been circling

   ### Theme 1: [name]
   Appeared in: [list of notes]
   Related tags: [tags]
   [Brief description of the pattern]

   ### Theme 2: [name]
   ...

   ## Hidden connections
   [Themes that seem unrelated but share notes/tags]

   ## Suggestion
   [What might be worth writing about or exploring next]
   ```

## Tips

- Always use actual vault data. Never fabricate connections.
- When reading notes for summaries, focus on the first few paragraphs — they usually contain the thesis.
- The user's wikilinks are intentional connections. Treat them as strong signals.
- For /drift, 2 weeks is the default window. The user can say "/drift last month" and you should use `--since 4w`.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [markfive-proto](https://github.com/markfive-proto)
- **Source:** [markfive-proto/obsidian-brain-vault](https://github.com/markfive-proto/obsidian-brain-vault)
- **License:** MIT
- **Homepage:** https://supermarcus.ai/brain-os

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: flagged — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-markfive-proto-obsidian-brain-vault-connect
- Seller: https://agentstack.voostack.com/s/markfive-proto
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.