Vibelevel Analyzer

Check any GitHub developer's vibe score across 7 dimensions. Compare coders, flex leaderboards, and discover who's really shipping.

Security Scan

The skill does what it says: it fetches public 'vibe' data from vibelevel.xyz for a given GitHub username and has no hidden credential or filesystem access.

Purpose & Capability

Name/description match the implementation: the script fetches vibe data for a GitHub username from https://vibelevel.xyz/api/vibe/{username}. No unrelated credentials, paths, or binaries are requested that would be unnecessary for this purpose.

Instruction Scope

SKILL.md instructs the agent to run scripts/check-vibe.sh and parse the returned JSON for presentation. The included script only uses curl and returns JSON; it does not read other files or credentials. Minor mismatch: SKILL.md and metadata list jq as required for JSON parsing, but the script itself does not call jq — the agent is expected to parse the JSON (jq would be a convenient tool).

Install Mechanism

This is an instruction-only skill with a small included shell script. There is no install spec, no downloads, and nothing written to disk beyond the provided script. Low install risk.

Credentials

No environment variables, secrets, or config paths are requested. The only required binaries are curl (used) and jq (declared but not used by the script). No sensitive credentials are needed; the skill only sends public GitHub usernames to a third-party API.

Persistence & Privilege

always:false and default invocation settings. The skill does not request permanent presence or modify other skills or system configs.

Assessment

This skill simply queries the public API at vibelevel.xyz with a GitHub username and returns JSON. Before installing, consider: (1) requests will go to an external third-party (vibelevel.xyz) — if you don't want your queries logged there, don't use it; (2) no secrets are required and nothing on disk is modified by the skill; (3) metadata lists jq although the script itself doesn't invoke it — the agent may use jq to format results but it's optional; (4) because the source/homepage are minimal, you may want to visit vibelevel.xyz to confirm you trust the service. Overall the package is coherent with its stated purpose and has low technical risk.

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.

Check a user's vibe

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

Compare two users

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."

Check your own vibe

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.

Error handling

• 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.

Dimension cheat sheet

Use these to add color to your responses:

Dimension	What it really means
Vibe Velocity	Shipping intensity over 90 days. The "do they actually code" check.
YOLO Factor	Direct pushes to main branch. Living dangerously and loving it.
Flow State Ratio	How evenly they ship across time. Marathoners score high, sprint-and-vanish types don't.
Soul Score	Longest streaks, current streaks, weekend coding. Are they doing this for love or LinkedIn?
Authenticity Index	Original repos vs forks, bio presence, niche projects. Building identity, not cloning tutorials.
Remix Energy	Pull Shark badges, Pair Extraordinaire. The "plays well with others" score.
Craft Signal	Dotfiles, vim configs, tmux setups, QMK keyboards. The "cares about their tools" signal.