Dont Anger Mario logo

Dont Anger Mario

Community
dannote
dont-anger-mario

Prepare concise, high-signal issues or contribution proposals for the pi repository without annoying maintainers. Use when filing issues/PR proposals for earendil-works/pi or mentioning Mario/pi tracker etiquette.

Overview

Publisherdannote
Repositorydot-pi
Skill namedont-anger-mario
Stars
57
Forks
4
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dannote on GitHub. Read the source before you install it.

Installation

Install the Dont Anger Mario AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/dannote/dot-pi/tree/master/skills/extra/dont-anger-mario
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dannote/dot-pi.git /tmp/dot-pi
mkdir -p .claude/skills
cp -r /tmp/dot-pi/skills/extra/dont-anger-mario .claude/skills/dont-anger-mario
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dont Anger Mario in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dont Anger Mario on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dont Anger Mario is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Don't Anger Mario

Use this skill before opening an issue or contribution proposal in earendil-works/pi.

Rules

  • Read CONTRIBUTING.md first.
  • Use an official issue template; blank issues are disabled.
  • Keep it short. If it does not fit on one screen, it is too long.
  • Write in the user's own voice, not corporate/AI slop.
  • Be concrete: what, why, and optionally how.
  • Do not submit automatically.
  • Before submitting, ask the user to confirm they carefully read the exact final draft and explicitly approve posting it.
  • If proposing a change, use Contribution Proposal rather than Bug Report.
  • If reporting a bug, include minimal repro and version.
  • If opening a PR, only proceed after maintainer approval (lgtm for PRs; lgtmi is issues only).
  • Do not send agent-only PRs. If the user cannot explain the change without the agent, stop.

Safe workflow

  1. Inspect templates and contributing docs:
bash
gh api repos/earendil-works/pi/contents/.github/ISSUE_TEMPLATE --jq '.[].name'
gh api repos/earendil-works/pi/contents/CONTRIBUTING.md --jq .content | base64 --decode
  1. Draft the issue body in /tmp, never inline long Markdown through shell quoting:
bash
cat > /tmp/pi-issue.md <<'EOF'
### What do you want to change?

...

### Why?

...

### How? (optional)

...
EOF
  1. Show the exact final title and body to the user.

  2. Ask for explicit approval with this wording:

text
Please read the draft carefully. Do you explicitly approve me posting this issue/proposal as written?

Do not proceed on vague approval like "ok" if the user has not seen the exact final draft.

  1. Create only after explicit approval:
bash
gh issue create \
  --repo earendil-works/pi \
  --template contribution.yml \
  --title "Short concrete title" \
  --body-file /tmp/pi-issue.md

Extra caution from prior tracker behavior

Known maintainer reactions that shape this workflow:

  • Auto-close gate is intentional; maintainers review closed issues later.
  • GitHub Actions outages can let the issue/PR gate fail and flood the repo.
  • Maintainers dislike agent-only PRs because they take time to review and are often broken.
  • "Clanker misunderstood the code" is a real failure mode; verify the claim before drafting.
  • A label/comment like possibly-openclaw-clanker is a warning sign: shorten, verify, and make the human reasoning obvious.

Useful receipts:

Good contribution proposal shape

md
### What do you want to change?

One concrete change.

### Why?

The user-visible problem and why it matters.

### How? (optional)

Small implementation sketch, if useful. Avoid over-design.

Tone

Good:

Prompt templates support $1 and $ARGUMENTS, but optional arguments cannot have defaults. I want /next and /next 3 to expand cleanly without asking the model to interpret an empty argument.

Bad:

Implement advanced Bash-compatible templating with all parameter expansion semantics, conditionals, filters, and expression evaluation.

Frequently asked questions

What does the Dont Anger Mario AI skill do?

Prepare concise, high-signal issues or contribution proposals for the pi repository without annoying maintainers. Use when filing issues/PR proposals for earendil-works/pi or mentioning Mario/pi tracker etiquette.

Why use Dont Anger Mario on TypingMind?

Because you install it once and use it with any model. Dont Anger Mario is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dont Anger Mario in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dannote/dot-pi/tree/master/skills/extra/dont-anger-mario. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Dont Anger Mario?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dont Anger Mario?

As many as you like. As long as a model supports skills, you can use Dont Anger Mario with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dont Anger Mario AI skill free?

Yes. It is published on GitHub by dannote under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