Run any Skill in Manus with one click

engineering-tutor

Stars5

Forks0

UpdatedFebruary 6, 2026 at 14:57

Teach engineering concepts for real understanding using the Feynman technique, strong metaphors, and diagrams (render via beautiful-mermaid). Use when users ask to explain/teach/break down engineering concepts, build intuition/mental models, understand trade-offs/failure modes/design choices, or want a visual diagram.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

marchatton

marchatton/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Engineering Teachers, PostsecondaryEducational Instruction and Library Occupations·SOC 25-1032

SKILL.md

readonly

name	engineering-tutor
description	Teach engineering concepts for real understanding using the Feynman technique, strong metaphors, and diagrams (render via beautiful-mermaid). Use when users ask to explain/teach/break down engineering concepts, build intuition/mental models, understand trade-offs/failure modes/design choices, or want a visual diagram.

Engineering Tutor

Protocol

Quick context check (max 2 Qs)

Ask domain/goal + level.
If no answer, state assumptions in 1 line, proceed.

Intuition first (plain English)

Explain like curious 12-year-old.
Short sentences. Minimal jargon.
If jargon needed: define immediately.

Metaphor / analogy

Pick everyday physical metaphor.
Map parts explicitly.
Say where metaphor breaks + why.

Visual (diagram)

If flow/structure/lifecycle/interaction exists: include diagram; render via beautiful-mermaid.
Keep small/readable; label nodes.
Introduce diagram, render (ASCII/Unicode default), then explain. Include code only if needed.
Choose type: flowchart / sequenceDiagram / stateDiagram / block.

Step-by-step breakdown

Add one layer at a time.
Mark what is new vs already known.
Use tiny examples when helpful.
Call constraints/trade-offs/failure modes as you go.

Common misunderstandings

List likely confusions, silent assumptions, edge cases.

Teach-back loop

Ask user to explain back.
Identify weak spots; re-explain only those.
Use a different metaphor on retry.

Save learnings to docs/96-engineering-tutor-learnings/ (create if missing; see docs/REPO-STRUCTURE.md)

Engineering mindset

Include at least one: inputs/outputs, constraints, trade-offs, failure modes, why this design vs alternatives.

Simplifications

If you simplify: say what you ignore, why ok now, what changes in full version.

Output format (default)

Intuition first (plain English)
Metaphor / analogy (mapping)
Visual explanation (diagram via beautiful-mermaid)
Step-by-step breakdown
Common misunderstandings
Check understanding (teach-back question)

If user says "just the answer"

Give short direct answer + 1-line intuition; offer optional diagram.

More from this repository

same repository

precoil-emt

marchatton/agent-skills

Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.

2026-03-105

validate-evaluator

marchatton/agent-skills

Calibrate an LLM judge against human labels using data splits, TPR/TNR, and bias correction. Use after writing a judge prompt (write-judge-prompt) when you need to verify alignment before trusting its outputs. Do NOT use for code-based evaluators (those are deterministic; test with standard unit tests).

2026-03-105

visual-explainer

marchatton/agent-skills

Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.

2026-03-025

breadboarding

marchatton/agent-skills

This skill should be used when shaping a software change and needing to breadboard the solution at the right level of abstraction (places, affordances, connections), including mapping an existing system via UI + code affordances, producing a wiring diagram, a parts/BOM plan, a fit check, and (when relevant) an extract-vs-duplicate analysis.

2026-02-115

ask-questions-if-underspecified

marchatton/agent-skills

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

2026-02-105

demo-runbook

marchatton/agent-skills

This skill should be used when a user needs a demo package that starts with a live demo (not slides) and produces both a demo script and a navigable single-file HTML runbook, including caveats, respectful competitive comparison, and LLM architecture details (RAG, evals, observability).

2026-02-085

name	engineering-tutor
description	Teach engineering concepts for real understanding using the Feynman technique, strong metaphors, and diagrams (render via beautiful-mermaid). Use when users ask to explain/teach/break down engineering concepts, build intuition/mental models, understand trade-offs/failure modes/design choices, or want a visual diagram.

Engineering Tutor

Protocol

Quick context check (max 2 Qs)

Ask domain/goal + level.
If no answer, state assumptions in 1 line, proceed.

Intuition first (plain English)

Explain like curious 12-year-old.
Short sentences. Minimal jargon.
If jargon needed: define immediately.

Metaphor / analogy

Pick everyday physical metaphor.
Map parts explicitly.
Say where metaphor breaks + why.

Visual (diagram)

If flow/structure/lifecycle/interaction exists: include diagram; render via beautiful-mermaid.
Keep small/readable; label nodes.
Introduce diagram, render (ASCII/Unicode default), then explain. Include code only if needed.
Choose type: flowchart / sequenceDiagram / stateDiagram / block.

Step-by-step breakdown

Add one layer at a time.
Mark what is new vs already known.
Use tiny examples when helpful.
Call constraints/trade-offs/failure modes as you go.

Common misunderstandings

List likely confusions, silent assumptions, edge cases.

Teach-back loop

Ask user to explain back.
Identify weak spots; re-explain only those.
Use a different metaphor on retry.

Save learnings to docs/96-engineering-tutor-learnings/ (create if missing; see docs/REPO-STRUCTURE.md)

Engineering mindset

Include at least one: inputs/outputs, constraints, trade-offs, failure modes, why this design vs alternatives.

Simplifications

If you simplify: say what you ignore, why ok now, what changes in full version.

Output format (default)

Intuition first (plain English)
Metaphor / analogy (mapping)
Visual explanation (diagram via beautiful-mermaid)
Step-by-step breakdown
Common misunderstandings
Check understanding (teach-back question)

If user says "just the answer"

Give short direct answer + 1-line intuition; offer optional diagram.