manifest
Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.
Best use case
manifest is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.
Teams using manifest should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/manifest/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How manifest Compares
| Feature / Agent | manifest | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Manifest Setup Follow these steps **in order**. Do not skip ahead. ## Use this skill when - User wants to set up observability or telemetry for their agent - User wants to connect their agent to Manifest for monitoring - User needs to configure a Manifest API key or custom endpoint - User is troubleshooting Manifest plugin connection issues - User wants to verify the Manifest plugin is running ## Do not use this skill when - User needs general observability design (use `observability-engineer` instead) - User wants to build custom dashboards or alerting rules - User is not using the Manifest platform ## Instructions ### Step 1 — Stop the gateway Stop the gateway first to avoid hot-reload issues during configuration. ```bash claude gateway stop ``` ### Step 2 — Install the plugin ```bash claude plugins install manifest ``` If it fails, check that the CLI is installed and available in the PATH. ### Step 3 — Get an API key Ask the user: > To connect your agent, you need a Manifest API key. Here's how to get one: > > 1. Go to **https://app.manifest.build** and create an account (or sign in) > 2. Once logged in, click **"Connect Agent"** to create a new agent > 3. Copy the API key that starts with `mnfst_` > 4. Paste it here Wait for a key starting with `mnfst_`. If the key doesn't match, tell the user the format looks incorrect and ask them to try again. ### Step 4 — Configure the plugin ```bash claude config set plugins.entries.manifest.config.apiKey "USER_API_KEY" ``` Replace `USER_API_KEY` with the actual key the user provided. Ask the user if they have a custom endpoint. If not, the default (`https://app.manifest.build/api/v1/otlp`) is used automatically. If they do: ```bash claude config set plugins.entries.manifest.config.endpoint "USER_ENDPOINT" ``` ### Step 5 — Start the gateway ```bash claude gateway install ``` ### Step 6 — Verify Wait 3 seconds for the gateway to fully start, then check the logs: ```bash grep "manifest" ~/.claude/logs/gateway.log | tail -5 ``` Look for: ``` [manifest] Observability pipeline active ``` If it appears, tell the user setup is complete. If not, check the error messages and troubleshoot. ## Safety - Never log or echo the API key in plain text after configuration - Verify the key format (`mnfst_` prefix) before writing to config ## Troubleshooting | Error | Fix | |-------|-----| | Missing apiKey | Re-run step 4 | | Invalid apiKey format | The key must start with `mnfst_` | | Connection refused | The endpoint is unreachable. Check the URL or ask if they self-host | | Duplicate OTel registration | Disable the conflicting built-in plugin: `claude plugins disable diagnostics-otel` | ## Examples ### Example 1: Basic setup ``` Use @manifest to set up observability for my agent. ``` ### Example 2: Custom endpoint ``` Use @manifest to connect my agent to my self-hosted Manifest instance at https://manifest.internal.company.com/api/v1/otlp ``` ## Best Practices - Always stop the gateway before making configuration changes - The default endpoint works for most users — only change it if self-hosting - API keys always start with `mnfst_` — any other format is invalid - Check gateway logs first when debugging any plugin issue ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
k8s-manifest-generator
Step-by-step guidance for creating production-ready Kubernetes manifests including Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
ckm:ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
ckm:design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.
ckm:design-system
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
ckm:brand
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.