New: 97,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

Helmor Debug Loop

by dohooo in dohooo/helmor

Autonomous local-development debugging loop for Helmor bugs.

Apache-2.0Auto-check passedDevelopment

Install Helmor Debug Loop

skills CLI
$ npx skills add dohooo/helmor --skill helmor-debug-loop -a claude-code

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

GitHub CLI
$ gh skill install dohooo/helmor helmor-debug-loop --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/dohooo/helmor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/helmor-debug-loop .claude/skills/helmor-debug-loop && 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
helmor-debug-loop
GitHub stars
1.3k
Token cost
~917 tokens
SKILL.md length
444 words
Files
5 (incl. scripts, references)
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Autonomous local-development debugging loop for Helmor bugs.

  • Works in 6 steps: Define the suspected behavior, expected… → Reproduce through $helmor-debug-operate… → If evidence is insufficient, add the… → …
  • The user asks an agent to reproduce
  • SKILL.md covers Core Loop, Fault Tolerance and Evidence Sources
  • Runs Python scripts from its folder

What it does

Helmor Debug Loop is an agent skill from dohooo/helmor. Autonomous local-development debugging loop for Helmor bugs. Use when the user asks an agent to reproduce, diagnose, instrument, fix, or verify a Helmor local dev build issue using repeated local UI simulation, temporary logging, Tauri MCP/towery MCP, screenshots, DOM/accessibility snapshots, IPC traces, console/system logs, terminal/run-script logs, or multi-attempt verification. This skill coordinates with $helmor-debug-operate for operating the running desktop app.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/debug-loop.md` and `scripts/build_evidence_pack.py`).

It sits in Development, covering Debugging and Accessibility. It works with Model Context Protocol and Tauri. The repository describes itself as: Open-source local workbench for multi-agent software development. The licence is Apache-2.0.

When your agent uses it

  • The user asks an agent to reproduce
  • Verify a Helmor local dev build issue using repeated local UI simulation
  • Temporary logging
  • Tauri MCP/towery MCP

Example prompts

  • “/helmor-debug-loop”

Requirements

  • Python 3

Workflow steps

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

  1. Define the suspected behavior, expected behavior, and success signal in one or two sentences.
  2. Reproduce through $helmor-debug-operate with real UI actions when possible. Start with screenshots, DOM/accessibility snapshots, IPC…
  3. If evidence is insufficient, add the smallest temporary log or probe with a unique prefix such as [debug-loop:], rerun the flow, then…
  4. Analyze the evidence before editing product code. Prefer a narrow fix that explains the observed signal.
  5. Verify the fix with the same user path. For user-visible flows, require three consecutive successful runs unless the user explicitly…
  6. Produce an evidence pack under .agent-contexts// with repro attempts, logs, screenshots, IPC, fix summary, and remaining uncertainty.

What it can do on your machine

Read from SKILL.md and the folder at commit a76cda1. 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

    Ships 2 files in scripts/ (Python), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

    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

Helmor Debug Loop loads about 917 tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 123 tokens; SKILL.md has 444 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~123
When it runs · the whole SKILL.md, loaded when a task matches
~917
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from dohooo/helmor at commit a76cda1, republished under its Apache-2.0 licence (© dohooo). 444 words, ~917 tokens.

Download SKILL.mdSave it as .claude/skills/helmor-debug-loop/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
helmor-debug-loop
description
Autonomous local-development debugging loop for Helmor bugs. Use when the user asks an agent to reproduce, diagnose, instrument, fix, or verify a Helmor local dev build issue using repeated local UI simulation, temporary logging, Tauri MCP/towery MCP, screenshots, DOM/accessibility snapshots, IPC traces, console/system logs, terminal/run-script logs, or multi-attempt verification. This skill coordinates with $helmor-debug-operate for operating the running desktop app.

Helmor Debug Loop

Use this skill to drive a bounded reproduce -> instrument -> inspect -> fix -> verify loop for Helmor local-dev bugs. Always use $helmor-debug-operate for actual local app control through Tauri MCP; this skill owns the debugging strategy and evidence discipline.

Core Loop

  1. Define the suspected behavior, expected behavior, and success signal in one or two sentences.
  2. Reproduce through $helmor-debug-operate with real UI actions when possible. Start with screenshots, DOM/accessibility snapshots, IPC monitor, console/system logs, and terminal buffers.
  3. If evidence is insufficient, add the smallest temporary log or probe with a unique prefix such as [debug-loop:<slug>], rerun the flow, then remove or justify the probe before finalizing.
  4. Analyze the evidence before editing product code. Prefer a narrow fix that explains the observed signal.
  5. Verify the fix with the same user path. For user-visible flows, require three consecutive successful runs unless the user explicitly lowers the bar.
  6. Produce an evidence pack under .agent-contexts/<task-slug>/ with repro attempts, logs, screenshots, IPC, fix summary, and remaining uncertainty.

Fault Tolerance

  • If you cannot reproduce after three distinct attempts, do not invent a failure. Mark the state as not reproduced, preserve evidence, inspect code paths that should have fired, and report the most likely missing precondition.
  • If the bug is flaky, run at least three attempts and compare evidence. Treat intermittent pass/fail as a valid finding, not a failure of the loop.
  • If Tauri MCP cannot connect, use $helmor-debug-operate recovery steps. If the bridge remains unavailable, fall back to static code analysis and terminal tests, and label UI verification as blocked.
  • If a skill recipe fails three times, follow $helmor-debug-operate stale-skill rules: reason from fresh screenshots/DOM/code, record a candidate skill update, and ask before editing that skill unless the user explicitly requested it.
  • If adding logs risks exposing secrets, log shape/count/state only. Never print access tokens, credentials, API keys, cookies, or private account details.
  • If verification cannot be run safely because it would mutate durable user data, switch to a disposable workspace/session or stop and state the risk.
Show full SKILL.md (107 more words)Show less

Evidence Sources

Use the available signals in this order:

  • Terminal buffers: use $helmor-debug-operate's Call App Commands helper to run debug_list_terminal_buffers, then debug_read_terminal_buffer with the returned raw scriptType.
  • UI state: screenshot plus accessibility or structure snapshot.
  • IPC: start monitor, perform one action, capture filtered commands/events, then stop monitor.
  • Logs: Tauri console/system logs, sidecar JSONL logs under the dev data dir when relevant.
  • Code probes: temporary logs with unique prefixes, guarded by debug context when possible.

Read references/debug-loop.md when the task needs the full loop checklist or when reproduction fails. Use scripts in scripts/ to summarize logs and build evidence packs instead of pasting raw dumps into the chat.

© dohooo, Apache-2.0. 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 4 other files (scripts, references) in .agents/skills/helmor-debug-loop of dohooo/helmor.

  • SKILL.md
  • agents/openai.yaml
  • references/debug-loop.md
  • scripts/build_evidence_pack.py
  • scripts/terminal_log_summary.py

Open the folder on GitHubat commit a76cda1

Compare with similar skills

Helmor Debug Loop 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.

Helmor Debug Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Helmor Debug Loop this skilldohooo/helmor1.3k—~917Automated safety check: PassApache-2.0
Memorywhale Debuggingwuisabel-gif/MemWhale151—~370Automated safety check: PassMIT
Memorywhalewuisabel-gif/MemWhale151—~765Automated safety check: PassMIT
Memorywhale Evidencewuisabel-gif/MemWhale151—~459Automated safety check: PassMIT
Change Maple Agent ModeMaplePrivacyLabs/Maple100—~5.5kAutomated safety check: NotesMIT
Gearcoleco Debuggingdrhelius/Gearcoleco141—~3.5kAutomated safety check: PassGPL-3.0

Similar skills

  • Memorywhale Debugging

    wuisabel-gif/MemWhale

    MemoryWhale debugging; compiler failures; terminal diagnostics.

    151 GitHub stars~370 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Memorywhale

    wuisabel-gif/MemWhale

    Query and write durable debugging memory recorded by MemoryWhale.

    151 GitHub stars~765 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Memorywhale Evidence

    wuisabel-gif/MemWhale

    Use MemoryWhale debugging evidence when the user requests recall or a recurring failure may have relevant recorded history.

    151 GitHub stars~459 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Change Maple Agent Mode

    MaplePrivacyLabs/Maple

    Develop and debug Maple Agent Mode across its React UI, Tauri command and event bridge, account-scoped native runtime, embedded Goose integration, OpenSecret provider, developer tools, permissions…

    100 GitHub stars~5.5k tokensUpdated today
    Agent WorkflowsAuto-check: notes

  • Gearcoleco Debugging

    drhelius/Gearcoleco

    Debug and trace ColecoVision and Super Game Module games using the Gearcoleco emulator MCP server.

    141 GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Octocode Code Research

    bgauryy/octocode

    Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.

    946 GitHub stars~1.5k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from dohooo/helmor

  • Helmor Bump Vendors

    dohooo/helmor

    Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab /…

    1.3k GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Helmor CLI

    dohooo/helmor

    Use the Helmor CLI to remote-control Helmor from the terminal.

    1.3k GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Helmor Release

    dohooo/helmor

    Prepare Helmor releases by inspecting the current branch, drafting a concise user-facing Changesets entry first (bump + body — keep it as short as possible), creating any needed pending in-app…

    1.3k GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check: warnings

  • Helmor Debug Operate

    dohooo/helmor

    Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge.

    1.3k GitHub stars~6.6k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Helmor Debug Loop

What does Helmor Debug Loop do?

Autonomous local-development debugging loop for Helmor bugs. Helmor Debug Loop is an agent skill from dohooo/helmor. Autonomous local-development debugging loop for Helmor bugs.

When should I use Helmor Debug Loop?

Helmor Debug Loop fits situations like: the user asks an agent to reproduce; verify a Helmor local dev build issue using repeated local UI simulation; temporary logging; tauri MCP/towery MCP.

How do I install Helmor Debug Loop in Claude Code?

Run `npx skills add dohooo/helmor --skill helmor-debug-loop -a claude-code`. Or copy the skill folder (.agents/skills/helmor-debug-loop in dohooo/helmor) into .claude/skills/helmor-debug-loop in your project. Claude Code loads it when a task matches its description.

How do I install Helmor Debug Loop in Codex?

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

Can I use Helmor Debug Loop 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 dohooo/helmor --skill helmor-debug-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/helmor-debug-loop, .gemini/skills/helmor-debug-loop, .github/skills/helmor-debug-loop and .opencode/skills/helmor-debug-loop in your project.

What does Helmor Debug Loop need to run?

Going by SKILL.md and its folder, Helmor Debug Loop needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Helmor Debug Loop access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Helmor Debug Loop 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Helmor Debug Loop use?

Helmor Debug Loop is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Helmor Debug Loop use?

About 917 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 905 tokens, read only when the agent opens those files.

What are the alternatives to Helmor Debug Loop?

Skills that share tags, products or a category with Helmor Debug Loop: Memorywhale Debugging (wuisabel-gif/MemWhale, 151 stars), Memorywhale (wuisabel-gif/MemWhale, 151 stars), Memorywhale Evidence (wuisabel-gif/MemWhale, 151 stars) and Change Maple Agent Mode (MaplePrivacyLabs/Maple, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Helmor Debug Loop?

dohooo (a GitHub user) maintains it in dohooo/helmor, which has 1,309 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on August 22, 2026.

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