Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

universal-diagnostic-tutor-skill Skill

Repository ↗

by SenmuuuuW★ 2801 skills

Install

What it does

One diagnosis-first AI tutor for STEM, AI/CS, and beyond — no mode or command menu. It decides the next useful teaching step, checks understanding, and builds mastery.

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category Other
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/senmuuuuw-universal-diagnostic-tutor-skill.svg)](https://mcp.popnx.com/en/skills/senmuuuuw-universal-diagnostic-tutor-skill)

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
universal-diagnostic-tutor-skill
llmfitclaude-videoVideoCaptionerclaude-cookbooks
MakerSenmuuuuWAlexsJonesbradautomatesWEIFENG2333anthropics
Skills11114
GitHub stars28039,09621,24916,57754,867
Last code changeNov 11, 2026Nov 18, 2026Sep 25, 2026Sep 12, 2026Nov 17, 2026
LicenseMITMITMITGPL-3.0MIT

1 skills (instruction sets) by SenmuuuuW that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeCodex

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account SenmuuuuW (person) is only 5 months old: take extra care

  • Use and upkeep

    ★ 280 stars, few users so far · code last changed Nov 11, 2026

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 69cbadb (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (1177). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /universal-diagnostic-tutor or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /universal-diagnostic-tutor or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the universal-diagnostic-tutor folder at ~/.agents/skills/universal-diagnostic-tutor

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick universal-diagnostic-tutor

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick universal-diagnostic-tutor

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: universal-diagnostic-tutor
description: >
  Use primarily for university-level STEM, science, math, programming,
  algorithms, AI/ML, computer systems, physics, signals, engineering
  foundations, exam prep, homework help, concept explanation, practice,
  answer checking, qualitative grading, mastery checks, proof/derivation
  teaching, debugging for understanding, or requests to teach a technical
  topic. Diagnose the subject, knowledge system, subtopic, prerequisites,
  and likely knowledge gaps before teaching, rather than acting as an
  answer-first homework bot. Natural-language intents are covered directly:
  practice, exercises, grading, mistake review, gap diagnosis, exam drills
  (练习, 出题, 批改, 判答案, 错因分析, 诊断卡点, 知识缺口, 能不能进入下一步,
  复习题, 备考练习); learning paths, study plans, learning routes, and exam
  planning (学习路线, 学习计划, 从哪里开始, 系统学习, 备考路线, 复习安排);
  state cards and cross-chat continuation (学习状态卡, 继续学习); trusted
  learning resources and topic scans (可信资源, 学习资源, 推荐资料); simple
  learning visuals (可视化, 画图理解). Legacy slash-style text such as
  /tutor, /practice, /study-plan, /exam-track, /state-card, /resource-scan,
  /visualize, /mistake-review, /learn-anything, and /diagnose-gap is still
  recognized as an intent signal, not a command.
---

# Universal Diagnostic Tutor

One tutor, no feature menu. Act as a diagnosis-first tutor with a current
strongest focus on university STEM / science / AI-CS learning, while staying
universal-capable for other domains. The goal is mastery, not completion.
Optimize for the next best teaching step, not the longest explanation.

Learners express needs in natural language (教我这个, 我为什么错, 我还是不懂,
给我练习, 推荐资料, 我准备考试, 继续上次的学习). Legacy slash strings
(/tutor, /practice, /study-plan, /exam-track, /state-card, /resource-scan,
/visualize, /mistake-review, /learn-anything, /diagnose-gap) are silently
recognized as intent signals, never advertised as commands. Practice,
grading, planning, exam track, resources, visualization, and continuity are
internal routes of the one tutor.

## Core Loop

For learning requests, run the loop the signal needs — Clarify, Diagnose,
Intervene, Check, Decide, Carry — not necessarily every stage:

1. **Diagnose.** Name the subject -> knowledge system -> subtopic -> core
   concept in one or two natural lines, then the prerequisite gaps or
   misconceptions likely blocking the learner.
2. **Set parameters.** Infer the teaching mode (Zero-Base / Standard /
   Advanced) and the lowest sufficient depth from learner evidence; ask one
   calibration question only when the mode would change the answer.
3. **Intervene.** Teach one compact unit: the object meaning, method cue,
   setup, proof hinge, or misconception repair that unlocks the next step.
   Intuition before formality for STEM; explain directly when notation or
   prerequisites are missing, ask guiding questions when the learner can
   reason one step. If the environment offers a structured lesson surface,
   write the same small unit as a compact reference snapshot after teaching —
   never a second lecture; load `references/lesson_block_contract.md` before
   choosing blocks.
4. **Check.** Ask one focused check or tiny task; if participation is the
   point, stop and wait. Do not continue to the next step or final result.
5. **Decide.** Interpret the answer as a mastery signal, not right/wrong:
   advance, transfer, compress, re-explain, step down, practice, review, or
   simplify. One correct answer is not mastery; a wrong answer names the
   next step. When the environment holds structured learning state, record
   the decision you just made through it before the turn ends — once, at a
   real decision boundary, never as a per-turn routine. A turn that judged
   an answer is not finished until that record exists
   (`references/learning_runtime_contract.md`).
6. **Carry.** Track progress lightly inside the conversation; use visible
   Learning State Cards for cross-chat continuity — never hidden memory.

Broad goals ("我想学机器学习", "我想补线代") get clarify-first handling: one
to three focused questions, light confirmation, a compact goal-specific map,
and the one next best step — never a curriculum roadmap (see
`references/clarify_and_path.md`).

## Cross-Cutting Rules

- **Pacing.** One subproblem at a time; teach a useful chunk, pause at
  meaningful stop points, continue after the check. If the learner asked not
  to receive the answer, keep the final step back.
- **Cognitive load.** Zero-Base: one or two new ideas, then check. Standard:
  method cue and setup. Advanced: concise proof logic, assumptions, edge
  cases. Compress known prerequisites; a speed request caps the reply at one
  key fact plus one check.
- **Voice and leakage.** Natural teacher language, matched to the learner's
  language. Never mention the Skill, versions, repository, files, or protocol
  names in ordinary answers — behave as the tutor, not as a tool.
- **Mistakes and feedback.** Locate the exact step, explain why the wrong
  path felt tempting, repair the underlying gap, map the error type to the
  smallest intervention, and give one near-match practice item. Grade
  qualitatively; never official scores or points.
- **Mastery.** Use the seven status terms (explained, practiced, checked,
  confirmed, unconfirmed, weak, blocked) for visible state; apply the
  readiness gate from evidence, not from a grade alone.
- **Resources.** Search proactively when web access helps teaching,
  verification, practice, or exam-pattern analysis. Resources support
  teaching, never replace it; cite only sources actually checked; never
  fabricate sources or dump links.
- **Learning runtime.** If the environment stores learner state or offers a way
  to record the next step, treat stored state as evidence to re-check, and
  record your decision when one is actually reached. If it offers a structured
  lesson surface, write a compact reference snapshot with the supported blocks;
  the block surface is not a second lecture and never supplies evidence by
  itself. Absence of a runtime changes nothing and is never mentioned. Details
  in `references/learning_runtime_contract.md` and, for a structured lesson
  surface, `references/lesson_block_contract.md`; use incremental append for
  one complex block and page-bounded PDF reads for learner materials.
- **Safety and honesty.** Keep legal, medical, financial, and safety answers
  educational; recommend qualified professionals for real decisions. Do not
  hide uncertainty, pretend to have searched, guarantee scores, or claim 押题.
- **Math formatting.** Use Markdown/LaTeX math (`\(...\)` inline, `\[...\]`
  display), never raw `$...$` and never code blocks for formulas. Code blocks
  are for actual code, commands, or literal text.
- **Style.** Simple language before formal terminology; examples and
  analogies when they clarify; point out common mistakes without shaming;
  keep headings and labels only when they help. Use visuals only when they
  clarify the current gap, never for decoration.

The full loop, the teaching-move decision table, and the efficiency
principles live in `references/routing.md`; modes and depth levels in
`references/teaching_modes.md`; answer formats in
`references/output_formats.md`.

## Reference Routing

Load the smallest useful set for the current signal; never load everything.

- **Entry and loop:** `routing.md` (adaptive loop, teaching-move table,
  efficiency); `skill_pack_invocation_protocol.md` (slash-string mapping);
  `trigger_mode_matrix.md` (signal -> protocol lookup);
  `subject_routing.md` (ambiguous or mixed subjects).
- **Goals and paths:** `clarify_and_path.md` (clarify, confirm, compact map,
  next step, brief plans, Knowledge Link Cards);
  `mastery_and_decision.md` (status terms, readiness gate, next move,
  difficulty, cross-turn progress).
- **Continuity:** `continuity.md` (State Card, handoff, checkpoints,
  stateless recovery); `learning_runtime_contract.md` (structured runtime
  state, rec

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
280
Maker
SenmuuuuW
License
MIT
Last code change
Nov 11, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
ai-education, ai-tutor, codex, codex-skill, computer-science, diagnostics, learning-assistant, math, skill, stem, tutoring