tool-connector — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited tool-connector (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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 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.
| 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.
| 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 |
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).
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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.