← Back to Skills Marketplace
Convex Deploy Env Doctor
by
okikeSolutions
· GitHub ↗
· v0.1.0
· MIT-0
116
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install convex-deploy-env-doctor
Description
Validate and fix Convex deployment configuration for skills/apps. Use when debugging Convex URL/callback/env issues, OAuth callback mismatches, .site vs .clo...
README (SKILL.md)
Convex Deploy + Env Doctor
Workflow
- Detect project config surface
- Check
.env,.env.example, runtime defaults in source, README/SKILL docs. - Extract all Convex URLs and callback URLs.
- Validate URL consistency
- Ensure one canonical backend URL intent (
.cloudfor API by default). - Flag mixed
.site/.cloudusage and explain where each is appropriate. - Ensure callback URLs match provider/app configuration.
- Validate required env vars
- Check required/optional env keys and whether docs match runtime usage.
- Flag hidden defaults that route data unexpectedly.
- Connectivity sanity check
- Run lightweight checks (lint/build and safe HTTP reachability if possible).
- Confirm configured backend is HTTPS and syntactically valid.
- Output
- Return:
- ✅ Passing checks
- ❌ Failing checks
- exact file-level patches required
- post-fix verification commands
- explicit data-routing disclosure (what endpoints/services were touched)
Output format
Use references/output-template.md.
Guardrails
- Never print secrets.
- Prefer minimal patch release changes.
- Keep docs and runtime behavior aligned.
- Include file+line evidence for each failing check.
Usage Guidance
This skill appears to do what it says, but it actively inspects project config files (.env, source defaults, READMEs) and can make outbound HTTP checks. Before running it: 1) Run it only in a trusted environment or on a repository copy that does not contain production secrets. 2) If you must run against real config files, ensure the agent/process will redact or mask secrets and that outputs are reviewed before sharing. 3) Expect the skill to contact discovered endpoints for reachability checks—if you need to restrict network access, run it offline or with an allowlist. 4) Ask the skill author (or require) an explicit policy for masking secrets in 'file+line evidence' and for what data is sent externally. 5) After fixes, verify changes manually (the skill suggests post-fix commands); do not auto-apply patches to production without inspection.
Capability Analysis
Type: OpenClaw Skill
Name: convex-deploy-env-doctor
Version: 0.1.0
The skill bundle is a utility designed to validate and fix Convex deployment configurations. Its workflow involves reading local environment files, checking URL consistency, and performing connectivity checks, all of which are aligned with its stated purpose. The instructions in SKILL.md include explicit guardrails against printing secrets and require a data-routing disclosure in the output (references/output-template.md), demonstrating a focus on transparency and security.
Capability Assessment
Purpose & Capability
Name/description (Convex deployment/env doctor) match the instructions: locate Convex URLs/callbacks, check .env and docs, validate callbacks and connectivity. The skill doesn't request unrelated credentials, binaries, or install steps.
Instruction Scope
Instructions explicitly tell the agent to read .env/.env.example, runtime defaults in source, and provide file+line evidence and exact file-level patches. That is in-scope for configuration validation, but it increases the risk of exposing secrets. The workflow also includes 'safe HTTP reachability' checks that will cause outbound requests to discovered endpoints — appropriate for verification but not constrained (no allowlist or explicit sanitization steps). The SKILL.md includes a guardrail 'Never print secrets' but does not require masking when producing file-level evidence or transmitting results.
Install Mechanism
Instruction-only skill with no install spec or bundled code. This minimizes supply-chain and install-time risk.
Credentials
The skill declares no required env vars (proportionate), but its runtime instructions will read environment/config files (.env, runtime defaults). Reading those files is reasonable for the stated purpose but is not reflected in the manifest as required access and may surface secrets if outputs are not carefully redacted.
Persistence & Privilege
No always:true, no install or persistence steps, and no instructions to modify other skills or global agent settings. Normal user-invocable behavior and not force-included.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install convex-deploy-env-doctor - After installation, invoke the skill by name or use
/convex-deploy-env-doctor - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release: adds routing disclosure + file/line evidence requirements in workflow and output template.
Metadata
Frequently Asked Questions
What is Convex Deploy Env Doctor?
Validate and fix Convex deployment configuration for skills/apps. Use when debugging Convex URL/callback/env issues, OAuth callback mismatches, .site vs .clo... It is an AI Agent Skill for Claude Code / OpenClaw, with 116 downloads so far.
How do I install Convex Deploy Env Doctor?
Run "/install convex-deploy-env-doctor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Convex Deploy Env Doctor free?
Yes, Convex Deploy Env Doctor is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Convex Deploy Env Doctor support?
Convex Deploy Env Doctor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Convex Deploy Env Doctor?
It is built and maintained by okikeSolutions (@okikesolutions); the current version is v0.1.0.
More Skills