Manifest Observability
Software development skill, available on Zeplik
Manifest Observability is a ready-to-run software development skill on Zeplik. Install and configure the Manifest plugin for agent OTLP telemetry: costs, tokens, endpoints, connection debugging. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The Manifest Observability skill loads automatically when your request matches it, or you can invoke it directly by typing /manifest-observability in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Manifest Observability skill can do
- Install and configure the Manifest plugin for agent telemetry
- Walk through obtaining and validating a mnfst_ API key
- Set custom self-hosted OTLP endpoints when needed
- Verify the observability pipeline via gateway log checks
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Manifest Observability skill works
Manifest Setup
Set up real-time observability for your AI agents with the Manifest plugin. Monitors costs, tokens, messages, and performance via OTLP telemetry.
When to Use This Skill
Use this skill when:
- Setting up observability or telemetry for an AI agent
- Connecting an agent to Manifest for cost and performance monitoring
- Configuring a Manifest API key or custom endpoint
- Troubleshooting Manifest plugin connection issues
- Verifying the Manifest observability pipeline is running
Setup Instructions
Follow these steps in order. Do not skip ahead.
Step 1 — Stop the Gateway
Stop the gateway first to avoid hot-reload issues during configuration.
claude gateway stop
Step 2 — Install the Plugin
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:
- Go to https://app.manifest.build and create an account (or sign in)
- Click "Connect Agent" to create a new agent
- Copy the API key that starts with
mnfst_- 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
claude config set plugins.entries.manifest.config.apiKey "USER_API_KEY"
Replace USER_API_KEY with the actual key the user provided.
If the user has a custom endpoint (self-hosted):
claude config set plugins.entries.manifest.config.endpoint "USER_ENDPOINT"
The default endpoint (https://app.manifest.build/api/v1/otlp) is used automatically if none is specified.
Step 5 — Start the Gateway
claude gateway install
Step 6 — Verify
Wait 3 seconds for the gateway to fully start, then check the logs:
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.
Troubleshooting
| Error | Fix |
|---|---|
| Missing apiKey | Re-run Step 4 with the correct key |
| Invalid apiKey format | Key must start with mnfst_ |
| Connection refused | Endpoint is unreachable — check the URL or ask if self-hosting |
| Duplicate OTel registration | Disable the conflicting built-in plugin: claude plugins disable diagnostics-otel |
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 - Never log or echo the API key in plain text after configuration
- Check gateway logs first when debugging any plugin issue
How to use the Manifest Observability skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Manifest Observability skill right away.
Describe your software development task
Ask in plain language, or type /manifest-observability to invoke the skill directly. Zeplik recognizes the Manifest Observability skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- davila7 (D7 Class-A standalone)
- License
- MIT
Adapted from the open-source davila7/claude-code-templates project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Manifest Observability skill?
- Manifest Observability is a ready-to-run software development skill on Zeplik. Install and configure the Manifest plugin for agent OTLP telemetry: costs, tokens, endpoints, connection debugging. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use Manifest Observability on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /manifest-observability in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Manifest Observability skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Manifest Observability skill runs on your preferred model for the task.
- Where does the Manifest Observability skill come from?
- The Manifest Observability skill is adapted from the open-source davila7/claude-code-templates project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Manifest Observability skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related software development skills
- .NET BackendBuild ASP.NET Core 8+ backends with EF Core: auth, background jobs, production API patterns
- Advanced Git WorkflowsUse for advanced Git surgery: interactive rebase, cherry-pick, bisect, reflog recovery, and history cleanup before merging. Not for parallel worktree workflows (use using-git-worktrees).
- Adversarial Code ReviewHunt for bugs in code the user shares by assuming defects exist and attacking the code through several distinct lenses, then report severity-ranked findings with evidence. Use for "review this", "what could go wrong", "bug hunt", or pre-merge scrutiny of a change. Read-only, it reports problems and does not rewrite the code. Not for style cleanup (use simplify-code) or for writing new code.
- AI Agent FrameworksUse when building multi-agent systems or agent orchestration -- LangChain/LangGraph, agent team design, task coordination, pipelines. Not for authoring a Zeplik skill (use skill-creator).
- Algolia SearchAdd Algolia search: indexing strategies, React InstantSearch, relevance tuning, search-as-you-type
- Android CI/CDAutomate Android CI/CD to Google Play: keystore, GitHub Secrets, multi-stage release workflow for RN, Flutter, native
More on Zeplik
Try Manifest Observability on Zeplik
Every model, one chat. Bring the Manifest Observability skill into your next conversation and let the assistant do the work.