---
title: "Native skills + connectors: what improvements are possible"
url: https://mdfy.app/LpLbS250
updated: 2026-05-15T16:43:23.665Z
source: "strategy-note"
---
# Native skills + connectors: what improvements are possible

> Strategy note. What changes when we ship native skills / connectors on Claude, ChatGPT, and Gemini vs. the current URL-paste-only path.

## What changes at the "layer above AI" level

| Today (URL / Chrome ext only) | With native skill / connector |
|---|---|
| User has to *remember* the URL and paste it | "Save this to my mdfy hub" as a single sentence |
| Capture is Chrome-desktop-only | iOS / Android / Claude Desktop all covered |
| Read-only (paste-as-context) | Bidirectional read + write — AI writes docs / updates bundles directly |
| User has to *decide* "I should save this now" | End-of-conversation auto-capture (with consent) |
| Hub search means going to mdfy.app | In-AI autocomplete: `@my-decisions`, `@cross-ai-thesis` |

## Per-platform menu

### 1. ChatGPT — `GPT + Actions`

The most mature surface. OpenAPI schema is a single config file.

- Wrap our public REST API (`/api/docs`, `/api/hub/<slug>/recall`, `/api/bundles`) as actions
- "mdfy memory" GPT — mid-conversation: *"what did I write about my cross-AI thesis?"* → action fires recall → answer cites the doc URL
- End-of-conversation: *"Should I save this?"* → action POSTs `/api/docs`
- Build cost: **near-zero**. OpenAPI spec + GPT instruction text.

### 2. Claude — `Claude Skill` + `Claude Code plugin`

MCP server is already shipped (Desktop / Code / Cursor ✓).

- **Claude.ai web Skill**: trigger `/mdfy` inside any Claude.ai conversation, including iOS Claude app — the surfaces our Chrome extension can't reach.
- **Claude Code hooks package** (`mdfy-hooks` npm): pre-edit / post-edit / pre-commit hooks that auto-update `mdfy.app/d/<repo-knowledge-id>` in real time. Same idea as the GitHub Action shipped this week, but at Claude Code session granularity.
- Future: Anthropic **Computer Use** — experimental, Claude actually drives mdfy.app UI directly.

### 3. Gemini — `Gemini Extension`

The largest potential user pool (Android default AI).

- **Workspace fit**: Gmail → *"save this email as a memo"* → mdfy URL
- **Docs fit**: Google Docs → *"cite from my mdfy hub"* → inline fetch + citation
- Approval path is the heaviest of the three (Google review).

### 4. Cross-cutting (one-time build, three platforms benefit)

- **iOS Share Sheet extension**: Safari / Mail / Slack → "Save to mdfy"
- **macOS QuickLook plugin**: Finder space-bar on a `.md` URL → mdfy-rendered preview
- **VS Code AI side panel deepening**: existing VS Code ext gets Cursor-style inline AI invocation

## Highest-leverage order (priority)

1. **ChatGPT GPT + Actions** — near-zero build cost, largest install base, public REST API already exists. Ship-able in 1-2 days.
2. **Claude Skill (.ai web)** — covers mobile Claude + the desktop Claude app that the Chrome ext can't reach. Available the moment Anthropic Skills API GA's.
3. **Claude Code hooks** — straight at the ICP. `mdfy-hooks` npm package. More real-time than the GitHub Action.
4. **iOS Share Sheet** — mobile capture is currently missing entirely. Apple review 1-2 weeks + Swift code ~1 week.

## Skip / defer (at least until post-v6 launch)

- Gemini Extension — Google approval path is heavy + Android ICP fit is weak
- NotebookLM connector — cannibalisation risk (NotebookLM is itself a hub product)
- OpenAI Apps SDK — too new (stability uncertain)

## The single biggest synergy effect

Shipping ChatGPT GPT + Claude Skill **simultaneously** turns the cross-AI thesis into a demonstrable artifact:

> Save in ChatGPT → search from Claude immediately → 30-second video clip → goes into the Show HN post as evidence.

That's the cross-AI moat made visible at the system level, not just at the URL-paste level.