bcos-wiki

Manage schema-validated wiki content in the BCOS ecosystem.

18|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/walm00/business-context-os --skill bcos-wiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bcos-wiki
Source: https://github.com/walm00/business-context-os/tree/main/.claude/skills/bcos-wiki
Command: npx skills add https://github.com/walm00/business-context-os --skill bcos-wiki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured system for ingesting, managing, and organizing knowledge within the BCOS ecosystem, enabling consistent documentation, source validation, and linkage.

Core Features & Use Cases

  • Wiki Zone Administration: Initiates and maintains a schema-driven, schema-validated wiki space in docs/_wiki/.
  • Content Ingestion & Promotion: Supports capturing URLs, local documents, and inbox messages into structured wiki pages with provenance and references.
  • Automated Index & Overview Updates: Regenerates index and overview artifacts to facilitate cross-source navigation and comprehension.
  • Documentation Lifecycle Management: Handles archiving, review, validation, and schema evolution for wiki content.
  • Use Case: Think of a technical team continuously updating APIs, guides, and architectural diagrams, all seamlessly integrated into the BCOS wiki for real-time knowledge sharing.

Quick Start

Run the /wiki init command to scaffold the BCOS wiki zone, then start ingesting content via /wiki promote for inbox messages or /wiki create for local files.

Frequently Asked Questions about bcos-wiki

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

FAQPage Schema
How do I manage wiki content ingestion and schema validation for engineering documentation?

Wiki content ingestion and schema validation are managed by capturing URLs, local documents, and inbox messages into structured pages, enforcing schema-governed consistency, and tracking provenance for engineering teams.

What is the best way to organize technical documentation with schema validation and versioning?

Schema validation and versioning organize technical documentation by maintaining a schema-driven wiki space, handling archiving, review, and schema migrations to ensure consistent referencing and comprehensive organizational learning.

How do I archive legacy content and handle schema migrations in a knowledge management system?

Legacy content archiving and schema migrations are handled through documentation lifecycle management, which validates evolving schemas and archives outdated wiki pages within a schema-governed framework.

Can I track provenance and references for ingested URLs and local documents in a wiki?

Yes, tracking provenance and references for ingested URLs and local documents is supported during content promotion, ensuring structured wiki pages maintain clear source validation and linkage.

Does schema-governed wiki management support multiple ingestion paths for operations teams?

Schema-governed wiki management supports multiple ingestion paths optimized for operations teams, enabling seamless integration of APIs, guides, and architectural diagrams with automated index and overview updates.

When do I need schema evolution and automated index regeneration for knowledge management?

Schema evolution and automated index regeneration are needed when technical teams continuously update documentation, requiring real-time knowledge sharing, cross-source navigation, and evolving schema adaptations.