Skip to content

Give the whole team the same AI toolbox

Pick the tools a job needs, lock the settings that must not change, and write down how the team does it. Everyone can use the same tools, with the same steps offered alongside, in whichever AI app they use.

  • Free 14-day trial
  • No credit card
  • Free plan for one person
ChatGPT Elaichi connected

Post this week’s pipeline numbers in #revenue-ops.

MB

Using the Pipeline update toolbox

  • Read 42 open deals in HubSpot
  • Read the deals that changed stage this week
  • Posted the update in #revenue-ops
  • Post in any other channel Locked in this toolbox

Posted in #revenue-ops: new pipeline, the deals that moved, and three at risk.

Three teams, one toolbox each

Each team builds its toolbox once. Everyone on it starts from the same tools and the same steps.

JM SupportJake Morgan

“Escalate ticket #4821 to engineering.”

Claude
Read ticket #4821 in Zendesk
Opened ENG-1293 with the steps to reproduce
File it in another projectLocked to the ENG project

Escalations that start from the same checklist

The support lead builds an escalation toolbox from Zendesk and Jira, with the engineering project locked in. The skill lists what every escalation must include, so every agent starts from the same checklist.

Uses Zendesk Jira

EC SalesEmily Carter

“Review the Acme Corp deal for the deal desk.”

Claude
Read the Acme Corp opportunity
Read its last 5 activities
Posted the review in #deal-reviews
Change the dealNot in this toolbox

One deal-review kit for every rep

A sales manager builds a deal-review toolbox from Salesforce reads and a Slack tool locked to #deal-reviews. The skill spells out how the team reviews a deal, so every rep starts from the same steps.

Uses Salesforce Slack

RH EngineeringRyan Hayes

“Start the incident checklist for the checkout outage.”

Cursor
Read incident #312 in PagerDuty
Opened a follow-up issue in Jira
Started the incident notes in Notion

A template every squad copies

A platform team shares an incident template with PagerDuty, Jira and Notion tools and a skill for the first hour. Each squad makes its own toolbox from it, with its own connections. Later changes to the template don’t touch a squad’s copy.

Uses PagerDuty Jira Notion

One toolbox, built once, for every AI app

How a team’s AI setup grows on its own

  • Each person picks their own tools from everything their apps offer.
  • How to do the task lives in each person’s own prompts.
  • When the process changes, everyone updates their own setup.

With Elaichi

  • Choose the tools for the job and rename them so the AI picks the right one. Lock the values that must not change.
  • Write a skill: plain steps for how the team does the task. Every edit is kept, and Elaichi flags the skill when tools are added, removed or renamed.
  • Share it with a person, a team or the whole company. Teammates run its tools without a login of their own, and their own role and restrictions still apply.
  • Every AI app a teammate connects with Everything I can use, or with this toolbox picked, is offered the same tools and the same skill.

Set it up in four steps

In the order an admin takes them.

  1. 1

    Pick the tools

    Create a toolbox and add the tools the job needs from your connected apps. Switch off anything the team shouldn’t use.

  2. 2

    Shape them for the AI

    Rename a tool and rewrite its description so the AI knows when to use it. Set defaults, and lock the values that must never change.

  3. 3

    Write the skill

    Add written steps for the task, up to 10,000 characters. Every edit is kept, and the skill is flagged when tools are added, removed or renamed under it.

  4. 4

    Share it

    Share the toolbox at use with a person, a team or the whole company, or share a template so each team makes its own copy.

For IT and engineering

An Elaichi toolbox is a named set of tools for one job, built from your connected apps. Each tool in it can be renamed and described for the model, given default or locked values, and switched on or off. A toolbox can also carry a skill: written guidance, up to 10,000 characters, on how to use its tools. Share it with a person, a team or the whole organization, or share a template that each team copies. It lives in Elaichi rather than in one AI app, so every AI app a teammate connects with Everything I can use, or with this toolbox picked, is offered the same tools and the same skill.

Details that matter

  • Guidance, not permission. A skill grants nothing. Elaichi serves it with a fixed notice that it is the owner’s guidance, not instructions from Elaichi or the user, and every call still runs under the person’s own role and restrictions.

  • A rename can’t slip past a restriction. Restrictions check the catalog tool’s own name and operation, so renaming a tool or changing its description inside a toolbox never gets it past a rule.

  • Templates copy once. A toolbox made from a template gets its own copy of the tools and the skill. Later edits to the template never change it.

  • How the skill reaches the AI. Elaichi offers a toolbox’s skill to every AI app that reaches the toolbox, through Everything I can use or because the toolbox was picked. Whether an AI app passes it to its model is that app’s choice.

Three ways to get a team using AI the same way

Aspect Prompts passed around Each AI app’s own connectors An Elaichi toolbox
Tools in reach Everything each person connected What was connected in that AI app Only the tools the toolbox holds
How tools are described As each app ships them As each app ships them Renamed and described for the job
Values that must not change Repeated in every prompt Up to each AI app’s settings Locked; the AI can’t change them when it calls the tool
The know-how Shared in chats and docs Set up again in each AI app A skill that goes with the toolbox, with every edit kept
A second AI app Copy the prompts over Set it up again there Offered the same toolbox
Updating it for everyone Shared again by hand Changed in each AI app Edit the toolbox once

Questions, answered

What is a toolbox in Elaichi?

A named set of tools for one job, built from your connected apps. Each tool can be renamed, described, given default or locked values, and switched on or off, and the toolbox can carry a skill: written steps for how to use it.

Can I stop the AI from changing a value, like a channel or a project?

Yes. Lock it in the toolbox. Locked values are filled in when the tool runs, so the AI can’t change them in a call. The AI may still see the value; it just can’t override it.

Do teammates need their own access to the apps behind a toolbox?

No. Someone you share it with at use runs its tools through the connections in it, without access of their own to those connections. Their own role and restrictions still apply to every call.

What is a skill?

Written guidance on how to use a toolbox’s tools, up to 10,000 characters. Every edit is kept, it is flagged when tools are added, removed or renamed under it, and it is served with a notice that it is guidance and grants no access.

Does a toolbox work the same in ChatGPT, Claude, Cursor and Microsoft Copilot?

Elaichi offers the same tools, locked values and skill to every AI app connected to it. Each AI app’s own model still decides how to use them, and whether an app passes Elaichi’s instructions to its model is that app’s choice.

How does my AI app get the skill?

An AI app connected with Everything I can use is offered the skill of each toolbox you can run, as an entry it can read. One connected to chosen toolboxes is offered only those toolboxes’ skills.

What is the difference between sharing a toolbox and sharing a template?

Sharing a toolbox gives people that same toolbox, so your edits reach them. Sharing a template lets each person or team make their own copy, with their own connections and a copy of the skill, and later template edits don’t reach copies already made.

Can’t I do this with ChatGPT’s or Claude’s own connectors?

Each AI app’s own connectors are set up in that app, with the tools each vendor ships. A toolbox is built once in Elaichi, so the same chosen tools, locked values and skill are offered in every AI app a teammate connects, under one set of roles and restrictions and one audit log.

Build one toolbox for one job

Start a trial, build a toolbox with a skill, and open it from two AI apps.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot