knowz-status

Diagnoses Knowz MCP server environment health and configuration integrity.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/knowz-io/knowz-skills --skill knowz-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowz-status
Source: https://github.com/knowz-io/knowz-skills/tree/main/plugins/knowz/skills/knowz-status
Command: npx skills add https://github.com/knowz-io/knowz-skills --skill knowz-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves configuration drift and connectivity issues by providing a centralized diagnostic view of your Knowz MCP environment and vault status.

Core Features & Use Cases

  • Health Monitoring: Verifies the availability of Knowz MCP tools and server connectivity.
  • Configuration Audit: Scans local environment variables and configuration files (like .codex/config.toml) to ensure correct setup.
  • Vault Validation: Cross-references vault IDs against server responses and checks for pending capture items.

Quick Start

Run the knowz-status skill to perform a full diagnostic check of your current MCP configuration and vault health.

Frequently Asked Questions about knowz-status

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

FAQPage Schema
How do I diagnose MCP server connection failures and verify API key availability?

To diagnose MCP server connection failures and verify API key availability, run a centralized health check that scans local environment variables and configuration files to validate server connectivity and configuration integrity.

What is the best way to audit vault synchronization status and check for pending capture items?

Auditing vault synchronization status involves cross-referencing vault IDs against server responses to verify synchronization state and identify any pending capture items currently queued in the MCP environment.

How do I troubleshoot configuration drift in my local MCP environment?

Troubleshooting configuration drift requires scanning local configuration files like .codex/config.toml and environment variables to detect missing settings, verify correct setup, and resolve connectivity issues across development platforms.

Does automated environment validation work across multiple development platforms for MCP servers?

Automated environment validation supports multiple development platforms by providing a centralized diagnostic view that verifies server connectivity, audits configuration files, and reports API key availability regardless of the local setup.

Why does my vault validation return mismatched IDs when cross-referencing server responses?

Vault validation returns mismatched IDs when local configuration drift occurs, meaning your environment variables or configuration files contain outdated vault IDs that no longer match the active server responses.