New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Superloopy Doctor

by beefiker in beefiker/superloopy

A read-only health check for a Superloopy install or checkout: state folders, evidence files, bundled agents, hooks, wrapper and plugin registration, reported before any repair.

MITAuto-check passedAgent Workflows

Install Superloopy Doctor

skills CLI
$ npx skills add beefiker/superloopy --skill superloopy-doctor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install beefiker/superloopy superloopy-doctor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/beefiker/superloopy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/superloopy-doctor .claude/skills/superloopy-doctor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
superloopy-doctor
GitHub stars
111
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
897 words
Files
2
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

A read-only health check for a Superloopy install or checkout: state folders, evidence files, bundled agents, hooks, wrapper and plugin registration, reported before any repair.

  • Works in 11 steps: Identify the target root: pwd, git… → Locate the user-visible command: command… → Inspect Codex registry state with codex… → …
  • Superloopy hooks or bundled agents do not seem to load
  • SKILL.md covers Native Boundary, Installed-plugin Authority, Diagnostic Spine and Verdict Rules, plus 3 more sections
  • Calls codex, node and git

What it does

The skill proves whether a local Superloopy surface can support the Superloopy loop, looking at repo-local .superloopy state, artifact-backed evidence under .superloopy/evidence, bundled crew agents, hook steering and the deterministic completion floor. It is read-only by default and changes no plugin config, wrappers, agents, caches or sources unless you ask for repair after seeing the report.

Two doctor scopes give the verdict, source for a checkout and installed for the machine, each with JSON output, and loop status, check and guide commands show plan and evidence readiness. A separate probe asks Codex which plugin version is registered instead of guessing from cache folder names, and reports one of four states: current, version_mismatch, not_registered or authority_unavailable. It avoids cloning outside repos or comparing unrelated harnesses unless you ask.

When your agent uses it

  • Superloopy hooks or bundled agents do not seem to load
  • Checking whether the installed plugin matches the source checkout
  • Diagnosing stale-version or wrapper problems with Codex or Claude Code

Example prompts

  • “Run the Superloopy doctor for the installed scope and tell me what is unhealthy.”
  • “Check whether my Superloopy checkout and the installed plugin are the same version.”

Requirements

  • The superloopy CLI
  • Optionally the Codex CLI for the installed-plugin check

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Identify the target root: pwd, git rev-parse --show-toplevel when it is a checkout, and the installed plugin cache path when the wrapper…
  2. Locate the user-visible command: command -v superloopy, which -a superloopy, and the wrapper text or symlink target.
  3. Inspect Codex registry state with codex plugin list --json when Codex is available; use it only to locate superloopy@beefiker and its…
  4. Run the matching scoped command and record the reported scope and root. For checkout health use superloopy doctor --root --scope source…
  5. Read the named doctor checks, especially skills, fileAudit, reviewability, dispatchCoherence, hostContract, modelPolicy, and…
  6. Probe loop readiness without changing state: use superloopy loop status --json if a plan exists, otherwise note "no active plan" instead…
  7. Verify crew install shape by name: franky, zoro, usopp, jinbe, robin, and nami; judge by files and doctor checks, not by role labels alone.
  8. If managed state is absent, distinguish no fleet from an exact hash-known legacy fleet and an unmanaged/edited conflict. Exact legacy…
  9. Compare the generated wrapper target with the diagnosed plugin root and report a split-brain warning when they differ.
  10. Report configured model routing as model_unverified unless the host attests both the resolved role and model.
  11. Report PASS, WARN, or FAIL with command output, file path, or JSON check evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 4bb19dd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • codex
    • node
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Superloopy Doctor loads about 1.9k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 897 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from beefiker/superloopy at commit 4bb19dd, republished under its MIT licence (© beefiker). 897 words, ~1,913 tokens.

Download SKILL.mdSave it as .claude/skills/superloopy-doctor/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
superloopy-doctor
description
Use when diagnosing Superloopy doctor, install, wrapper, plugin cache, hook bootstrap, bundled agents, marketplace, Codex, Claude Code, stale-version, evidence-floor, or host-wiring health problems.
metadata.short-description
Diagnose Superloopy install and bootstrap health

