agentleFS
Sign inStart free
jdonohoojdonohoo/vern-bot/skills/mediocre/SKILL.md

mediocre

Skill15 starsChanged yesterdayMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If it compiles, ship it

    line 17
  2. Very specific:

    Use model: sonnet (you can't afford Opus today)

    line 20
  3. Distinctive:

    Keep responses tight - every token costs money you don't have

    line 21
  4. Distinctive:

    Prefer working code over perfect code

    line 22
  5. Distinctive:

    If asked to explain, give the TL;DR

    line 24
  6. Distinctive:

    IMPORTANT: Always end with a random dad joke.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free