knowledge-sharing

Name: knowledge-sharing
Availability: InStock
Author: manager-dot-dev

Diagnose knowledge silos and recommend frameworks for engineering teams.

104|7|Updated Apr 10, 2026

Search Tags:#documentation #onboarding #root-cause #cross-team #guilds #knowledge-silos

Ready to run

npx skills add https://github.com/manager-dot-dev/manager-skills --skill knowledge-sharing-manager-dot-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: knowledge-sharing
Source: https://github.com/manager-dot-dev/manager-skills/tree/main/skills/knowledge-sharing
Command: npx skills add https://github.com/manager-dot-dev/manager-skills --skill knowledge-sharing-manager-dot-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Engineering managers struggle with isolated information, missing documentation, slow onboarding, and cross‑team friction that reduce productivity and increase duplication of effort.

Core Features & Use Cases

Root‑cause diagnostic: Identifies whether silos stem from lack of horizontal flow, ineffective documentation, poor onboarding, or “us vs. them” thinking.
Framework recommendations: Suggests Engineering Guilds, ADR‑based lightweight docs, onboarding buddies, or clear cross‑team request paths.
Use case: A manager notices that multiple teams are rebuilding the same component; the skill pinpoints the cause and proposes a guild and ADR process to prevent future duplication.

Quick Start

Use the knowledge-sharing skill to diagnose my team’s knowledge silo and receive a brief action plan.

Frequently Asked Questions about knowledge-sharing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify the root cause of knowledge silos in my engineering team?▼

To diagnose knowledge silos, evaluate whether isolated information stems from poor horizontal flow, ineffective documentation, inadequate onboarding, or cross-team friction. Identifying the specific source allows you to apply targeted frameworks like Engineering Guilds or ADR-based lightweight docs to resolve the isolation.

What is the best way to stop multiple teams from rebuilding the same component?▼

The best way to prevent duplicate effort is to establish an Engineering Guild and implement ADR-based lightweight documentation. This framework captures decisions and shares architectural knowledge across teams, ensuring existing component solutions are visible and reusable.

How can I improve cross-team collaboration and reduce friction during onboarding?▼

Improve cross-team collaboration by assigning onboarding buddies and defining clear cross-team request paths. These frameworks bridge knowledge gaps and reduce "us vs. them" thinking, ensuring new engineers integrate smoothly without triggering inter-team friction.

When do I need to introduce an Engineering Guild to fix documentation gaps?▼

Introduce an Engineering Guild when documentation gaps persist across multiple teams and horizontal knowledge flow is blocked. A guild facilitates cross-team communication and standardizes lightweight documentation practices to prevent siloed information.

Can I resolve knowledge silos without relying on external documentation tools?▼

Yes, you can resolve knowledge silos without external tools by applying structural frameworks like onboarding buddies, clear cross-team request paths, and ADR-based lightweight docs. These methods address root causes directly through process adjustments rather than software dependencies.