In the article you bookmarked, LangChain co-founder Harrison Chase argues that what business agents lack isn't a better model or more context but maintained knowledge in three kinds: how work is done here (written down as skills), how the business works (definitions, policies, product and customer facts), and where current data lives and how to query it. Don't try to keep it up to date by hand. Give working agents a tool to flag knowledge that's missing or wrong, run a separate 'curator' agent on a schedule that reads those flags, the agents' logs and sources like Notion and Slack, and let it update the knowledge. Store it wherever suits you: skill files in GitHub, a Notion page or LangChain's own Context Hub. His example: an agent writing a revenue report notices a renamed database column and flags it, the finance lead corrects a header in chat, and that night the curator updates both skills. LangChain says its own sales, content and LangSmith Engine agents work this way, and it sells help building these, so read it as a well-argued pitch.
Why it mattersIf you've already written a few skills or instructions for your AI, this is the next step: a routine where everyday use reveals the gaps and something fixes them. Start, as Chase suggests, with one recurring job and note where the agent gets stuck.