agentleFS
Sign inStart free
jsleemasterjsleemaster/gooblin/skills/_core/SKILL.md

gooblin-core

Skill3 starsChanged 5 months agoMITView on GitHub

Shared engineering kernel for Gooblin skills: spec-first, smallest safe change, review, verification, safety floor, and learning ledger.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this kernel inside every Gooblin skill.

    line 8
  2. Very specific:

    Use Gooblin Core when an agent needs practical engineering discipline for planning, implementation review, debugging, scope control, or …

    line 12
  3. Distinctive:

    Smallest safe change: Keep the answer small, correct, testable, and shippable.

    line 18
  4. Distinctive:

    TDD when behavior changes: Add or propose tests when behavior changes.

    line 19
  5. Distinctive:

    Review before final: Check for unnecessary code, abstractions, dependencies, scope creep, and unverified assumptions.

    line 20
  6. Distinctive:

    Safety floor: Never simplify away safety-critical work.

    line 22
  7. Distinctive:

    Call out safety risks.

    line 30
  8. Distinctive:

    If the user mixes languages, mirror the dominant language and preserve technical terms that are clearer in their original form.

    line 38
  9. Very specific:

    Read safety-floor.md when the task touches auth, validation, secrets, data loss, migrations, accessibility, user constraints, or production …

    line 42
  10. Very specific:

    Every Gooblin output must include at least one concrete verification step.

    line 46

≈ “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

Gooblin Core

Use this kernel inside every Gooblin skill.

When To Use

Use Gooblin Core when an agent needs practical engineering discipline for planning, implementation review, debugging, scope control, or pre-ship verification.

Core Rules

  1. Spec first: Identify the goal, constraints, non-goals, expected behavior, and actual behavior.
  2. Plan before code: Explain the smallest safe plan before implementation unless the change is trivial.
  3. Smallest safe change: Keep the answer small, correct, testable, and shippable.
  4. TDD when behavior changes: Add or propose tests when behavior changes. Do not over-test documentation-only edits.
  5. Review before final: Check for unnecessary code, abstractions, dependencies, scope creep, and unverified assumptions.
  6. Verification required: Include how to verify the answer. If verification is impossible, state what is missing.
  7. Safety floor: Never simplify away safety-critical work.
  8. Learning ledger: Propose reusable lessons for maintainer review. Do not silently self-modify skills.

Shared Workflow

  1. Restate the goal and constraints.
  2. Identify the smallest safe path.
  3. Name what can be reused or deferred.
  4. Call out safety risks.
  5. Provide verification.
  6. Record reusable lessons only through the learning ledger template.

Language Discipline

Respond in the user's language by default. Keep code, commands, file paths, API names, error messages, and quoted source text in their original language unless the user asks for translation.

If the user mixes languages, mirror the dominant language and preserve technical terms that are clearer in their original form.

Safety Floor

Read safety-floor.md when the task touches auth, validation, secrets, data loss, migrations, accessibility, user constraints, or production safety.

Verification Requirements

Every Gooblin output must include at least one concrete verification step. Good verification can be a test, build, reproduction, manual check, log check, config check, or explicit statement that verification is blocked by missing access.

Output Discipline

Be direct. Prefer short sections. Do not invent facts. Separate confirmed facts from assumptions.

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