Run any Skill in Manus with one click

muggle-preferences

Stars16

Forks2

UpdatedJune 30, 2026 at 18:25

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'.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

multiplex-ai

multiplex-ai/muggle-ai-works

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

File Explorer

29 files

SKILL.md

readonly

name	muggle-preferences
model	haiku
description	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'.

Muggle Test Preferences

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

Pick the operation, then read its op file for the procedure.

Intent	Op file
`/muggle-preferences <key>` or "change my `<key>` preference"	`ops/change-one.md`
User names key + value (e.g. "set autoLogin to always")	`ops/set.md`
"show preferences" / no args	`ops/list.md`
"configure muggle" / "muggle setup" / change without naming a key	`ops/configure.md`
"reset preferences"	`ops/reset.md`

Shared context (all ops)

Current values: session-context line Muggle Test Preferences key=value …. Default ask.
Per-key files: preference-gates/<key>.md. Key list = ls preference-gates/*.md minus README.md.
Allowed values: always/never/ask (or local/remote/ask for defaultExecutionMode).
Scope: global default; project if user says "for this project" / "just this repo" (pass cwd).

More from this repository

same 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-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

muggle-pr-visual-walkthrough

multiplex-ai/muggle-ai-works

Renders and posts a visual walkthrough of Muggle AI E2E acceptance test results to a PR — per-test-case dashboard links, step-by-step screenshots, and pass/fail summary — using the `muggle build-pr-section` CLI for deterministic formatting with automatic fit-vs-overflow. Use at the end of any Muggle Test test run (local or remote) to give PR reviewers clickable visual evidence that user flows work. Triggers on 'post results to PR', 'attach walkthrough to PR', 'share E2E screenshots on the PR', 'add visual walkthrough to PR'.

2026-06-2416

name	muggle-preferences
model	haiku
description	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'.

Muggle Test Preferences

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

Pick the operation, then read its op file for the procedure.

Intent	Op file
`/muggle-preferences <key>` or "change my `<key>` preference"	`ops/change-one.md`
User names key + value (e.g. "set autoLogin to always")	`ops/set.md`
"show preferences" / no args	`ops/list.md`
"configure muggle" / "muggle setup" / change without naming a key	`ops/configure.md`
"reset preferences"	`ops/reset.md`

Shared context (all ops)

Current values: session-context line Muggle Test Preferences key=value …. Default ask.
Per-key files: preference-gates/<key>.md. Key list = ls preference-gates/*.md minus README.md.
Allowed values: always/never/ask (or local/remote/ask for defaultExecutionMode).
Scope: global default; project if user says "for this project" / "just this repo" (pass cwd).