Convex Cleanup

Run the PromptLens Convex deployment cleanup on explicit user invocation. Do not run on schedules, during ordinary development, or merely because Convex is mentioned. Creating or editing this skill does not invoke cleanup.

An invocation authorizes deleting verified stale temporary deployments and their data. Complete eligible cleanup without another permission question. Retain ambiguous candidates and explain why; ask only if the user wants to expand deletion beyond the verified scope. Do not interpret this skill as authorization to delete production, shared development, or another project's deployments.

Establish the current scope

• Default repository: /Users/akshitkrnagpal/Work/promptlens. Read its applicable AGENTS.md and DEVELOPMENT.md, and start with git status --short.
• Resolve Convex team akn, project promptlens live. Historical project ID 1111599 is a cross-check, not a substitute for checking project identity.
• Resolve current default production and personal development names. At creation they were notable-flamingo-231 and aromatic-narwhal-649; protect these names as well as the current defaults and the main checkout's configured targets.
• Inspect only deployment selectors and public Convex URLs from env files. Never print complete env files, access tokens, deploy keys, or secrets.

Inventory and classify

Use the installed Convex CLI where supported, otherwise the official Management API at https://api.convex.dev/v1. Confirm current API contracts in official documentation before mutations. Existing CLI authentication in ~/.convex/config.json can be read in-process for bearer authentication; never place credentials in shell arguments, tool output, or audit files. If authentication fails, report the blocker instead of provisioning resources or collecting unrelated credentials.

Relevant API operations: