Skip to content

Sync SDK skills with MCP verification flow #5

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 11, 2026
Merged

Sync SDK skills with MCP verification flow #5

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
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@proofable/sdk",
"version": "0.1.5",
"version": "0.1.6",

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add the 0.1.6 changelog entry before publishing

When this version is tagged and published, CHANGELOG.md will still jump from Unreleased directly to 0.1.5, so users upgrading to 0.1.6 will have no record of the newly documented external-signer verification flow. This is a user-facing packaged-skill change, and the repository's PR template requires such changes to be recorded under Unreleased; add and link the 0.1.6 release entry as part of this version bump.

Useful? React with 👍 / 👎.

"description": "SDK and CLI for verification gates, reusable proof, and agent permissions.",
"bin": {
"proofable": "cli/proofable.mjs"
Expand Down
2 changes: 1 addition & 1 deletion skills/proofable-integrate/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ license: Apache-2.0
compatibility: Requires @proofable/sdk (npm).
metadata:
author: Proofable
version: "0.1.6"
version: "0.1.7"
homepage: https://docs.proofable.me/use-cases/gate-access
---

Expand Down
2 changes: 1 addition & 1 deletion skills/proofable-setup/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ license: Apache-2.0
compatibility: Requires an MCP-capable client that can register a remote HTTP server.
metadata:
author: Proofable
version: "0.1.6"
version: "0.1.7"
homepage: https://docs.proofable.me/mcp/setup
---

Expand Down
4 changes: 2 additions & 2 deletions skills/proofable-trust-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ license: Apache-2.0
compatibility: Requires a client that supports remote HTTP MCP servers and hosted OAuth.
metadata:
author: Proofable
version: "0.1.6"
version: "0.1.7"
homepage: https://docs.proofable.me/mcp/setup
---

Expand All @@ -25,7 +25,7 @@ Use this before an assistant runs sensitive tools or takes another verification-

1. **`proofable_context`** once per session. Prefer signed-in profile context; omit wallet fields on check/verify tools.
2. **Profile agent:** **`proofable_agent_mount`** (or `proofable mount <agentId> --apply <host>`) for identity, permissions, skills, and context.
3. **Trust before action:** use **`proofable_verify_or_guide`** directly. It reuses qualifying proofs or returns the next secure step. Use **`proofable_proofs_check`** only for an explicit yes/no eligibility, gate, or access question; never use it for memory, context, or content retrieval. When signed in, ownership checks continue with **`proofable_verify`**. Share a browser link only when a tool returns one.
3. **Trust before action:** use **`proofable_verify_or_guide`** directly. It reuses qualifying proofs or returns the next secure step. Use **`proofable_proofs_check`** only for an explicit yes/no eligibility, gate, or access question; never use it for memory, context, or content retrieval. When signed in, ownership checks continue with **`proofable_verify`**. For another signer, prepare with **`proofable_verify_prepare`** and submit with **`proofable_verify_submit`**. Share a browser link only when a tool returns one.
4. **Agent:** **`proofable_agent_link`**. If missing, **`proofable_agent_create`** (a dedicated account needs a key you create and hold; pass only its public address). Then **`proofable_agent_mount`**.
5. **Proofs and context:** use the `proofable_context` context index first, then **`proofable_proofs_get`** with a known proof ID and `include=content` for an exact body.
6. **Vault:** **`proofable_secret_list`** / **`proofable_secret_create`** / **`proofable_secret_revoke`**.
Expand Down
Loading