manifest-status

Displays the current GitBook project's metadata and statistics in a sidebar.

7.4k|494|Updated Sep 27, 2022
One-click install
npx skills add https://github.com/mnfst/manifest --skill manifest-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manifest-status
Source: https://github.com/mnfst/manifest/tree/main/skills/manifest-status
Command: npx skills add https://github.com/mnfst/manifest --skill manifest-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a clear, at-a-glance overview of the Manifest OpenClaw plugin's current configuration and operational status, helping users diagnose issues and understand their setup.

Core Features & Use Cases

  • Diagnostic Table: Displays key settings like installation status, version, enabled state, mode, API keys, model routing, and local database path.
  • Key Sync Check: Verifies if plugin and provider API keys are synchronized.
  • Use Case: When a user reports that Manifest isn't routing requests correctly, they can use this Skill to quickly see if the plugin is enabled, if the correct API keys are configured, and if the model routing is set up as expected.

Quick Start

Show the current Manifest plugin configuration.

Frequently Asked Questions about manifest-status

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

FAQPage Schema
How do I check the configuration status of my Manifest OpenClaw plugin?

To check the Manifest OpenClaw plugin configuration status, use a diagnostic tool that displays installation, version, enabled state, operational mode, endpoint, API keys, provider details, default model, model routing, and local database path.

Why does my Manifest plugin route requests incorrectly?

Incorrect Manifest plugin request routing often stems from disabled states, unsynchronized API keys, or misconfigured model routing; a diagnostic status check verifies these exact settings to identify the configuration mismatch.

How do I verify if my plugin and provider API keys are synchronized?

To verify API key synchronization, run a diagnostic status check that compares the plugin API keys against the provider API keys, ensuring both are correctly configured and matched for seamless operational connectivity.

What details are included in a Manifest plugin diagnostic table?

A Manifest plugin diagnostic table includes installation status, version, enabled state, operational mode, endpoint, API keys, provider details, default model, model routing settings, and the local database path for comprehensive setup verification.

Can I see the local database path and default model configured for my Manifest plugin?

Yes, you can see the local database path and default model by displaying the current configuration status of the Manifest plugin, which outputs all operational settings for troubleshooting and verification purposes.