Agent skill · operations · sickn33
manifest
Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.
Why this skill is useful
Adds specific commands and configurations for setting up the Manifest observability plugin that the AI wouldn't reliably generate on its own.
What it needs
Requires claude installed locally. Requires manifest account access. About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Manifest setup and verification When to Use Configure an explicitly requested Manifest telemetry or gateway integration. Diagnose missing authorized telemetry without changing unrelated provider routing. Availability This AAS tree bundles instructions, not a plugin, CLI or gateway. Identify the actual host, installed versions and current supported Manifest integration from official documentation. The historical claude gateway / claude plugins commands in earlier copies are not a verified Claude Code setup contract; do not run them or infer a host configuration path. Telemetry-only setup and routing all inference through a gateway are distinct changes. Use the user's requested scope and preserve existing providers, credentials and other host entries. Procedure 1. Inspect the current authorized integration and target account/endpoint. Verify available tools or CLI help and the exact package/source version. Back up affected configuration privately before a scoped edit. 2. Reuse an existing authorized credential through the host's private credential mechanism. If absent, let the user enter it in the service or a supported local secret interface; never ask them to paste a key in chat or put it in shell arguments. A prefix check is not authentication proof. 3. Establish what data will leave the host: prompts, responses, account identifiers, costs, tool traces and error payloads. Choose actual redaction/retention controls and obtain authorization for private transmission and provider charges. Do not assume metadata-only telemetry when full-body logging is enabled. 4. Prepare the concrete supported configuration for the selected integration. Use HTTPS for remote endpoints and reject userinfo/unintended redirects; local loopback may be appropriate for a separately reviewed self-hosted service. Change only the authorized entries. Restart only the relevant service when the integration actually requires it; preserve other running tasks. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/manifest