Sentry Alert Tuner
LeoYeAI/openclaw-master-skills
Reduce Sentry alert fatigue by surgically tuning issue grouping, fingerprint rules, severity mapping, sample rates, before-send filters, sourcemap pipelines, and release-health gates.
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…
Install Tool Connector
$ npx skills add ZhixiangLuo/10xProductivity --skill tool-connector -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZhixiangLuo/10xProductivity tool-connector --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/ZhixiangLuo/10xProductivity.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/tool-connector .claude/skills/tool-connector && 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 "tool-connector" agent skill from https://github.com/ZhixiangLuo/10xProductivity/tree/main/.cursor/skills/tool-connector into .claude/skills/tool-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-connector", 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/ZhixiangLuo/10xProductivity/tree/main/.cursor/skills/tool-connectorType 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 ZhixiangLuo/10xProductivity --skill tool-connector -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZhixiangLuo/10xProductivity tool-connector --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZhixiangLuo/10xProductivity.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/tool-connector .agents/skills/tool-connector && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tool-connector" agent skill from https://github.com/ZhixiangLuo/10xProductivity/tree/main/.cursor/skills/tool-connector into .agents/skills/tool-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-connector", 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 ZhixiangLuo/10xProductivity --skill tool-connector -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZhixiangLuo/10xProductivity tool-connector --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZhixiangLuo/10xProductivity.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/tool-connector .cursor/skills/tool-connector && 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 "tool-connector" agent skill from https://github.com/ZhixiangLuo/10xProductivity/tree/main/.cursor/skills/tool-connector into .cursor/skills/tool-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-connector", 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/ZhixiangLuo/10xProductivity.git --path .cursor/skills/tool-connector--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 ZhixiangLuo/10xProductivity --skill tool-connector -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZhixiangLuo/10xProductivity tool-connector --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZhixiangLuo/10xProductivity.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/tool-connector .gemini/skills/tool-connector && 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 "tool-connector" agent skill from https://github.com/ZhixiangLuo/10xProductivity/tree/main/.cursor/skills/tool-connector into .gemini/skills/tool-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-connector", 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 ZhixiangLuo/10xProductivity tool-connectorInstalls 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 ZhixiangLuo/10xProductivity --skill tool-connector -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ZhixiangLuo/10xProductivity.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/tool-connector .github/skills/tool-connector && 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 "tool-connector" agent skill from https://github.com/ZhixiangLuo/10xProductivity/tree/main/.cursor/skills/tool-connector into .github/skills/tool-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-connector", 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 ZhixiangLuo/10xProductivity --skill tool-connector -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ZhixiangLuo/10xProductivity tool-connector --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZhixiangLuo/10xProductivity.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/tool-connector .opencode/skills/tool-connector && 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 "tool-connector" agent skill from https://github.com/ZhixiangLuo/10xProductivity/tree/main/.cursor/skills/tool-connector into .opencode/skills/tool-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-connector", 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.
Facts
- Skill name
tool-connector- GitHub stars
- 479
- Token cost
- ~925 tokens
- SKILL.md length
- 413 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- The user wants to set up a tool connection
- SKILL.md covers Internal tools are first-class…, Core principles, Routing and Auth priority order, plus 2 more sections
- Calls git
- Connect an internal
What it does
Tool Connector is an agent skill from ZhixiangLuo/10xProductivity. 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.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Monitoring and alerting. It works with GitHub, Confluence, Jira and Slack. The repository describes itself as: Personal AI assistant for work inside corporate constraints, built on coding agents and the tools, sessions, and permissions you already have. The licence is MIT.
When your agent uses it
- The user wants to set up a tool connection
- Connect an internal
- Custom-built tool
- Add a new tool integration from scratch
Example prompts
- “/tool-connector”
What it can do on your machine
Read from SKILL.md and the folder at commit 9a7da40. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Tool Connector loads about 925 tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 413 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from ZhixiangLuo/10xProductivity at commit 9a7da40, republished under its MIT licence (© ZhixiangLuo). 413 words, ~925 tokens.
Download SKILL.mdSave it as
.claude/skills/tool-connector/SKILL.md (or your agent's skills folder).- name
- tool-connector
- description
- 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.
- source
- https://github.com/zhixiangluo/10xProductivity
- author
- zhixiangluo
Tool Connector — Connect Any Work Tool to Your Agent
Requires the repo cloned locally. Check if it's already present (
ls setup.md), then readsetup.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.
Show full SKILL.md (155 more words)Show less
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 10xProductivityThen read setup.md. It routes to pre-built recipes, your own recipes, and add-new-tool.md for anything new.
© ZhixiangLuo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .cursor/skills/tool-connector of ZhixiangLuo/10xProductivity.
Open the folder on GitHubat commit 9a7da40
Compare with similar skills
Tool Connector 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 |
|---|---|---|---|---|---|---|
| Tool Connector this skillZhixiangLuo/10xProductivity | 479 | — | ~925 | Automated safety check: Pass | MIT | |
| Sentry Alert TunerLeoYeAI/openclaw-master-skills | 2.2k | — | ~7.3k | Automated safety check: Pass | MIT | |
| Kibana Connectorsaspectrr/deer | 405 | — | ~2k | Automated safety check: Pass | MIT | |
| Alerting Irmgrafana/skills | 282 | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| AirweaveCraftOS-dev/CraftBot | 392 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Supercheck Monitoring Alertssupercheck-io/supercheck | 215 | — | ~855 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Kibana Connectors
aspectrr/deer
Create and manage Kibana connectors for Slack, PagerDuty, Jira, webhooks, and more via REST API or Terraform.
- Official
Alerting Irm
grafana/skills
Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack/PagerDuty/email/webhook)…
Airweave
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
Supercheck Monitoring Alerts
supercheck-io/supercheck
Work on Supercheck HTTP, ping, or DNS monitors, regional scheduling and aggregation, alert state/history, incidents, or email, Slack, PagerDuty, and webhook notifications.
- Official
Oncall Irm
grafana/skills
Route alerts, run on-call rotations, and drive incidents in Grafana IRM / OnCall — integrations (Alertmanager / Grafana Alerting / generic webhook / PagerDuty), Jinja2 routing + grouping templates…
More from ZhixiangLuo/10xProductivity
Colleague Distillation
ZhixiangLuo/10xProductivity
Distill a colleague into a reusable AI skill (work + persona) using tool connections — Slack, Slack AI, Jira, GHE, Bitbucket, Confluence, SharePoint, Teams, Outlook, Notion, Linear, Google Docs, and…
Enterprise Search
ZhixiangLuo/10xProductivity
Search your entire company's institutional knowledge in one query — Slack, Confluence, Jira, Linear, Notion, GitHub, plus any AI or multi-source search tool listed in verifiedconnections.md.
Discover UI Surface
ZhixiangLuo/10xProductivity
Walk through a UI flow once manually and capture a durable interaction map — which DOM elements to click, which network requests they trigger, and what field shapes they expose.
Linkedin Engagement
ZhixiangLuo/10xProductivity
Automated LinkedIn engagement workflow. An agent skill from ZhixiangLuo/10xProductivity.
Related
Categories
Questions about Tool Connector
What does Tool Connector do?
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…. Tool Connector is an agent skill from ZhixiangLuo/10xProductivity. 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.
When should I use Tool Connector?
Tool Connector fits situations like: the user wants to set up a tool connection; connect an internal; custom-built tool; add a new tool integration from scratch.
How do I install Tool Connector in Claude Code?
Run `npx skills add ZhixiangLuo/10xProductivity --skill tool-connector -a claude-code`. Or copy the skill folder (.cursor/skills/tool-connector in ZhixiangLuo/10xProductivity) into .claude/skills/tool-connector in your project. Claude Code loads it when a task matches its description.
How do I install Tool Connector in Codex?
Run `npx skills add ZhixiangLuo/10xProductivity --skill tool-connector -a codex`. Or copy the skill folder (.cursor/skills/tool-connector in ZhixiangLuo/10xProductivity) into .agents/skills/tool-connector in your project. Codex loads it when a task matches its description.
Can I use Tool Connector in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ZhixiangLuo/10xProductivity --skill tool-connector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tool-connector, .gemini/skills/tool-connector, .github/skills/tool-connector and .opencode/skills/tool-connector in your project.
What does Tool Connector need to run?
Going by SKILL.md and its folder, Tool Connector needs the command-line tools its instructions call (git).
Does Tool Connector access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Tool Connector safe to install?
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.
What licence does Tool Connector use?
Tool Connector is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tool Connector use?
About 925 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Tool Connector?
Skills that share tags, products or a category with Tool Connector: Sentry Alert Tuner (LeoYeAI/openclaw-master-skills, 2.2k stars), Kibana Connectors (aspectrr/deer, 405 stars), Alerting Irm (grafana/skills, 282 stars) and Airweave (CraftOS-dev/CraftBot, 392 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tool Connector?
ZhixiangLuo (a GitHub user) maintains it in ZhixiangLuo/10xProductivity, which has 479 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on July 13, 2026.
Source: ZhixiangLuo/10xProductivity on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.