Getting started
A library your
AI can use.
Understand what Gist brings to your client—and what you need to bring with it.
Discover. Resolve. Use.
Gist is a catalog and context library for AI clients. It helps a client find relevant skills and tools, retrieve complete packages at an exact version, and resolve the capabilities a skill requires.
- Skill
- A reusable workflow with instructions, supporting assets, and declared requirements.
- Tool
- A described operation with a schema your client can inspect and validate.
- Capability
- What a workflow needs to accomplish, such as listing or reading messages.
- Binding
- The versioned link from a capability to a concrete tool available to your client.
Gist narrows the context your agent receives to relevant content. The number of tokens and model turns saved depends on the workload and integration; it is not a fixed promise.
Open your workspace
- Sign in with GitHub. Access is invitation based, so use the GitHub account your operator invited.
- Open your workspace. Search by intent or name and filter by artifact kind.
- Open an artifact to inspect its version, state, digest, and published metadata.
The public library is open to everyone. Your workspace shows only your authorized artifacts and private integrations. An entry is metadata for your client to inspect; it does not connect an account.
Illustrative workflow
A quieter start to your inbox
Imagine asking Zati for a briefing of unread mail. A maintained skill can describe the briefing and declare the capabilities it needs: list messages and read selected messages.
- Gist helps your client discover the relevant skill and retrieve its exact package.
- The client checks the requirements against its own admitted mail tools and authorized connection.
- You connect your mail account and grant access in the client, if you have not already.
- The client reads the permitted messages and prepares the briefing under its own execution policy.
This example needs message listing and reading. A catalog entry does not grant access to Gmail or provide a connected mail account. Availability depends on your client's implementation and connections.
Bring it to your client
In Zati, use its Services experience and the setup supported by your installed version. Account connections, tool admission, approvals, and workflow execution live there. Browsing Gist does not automatically install or activate a skill in Zati.
Other clients can integrate through the Go library or the authenticated MCP endpoint. Follow the client’s supported authorization and package import workflow.
Developer setupWhen something is missing
- I cannot sign in
- Check that you are using the invited GitHub account. Ask your workspace operator to confirm access. If GitHub returns an error, return to sign-in and start a fresh flow.
- My library is empty
- No matching records may be published for your workspace. Clear your search and kind filter, then ask your operator about catalog content.
- A skill cannot run
- Inspect its requirements in your client. An absent binding, missing provider connection, or unsupported tool can prevent execution even when a skill is visible.
- The service is unavailable
- Try again shortly. Operators can inspect process health and service readiness. First enrollment may leave catalog access unavailable until the configured founder completes sign-in.