Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,16 @@
"author": {
"name": "Composio"
}
},
{
"name": "refyner",
"source": "./refyner",
"description": "Companion for your Refyner second brain — research grounded in what you've saved, plus propose→confirm capture. Bundles the Refyner MCP (OAuth). Free account at refyner.me.",
"category": "integrations",
"tags": ["second-brain", "knowledge", "research", "mcp", "notes", "memory"],
"author": {
"name": "Dragos Rebegea"
}
}
]
}
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,7 @@ Claude Plugins are extensions that enhance Claude Code with custom slash command
### Integrations

- [connect-apps](./connect-apps) - Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
- [refyner](./refyner) - Research grounded in your Refyner second brain, with propose→confirm capture. Bundles the Refyner MCP.
- [kaggle-skill](https://github.com/shepsci/kaggle-skill) - Complete Kaggle integration — account setup, competition reports, dataset/model downloads, notebook execution, submissions, and badge collection.

### Frontend & Design
Expand Down
19 changes: 19 additions & 0 deletions refyner/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{
"name": "refyner",
"description": "Companion for your Refyner second brain: research grounded in your saved knowledge, plus propose→confirm capture. Requires a free Refyner account (https://refyner.me).",
"version": "0.1.0",
"author": {
"name": "Dragos Rebegea",
"email": "dragos.rebegea@buidly.com"
},
"license": "MIT",
"homepage": "https://refyner.me",
"repository": "https://github.com/buidly/refyner-claude",
"keywords": ["refyner", "second-brain", "mcp", "research", "notes", "knowledge"],
"mcpServers": {
"refyner": {
"type": "http",
"url": "https://refyner.me/api/mcp"
}
}
}
53 changes: 53 additions & 0 deletions refyner/skills/second-brain/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
name: second-brain
description: Use when the user researches a topic that could draw on their own saved knowledge, or wants to recall or save something in their Refyner second brain — "research X using my second brain", "what have I saved about Y", "save this to my second brain", "add this to Refyner", "check my vault". Requires the bundled Refyner MCP (connect once via /mcp).
---

# Refyner Second Brain

Ground research in the user's own saved knowledge, and capture new insights with
their confirmation — using the Refyner MCP tools bundled with this plugin.

## Prerequisites

This skill needs the `refyner` MCP server (bundled with this plugin) connected
and authenticated. If the `search_vault` tool is not available:

1. Tell the user to run `/mcp`, select **refyner**, and choose **Authenticate**
(a one-time browser OAuth login).
2. A free Refyner account is required — https://refyner.me.

Do not fabricate vault contents. If the tools are unavailable, say so and stop.

## Workflow

### Researching a topic → check the second brain first

1. Call `search_vault(query)` with the user's topic BEFORE answering. This
returns snippets of what they've already saved (articles, transcripts, notes).
2. For the most relevant hits, call `get_vault_entry(id)` to read the full text.
3. Combine that with your own web search, then answer — clearly distinguishing
**what came from the user's second brain** vs. what came from the web.

### Saving something → always propose, never auto-save

1. When something is worth keeping, call `propose_to_vault(...)`. This does NOT
write — it returns a normalized preview plus duplicate signals
(`duplicate_status`, `exact_match`, `similar_existing`).
2. Show the user the proposal, including any duplicates. Let them decide.
3. Only after the user confirms, call `confirm_vault_capture(...)` with the
`normalized` fields from the proposal. Never call `confirm_vault_capture`
without an explicit confirmation.

### Reference

The `refyner://vault-guide` MCP resource documents this same flow — consult it
if unsure.

## Examples

- "Research context engineering — check my second brain too." → `search_vault` →
`get_vault_entry` on top hits → web search → synthesized answer with sources.
- "Save this thread to my second brain." → `propose_to_vault` → show preview →
`confirm_vault_capture` after the user says yes.
- "What have I saved about pricing?" → `search_vault("pricing")` → summarize hits.