For your local agents

Your tools.
One place for the work.

Give Codex, Claude Code and your own tools the context they need to work with TekPartner. A focused skill, a practical manual and a shared API.

Public downloads · No login needed · Version 1.0.25

Install the skill

Run these commands on each machine where your agent works. The same package supports both clients, with the manual and Gateway brief included.

Install for

Installation commands

curl --fail --show-error --silent --proto '=https' --tlsv1.2 \
  https://www.tekpartner.app/agent-skills/install.py -o tekpartner-install.py
python3 tekpartner-install.py --client codex

Python 3.9 or newer. Review the installer before running it. Add --dry-run to validate the download and see its destination first.

Locations, updates and manual installation

Codex: $CODEX_HOME/skills when configured; otherwise the installer reuses an existing V3 skill in ~/.agents/skills or ~/.codex/skills. A fresh installation uses ~/.agents/skills.
Claude Code: ~/.claude/skills/tekpartner-v3

Run the installer again to update. Existing instructions are backed up under skill-backups beside the skills directory; the installer prints the exact path. Each client installs independently. It does not edit MCP configuration, issue keys or remove older skills with other names.

For a custom client location, choose one client and add --directory /path/to/skills. For example, a runtime using $CODEX_HOME/skills can use that directory. Keep one active copy of this skill.

For manual installation, download the ZIP and put its tekpartner-v3 folder in your client’s skills directory. Move any previous copy to a private backup first. Restart your client, then invoke $tekpartner-v3 in Codex or /tekpartner-v3 in Claude Code.

Client references: Codex skills · Claude Code skills.

Archive SHA-256: 6034938db65079b0bda26f1f6e199a3573d676c20fa606ca230d5368d9ff4c67. The installer checks this release’s file list, size and checksums before installation.

Download ZIP Manual install

Set up your project with your agent

After installing, open your project in Codex, Claude Code or your preferred client and send this prompt. Your agent will help connect its own key, select the right project and set your preference for concise session reports.

First-project setup prompt

Use the tekpartner-v3 skill to set up this project with me, reusing existing choices.
Confirm the agent, organization and project. Help configure this client's own key; ask where it is saved, never for its value in chat. Different organizations and agents need separate credentials.
Share project context through .tekpartner.json while keeping Codex and Claude identities and session pointers separate.
Verify the actual identity and project access. Offer concise session reports and check their permissions. Report anything still missing; do not create test work or claim readiness from configuration alone.

https://api.tekpartner.app/v3/mcpStreamable HTTP

Reuse a connection for allowed projects in the same organization. Projects in another organization need that organization’s own key and connection. Keys can be valid until a chosen date or until revoked; use the signed-in setup page to issue one. The agent can also start a browser request with suggested restrictions for you to edit and approve.

Connect with browser approval

Sign-in required for credentials. The public skill never contains a key or customer data.

Verify access

Project setup includes these checks. To check an existing connection again, restart your client after configuration changes and send this prompt.

Verification prompt

Verify my tekpartner_v3 connection without creating or changing records.
1. Call tekpartner_whoami with {}. Confirm the expected independent agent/service identity and organization before further reads; stop on mismatch. Report its agent ID, not its secret.
2. Call tekpartner_activity with {"action":"list","limit":10}.
3. Call tekpartner_capabilities with {"surface":"current_work"}.
4. If projects are readable, call tekpartner_project with {"action":"list","limit":10}.
5. Summarize identity, available operations and any error code. An empty list is valid. Do not claim write access was tested by these read calls.
Use the V3 agent manual supplied with this connection. Do not use a legacy TekPartner connection or create setup/test work.

Confirm the returned agent and organization. An empty work queue is valid. A listed tool still needs permission for each action.

For interface builders

Build on the same contracts.

Agents can manage authorized project releases and milestones, customize work pipelines, move work between stages, and update their own icons. The maintained guides include permissions, versioned writes and refresh instructions.

Use the existing API and MCP from your Gateway, desktop client or another tool. Keep credentials and execution policy local.

Agent manual

Current tools, permissions, response shapes and recovery.

Gateway handoff

Build sequence, vault integration, action policy and acceptance checks.

The handoff describes the integration contract and acceptance checks. Verify your Gateway’s current support; installing this skill supplies instructions for the agent.

Your tools.One place for the work.