TLDR: A subscriber adds your connector to their assistant once and signs in once. From then on, every Skill you have granted them appears as a tool the assistant can call. They ask in plain language, the assistant picks the Skill, our server checks the subscriber is still on your list, and the Skill runs. Group Skills into Stacks so a subscriber gets a set that makes sense, not a pile. Add a Skill to the Stack and every subscriber in it has it the next time their assistant refreshes its tool list. Remove a subscriber and their next call is refused.

Key Takeaways

  • One connector, one sign-in, every granted Skill.
  • The subscriber never installs a file; the assistant calls the Skill through the connector.
  • Stacks are how you give a group of people a set of Skills in one move.
  • Access is checked on every call, not once at setup.
  • A new Skill in a Stack reaches everyone in it in their next chat, or after reconnecting once.
  • The subscriber's assistant can be Claude or Perplexity today, with more under test.

The subscriber's side, start to finish

  1. They add your connector to their assistant. The steps are on their setup page after they sign in, and in your portal's connection guide.
  2. They sign in once with the email and password you gave them. The connection renews itself for as long as they keep using it within 30 days.
  3. Your Skills appear as tools in their assistant. They do not see Skills you have not granted.
  4. They ask for what they want in ordinary language. The assistant chooses the matching Skill and calls it.
  5. Our server checks they are still on your list, then runs the Skill in the mode you chose.
  6. The assistant shows the answer.

There is nothing to download and nothing to keep up to date on their side.

The creator's side

You build or paste a Skill, decide its protection mode, and put it in a Stack. A Stack is a named set of Skills. You grant subscribers a Stack, by hand or by CSV, or through webhooks from your billing system on the larger plans. From then on, the Stack is the unit you manage: add a Skill to it and everyone in it has the Skill from their next chat; move someone out and they lose the set.

Why the check happens on every call

A GPT link worked for anyone who had it, forever. A Skill call is checked each time against your list. That is what makes a subscription a subscription: when someone stops paying, the next call is refused, with no awkward "please stop using it" email from you. One thing to know about Password mode: if the subscriber already has the Skill's text in an open chat, that chat keeps it; IP mode stops even mid-chat, because the method was never handed over.

Connecting Skills together

Today, "together" means Stacks: a subscriber gets a coherent set, and their assistant can draw on each Skill in the set within one conversation.

What the assistant sees

In Password mode, the assistant receives the Skill's text for that chat when the Skill is called, after the access check. In IP mode, the assistant only ever sends the request and receives the result; our server runs the method with the model provider's API, and the method never reaches the subscriber or their assistant. Choose per Skill.

Try it from the subscriber's chair

Connect free. You become a subscriber on our demo Stack with two Skills. Add the connector to Claude, sign in, and call both. You will see the whole path in five minutes, and the difference between a Password Skill and an IP Skill with your own eyes.