Internal tooling & knowledgeIn production

One searchable place for every automation, Claude skill and app the team has built.

A catalogue where anyone signed in can find a tool, read how to start using it and add their own. Nothing is ever deleted, so it stays a record of what has been built.

3tool types: Claude skills, automations, apps
223automated tests in the repository
Search-first catalogue of internal Claude skills, automations and apps, with filters and tool cards
Rebuilt interface · illustrative data

The business problem

The team was building Claude skills, workflow automations and small apps. They lived in scattered documents and chat threads. People could not tell what already existed, so work was at risk of being rebuilt, and nobody could show clearly what was automated and how.

What changed

Yash built an internal catalogue. Each entry has a description, a short quick-start guide, integration tags, an audience (internal or client-facing), an owner and a link to where the tool actually runs. The home page starts with one question, "What are you trying to get done?", and a search box. Filters narrow by type, audience and integration.

Before & after

AreaBeforeAfter
Finding a toolAsk around or search old threadsOne search across title, description and integrations
Starting to use itFind the builder and askA quick-start guide on the tool's own page
Retiring a toolIt disappears from viewIt is archived and stays in the record
Knowing what is automatedNo complete listOne catalogue, with an owner on every entry

The business value

The aim is discovery: less rebuilding and a clear answer to "what do we have?". The catalogue is the first step of a wider effort to give the team consistent workflows and to show, internally and later to clients, what is automated.

How to read the return

The source holds no usage or time-saved figures, so none are claimed here. The screens shown use made-up tools and people.

Why the system is dependable

Access is limited to company Google accounts, and that rule is checked in four places, including the database itself. There is no delete permission on tools at all. Edits warn if someone else saved first. The repository holds 223 automated tests and a script that probes every table to confirm signed-out users see nothing.

Rebuilt screens in the style of the real product. All tools, names and counts shown are fictional.

Could this work for your team?

If your team has built automations and prompts that only their authors know about, a small searchable catalogue with owners and quick-start notes is a cheap way to stop rebuilding them.

Talk through a similar project
Keep exploring

More case studies

All case studies