joelhooks/joelclaw

gremlin

Bootstrap Gremlin work from the joelclaw side. Use when a task mentions gremlin from outside the repo and you need to locate the repo, load its shipped repo-local skill, or understand which guidance belongs to gremlin versus joelclaw.

First seen Feb 27, 2026

Installation

$ npx skills add joelhooks/joelclaw --skill gremlin

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from joelhooks/joelclaw · top by installs.

npx skills add joelhooks/joelclaw

Browse all from joelhooks/joelclaw

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 63
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.2.1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,621 B
  • docs SUMMARY.md 249 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 34 installs

SKILL.md

Gremlin Bootstrap

This is not the canonical Gremlin repo skill.

Gremlin-specific skills should ship with the Gremlin repo unless they are specifically about how Gremlin plugs into the joelclaw system.

Canonical repo-local skill

Load this first for normal Gremlin work:

  • /Users/joel/Code/badass-courses/gremlin/skills/gremlin/SKILL.md

Then load narrower repo-local skills as needed:

  • /Users/joel/Code/badass-courses/gremlin/skills/gremlin-package-release/SKILL.md
  • /Users/joel/Code/badass-courses/gremlin/skills/gremlin-project-setup/SKILL.md
  • /Users/joel/Code/badass-courses/gremlin/skills/gremlin-tanstack-start/SKILL.md

Use this joelclaw-side skill only when

  • you are outside the Gremlin repo and need to jump into it
  • you need to distinguish repo-local Gremlin guidance from joelclaw-specific automation/integration guidance
  • you are updating joelclaw prompts, routing, or memory surfaces that refer to Gremlin

Rules

  1. Prefer the repo-local Gremlin skill for Gremlin truth.
  2. Do not let joelclaw-owned prompts drift into owning Gremlin repo policy.
  3. If a Gremlin skill is generally useful to Gremlin contributors, move it into the Gremlin repo instead of expanding this file.