The library

The library is where you find toolkits to install. It’s a browsable catalog inside your Jootle instance, kept fresh from the platform.

You don’t have to leave Jootle to install. You don’t have to download anything. You don’t have to configure files. The flow is: open the library, find a toolkit, click install.

This chapter covers what’s in the library, how to evaluate a toolkit, and what happens during install.

Opening the library

In the sidebar, find Toolkits (or Library under it, depending on your version). The library view shows:

Featured toolkits. Curated picks for what most customers find useful first.
Categories. Productivity, Content, Finance, CRM, Engineering, Personal, and so on.
Search. Type what you’re looking for.
Recently added. New toolkits that have shipped.

Each toolkit has a tile showing its name, a one-line description, and a badge for its source (Official, Community, or Custom).

Toolkit sources

A toolkit’s badge tells you who maintains it:

Official. Built and maintained by Jootle. Updates flow automatically. Bug reports go to us.
Community. Built by someone else, submitted to the library, and vetted. Updates are independent; the maintainer is listed on the toolkit’s detail page.
Custom. Toolkits you (or your team) built for yourselves. Live in your instance, not the public library.

We’re conservative about what makes it into the public library. Each community submission goes through review, and toolkits that include external connections (API keys, third-party services) get extra scrutiny.

What a toolkit’s detail page tells you

Click any tile to see the detail page. It covers:

What it does. A short essay on the use case.
What it adds. The specific sidebar entries, playbooks, goals, and entity types.
What it requires. Any external services you’d need (a Stripe account, a Calendar integration, etc.).
Pricing. Most are free. Some use third-party services with their own pricing; the toolkit page is clear about this.
Reviews / ratings. Honest customer feedback. Not curated, not removed except for spam.
Source & maintainer. Who built it, when last updated, where to ask questions.

If you’re considering a toolkit, read its detail page before installing. Two minutes there saves “huh, that wasn’t what I expected” later.

The install flow

Installing is one click on the detail page. What actually happens:

The toolkit’s package is fetched from the library.
Your AI verifies the signature (every official toolkit and reviewed community toolkit is signed).
The toolkit’s components register with your instance: sidebar entries, playbooks, goals, entity types.
If the toolkit needs setup (e.g., paste an API key for an external service), a setup wizard runs.
The install completes. The new sidebar entry appears.

Total time, in most cases: under a minute, including any setup wizard.

You’re not asked to restart anything, your AI doesn’t need a refresh, and you can start using the new capabilities immediately.

After installing: try one thing

After installing a toolkit, the best first move is to try one thing it adds. Don’t try to “learn the whole toolkit”; just use one feature.

Installed Ideas? Capture one idea right now.
Installed Forge? Define one content type.
Installed CRM? Add one contact.

The toolkit reveals itself as you use it. Most have onboarding walkthroughs on first open; those are worth following.

What can go wrong

Two cases worth knowing:

Install fails. Rare, but if a toolkit’s signature doesn’t validate or a required dependency isn’t met, install aborts and tells you why. Reach out to support if it’s not obvious.

Toolkit conflicts. Very rare. Two toolkits both want to claim “shopping list” as their entity name, for example. The library detects this and offers to resolve at install time.

Updates

Official toolkits update automatically as Jootle ships improvements. You’ll see a small “updated” tag next to the toolkit, and changes appear in the changelog.

Community toolkits update when their maintainer pushes a new version. You’ll see an “update available” indicator on the toolkit; one click applies it.

Custom (your-own) toolkits update when you push a new version.

Uninstalling from the library view

Each installed toolkit has an uninstall option in its detail page. Removing a toolkit is reversible (data is preserved); deleting a toolkit’s data is irreversible.

The uninstall flow asks if you want to keep the data. Default is yes.

A note on first impressions

The library can look overwhelming the first time. Don’t try to absorb it all. The categories and search exist so you can come back when you have a specific need.

A useful first browse:

Look at Featured. Five to ten tiles, hand-picked.
Look at the category that matches your work (Finance, Content, CRM).
Install nothing if nothing speaks to you.

You can come back next week. The library will still be there.

Suggesting a toolkit

If there’s a toolkit you wish existed, tell us. Suggestions are how the library grows. The contact form, the feedback button in the library, or directly via email all work.

If you build a toolkit you’d be willing to share, the community submission flow is in the library’s settings. We review, we test, we publish if it fits.