SKILLEMALL.ai
GitHub ↗ RU Sign in

AC manage-settings

Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent read_skill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool first. Never use for repository, app, eval, or other non-Muse configuration.

asgeirtj/system_prompts_leaks Agent Skills author: asgeirtj CC0-1.0 1 file body ≈ 3 018 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST…

As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 60/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 4 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, read, python) that frontmatter does not declare
    • 100Steps. 35 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3018 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 273: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 35 items
    • +4Has examples (2 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.