Alex Yarosh Get Free Snapshot

Source record

@tjrobertson52 TikTok profile avatar

@tjrobertson52

2026-04-25

AI can't do real work in your business without these 2 documents. Here's how to build both fast ๐Ÿ‘‡ What task would you automate first?...

Source Text

i

There's really only one thing you need to do to keep up with AI, and that's create and maintain documentation. Without documentation, AI will never be able to do meaningful work in your organization. And with it, it can already handle most works done on a computer better than a human.

I'm gonna talk about the two types of documentation you need and how you can start creating it now very quickly. This is gonna be the abbreviated version of the much longer process we go through for all of our clients at our agency.

The first kind of documentation you need is a company knowledge base. If you want the AI to do any kind of meaningful work in your organization, it needs to understand everything about your organization. Collecting and structuring all that information takes a lot of time, but you don't have to do it all at once, and Claude can help.

Even if you're going to be using ChatGPT or Gemini for the actual work, you want to use Claude for putting together your documentation. And that's why this is such a good use of your time right now. Once you create this, you can easily connect it to any model.

ai.

Start by just telling it exactly what you're doing. So: I need your help putting together a company knowledge base. So this will be a comprehensive set of documents covering information on my company and my industry.

The goal is to create something that I can give to AI models that would provide everything they could possibly need to work in and for my company. Your job is to collect all this information and structure it in a way where it's easy and efficient to retrieve just the information you need for a given task.

Then you're gonna give it your website URL, any social media handles, and any other documentation or data you have about your company. Just dump everything in there. Claude is really good at handling large amounts of messy content.

One pro tip: instruct Claude to separate the documents into those that contain information that can be shared publicly and those that contain internal information. If you don't do this, you will probably find AI models are sharing internal information in public-facing content.

Once it's done creating the documents, ask Claude to create instructions for how to use the documents. This will just be a short description of each document and where it should be used, as well as which documents are for internal use only and which have information that can be shared publicly.

Now, these documents can be hosted locally or somewhere like Google Drive or Notion. Either way, you can now easily connect these same documents to multiple different AI models by creating a project on the respective platform, putting the documents in that project, and then putting the instructions in the project instructions.

But, of course, that's just the first draft of your knowledge base. You're going to need to update and maintain it, and for that, you're gonna need the second type of documentation. So the first type of documentation was your knowledge base.

The second type is instructions. And these are gonna take the form of skills.

A skill is just a set of instructions that can be read by any AI model. You're gonna want one of these for every task the AI will be handling for you. The first skill you should build is one to update and maintain that knowledge base.

In that same chat conversation you had to create your knowledge base, just tell Claude: I now want you to make a skill for updating and maintaining this knowledge base. Whenever I give you new information about our company or industry, you should look through all of our current documents and determine if any of them need to be updated. If the information doesn't fit in an existing document, you should create a new one.

And that's all you have to do. Claude knows everything it needs to create the skill. You can then just save that to your Claude account, and you can also download it to be used on other AI models.

And now, whenever you do any task, whether it's drafting an email, writing a press release, brainstorming strategy, you're gonna make sure you have a skill for that specific task. You don't just start the task by saying, we're gonna do this task, and at the end, you're gonna create a skill for doing that task in the teacher.

And then the next time you do that task, you just tell Claude to use that skill. And then after you finish the task, you tell Claude, please take all the feedback I've provided and everything you've learned throughout this process and update the skill to make it better for next time.

And now, anytime you're using AI, which really should be every time you're doing something on a computer, you're building and improving both types of documentation. This is the way. No matter how smart and capable the models get, they will always need this documentation to work in your business.

In fact, the smarter they get, the more important this documentation is gonna become.

Source Intelligence

i

AI knowledge bases should separate public-shareable material from internal-only material before models use them for public-facing work.

3 related signals ยท AI knowledge base / public vs internal / AI knowledge base / instructions / AI skills / continuous improvement

  • Classify every knowledge-base document as public-shareable or internal-only, then reflect that boundary in model instructions.
  • Create a short knowledge-base guide that maps documents to use cases and marks public-shareable versus internal-only sources.
  • Add a post-task step that updates the relevant AI skill with feedback, edge cases, and lessons from the completed work.

Questions this source answers

i

What is this source mainly about?

AI knowledge bases should separate public-shareable material from internal-only material before models use them for public-facing work.

What should an operator take from it?

Classify every knowledge-base document as public-shareable or internal-only, then reflect that boundary in model instructions.

Which topics does it connect to?

This source is connected to AI knowledge base / public vs internal, AI knowledge base / instructions, AI skills / continuous improvement.

What public evidence supports the record?

t to retrieve just the information you need for a given task. Then you're gonna give it your website URL, any social media handles, and any other documentation or data you have about your company. Just dump everything in there. Claude is really good at handling large amounts of messy content...