From 991eb503ad52d65bf23efa4a63b6a7e750596fe8 Mon Sep 17 00:00:00 2001 From: Proofable Date: Mon, 5 Oct 2026 11:27:20 -0500 Subject: [PATCH] fix(skills): canonical host-accurate install copy, keep 0.1.3 SSOT frontmatter --- .../proofable-mcp/skills/proofable-setup/SKILL.md | 8 +++++--- .../proofable-trust-workflow/references/setup.md | 12 +++++++----- skills/proofable-setup/SKILL.md | 8 +++++--- skills/proofable-trust-workflow/references/setup.md | 12 +++++++----- 4 files changed, 24 insertions(+), 16 deletions(-) diff --git a/plugins/proofable-mcp/skills/proofable-setup/SKILL.md b/plugins/proofable-mcp/skills/proofable-setup/SKILL.md index c115b3e..ec78c63 100644 --- a/plugins/proofable-mcp/skills/proofable-setup/SKILL.md +++ b/plugins/proofable-mcp/skills/proofable-setup/SKILL.md @@ -15,11 +15,13 @@ Give AI agents verified identity, scoped permissions, and reusable proof through Add Proofable to any app, chat, or agent that speaks MCP. Cursor, Claude, Codex, and VS Code are shortcuts. -Install Proofable, then click **Connect**: +Add Proofable, then finish sign-in in your client: `https://mcp.proofable.me/mcp` -If the host offers the Proofable plugin, install it and click **Connect** instead of adding the URL by hand. Do not add a second `proofable` entry. +There is no universal Connect button. Cursor, VS Code, Claude Code, and Codex each run their own sign-in after the server is registered; only Claude connectors and Devin show a control called Connect. + +If the client offers the Proofable plugin, install that instead of adding the URL by hand. It ships these skills, and in Cursor it registers the server too. Do not add a second `proofable` entry. Have the CLI? @@ -27,7 +29,7 @@ Have the CLI? proofable setup ``` -After Connect, ask: +After sign-in, ask: ```text Show my Proofable profile and current proofs. diff --git a/plugins/proofable-mcp/skills/proofable-trust-workflow/references/setup.md b/plugins/proofable-mcp/skills/proofable-trust-workflow/references/setup.md index 81a84e5..497bd47 100644 --- a/plugins/proofable-mcp/skills/proofable-trust-workflow/references/setup.md +++ b/plugins/proofable-mcp/skills/proofable-trust-workflow/references/setup.md @@ -4,13 +4,15 @@ Load this file only when the user needs install, sign-in, access keys, or projec ## Install -Install Proofable on this host, then click **Connect**: +Install Proofable on this host, then finish sign-in in the client itself: `https://mcp.proofable.me/mcp` -If the host already has a Proofable plugin, use that Connect path. Do not also write a second `proofable` entry. +There is no universal Connect button. Cursor, VS Code, Claude Code, and Codex each run their own sign-in once the server is registered; only Claude connectors and Devin render a control named Connect. -If Connect is missing, use the host’s own MCP login after the URL is registered. +If the host already has a Proofable plugin, use the plugin path. Do not also write a second `proofable` entry. + +If the client shows no sign-in, use its own MCP login command after the URL is registered. Have the CLI? @@ -28,7 +30,7 @@ Create access keys under **Account → Access keys** on [proofable.me](https://p Hosted MCP: **`https://mcp.proofable.me/mcp`** -After Connect, call `proofable_context`. To sell: set payouts at https://proofable.me/profile?tab=credits, then create a listing at https://proofable.me/profile/portals/new. Full page: https://docs.proofable.me/mcp/setup +After sign-in, call `proofable_context`. To sell: set payouts at https://proofable.me/profile?tab=credits, then create a listing at https://proofable.me/profile/portals/new. Full page: https://docs.proofable.me/mcp/setup ## Connect an agent to a project @@ -44,4 +46,4 @@ proofable mount --apply | **Project** | `proofable mount --apply ` | | **Session** | `proofable_context` → `proofable_agent_mount` when acting as the agent | -Use `proofable mount` only when acting as a registered profile agent. For proofs and secrets, Connect plus `proofable_context` is enough. +Use `proofable mount` only when acting as a registered profile agent. For proofs and secrets, a completed sign-in plus `proofable_context` is enough. diff --git a/skills/proofable-setup/SKILL.md b/skills/proofable-setup/SKILL.md index c115b3e..ec78c63 100644 --- a/skills/proofable-setup/SKILL.md +++ b/skills/proofable-setup/SKILL.md @@ -15,11 +15,13 @@ Give AI agents verified identity, scoped permissions, and reusable proof through Add Proofable to any app, chat, or agent that speaks MCP. Cursor, Claude, Codex, and VS Code are shortcuts. -Install Proofable, then click **Connect**: +Add Proofable, then finish sign-in in your client: `https://mcp.proofable.me/mcp` -If the host offers the Proofable plugin, install it and click **Connect** instead of adding the URL by hand. Do not add a second `proofable` entry. +There is no universal Connect button. Cursor, VS Code, Claude Code, and Codex each run their own sign-in after the server is registered; only Claude connectors and Devin show a control called Connect. + +If the client offers the Proofable plugin, install that instead of adding the URL by hand. It ships these skills, and in Cursor it registers the server too. Do not add a second `proofable` entry. Have the CLI? @@ -27,7 +29,7 @@ Have the CLI? proofable setup ``` -After Connect, ask: +After sign-in, ask: ```text Show my Proofable profile and current proofs. diff --git a/skills/proofable-trust-workflow/references/setup.md b/skills/proofable-trust-workflow/references/setup.md index 81a84e5..497bd47 100644 --- a/skills/proofable-trust-workflow/references/setup.md +++ b/skills/proofable-trust-workflow/references/setup.md @@ -4,13 +4,15 @@ Load this file only when the user needs install, sign-in, access keys, or projec ## Install -Install Proofable on this host, then click **Connect**: +Install Proofable on this host, then finish sign-in in the client itself: `https://mcp.proofable.me/mcp` -If the host already has a Proofable plugin, use that Connect path. Do not also write a second `proofable` entry. +There is no universal Connect button. Cursor, VS Code, Claude Code, and Codex each run their own sign-in once the server is registered; only Claude connectors and Devin render a control named Connect. -If Connect is missing, use the host’s own MCP login after the URL is registered. +If the host already has a Proofable plugin, use the plugin path. Do not also write a second `proofable` entry. + +If the client shows no sign-in, use its own MCP login command after the URL is registered. Have the CLI? @@ -28,7 +30,7 @@ Create access keys under **Account → Access keys** on [proofable.me](https://p Hosted MCP: **`https://mcp.proofable.me/mcp`** -After Connect, call `proofable_context`. To sell: set payouts at https://proofable.me/profile?tab=credits, then create a listing at https://proofable.me/profile/portals/new. Full page: https://docs.proofable.me/mcp/setup +After sign-in, call `proofable_context`. To sell: set payouts at https://proofable.me/profile?tab=credits, then create a listing at https://proofable.me/profile/portals/new. Full page: https://docs.proofable.me/mcp/setup ## Connect an agent to a project @@ -44,4 +46,4 @@ proofable mount --apply | **Project** | `proofable mount --apply ` | | **Session** | `proofable_context` → `proofable_agent_mount` when acting as the agent | -Use `proofable mount` only when acting as a registered profile agent. For proofs and secrets, Connect plus `proofable_context` is enough. +Use `proofable mount` only when acting as a registered profile agent. For proofs and secrets, a completed sign-in plus `proofable_context` is enough.