agent-resource-manager

To maintain consistent CLAUDE.md and SKILL.md documentation across agents, you need an institutional substrate manager that updates onboarding paths, templates, and access controls during startup and role evolution. This ensures every session starts with current docs.

Cold-starting a new AI agent with zero context requires structured onboarding guides and updated templates encoded into the institutional substrate. This allows new agents to initialize with current access controls, conventions, and documentation automatically.

Managing onboarding and version pinning for an agent plugins repository involves applying marketplace hygiene practices to the contribution flow and release process. This maintains repository templates and ensures agents use correct plugin versions during session recovery.

Yes, you can use automation to refresh agent onboarding docs and post leadership digests daily. Automating substrate maintenance ensures that institutional knowledge, recent refactors, and cross-agent coordination patterns are consistently logged and distributed.

Cross-agent coordination works by encoding shared interaction patterns into shareable documentation within the institutional substrate. This maintains logs of significant refactors and antipatterns so all agents remain aligned across sessions and role evolutions.

AI agents lose context after a session restart when CLAUDE.md and SKILL.md files are not actively maintained. Implementing session recovery protocols through substrate management restores up-to-date access controls, conventions, and documentation automatically.