Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Inicia sesión con Google para escribir reseñas.Prototipo · se actualiza cada 30 min
PopNx MCPServidores MCP para quienes usan IA · en palabras sencillas

universal-diagnostic-tutor-skill Skill

Repositorio ↗

de SenmuuuuW★ 2781 skills

Instalar

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 Not confirmed yet (README not read yet)
  • Category Otros
Para autores: añade una insignia a tu README

Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.

[![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)

Skills parecidas

Mismo tipo de trabajo, ordenadas como la lista de Skills

Comparado con otros parecidos
Este
universal-diagnostic-tutor-skill
llmfitclaude-videoVideoCaptionerclaude-cookbooks
AutorSenmuuuuWAlexsJonesbradautomatesWEIFENG2333anthropics
Skills11114
Estrellas de GitHub27839.06421.16816.57054.832
Último cambio de código11 nov 202618 nov 202625 sept 202612 sept 202617 nov 2026
LicenciaMITMITMITGPL-3.0MIT

1 skills (conjuntos de instrucciones) de SenmuuuuW que la IA lee y sigue · no es un MCP server

En qué se diferencia un Skill de MCP

MCP = las manos

Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.

Skill = el manual

Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.

A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.

Funciona con

Claude CodeCodex

Según el README del autor y las carpetas del repo

Instalar

Is it safe?

  • Who made it

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

  • Use and upkeep

    ★ 278 stars, few users so far · code last changed 11 nov 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

Primero: ¿qué IA usas?

Elige tu app y esta página mostrará solo cómo instalarlo en ella

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 1Deja que Claude Code lo instale

Copia esta frase y pégala en un chat de Claude Code

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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

Vuelve a abrir Claude Code y escribe /universal-diagnostic-tutor, o pide una tarea relacionada y Claude lo usará

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

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.claude/skills

    Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md

    Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

  3. Vuelve a abrir Claude Code y escribe /universal-diagnostic-tutor, o pide una tarea relacionada y Claude lo usará

Las skills que instalas tú funcionan en la app de escritorio de ChatGPT, en Codex CLI y en la extensión de Codex para el IDE · ChatGPT en la web y el móvil no puede usar skills instaladas por ti, solo las que vienen con un plugin del directorio

App de escritorio de ChatGPT

La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills

Option 1Deja que ChatGPT lo instale

Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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 2Coloca la carpeta tú mismo

Coloca la carpeta universal-diagnostic-tutor en ~/.agents/skills/universal-diagnostic-tutor

~ es tu carpeta de inicio ($HOME)

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.agents/skills

    Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md

    Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Después de instalar

  • App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
  • Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
  • Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex

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

ChatGPT en la web y el móvil

Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio

Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba

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

Option 1Deja que Codex lo instale

Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill

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

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.agents/skills

    Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md

    Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

  3. Vuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill

Option 1Deja que Cursor lo instale

Copia esta frase y pégala en un chat de Cursor

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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

En el chat Agent de Cursor escribe / y elige universal-diagnostic-tutor

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

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. Copia la carpeta del skill a ~/.cursor/skills

    Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md

    Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

  3. En el chat Agent de Cursor escribe / y elige universal-diagnostic-tutor

Option 1Let the AI install it

Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat

Where to install

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión

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 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.

Ver en GitHub ↗

Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026

Ver el SKILL.md original

El texto siguiente viene del repo del autor, no de PopNx MCP

Se muestran los primeros 8000 caracteres · Abrir el archivo completo en 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

Conversación

Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.

Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.

Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.

Inicia sesión para publicar

Desde GitHub

Estrellas en GitHub
278
Autor
SenmuuuuW
Licencia
MIT
Último cambio de código
11 nov 2026
Archivos SKILL.md del repo (con traducciones y plantillas)
1
Temas
ai-education, ai-tutor, codex, codex-skill, computer-science, diagnostics, learning-assistant, math, skill, stem, tutoring