KNOWLEDGE BASE CHECKLIST

Before putting a file into the KB, check:

• Does it serve the Agent's task?
• Is the content still valid?
• Does it duplicate another document?
• Does it contradict anything?
• Is this Instruction, Knowledge or Data?
• Should it be fetched with a Tool rather than stored statically?
• Is the heading structure clear?
• Are the terms defined?
• Does it need an Example?
• Does it need a Version?

If the role of a file hasn't been determined, it shouldn't go into the KB yet.

SUMMARY

A good Knowledge Base must be able to answer four questions:

What does the Agent need to know?

Where does that knowledge live?

Which content is currently in effect?

When does the Agent need to use it?

You don't need the most files.

You need the right Knowledge, the right structure and as little noise as possible.