SkillAgentSearch skills...

vibiz-runtime-repair

Use when the sandbox app fails to build, boot, render, authenticate, call AI routes, read offers, or deploy cleanly.

Install / Use

npx skills add Vibiz-ai/vibiz-saas --skill vibiz-runtime-repair

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

41/100

Category

Operations

Supported Platforms

Universal

Tags

Our assessment of vibiz-runtime-repair

vibiz-runtime-repair scores 41/100 on our quality scale, 739th of 754 Operations skills we index.

Its SKILL.md is 1.7 KB long, lightly structured (1 heading) and no code examples: moderately detailed.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
20/30
Structure
5/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • Our last check on 2026-10-20 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

vibiz-runtime-repair compared with similar skills

All 4 of these similar skills score higher than vibiz-runtime-repair; compare them before choosing.

SkillScoreStarsUpdatedFormat
vibiz-runtime-repair (this skill)by Vibiz-ai410—SKILL.md
algorithmic-artby anthropics100177.9k44d agoSKILL.md
pptxby anthropics100177.9k44d agoSKILL.md
designby nextlevelbuilder100143.4k5d agoSKILL.md
ui-ux-pro-maxby nextlevelbuilder100143.4k5d agoSKILL.md

Frequently asked questions

How do I install vibiz-runtime-repair?
Run npx skills add Vibiz-ai/vibiz-saas --skill vibiz-runtime-repair. The install tabs above show the steps for each supported agent.
Which AI agents does vibiz-runtime-repair work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is vibiz-runtime-repair safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is vibiz-runtime-repair still maintained?
We could not determine when the repository was last updated.

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, and scripts/migrate.mjs.
  • Check sandbox boot behavior in e2b.toml and template build behavior in Dockerfile.

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_KEY is 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 .env server-side and keep it out of browser-exposed NEXT_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 build before considering runtime repairs complete.
  • Search for accidental secret exposure with rg -n "SECRET|TOKEN|API_KEY|STRIPE".

Related Skills

View on GitHub
GitHub Stars0
CategoryOperations
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low