X Use Setup
ihuzaifashoukat/x-use
Zero-knowledge onboarding for x-use that verifies the install, registers the MCP server, then interviews the user to configure their first X account (cookies, niche, keywords, persona).
Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.
$ npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills bind-mcp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bind-protocol-mcp .claude/skills/bind-mcp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bind-mcp" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/bind-protocol-mcp into .claude/skills/bind-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-mcp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/bind-protocol-mcpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills bind-mcp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/bind-protocol-mcp .agents/skills/bind-mcp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bind-mcp" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/bind-protocol-mcp into .agents/skills/bind-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-mcp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills bind-mcp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/bind-protocol-mcp .cursor/skills/bind-mcp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bind-mcp" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/bind-protocol-mcp into .cursor/skills/bind-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-mcp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/bind-protocol-mcp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills bind-mcp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/bind-protocol-mcp .gemini/skills/bind-mcp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bind-mcp" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/bind-protocol-mcp into .gemini/skills/bind-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-mcp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills bind-mcpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/bind-protocol-mcp .github/skills/bind-mcp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bind-mcp" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/bind-protocol-mcp into .github/skills/bind-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-mcp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills bind-mcp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/bind-protocol-mcp .opencode/skills/bind-mcp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bind-mcp" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/bind-protocol-mcp into .opencode/skills/bind-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bind-mcp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
bind-mcpBind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.
Bind MCP is an agent skill from LeoYeAI/openclaw-master-skills. Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.
Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
It sits in Agent Workflows, covering MCP servers and Cryptography. It works with Model Context Protocol. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
api.bindprotocol.xyzAlso links to:
dashboard.bindprotocol.xyzFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
BIND_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Bind MCP loads about 4.5k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 1,574 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,574 words, ~4,508 tokens.
.claude/skills/bind-mcp/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You have access to the Bind Protocol MCP server. This document teaches you how to use it.
npx handles package installation automatically)idbr_agent_...) — Required for API-backed tools. Regular API keys (idbr_) are not supported for MCP.Bind uses agent keys for MCP authentication. Agent keys are scoped API keys that let org admins control exactly which tools are available, set daily rate limits, and get audit logs.
| Key type | Format | MCP supported |
|---|---|---|
| Agent key | idbr_agent_<keyId>_<secret> | Yes — required for API-backed tools |
| Regular API key | idbr_<keyId>_<secret> | No — rejected by MCP server |
To create an agent key:
Add the server to your MCP client configuration. The exact file depends on your tool:
| Tool | Config file |
|---|---|
| Claude Code | .mcp.json in your project root, or ~/.claude/claude_desktop_config.json |
| Claude Desktop | Settings > Developer > Edit Config |
| Cursor | .cursor/mcp.json in your project root |
| Windsurf | MCP settings |
Configuration JSON:
{
"mcpServers": {
"bind": {
"command": "npx",
"args": ["@bind-protocol/mcp-server"],
"env": {
"BIND_API_KEY": "${BIND_API_KEY}"
}
}
}
}The BIND_API_KEY environment variable must be set in your shell to your agent key before launching your AI tool. Never hardcode the key directly in config files — always use environment variable references to avoid accidental credential leakage in shared configs or repositories.
Environment variables:
| Variable | Required | Default | Description |
|---|---|---|---|
BIND_API_KEY | For API-backed tools | — | Agent key (idbr_agent_...). Without this, only local tools are available. |
BIND_API_URL | No | https://api.bindprotocol.xyz | Base URL for API calls |
BIND_RECEIPTS_PATH | No | ~/.bind/receipts | Directory for receipt chain data |
LOG_LEVEL | No | info | Logging verbosity (debug, info, warn, error) |
If you do not have bind tools available, prompt the user to complete the setup above. You can test connectivity by calling bind_whoami — if it returns org info, the agent key is authenticated. Without a BIND_API_KEY, only local tools (parse, verify, hash) are available.
The server runs locally via npx and communicates with your AI tool over stdio. It provides both local tools (always available) and API-backed tools (require an agent key). You just call the tool by name — routing is handled automatically.
| Tool type | Auth | Purpose |
|---|---|---|
| Local tools | None | Parse, verify, and hash VC-JWTs on-device |
| API-backed tools | Agent key via BIND_API_KEY | Policies, proofs, issuers, revocation, and more |
This is critical for understanding the privacy model:
Local tools (credential data NEVER leaves the machine):
bind_parse_credential — Decodes the JWT entirely on your machinebind_verify_credential — Fetches the issuer's public JWKS from the Bind API (public keys only), then verifies the signature locally. The credential itself is never sent.bind_hash_credential — Computes a SHA-256 hash locally. Only the irreversible hash is used for revocation checks.API-backed tools (send requests to api.bindprotocol.xyz):
bind_check_revocation — Sends only the credential hash (not the credential). The hash is not reversible.bind_resolve_issuer — Fetches public keys for an org. No credential data involved.bind_explain_policy, bind_list_policies, bind_list_circuits — Read-only public metadata. No credential data involved.bind_submit_prove_job — Sends circuit inputs to the Bind proving service. These are the raw values being proven (e.g., income amount, mileage count).bind_issue_credential — Requests the Bind API to sign and issue a VC-JWT from a completed proof.bind_create_policy, bind_validate_policy — Sends policy spec JSON to Bind for validation/storage.bind_share_proof — Shares a proof record with a verifier org via the Bind API.In short: Raw credentials are local-only. Hashes, policy specs, proof inputs, and metadata go to the API.
| Tool | What it does |
|---|---|
bind_parse_credential | Decode a VC-JWT into header + payload + signature without verification |
bind_verify_credential | Full verification: parse, fetch issuer JWKS, verify ES256 signature, check expiration. Does NOT check revocation. |
bind_hash_credential | SHA-256 hash a VC-JWT. Use the hash with bind_check_revocation. |
BIND_API_KEY)Discovery & Inspection
| Tool | What it does |
|---|---|
bind_resolve_issuer | Fetch an org's public signing keys (JWKS) by org ID |
bind_explain_policy | Get the public spec for a policy by policy ID |
bind_check_revocation | Check if a credential is revoked by its hash (hash only — not the credential) |
bind_list_policies | List available policies (supports limit/offset pagination) |
bind_list_circuits | List available ZK circuits |
Proof Generation & Credential Issuance
| Tool | What it does |
|---|---|
bind_submit_prove_job | Submit a ZK proof generation job with circuit ID and inputs |
bind_get_prove_job | Poll a prove job's status by job ID |
bind_list_prove_jobs | List prove jobs, optionally filtered by status |
bind_issue_credential | Issue a verifiable credential from a completed prove job |
bind_share_proof | Share a completed proof with a verifier org |
bind_list_shared_proofs | List proofs shared with/by your org |
Policy Authoring
| Tool | What it does |
|---|---|
bind_whoami | Get authenticated org info, tier, policy limits, and agent key permissions |
bind_validate_policy | Dry-run validation of a policy spec (catches errors before creation) |
bind_create_policy | Create a new verification policy |
bind_generate_circuit | Trigger ZK circuit compilation for a saved policy |
bind_get_circuit_status | Poll circuit compilation job status |
When to use: A user gives you a VC-JWT string (starts with eyJ...) and wants to know if it's valid.
Steps:
bind_parse_credential — Decode the JWT to inspect claimsbind_verify_credential — Verify signature and expirationbind_hash_credential — Compute SHA-256 hashbind_check_revocation — Send the hash (not the credential) to check revocationSteps 1 and 2 can be combined (verify includes parsing), but parsing first lets you show the user what the credential contains before the full check. Steps 1–3 run locally; step 4 sends only the hash to the API.
Important: bind_verify_credential does NOT check revocation. You must always follow up with hash + revocation check for a complete verification.
parse → verify → hash → check_revocationWhen to use: A user wants to know about an organization's keys or policies.
bind_resolve_issuer(orgId) — Fetch their JWKSbind_list_policies or bind_explain_policy — Look up their policiesWhen to use: A user wants to define a new verification policy.
Steps:
bind_whoami — Check org name, tier, and limits. You need the org name for the namespace.bind_validate_policy — Dry-run to catch errors before creationbind_create_policy — Save the policybind_generate_circuit — Queue ZK circuit compilationbind_get_circuit_status — Poll until status is completed or failedCritical rules:
metadata.namespace MUST start with your org's slugified name (from bind_whoami). The namespaces bind and system are reserved.id MUST start with the namespace (e.g., acme.finance.creditCheck for namespace acme).encoding block mapping values to numbers (ZK circuits only work with numbers).When to use: A user wants to generate a ZK proof and get a verifiable credential.
bind_list_policies or bind_explain_policy — Find the right policy/circuitbind_submit_prove_job(circuitId, inputs) — Submit the proof jobbind_get_prove_job(jobId) — Poll until status is completedbind_issue_credential(proveJobId) — Issue the VC from the completed proofbind_share_proof(proveJobId, verifierOrgId) — Share with a verifierA policy is a JSON object with this structure. All fields shown are required unless marked optional.
{
"id": "<namespace>.<category>.<name>",
"version": "0.1.0",
"metadata": {
"title": "Human-readable title",
"description": "What this policy verifies",
"category": "finance|mobility|identity|demo",
"namespace": "your-org-name"
},
"subject": {
"type": "individual|organization|vehicle|device",
"identifier": "wallet_address|did|vin|vehicleTokenId"
},
"inputs": [
{
"id": "input_name",
"source": { "kind": "static|api", "api": "optional_api_name" },
"signal": "input_name",
"valueType": "number|boolean|string",
"unit": "USD|count|months",
"time": { "mode": "point|range|relative", "lookback": "30d" },
"aggregation": { "op": "latest|sum|mean|count" },
"encoding": {
"type": "enum",
"values": { "label1": 1, "label2": 2 }
}
}
],
"rules": [
{
"id": "rule_name",
"description": "Human-readable description",
"assert": { /* expression — see below */ },
"severity": "fail|warn|info"
}
],
"evaluation": {
"kind": "PASS_FAIL|SCORE",
"scoreRange": { "min": 0, "max": 100 },
"baseline": 50,
"contributions": [
{ "ruleId": "rule_name", "points": 30, "whenPasses": true }
]
},
"outputs": [
{
"name": "output_name",
"type": "boolean|enum|number",
"derive": {
"kind": "PASS_FAIL|SCORE|BAND|CONST",
"from": "SCORE|input_id",
"bands": [
{ "label": "LOW", "minInclusive": 0, "maxExclusive": 40 },
{ "label": "HIGH", "minInclusive": 40, "maxExclusive": 101 }
],
"value": 42
},
"disclosed": true
}
],
"validity": { "ttl": "P30D" },
"disclosure": {
"default": "SELECTIVE",
"exposeClaims": ["output_name"]
},
"proving": {
"circuitId": "<namespace>.<name>.v<version>",
"inputTypes": { "input_name": "u32" },
"outputType": "u8"
}
}rules[].assert)| Type | Shape | Example |
|---|---|---|
ref | { "type": "ref", "inputId": "<input_id>" } | Reference an input value |
const | { "type": "const", "value": <number|boolean> } | Literal number or boolean (never strings) |
cmp | { "type": "cmp", "cmp": ">=|<=|>|<|==|!=", "left": <expr>, "right": <expr> } | Comparison |
op | { "type": "op", "op": "+|-|*|/", "args": [<expr>, ...] } | Arithmetic |
and | { "type": "and", "args": [<expr>, ...] } | Logical AND |
or | { "type": "or", "args": [<expr>, ...] } | Logical OR |
not | { "type": "not", "arg": <expr> } | Logical NOT |
Field name gotchas:
"inputId" in ref expressions, NOT "path""cmp" for the comparison operator, NOT "operator""args" for operand lists, NOT "children""arg" (singular) for not, NOT "expr"const values must be numbers or booleans, never stringsPASS_FAIL: All severity: "fail" rules must pass. No scoring.
SCORE: Starts at baseline, adds/subtracts points from rule contributions.
{
"kind": "SCORE",
"scoreRange": { "min": 0, "max": 100 },
"baseline": 50,
"contributions": [
{ "ruleId": "has_high_income", "points": 25, "whenPasses": true },
{ "ruleId": "has_delinquencies", "points": -20, "whenPasses": true }
]
}| Kind | Use for | Required fields |
|---|---|---|
PASS_FAIL | Boolean pass/fail from evaluation | None |
SCORE | Raw numeric score | from: "SCORE" |
BAND | Map score to labeled bands | from: "SCORE", bands array |
CONST | Fixed value | value |
ZK circuits only work with numbers. When a policy uses string inputs (employer names, country codes, etc.), you MUST include an encoding block:
{
"id": "employer",
"source": { "kind": "static" },
"signal": "employer",
"valueType": "string",
"encoding": {
"type": "enum",
"values": {
"Acme Corp": 1,
"Globex Inc": 2,
"Initech": 3
}
}
}The proving section maps inputs to Noir types for the ZK circuit:
{
"proving": {
"circuitId": "acme.safe_driver.v0_1_0",
"inputTypes": {
"miles_driven": "u32",
"hard_brake_pct": "u8",
"is_commercial": "bool"
},
"outputType": "u8"
}
}Available Noir types: u8, u16, u32, u64, i8, i16, i32, i64, bool, Field
Policy authoring is gated by organization tier. Always call bind_whoami first to check limits.
| Tier | Can Create Policies | Notes |
|---|---|---|
| Basic | No | Verification only |
| Premium | Yes | Limited inputs/rules/outputs |
| Scale | Yes | Expanded limits, can create extractors |
| Enterprise | Yes | Unlimited |
| Verifier | No | Cannot create proofs or policies |
| Error | Cause | Fix |
|---|---|---|
NAMESPACE_MISMATCH | Policy namespace doesn't match your org | Use your org name from bind_whoami as the namespace prefix |
TIER_LIMIT_EXCEEDED | Your tier doesn't allow this operation | Check bind_whoami for limits |
INVALID_EXPRESSION | Malformed rule assertion | Check expression field names (inputId, cmp, args, arg) |
MISSING_ENCODING | String input without encoding | Add encoding.type: "enum" with values map |
CIRCUIT_COMPILATION_FAILED | Circuit couldn't compile | Check the error in bind_get_circuit_status, fix the policy, recreate, and regenerate |
Here is a complete example of creating a credit score policy for org acme:
{
"id": "acme.finance.credit-check",
"version": "0.1.0",
"metadata": {
"title": "Credit Eligibility Check",
"description": "Evaluates creditworthiness based on income and debt ratio",
"category": "finance",
"namespace": "acme"
},
"subject": {
"type": "individual",
"identifier": "wallet_address"
},
"inputs": [
{
"id": "annual_income",
"source": { "kind": "static" },
"signal": "annual_income",
"valueType": "number",
"unit": "USD"
},
{
"id": "debt_ratio",
"source": { "kind": "static" },
"signal": "debt_ratio",
"valueType": "number",
"unit": "percent"
}
],
"rules": [
{
"id": "min_income",
"description": "Annual income must be at least $30,000",
"assert": {
"type": "cmp",
"cmp": ">=",
"left": { "type": "ref", "inputId": "annual_income" },
"right": { "type": "const", "value": 30000 }
},
"severity": "fail"
},
{
"id": "max_debt_ratio",
"description": "Debt-to-income ratio must be under 40%",
"assert": {
"type": "cmp",
"cmp": "<",
"left": { "type": "ref", "inputId": "debt_ratio" },
"right": { "type": "const", "value": 40 }
},
"severity": "fail"
}
],
"evaluation": {
"kind": "PASS_FAIL"
},
"outputs": [
{
"name": "eligible",
"type": "boolean",
"derive": { "kind": "PASS_FAIL" },
"disclosed": true
}
],
"validity": { "ttl": "P30D" },
"disclosure": {
"default": "SELECTIVE",
"exposeClaims": ["eligible"]
},
"proving": {
"circuitId": "acme.credit_check.v0_1_0",
"inputTypes": {
"annual_income": "u32",
"debt_ratio": "u8"
},
"outputType": "u8"
}
}Agent workflow for this:
bind_whoami — Confirm org is acme and tier allows policy creationbind_validate_policy(policy) — Dry-run validationbind_create_policy(policy) — Create the policybind_generate_circuit("acme.finance.credit-check") — Compile the circuitbind_get_circuit_status(jobId) — Poll until complete© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/bind-protocol-mcp of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Bind MCP next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bind MCP this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.5k | Automated safety check: Pass | MIT | |
| X Use Setupihuzaifashoukat/x-use | 171 | — | ~731 | Automated safety check: Warn | MIT | |
| Protect MCP Setupwshobson/agents | 40k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Webcrypt MCPputervision/state-memory-mcp | 111 | — | ~847 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT |
ihuzaifashoukat/x-use
Zero-knowledge onboarding for x-use that verifies the install, registers the MCP server, then interviews the user to configure their first X account (cookies, niche, keywords, persona).
wshobson/agents
Configure Cedar policy enforcement and Ed25519 signed receipts for Claude Code tool calls.
putervision/state-memory-mcp
Teaches the agent to use the WebCrypt MCP server for AES-256-GCM symmetric encryption, RSA-4096 hybrid encryption, key generation, digital signatures, hashing, and post-quantum cryptography.
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Works with
Categories
Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation. Bind MCP is an agent skill from LeoYeAI/openclaw-master-skills. Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.
Bind MCP fits situations like: tasks that involve MCP servers; tasks that involve Cryptography.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a claude-code`. Or copy the skill folder (skills/bind-protocol-mcp in LeoYeAI/openclaw-master-skills) into .claude/skills/bind-mcp in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a codex`. Or copy the skill folder (skills/bind-protocol-mcp in LeoYeAI/openclaw-master-skills) into .agents/skills/bind-mcp in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bind-mcp, .gemini/skills/bind-mcp, .github/skills/bind-mcp and .opencode/skills/bind-mcp in your project.
Going by SKILL.md and its folder, Bind MCP needs credentials named BIND_API_KEY. Our summary lists: Node.js; A credential in BIND_API_KEY.
SKILL.md names 2 domains. In commands or code: api.bindprotocol.xyz; the agent is likely to contact it when it follows the instructions. As links in the text: dashboard.bindprotocol.xyz. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Bind MCP is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Bind MCP: X Use Setup (ihuzaifashoukat/x-use, 171 stars), Protect MCP Setup (wshobson/agents, 40k stars), Webcrypt MCP (putervision/state-memory-mcp, 111 stars) and MCP Server Builder (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.