一键在 Manus 中运行任何 Skill

muggle-preferences

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

在 Manus 中运行

概览

安装命令

npx skills add https://github.com/multiplex-ai/muggle-ai-works --skill muggle-preferences

复制此命令并粘贴到 Claude Code 中以安装该技能

来源

multiplex-ai/muggle-ai-works

星标2

分支2

更新时间2026年6月3日 01:07

文件资源管理器

30 个文件

SKILL.md

readonly

name

muggle-preferences

description

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

同仓库更多 Skills

同仓库

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

muggle-test

multiplex-ai/muggle-ai-works

Run change-driven E2E acceptance testing using Muggle AI — detect the user's recent code changes (local diff or a PR), map them to affected user flows, then run real-browser acceptance tests on localhost or a deployed preview/staging URL, publish results to the dashboard, and post a screenshot summary to the PR. Use this whenever the user wants to test, validate, check, or regression-test their own changes or work — 'test my changes', 'validate my changes', 'regression test my work', 'make sure I didn't break anything', 'did my recent commits/changes break anything or any user flows?', 'test before I push' — and especially as the acceptance-test gate before opening a pull request or merging (e.g. 'validate my changes before I open the PR' means run the acceptance suite, not just a completion checklist). The defining signal is change-driven validation of in-progress work tied to a commit, push, PR, or merge. For testing one specific named feature/flow use muggle-test-feature-local; this is not importing existi

2026-06-032

muggle-do

multiplex-ai/muggle-ai-works

Unified Muggle AI workflow entry point. Use when user types muggle do or asks for autonomous implementation to PR. Also handles the `address-reviews` directive (dispatched by the muggle-pr-followup watcher when new submitted reviews land on a PR).

2026-06-032

muggle-pr-followup

multiplex-ai/muggle-ai-works

Use this skill 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", "follow up on my PR's reviews", "babysit my PR's review thread", "auto-handle reviews on the PR I just opened", "I'm stepping away — handle my PR's reviews while I'm gone". Run with no args to track every PR you pushed this session (any repo); pass a PR URL to start watching a specific one. This is PR-review-specific automation: when the recurring thing the user wants handled is a PR's review comments, use this — not 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-06-032

mbt

multiplex-ai/muggle-ai-works

Explicit short alias for the `muggle-browser-task` skill. ONLY invoke when the user explicitly types `mbt` or `/mbt` — never auto-trigger from any other phrasing.

2026-05-312

mdo

multiplex-ai/muggle-ai-works

Explicit short alias for the `muggle-do` skill. ONLY invoke when the user explicitly types `mdo` or `/mdo` — never auto-trigger from any other phrasing.

2026-05-312

来源

multiplex-ai

multiplex-ai/muggle-ai-works

打开 GitHub 仓库查看创作者相关仓库

安装命令

下载

在 Manus 中运行

适用职业SOC

软件质量保证分析师与测试员计算机与数学类职业15-1253L4

name

muggle-preferences

description

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