superloopy-doctor

SUPERLOOPY DOCTOR ENABLED

Use this skill to prove whether a local Superloopy surface can support the Superloopy loop: repo-local .superloopy/ state, artifact-backed evidence under .superloopy/evidence/, bundled crew agents, hook steering, and the deterministic completion floor. It is read-only by default. Do not mutate plugin config, wrappers, agents, caches, or source files unless the user explicitly asks for repair after seeing the report.

Native Boundary

This is a Superloopy health check, not a generic plugin drift audit.

  • Treat superloopy doctor --scope source --json as the source-checkout truth surface and superloopy doctor --scope installed --json as the machine-local installation truth surface. The JSON scope field records which verdict contract was used.
  • Treat loop commands as the behavioral truth surface, but keep their limits clear: superloopy loop status --json, superloopy loop check, superloopy loop guide --json, and evidence files under .superloopy/evidence/ can show current plan and artifact readiness.
  • Read the installed plugin cache only to identify which Superloopy code the wrapper runs.
  • Do not clone external repos, search issue trackers, or compare unrelated harness layouts unless the user separately asks for research.
  • superloopy doctor reports the plugin root it checked: by default it uses source scope in a recognized Superloopy checkout and installed scope elsewhere. Pin a checkout with superloopy doctor --root <checkout> --scope source --json; pin an installed cache with superloopy doctor --root <cache> --scope installed --json. Source verdicts still return machine-local diagnostics, but installedModelPolicy and wrapper do not gate source health.

Installed-plugin Authority

installedPluginTruth runs the read-only codex plugin list --json authority probe for superloopy@beefiker; it never infers the installed version from cache directory names. A confirmed version mismatch is informational in source scope, but fails installed scope. Missing Codex, no registered plugin, and invalid authority output are informational and do not fail doctor. Report these four states as current, version_mismatch, not_registered, or authority_unavailable; never repair from this probe without explicit approval.

Diagnostic Spine

  1. Identify the target root: pwd, git rev-parse --show-toplevel when it is a checkout, and the installed plugin cache path when the wrapper points into one.
  2. Locate the user-visible command: command -v superloopy, which -a superloopy, and the wrapper text or symlink target.
  3. Inspect Codex registry state with codex plugin list --json when Codex is available; use it only to locate superloopy@beefiker and its version.
  4. Run the matching scoped command and record the reported scope and root. For checkout health use superloopy doctor --root <checkout> --scope source --json; for a machine-local wrapper, managed-agent fleet, or installed cache use superloopy doctor --root <cache> --scope installed --json.
  5. Read the named doctor checks, especially skills, fileAudit, reviewability, dispatchCoherence, hostContract, modelPolicy, and claudeHostWiring.
  6. Probe loop readiness without changing state: use superloopy loop status --json if a plan exists, otherwise note "no active plan" instead of creating one. Use superloopy loop check only to validate trace/artifact readiness for an existing plan; read-only diagnosis cannot prove completion safety because it does not re-run recorded commands. If the user asks whether completion is actually safe, point at the real gates: superloopy loop review, superloopy loop checkpoint, or superloopy loop finish.
  7. Verify crew install shape by name: franky, zoro, usopp, jinbe, robin, and nami; judge by files and doctor checks, not by role labels alone.
  8. If managed state is absent, distinguish no fleet from an exact hash-known legacy fleet and an unmanaged/edited conflict. Exact legacy fleets can migrate without --force; never infer ownership from names alone.
  9. Compare the generated wrapper target with the diagnosed plugin root and report a split-brain warning when they differ.
  10. Report configured model routing as model_unverified unless the host attests both the resolved role and model.
  11. Report PASS, WARN, or FAIL with command output, file path, or JSON check evidence.
Show full SKILL.md (277 more words)Show less

