KM Job Description Now Requires Five Capabilities That Did Not Exist Five Years Ago

Research surfaced at the KM&I for Legal conference and compiled by Inside Legal KM identifies five capabilities now required in KM roles that were not in the standard job description five years ago: knowledge graph architecture (structuring legal knowledge as connected entities with typed relationships, not a document taxonomy); MCP and API integration (commissioning and governing MCP server connections across transaction, matter, and DMS platforms); AI curation governance (classification, summarization, and tagging standards that determine what enters the AI-readable knowledge base); context engineering (designing prompt libraries, matter profiles, playbooks, and metadata schemas that shape AI output quality rather than writing prompts individually); and AI output QA (lightweight practices for verifying research accuracy, citation integrity, and hallucination risk in AI-assisted work product). For KM directors, this capability map is simultaneously a hiring framework and a skills gap assessment: most existing KM teams were built around a document-centric operating model that none of these five capabilities require.