build-knowledge-company

Generate per-team and per-service operational dossiers from live Tsuga telemetry and codebase context.

2|Updated May 28, 2026
One-click install
npx skills add https://github.com/tsuga-dev/agent-plugins --skill build-knowledge-company
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-knowledge-company
Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/tsuga/skills/build-knowledge-company
Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill build-knowledge-company

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns a live Tsuga account plus a list of codebases (and optional architecture docs) into a ready-to-use knowledge-company skill directory containing per-team and per-service operational dossiers with runnable tsuga CLI probes.

Core Features & Use Cases

  • Creates a complete knowledge-company reference tree: generates COMPANY_GENERAL_KNOWLEDGE.md, COMPANY_TELEMETRY_KNOWLEDGE.md, TEAM_KNOWLEDGE.md, and per-service SERVICE_KNOWLEDGE.md files.
  • Grounds dossiers in live telemetry: discovers teams/services/monitors/dashboards and derives canonical query patterns from real Tsuga CLI output.
  • Produces safe, runnable investigation commands: ensures Ready-to-run sections use real tsuga CLI syntax and validates against forbidden pseudo-syntax with verification gates.
  • Use Cases: first-time bootstrap for a new customer/company, refresh after major service taxonomy changes, and re-validation after tsuga CLI syntax changes.

Quick Start

Ask an AI agent to run build-knowledge-company with an authenticated Tsuga CLI account and local codebase paths, producing a populated skills/knowledge-company/references tree for the runtime knowledge-company skill to load.

Frequently Asked Questions about build-knowledge-company

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

FAQPage Schema
How do I generate operational playbooks from live Tsuga telemetry and codebases?▼

To generate operational playbooks from live Tsuga telemetry, the Skill transforms authenticated Tsuga CLI account data and local codebase paths into a populated reference tree of per-team and per-service dossiers.

What is included in a telemetry-driven service taxonomy reference corpus?▼

A telemetry-driven service taxonomy reference corpus includes COMPANY_GENERAL_KNOWLEDGE, COMPANY_TELEMETRY_KNOWLEDGE, TEAM_KNOWLEDGE, and per-service SERVICE_KNOWLEDGE files populated with canonical query patterns.

How do I ensure tsuga CLI command generation avoids forbidden pseudo-syntax?▼

To ensure tsuga CLI command generation avoids forbidden pseudo-syntax, the Skill enforces structural and command-shape validation through verification gates before producing ready-to-run investigation probes.

Do I need an authenticated Tsuga CLI account to bootstrap company knowledge dossiers?▼

Yes, you need an authenticated Tsuga CLI account and local codebase paths to bootstrap company knowledge dossiers, allowing the Skill to discover live teams, services, monitors, and dashboards.

When should I refresh operational playbooks after service taxonomy changes?▼

You should refresh operational playbooks after major service taxonomy changes or re-validate them after tsuga CLI syntax changes to maintain service investigation readiness and command accuracy.

How to derive canonical query patterns from live Tsuga discovery output?▼

To derive canonical query patterns from live Tsuga discovery output, the Skill extracts real telemetry data from discovered teams, services, monitors, and dashboards to ground the generated dossiers.