Skip to content

fix(skills): canonical host-accurate install copy, keep 0.1.3 SSOT frontmatter #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chrisjleal merged 1 commit into from
Oct 5, 2026
Merged

fix(skills): canonical host-accurate install copy, keep 0.1.3 SSOT frontmatter #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 5 additions & 3 deletions plugins/proofable-mcp/skills/proofable-setup/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,19 +15,21 @@ 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?

```bash
proofable setup
```

After Connect, ask:
After sign-in, ask:

```text
Show my Proofable profile and current proofs.
Expand Down
12 changes: 7 additions & 5 deletions plugins/proofable-mcp/skills/proofable-trust-workflow/references/setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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?

Expand All @@ -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

Expand All @@ -44,4 +46,4 @@ proofable mount <agentId> --apply <host>
| **Project** | `proofable mount <agentId> --apply <host>` |
| **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.
8 changes: 5 additions & 3 deletions skills/proofable-setup/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,19 +15,21 @@ 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?

```bash
proofable setup
```

After Connect, ask:
After sign-in, ask:

```text
Show my Proofable profile and current proofs.
Expand Down
12 changes: 7 additions & 5 deletions skills/proofable-trust-workflow/references/setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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?

Expand All @@ -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

Expand All @@ -44,4 +46,4 @@ proofable mount <agentId> --apply <host>
| **Project** | `proofable mount <agentId> --apply <host>` |
| **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.
Loading