skills.rest
cosmicstack-labs
cosmicstack-labsOFFICIAL
Explore all skills by this author →
Website𝕏@cosmicstackGitHub

knowledge-base

Turn scattered internal documentation into a structured, searchable wiki.

364|53|Updated May 9, 2026
Search Tags:#knowledge management#information architecture#content governance#documentation maintenance#search optimization#documentation templates#internal documentation
One-click install
npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill knowledge-base-cosmicstack-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-base
Source: https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/development/knowledge-base
Command: npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill knowledge-base-cosmicstack-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create and maintain a knowledge base that people can actually search and trust, preventing “tribal knowledge” from getting lost over time.

Core Features & Use Cases

  • Search-first knowledge design: Organize information so users can find answers in a few searches using strong titles, summaries, tags, and internal links.
  • Actionable structure and maturity model: Use a staged model (from “graveyard” to “living”) to plan improvements, governance, and maintenance.
  • Content operations guidance: Apply repeatable workflows for contribution, review, contribution barriers reduction, stale-content detection, and feedback/analytics loops.
  • Platform selection support: Choose and justify common KB platforms (e.g., Docusaurus, MkDocs, GitBook, Notion, Confluence) based on versioning, search quality, hosting needs, and cost.
  • Maintenance and governance framework: Define owners, stewards, review cadence, and measurable health metrics like stale-page rates and search success.

Quick Start

Use the knowledge-base skill to design a Level 3–4 internal documentation wiki for your team, starting from your current content and choosing a platform that best fits your hosting and search needs.

Frequently Asked Questions about knowledge-base

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

FAQPage Schema
How do I structure internal documentation so it is actually searchable?▼

Searchable internal documentation requires strong titles, summaries, tags, and internal links. You organize scattered team content into a structured wiki using a search-first knowledge design, enabling users to find answers quickly.

What is the best way to manage tribal knowledge before it gets lost?▼

Managing tribal knowledge involves applying a staged maturity model from graveyard to living content. You establish content governance with defined owners, stewards, and review cadences to capture and maintain critical team information.

How do I choose a platform for an internal team wiki?▼

Choosing an internal team wiki platform requires evaluating versioning, search quality, hosting needs, and cost. You justify options like Docusaurus, MkDocs, GitBook, Notion, or Confluence based on your specific engineering workflows.

How do I set up content governance workflows for a knowledge base?▼

Content governance workflows require defining owners, stewards, and review cadences for your knowledge base. You establish repeatable contribution processes, stale-content detection, and feedback loops to reduce contribution barriers.

Can I measure the health of my internal documentation portal?▼

You can measure internal documentation portal health using maintenance metrics like stale-page rates and search success. Tracking these analytics helps transition your knowledge base from a static graveyard to a living resource.

What are the limitations of relying on ad hoc team documentation?▼

Ad hoc team documentation lacks information architecture, leading to lost tribal knowledge and poor searchability. Without structured contribution workflows and content governance, stale-page rates increase and users cannot find reliable answers.

Related Skills

Explore More Software Engineering Skills→
nielsmadannielsmadan
1

read-docs

Search internal project documentation by keywords and prioritize Markdown content matches.

Community
Intermediate
chelleboyerchelleboyer

knowledge-management

Creates structured, searchable knowledge base articles from resolved support tickets.

Community
Advanced
musher-devmusher-dev

auditing-docs-metrics

Audit developer documentation effectiveness by computing KPIs like Time to First Success.

Official
Advanced
qodex-aiqodex-ai
39

workspace-documentation

Capture and structure conversation knowledge into Notion wikis, databases, and knowledge graphs.

Official
Intermediate