Automated summary
Repairs runtime failures in a sandboxed application by reading exact errors, checking env-dependent code, applying safe patterns that preserve fallback behavior, and verifying with build and secret scans.
Strengths
- Focuses on root cause instead of masking errors.
- Provides specific files and configs to inspect.
- Emphasizes safe fallback patterns and no secret exposure.
- Includes verification steps such as rebuild and secret scanning.
Limitations
- Specific to the described Vibiz codebase structure and stack.
- Assumes a Next.js, E2B sandbox, and deployment conventions.
- Does not cover every possible runtime error.
Use when the sandbox app fails to build, boot, render, authenticate, call AI routes, read offers, or deploy cleanly.
Do not use for feature development or when you need to add new capabilities.
Security analysis
SafeThe skill provides safe repair guidelines for a sandbox app, emphasizing preservation of security guards, avoidance of secret exposure, and using standard debugging tools. There are no instructions for destructive or exfiltrating actions.
No concerns found
How this analysis is madeExamples
The app boots but the landing page shows a 500 and I see a Turso env var missing error in the console. Apply the runtime repair skill to fix it safely.The build fails because SAPIOM_API_KEY is absent during `npm run build`. Make it tolerate missing env keys without exposing secrets.After deploying, auth routes fail. Follow the runtime repair skill to inspect auth.ts, middleware, and api-guard, and apply the safe pattern to preserve landing-page-only mode.name: vibiz-runtime-repair description: Use when the sandbox app fails to build, boot, render, authenticate, call AI routes, read offers, or deploy cleanly. compatibility: opencode
Vibiz Runtime Repair
Repair the real failure. Do not bypass platform contracts to make an error disappear.
Start here:
- Read the exact error, terminal output, browser console, or failing route response.
- Inspect the file named in the stack trace before changing adjacent code.
- Check env-dependent code in
src/lib/auth.ts,src/middleware.ts,src/lib/sapiom.ts,src/lib/api-guard.ts, andscripts/migrate.mjs. - Check sandbox boot behavior in
e2b.tomland template build behavior inDockerfile.
Safe repair patterns:
- If auth is unavailable because Turso env vars are missing, preserve landing-page-only mode and existing guards.
- If AI routes fail because
SAPIOM_API_KEYis missing, keep server-only behavior and return a clear unavailable state. - If a user-supplied third-party integration truly requires a runtime key, put it in
.envserver-side and keep it out of browser-exposedNEXT_PUBLIC_*vars unless the key is designed to be public. - If offers are missing, preserve
getSeededOffers()fallback behavior and do not fabricate seeded offers. - If Tailwind fails, fix class/config/CSS compatibility instead of removing whole sections.
- If Next build fails from runtime-only env assumptions, make the code tolerate absent envs during build without exposing secrets or disabling production behavior.
Verification:
- Run the failing command again after each targeted fix.
- Run
npm run buildbefore considering runtime repairs complete. - Search for accidental secret exposure with
rg -n "SECRET|TOKEN|API_KEY|STRIPE".
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/vibiz-runtime-repair-msh3uub6/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/vibiz-runtime-repair-msh3uub6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/vibiz-runtime-repair-msh3uub6/download' --output '.skill-downloads/vibiz-runtime-repair-msh3uub6/SKILL.md.part' && mv '.skill-downloads/vibiz-runtime-repair-msh3uub6/SKILL.md.part' '.skill-downloads/vibiz-runtime-repair-msh3uub6/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Environment declared by the author: opencode
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/vibiz-runtime-repair-msh3uub6'openskills read 'vibiz-runtime-repair-msh3uub6'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/vibiz-runtime-repair-msh3uub6/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.