Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

muggle-repair

Sterne16

Forks2

Aktualisiert24. Juni 2026 um 18:39

Diagnose and fix a broken Muggle AI installation. Use when user types muggle repair or asks to fix Muggle Test setup.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

multiplex-ai

multiplex-ai/muggle-ai-works

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	muggle-repair
model	haiku
description	Diagnose and fix a broken Muggle AI installation. Use when user types muggle repair or asks to fix Muggle Test setup.

Muggle Test Repair

Telemetry first step: see _shared/telemetry-emit.md. Use skillName: "muggle-repair".

Automatically diagnose and fix broken components.

Steps

Run the same checks as /muggle:muggle-status to identify what is broken.
If everything passes, report: "Nothing to repair — installation looks healthy."
For each failing component:
- Electron app missing or corrupt — run muggle setup --force to re-download.
- Authentication expired or invalid — run muggle-remote-auth-login to re-authenticate.
- MCP server unresponsive — report the error and suggest restarting the session.
Run status checks again to confirm all components are healthy.
Report what was repaired.

Output

Show before/after status for each repaired component. If repair fails, report the error with enough context for the user to investigate.

Mehr aus diesem Repository

gleiches Repository

muggle-pr-followup

multiplex-ai/muggle-ai-works

Use when the user wants a pull request's incoming review feedback handled for them — it watches one PR's review thread and, each time a reviewer submits new comments, dispatches the work to address them. Engage on PR-review-follow-up intent: "watch my PR and address review comments as they come in", "keep an eye on PR #123 and respond to reviewer feedback", "babysit my PR's review thread", "I'm stepping away — handle my PR's reviews while I'm gone". This is PR-review-specific automation — prefer it over the generic loop skill. It only watches and dispatches; the actual edits and replies are muggle-do. Not for posting test results to a PR (use muggle-pr-visual-walkthrough).

2026-07-2316

muggle-do

multiplex-ai/muggle-ai-works

Take a feature request, spec, design, bug, or ticket and carry it autonomously to an opened pull request — write the code, test it, raise the PR. Use whenever the user wants something built, implemented, added, or fixed with a PR opened, raised, or put up at the end — "implement rate limiting and raise a PR", "build the CSV export and put up a PR", "take this Jira ticket and run with it, ping me when the PR is up", "fix this bug and open a pr", or "muggle do …". Also handles the internal `address-reviews` directive the muggle-pr-followup watcher dispatches when new reviews land. Not for testing or validating existing changes (use muggle-test), nor watching a PR's incoming reviews (use muggle-pr-followup).

2026-06-3016

muggle-preferences

multiplex-ai/muggle-ai-works

View, set, or reset Muggle AI preferences that control testing behavior. Use when user asks to see preferences, change a setting, configure Muggle Test defaults, or manage muggle config. Triggers on: 'muggle preferences', 'show muggle settings', 'change muggle preference', 'set autoLogin to always', 'muggle config', 'reset muggle preferences', 'show my muggle settings', 'configure muggle', 'muggle setup'.

2026-06-3016

muggle-test-feature-local

multiplex-ai/muggle-ai-works

Run a real-browser end-to-end (E2E) acceptance test against localhost to verify a feature works correctly — signup flows, checkout, form validation, UI interactions, or any user-facing behavior. Launches a browser that executes test steps and captures screenshots. Use this skill whenever the user asks to test, validate, or verify their web app, UI changes, user flows, or frontend behavior on localhost or a dev server — even if they don't mention 'muggle' or 'E2E' explicitly.

2026-06-2916

muggle-works-npm-release

multiplex-ai/muggle-ai-works

Cut @muggleai/works release: AskUserQuestion (major/minor/patch), sync master, stop if nothing ships, semver baseline + Electron from GitHub, confirm plan, bump package.json + sync:versions, full local verify, chore(release) PR, merge via gh, dispatch publish-works-to-npm.yml—no local npm publish.

2026-06-2916

muggle-feedback

multiplex-ai/muggle-ai-works

Use when the user wants to flag that a generated Muggle Test action script — or one specific step in it — did the wrong thing, so Muggle can analyze and regenerate affected scripts. Covers any report that a script or step is wrong, broken, or misbehaving (clicked the wrong element, step N did not work, broken at the submit step), whether from a recent local/remote run or a pasted Muggle dashboard run/script URL. Also lists, views, or deletes previously submitted feedback. Triggers on /muggle-feedback, give feedback on this run, the test was wrong, flag this run.

2026-06-2416

name	muggle-repair
model	haiku
description	Diagnose and fix a broken Muggle AI installation. Use when user types muggle repair or asks to fix Muggle Test setup.

Muggle Test Repair

Telemetry first step: see _shared/telemetry-emit.md. Use skillName: "muggle-repair".

Automatically diagnose and fix broken components.

Steps

Run the same checks as /muggle:muggle-status to identify what is broken.
If everything passes, report: "Nothing to repair — installation looks healthy."
For each failing component:
- Electron app missing or corrupt — run muggle setup --force to re-download.
- Authentication expired or invalid — run muggle-remote-auth-login to re-authenticate.
- MCP server unresponsive — report the error and suggest restarting the session.
Run status checks again to confirm all components are healthy.
Report what was repaired.

Output

Show before/after status for each repaired component. If repair fails, report the error with enough context for the user to investigate.