Tool Connector Agent Skill
Connect any tool you use at work to your agent — including internal company tools, custom-built systems, deployment portals, incident trackers, internal knowledge bases, HR systems, and commercial tools like Slack, Confluence, Jira, Linear, GitHub, Outlook, Datadog, and PagerDuty. Use when the user wants to set up a tool connection, connect an internal or custom-built tool, or add a new tool integration from scratch.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/ZhixiangLuo/10xProductivity --skill tool-connectorThe instruction itself
7 sections, as written by the authorTool Connector — Connect Any Work Tool to Your Agent
> Requires the repo cloned locally. Check if it's already present (ls setup.md), then read setup.md — that is the full entry point. The sections below summarize the approach for reference.
Full methodology and pre-built recipes: https://github.com/zhixiangluo/10xProductivity
Internal tools are first-class citizens
Internal and custom-built tools are often the most valuable to connect — deployment portals, incident trackers, internal knowledge bases, custom dashboards, HR systems, anything your company built or runs. They follow the exact same setup path as commercial tools and stay private in personal/ (gitignored, never committed).
If a tool has an API or a web UI, it can be connected.
Core principles
- Ask for a URL first, not credentials — a URL the user has open reveals the base URL, workspace, and regional variant without requiring them to know anything about auth
- Run every command yourself — never paste a command and ask the user to run it
- Validate with real output before marking anything done — no illustrative output, no copy-paste from docs
- Zero friction — never require the user to create an OAuth app, register redirect URIs, or configure anything outside of this flow
Routing
| Situation | Action |
|-----------|--------|
| Tool already in verified_connections.md | Reverify — run its verify snippet; if it passes, done |
| Tool has a recipe in personal/{tool}/ | Load it and try; patch in personal/ if it fails |
| Tool has a recipe in tool_connections/{tool}/ | Read that tool's setup.md and follow it |
| Tool not found anywhere | Follow add-new-tool.md to build a recipe from scratch |
Never edit tool_connections/ directly — copy to personal/{tool}/ and patch there.
Auth priority order
| Priority | Method | User friction |
|----------|--------|---------------|
| 1 | API token | ~30s — generate in tool settings |
| 2 | Browser session (SSO, cached) | Run once — session cached for days/weeks |
| 3 | Browser session (per operation) | Playwright on every call — only if no API exists |
| 4 | Username + password | Legacy tools only |
| ✗ | OAuth requiring user to create their own app | Never — too much friction |
Pre-built recipes available
Slack, Confluence, Jira, Linear, GitHub, Microsoft Teams, Outlook, Google Drive, Datadog, Grafana, PagerDuty, Jenkins, Backstage, Bitbucket Server, Artifactory.
Internal and custom tools follow the same path — they stay private in personal/ (gitignored).
Getting started
First, check if you already have the repo:
ls setup.md 2>/dev/null && echo "repo present" || echo "need to clone"
Repo present → if python3 (or Windows py -3) is missing or .venv is not set up for Playwright, read setup-python.md first; then read setup.md — it is the full entry point for tool connections.
Need to clone →
git clone https://github.com/zhixiangluo/10xProductivity.git
cd 10xProductivity
Then read setup.md. It routes to pre-built recipes, your own recipes, and add-new-tool.md for anything new.
Other skills for the same job
different authors, same section of the catalogue
Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting system deployment architecture.
When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment.
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
Plans and executes safe Convex schema and data migrations using the widen-migrate-narrow workflow and the @convex-dev/migrations component. Use this skill when a deployment fails schema validation, existing documents need backfilling, fields need adding or removing or changing type, tables need splitting or merging, or a zero-downtime migration strategy is needed. Also use when the user mentions breaking schema changes, multi-deploy rollouts, or data transformations on existing Convex tables.
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models.
Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping.
How to use it
Take zhixiangluo/tool-connector from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.