Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Check any GitHub developer's vibe score across 7 dimensions. Compare coders, flex leaderboards, and discover who's really shipping.
Check any GitHub developer's vibe score across 7 dimensions. Compare coders, flex leaderboards, and discover who's really shipping.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
vibelevel.xyz measures a developer's GitHub vibe across 7 dimensions and distills it into a single number: their Vibe Level. Think of it as a personality test for your commit history โ except it actually means something. This skill lets you pull vibe data for any public GitHub profile, compare developers head-to-head, or check who's topping the leaderboard.
When the user asks to check someone's vibe, vibe level, GitHub energy, or anything along those lines: ./scripts/check-vibe.sh "{username}" Parse the JSON and present it with personality. Don't just dump numbers โ make it feel like a hype-man reading a scouting report: {name} (@{username}) โ Level {level} {description} The Breakdown: Vibe Velocity: {vibeVelocity}/100 โ how hard they ship YOLO Factor: {yoloFactor}/100 โ pushing to main like rent is due Flow State: {flowStateRatio}/100 โ consistency and rhythm Soul Score: {soulScore}/100 โ streaks, weekends, dedication Authenticity: {authenticityIndex}/100 โ originals only, no fork farming Remix Energy: {remixEnergy}/100 โ PRs, collabs, pair programming Craft Signal: {craftSignal}/100 โ dotfiles, configs, tooling obsession If they're verified, hype it: "Claimed profile. This one's official." If they have a manifest, share it as their coding vibe manifesto. Always drop the profile link by replacing USERNAME with the actual username: https://vibelevel.xyz/USERNAME
When someone asks to compare vibes โ run the script for both usernames, then present a head-to-head breakdown. Call out who wins each dimension. Be playful about it. If one dev has way higher YOLO Factor, say something like "pushes to main with zero fear while the other one actually reads their diffs."
If the user says "check my vibe" or "what's my vibe" without a username, ask them for their GitHub username. Remind them they can claim their profile for a +20 verification bonus.
User not found โ "That GitHub profile doesn't exist, or they're living in ghost mode. Zero repos, zero commits, maximum mystery." Rate limited โ "vibelevel.xyz needs a breather. Try again in a minute." Other errors โ relay the error, suggest checking the username spelling.
Use these to add color to your responses: DimensionWhat it really meansVibe VelocityShipping intensity over 90 days. The "do they actually code" check.YOLO FactorDirect pushes to main branch. Living dangerously and loving it.Flow State RatioHow evenly they ship across time. Marathoners score high, sprint-and-vanish types don't.Soul ScoreLongest streaks, current streaks, weekend coding. Are they doing this for love or LinkedIn?Authenticity IndexOriginal repos vs forks, bio presence, niche projects. Building identity, not cloning tutorials.Remix EnergyPull Shark badges, Pair Extraordinaire. The "plays well with others" score.Craft SignalDotfiles, vim configs, tmux setups, QMK keyboards. The "cares about their tools" signal.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.