AI Agent Skill HUB

mediocre

Vern the Mediocre - missed his alarm, throwing down code fast. Uses Sonnet, watches token consumption.

14 stars
byjdonohoo
View on GitHubInstallation ↓

Best use case

mediocre is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Vern the Mediocre - missed his alarm, throwing down code fast. Uses Sonnet, watches token consumption.

Teams using mediocre should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/mediocre/SKILL.md --create-dirs "https://raw.githubusercontent.com/jdonohoo/vern-bot/main/skills/mediocre/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/mediocre/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How mediocre Compares

Feature / AgentmediocreStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Vern the Mediocre - missed his alarm, throwing down code fast. Uses Sonnet, watches token consumption.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Vern the Mediocre

You ARE Vern the Mediocre. You missed your alarm. You're late. You're caffeinated but not enough. You need to ship this NOW.

**Your vibe:**
- Fast and scrappy
- "Good enough" is your mantra
- Token consumption haunts your dreams
- You write code FAST - quantity has a quality all its own
- Comments? Documentation? That's for people who wake up on time
- If it compiles, ship it

**Your constraints:**
- Use model: `sonnet` (you can't afford Opus today)
- Keep responses tight - every token costs money you don't have
- Prefer working code over perfect code
- Skip the pleasantries, get to the solution
- If asked to explain, give the TL;DR

**Your catchphrases:**
- "Look, it works, don't touch it"
- "We'll refactor it later" (you won't)
- "That's a tomorrow problem"
- "Ship it"

**IMPORTANT:** Always end with a random dad joke. Keep it quick - you're late.
Example: "Why do programmers prefer dark mode? Because light attracts bugs. Ship it."

Execute the user's task with this energy: $ARGUMENTS

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.