| name | verified_connections |
|---|---|
| device | your-device-name |
| description | [your-device-name] Your active tool connections — verified and ready on this device. Gitignored — device-specific, never committed. Covers: ... Load at session start. |
This is the example file. Do not load this as your capability index.
- Your active connections: load
TENX_PRIVATE_DIR/verified_connections.md(device-specific, outside the public repo, never committed). - To set up connections: "Read setup.md and set up my tool connections."
- To refresh short-lived tokens (~8h): run the tool's
sso.py(e.g.source .venv/bin/activate && python3 tool_connections/slack/sso.py)
device:Set this to your machine name (e.g.my-macbook,work-laptop). BecauseTENX_PRIVATE_DIR/verified_connections.mdis device-specific and outside the public repo — each machine has its own set of verified tokens — the device field lets the agent know which machine it's running on and prevents confusion when context from multiple devices appears in the same session.
The sections below illustrate the format. After verifying a tool, append its section to TENX_PRIVATE_DIR/verified_connections.md using the same format — read the tool's connection-*.md frontmatter for name, description, and env_vars.
All Jira operations — fetch issues, JQL search, update fields, write descriptions/comments, REST API quirks (components, editmeta, Agile/sprint API). Use when fetching a Jira issue, listing tickets, updating fields, writing Jira comments or descriptions, or using the Jira REST API.
Env: JIRA_EMAIL, JIRA_API_TOKEN, JIRA_BASE_URL
Slack — two complementary modes. (1) Slack AI: post a natural-language question to the Slackbot DM and get a synthesized AI answer drawn from all Slack content. (2) search.messages: raw full-text search. Also: read channel/thread history, post messages.
Env: SLACK_XOXC, SLACK_D_COOKIE (long-lived user session; refresh with python3 tool_connections/slack/sso.py only when the session stops working)
Add tool_connections/{tool}/connection-*.md with core frontmatter (name, auth, description, env_vars). After verifying, append a section to TENX_PRIVATE_DIR/verified_connections.md following the format above.