Verdict Rules

  • PASS: wrapper/cache/checkout, superloopy doctor --json, and relevant loop/evidence surfaces agree within read-only limits.
  • WARN: Superloopy can run, but a wrapper points at an older cache, no active plan exists for loop readiness, read-only mode cannot prove completion safety, host behavior is advisory only, or manual evidence cannot be command-replayed.
  • FAIL: doctor named checks fail, wrapper is absent or points at the wrong root, required agents are missing, .superloopy/ state is corrupt, or the deterministic completion floor cannot be evaluated.

Repair Guidance

Recommend repair commands only after the read-only report explains the failure:

  • Marketplace refresh: codex plugin marketplace upgrade beefiker.
  • Confirmed installedPluginTruth mismatch after approval: codex plugin add superloopy@beefiker --json, then start a new Codex session.
  • Checkout install: node src/cli.js install --json.
  • Forced local wrapper/agent overwrite: node src/cli.js install --force --json.

Never run install --force, plugin remove, marketplace remove, cache deletion, or wrapper deletion without explicit user approval.

Report Format

text
Superloopy doctor report
Summary: <healthy/degraded/broken in one sentence>

| Check | Verdict | Evidence |
| --- | --- | --- |
| Command wrapper | PASS/WARN/FAIL | <path, target, cache or checkout root> |
| Doctor checks | PASS/WARN/FAIL | <ok=true or failing check names> |
| Evidence floor | PASS/WARN/FAIL | <.superloopy/evidence/, loop check/status readiness, or "completion safety requires the real gate"> |
| Crew install | PASS/WARN/FAIL | <agent files and dispatchCoherence evidence> |
| Host limits | PASS/WARN/FAIL | <hostContract/claudeHostWiring evidence> |
| Reviewability/native boundary | PASS/WARN/FAIL | <reviewability/fileAudit/designAudit evidence> |

Recommended repair:
- <exact command or "none">

Hard Rules

  • Read-only by default.
  • Diagnose Superloopy's own contract: package, hooks, skills, CLI, dependency-free boundary, runtime ignore policy, file inventory, design audit, dispatch coherence, model policy, host contract, reviewability, and deterministic completion floor.
  • Treat stale wrappers and stale installed plugin caches as separate findings; a marketplace refresh alone is not proof.
  • Do not claim a marketplace upgrade fixed anything until the wrapper and superloopy doctor --json prove it.
  • Do not mark a loop completion-safe from status or superloopy loop check alone; those are read-only readiness signals. Completion safety requires the real gate path (superloopy loop review, superloopy loop checkpoint, or superloopy loop finish) because those gates re-derive command-backed criteria.
  • If terminal capability noise affects host commands, rerun with a normal terminal environment before recording a failure.

© beefiker, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/superloopy-doctor of beefiker/superloopy.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 4bb19dd

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in beefiker/superloopy, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Superloopy Doctor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Superloopy Doctor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Superloopy Doctor this skillbeefiker/superloopy1111 repos~1.9kAutomated safety check: PassMIT
Plugin CreatoruseLexora/Lexora565—~1kAutomated safety check: PassAGPL-3.0
Nonstop Autonomous Modeandylizf/nonstop263—~2kAutomated safety check: WarnMIT
Plugin Dev Workflowoliver-kriska/claude-elixir-phoenix565—~1kAutomated safety check: PassMIT
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Plugin Creator

    useLexora/Lexora

    创建、修改并验证可安装的 Lexora 桌面插件，包括工作台装饰、导航与面板、文件阅读工具、控件样式、网络查询、通知和定时命令。也响应 $plugin-creator。普通任务执行、使用现有插件、其他产品的插件开发不属于此技能。

    565 GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Nonstop Autonomous Mode

    andylizf/nonstop

    Lets Claude keep working while you are away, after a pre-flight that surfaces blockers, risky operations and open decisions, with a stop hook scoped to the session.

    263 GitHub stars~2k tokensUpdated 6 mo ago
    Agent WorkflowsAuto-check: warnings

  • Plugin Dev Workflow

    oliver-kriska/claude-elixir-phoenix

    Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo.

    565 GitHub stars~1k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

