knowledge-architecture-advisor

Diagnose knowledge management needs and recommend wiki, database, or hybrid architectures.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill knowledge-architecture-advisor-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-architecture-advisor
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/prompt-workflows/skills/knowledge-architecture-advisor
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill knowledge-architecture-advisor-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between a wiki, a structured database, or a hybrid system for AI-native knowledge management is hard, and picking wrong leads to wiki drift, database gaps, or constant re-derivation of understanding. This Skill interviews you about your usage profile, operational needs, and current pain points, then delivers a direct, opinionated architecture recommendation. ## Core Features & Use Cases - Structured Intake Interview: Asks grouped questions about usage profile, operational needs, and current pain, waiting for answers before proceeding. - Signal-Based Diagnosis: Maps your answers against explicit wiki, database, and hybrid signal criteria rather than defaulting to a safe middle option. - Full Recommendation Document: Produces a diagnosis, recommendation, fit rationale, failure modes of rejected options, risk profile, implementation checklist, and upgrade path. - Use Case: A solo researcher drowning in papers and notes answers the intake questions and receives a concrete wiki-first architecture with a 6-step implementation checklist and criteria for when to add a database layer. ## Quick Start Use the knowledge-architecture-advisor skill to help me decide whether to build a wiki, a database, or a hybrid system for managing my research notes and team knowledge.

Frequently Asked Questions about knowledge-architecture-advisor

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

FAQPage Schema
How do I choose between a wiki and a database for knowledge management?

Choose a wiki when you do deep research on focused topics, work solo, and value connections between sources. Choose a database when multiple AI tools need the same memory, volume is high across categories, and you need precise queries, filters, and automated workflows.

When should I build a hybrid knowledge architecture?

Build a hybrid only when signals genuinely point both directions: you need both browsable synthesis and precise queries, or both human reading and multiple AI agents. It is more complex to build and maintain, so it should not be the safe default.

What is the difference between write-time compilation and query-time retrieval?

Write-time compilation means the AI synthesizes understanding when information arrives, producing human-readable wiki artifacts. Query-time retrieval stores structured data and synthesizes answers on demand, suiting high-volume, multi-tool access patterns.

What goes wrong if I pick the wrong knowledge architecture?

Wikis risk drift, where confident prose is quietly wrong, and can hide valuable contradictions. Databases show visible ignorance with no pre-built synthesis and impose a re-derivation tax where the AI rebuilds understanding from scratch every query.

Does this approach work for teams as well as solo users?

Yes, the intake explicitly asks whether you are solo or on a team and how many people are involved. For team scenarios, the recommendation addresses contradiction surfacing, since teams often need disagreements preserved rather than smoothed over.