Tool Connector
Connect work tools (Slack, Jira, GitHub, internal apps) to your agent via local recipes
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · b67acca
Fetched SKILL.md from .cursor/skills/tool-connector/ (repo has no .claude/skills/ copy); frontmatter parses with name+description, and referenced setup.md, add-new-tool.md, setup-python.md all return HTTP 200. Ran the install in a temp HOME — SKILL.md landed correctly at ~/.claude/skills/tool-connector/SKILL.md. Grepped setup.md, add-new-tool.md, SKILL.md, and playwright_sso.py for exfil/curl-pipe-sh/base64/webhook patterns and found none; add-new-tool.md explicitly warns against curl|bash and gates every write action behind user approval. Could not run OUTPUT vs baseline: the core connect-and-verify loop needs the full repo cloned, a Python/Playwright venv, and real credentials against live services (GitHub PAT, Slack SSO, etc.), none of which I could supply.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 5/10
- Docs & honesty 4/5
What Tool Connector does
A setup skill that connects work tools to a coding agent by cloning a recipe repo and running per-tool auth/verify flows locally, storing API tokens and browser-SSO session cookies in a private local .env rather than any cloud middleware. Ships pre-built recipes for ~15 tools (Slack, Confluence, Jira, Linear, GitHub, Datadog, Outlook, and more) plus an add-new-tool path for internal or custom systems. Triggers when the user wants to set up a tool connection, connect an internal or custom-built tool, or add a new integration from scratch.
How to install Tool Connector
git clone --depth 1 https://github.com/ZhixiangLuo/10xProductivity.git /tmp/tool-connector-src
mkdir -p ~/.claude/skills
cp -R /tmp/tool-connector-src/.cursor/skills/tool-connector ~/.claude/skills/tool-connector
# The SKILL is a thin pointer: its body reads setup.md, add-new-tool.md, setup-python.md
# and tool_connections/ from the FULL repo clone at /tmp/tool-connector-src (keep that clone).
# To actually connect a tool you also need: python3>=3.11 + a venv (`pip install -e ".[dev]"`),
# `playwright install chromium`, and a real API token OR browser SSO session per target tool.
# Private runtime state (tokens, verified_connections.md) lives in ~/.10xProductivity (TENX_PRIVATE_DIR).
# Repo ships skills under .cursor/skills/ (not .claude/skills/); the copy above fixes that for Claude Code.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Tool Connector
-
/tool-connectorConnect work tools (Slack, Jira, GitHub, internal apps) to your agent via local recipes
It also activates on plain-language prompts like these:
-
Connect our internal deployment portal to the agent -
Set up a Jira connection for this workspace -
Add PagerDuty as a new tool integration
Frequently asked questions
- Is the Tool Connector skill free?
- Yes. The skill itself is free from ZhixiangLuo/10xProductivity. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Tool Connector work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Works with setup. Fetched SKILL.md from .cursor/skills/tool-connector/ (repo has no .claude/skills/ copy); frontmatter parses with name+description, and referenced setup.md, add-new-tool.md, setup-python.md all return HTTP 200. Ran the install in a temp HOME — SKILL.md landed correctly at ~/.claude/skills/tool-connector/SKILL.md. Grepped setup.md, add-new-tool.md, SKILL.md, and playwright_sso.py for exfil/curl-pipe-sh/base64/webhook patterns and found none; add-new-tool.md explicitly warns against curl|bash and gates every write action behind user approval. Could not run OUTPUT vs baseline: the core connect-and-verify loop needs the full repo cloned, a Python/Playwright venv, and real credentials against live services (GitHub PAT, Slack SSO, etc.), none of which I could supply.
- What is the Tool Connector SkillProof Score?
- 7.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 4/5.
- How do I install Tool Connector?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Tool Connector with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.