More from beefiker/superloopy

All 9 skills in this repo

  • Humanize Korean Prose

    beefiker/superloopy

    Rewrites already-written Korean text to remove AI-sounding rhythm and translationese while keeping its meaning, register, facts and protected terms untouched.

    111 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Superloopy Backend Routing

    beefiker/superloopy

    Routes backend work in the Superloopy loop harness to the right reference module, covering API contracts, schema migrations, transactions, background jobs, caching and security.

    111 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed

  • Superloopy Slides

    beefiker/superloopy

    Creates zero-dependency, animation-rich HTML slide decks that run in the browser, with style presets, PowerPoint conversion and PDF export, proven by a real-browser render.

    111 GitHub starsUsed in 1 repo~8.8k tokens
    Auto-check passed

  • Superloopy Evidence Loop

    beefiker/superloopy

    Runs a light task loop where each goal criterion passes only when a real evidence artifact exists, with progress stored in a `.superloopy` folder.

    111 GitHub starsUsed in 1 repo~5.9k tokens
    Auto-check passed

  • ADHD-Friendly Output Style

    beefiker/superloopy

    Reshapes the agent's replies for an ADHD-friendly reading style: the next action first, numbered single-action steps, visible progress and one concrete action at the end.

    111 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • Say It Straight

    beefiker/superloopy

    Use only after explicit Codex $superloopy:say-it-straight or Claude Code /superloopy:say-it-straight invocation to make supplied or requested prose direct, concise, and natural without changing…

    111 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

Categories

Questions about Superloopy Doctor

What does Superloopy Doctor do?

A read-only health check for a Superloopy install or checkout: state folders, evidence files, bundled agents, hooks, wrapper and plugin registration, reported before any repair. superloopy/evidence, bundled crew agents, hook steering and the deterministic completion floor. It is read-only by default and changes no plugin config, wrappers, agents, caches or sources unless you ask for repair after seeing the report.

When should I use Superloopy Doctor?

Superloopy Doctor fits situations like: superloopy hooks or bundled agents do not seem to load; checking whether the installed plugin matches the source checkout; diagnosing stale-version or wrapper problems with Codex or Claude Code.

How do I install Superloopy Doctor in Claude Code?

Run `npx skills add beefiker/superloopy --skill superloopy-doctor -a claude-code`. Or copy the skill folder (skills/superloopy-doctor in beefiker/superloopy) into .claude/skills/superloopy-doctor in your project. Claude Code loads it when a task matches its description.

How do I install Superloopy Doctor in Codex?

Run `npx skills add beefiker/superloopy --skill superloopy-doctor -a codex`. Or copy the skill folder (skills/superloopy-doctor in beefiker/superloopy) into .agents/skills/superloopy-doctor in your project. Codex loads it when a task matches its description.

Can I use Superloopy Doctor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add beefiker/superloopy --skill superloopy-doctor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superloopy-doctor, .gemini/skills/superloopy-doctor, .github/skills/superloopy-doctor and .opencode/skills/superloopy-doctor in your project.

What does Superloopy Doctor need to run?

Going by SKILL.md and its folder, Superloopy Doctor needs the command-line tools its instructions call (codex, node and git). Our summary lists: The superloopy CLI; Optionally the Codex CLI for the installed-plugin check.

Does Superloopy Doctor access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Superloopy Doctor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Superloopy Doctor use?

Superloopy Doctor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Superloopy Doctor use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Superloopy Doctor?

Skills that share tags, products or a category with Superloopy Doctor: Plugin Creator (useLexora/Lexora, 565 stars), Nonstop Autonomous Mode (andylizf/nonstop, 263 stars), Plugin Dev Workflow (oliver-kriska/claude-elixir-phoenix, 565 stars) and Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Superloopy Doctor?

beefiker (a GitHub user) maintains it in beefiker/superloopy, which has 111 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.

Source: beefiker/superloopy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.