REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A layout engine for AI diagrams: the model says what to draw, Sketchy figures out where. Hand-drawn, interactive, in Claude, Cursor and VS Code.
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/ddkbs-sketchy)같은 작업에서 AI를 서비스에 연결하는 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 sketchy | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | ddkbs | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 449 | 465,460 | 233,910 | 149,364 | 144,149 |
| 마지막 코드 변경 | 2026년 11월 13일 | 2026년 11월 17일 | 2026년 4월 20일 | 2026년 11월 17일 | 2026년 11월 17일 |
| 라이선스 | MIT | MIT | – | Apache-2.0 | MIT |
ddkbs의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeClaude (เว็บ/แอป)CodexCursorWindsurfOpenCode
제작자 README와 repo 폴더 기준
GitHub account ddkbs (person), 1 years old
★ 449 stars, few users so far · code last changed 2026년 11월 13일
1 scripts that can run on a computer: render.ts
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit c246cd4 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Uploading to claude.ai would fail: the description is over 200 characters (448). Use "Let the AI install it" instead
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
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
Claude Code를 다시 열고 /skill를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
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
sketchy 폴더를 ~/.agents/skills/sketchy에 넣으세요
~는 홈 폴더($HOME)입니다
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
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는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
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
Cursor Agent 채팅에서 /를 입력하고 skill 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat
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 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · GitHub에서 전체 파일 열기
---
name: sketchy
description: Draws hand-sketched, interactive diagrams (architecture, flows with step-by-step walkthroughs, comparisons, metaphors, Arduino circuits) right in the chat. Use whenever a concept, system, process or comparison is easier to understand as a drawing, or when the user asks for a sketch, diagram or visual explanation. In the regular Claude chat, use this skill even if Sketchy MCP tools are connected, because the chat does not display their drawings.
---
# Sketchy
In the regular Claude chat, always use this skill instead of the Sketchy MCP tools: the chat runs those tools but does not show their drawings.
You describe **what** to draw in a few short lines; Sketchy computes every position and renders it in a hand-drawn style with hover details and step navigation. Never pass coordinates.
## Workflow
Draw inline with your visualization tool (the one that renders HTML widgets in the conversation). Pass this HTML as the widget code, with the scene between the backticks:
```html
<h2 class="sr-only">One-sentence summary of the drawing</h2>
<div id="sketchy" style="min-height: 320px"></div>
<script src="{{CDN}}/sketchy.js" {{SRI}}></script>
<script>
Sketchy.draw(
"#sketchy",
`
title How a web request works
dir right
group net The internet
browser Browser @globe ~ Shown on hover
server Server @server in net !accent
db Database (cylinder) in net
browser -> server HTTPS
server --> db query
step Request: The browser asks the server | browser server browser->server
`,
);
</script>
```
Keep the widget code exactly like this: no other markup, styles or text. Then explain the drawing in 2–4 sentences in your reply instead of describing it again. If the widget shows "Sketchy could not draw this", fix the line the message names and draw again.
To change an earlier drawing, draw the whole scene again with the same ids.
Without a visualization tool, write the scene to a file and render a standalone page with the script in this skill's folder (Node.js, no network needed), then share the file:
```bash
node <skill-folder>/scripts/render.mjs /tmp/scene.txt /mnt/user-data/outputs/<short-name>.html
```
## Scene syntax
One element per line:
```
title <text> subtitle <text> dir right|down
group <id> <label> [in <parent group>]
<id> <label> [@icon] [(shape)] [in <group>] [!accent|!muted] [~ hover text]
<a> -> <b> [label] [!accent|!muted] (--> dashed, <-> arrowheads on both ends)
label <id>[.<pin>] <text>
step <title>: <text> | <ids to highlight; edges as a->b>
part <id> <type> [key=value] [caption]
wire <part.pin> -> <part.pin> [red|black|blue|green|yellow|orange|purple|gray|white]
draw <id> [WxH] [in <group>] [: title] (free drawing, its shape lines follow)
```
A free drawing has its own canvas (default `100x100`, y pointing down) and sits in the scene like a node, so arrows can connect to it. Later lines paint on top:
```
circle [name] x,y r ellipse [name] x,y rx ry rect [name] x,y w h (x,y = top left)
line|arrow|curve [name] x,y x,y … curve is smooth
shape|blob [name] x,y x,y x,y … closed; blob is smooth
arc [name] x,y r from to degrees, 0 = right, counter-clockwise
text [name] x,y words [size=14]
object <type> [name] x,y [size] [rotate=45] [flip] a ready-made thing
icon [name] x,y <lucide name> [size]
repeat i=0..7: <shape line> i in coordinates, {i+1} in names and labels
slider a 0..1 [= 0] [hidden] before the shapes using it
let w = 84-12*a names a sub-expression for the lines below
angle [name] x,y cx,cy x,y [r] arc at the middle point; 90° gets the square
measure [name] x,y x,y [offset] dimension line with arrows
brace [name] x,y x,y [depth] curly brace, bulging to the right of the way
axes [name] x,y w h [ticks=10] [~ x name | y name] x,y is the origin
grid [name] x,y w h [step] x,y is the top left
```
Object types: person, tree, cloud, house, car, bike, gear, sun, bulb, battery, laptop, phone, server, book, heart, drop, flame, mountain, flask, rocket, lock, key.
- Options: `fill=<color>`, `hatch=<color>`, `color=<color>`, `width=2`, `--dashed`, `arrow`, `both`, `!accent`, `!muted`, `stage=2`, `along=<shape name>@<0..1>`, `move=<dx>,<dy>`, `~ label`.
- Colors: black, gray, white, accent, yellow, blue, red, green, purple, orange.
- Prefer `~ label` over `text`: Sketchy places labels clear of the drawing. Coordinates may be math, such as `50+30*cos(1),50`.
- In steps, `| pic[name]` circles a named shape and `pic=2` shows only shapes up to stage 2, so a picture can build up. Start with `pic=1`. `a=0.5` glides a slider there, which is how things move. Draw a moving shape at its start and shift it with `move=40*a,0`; a shape with `along=wire@a` rides on the shape named `wire`. Every step should end in a clear picture: move things all the way, one idea per step, never stop a motion halfway.
Ready-made explanation shapes take only their contents, one entry per line, ended by a blank line. End an entry with `!accent`, `!muted` or `~ small print`:
```
timeline t: History <when> | <what>
cycle c: Water cycle <entry>
pyramid p: Needs <entry>, top first
funnel f: Sales <entry>, top first
mindmap m: Topic <centre>, then - <branch>, -- <sub-branch>
venn v: Pets set a Cats, set b Dogs, then a | purrs, a,b | pets (2 or 3 sets)
matrix x: Plans cols Option | Price, then Cheap | 1 €
```
In steps, `| t[2]` circles the 2nd entry and `t=2` shows only the first two.
Molecules and maps:
```
molecule m CC(=O)O [full] : Acetic acid SMILES; full writes out every C and H; steps circle atoms as m[3]
map m europe : Title world, europe, africa, asia, middle-east, north-america,
Germany !accent ~ Start south-america, americas, oceania, a country, or w,s,e,n
France fill=blue countries by English name: fill=, hatch=, !accent, ~ label
place berlin 52.52,13.40 Berlin a dot with a label, at latitude,longitude
route r: berlin -> 48.86,2.35 --dashed ~ 8 h
```
In steps, `| m[Germany]` (spaces as dashes: `m[United-Kingdom]`) circles a country, `m[berlin]` a place or route.
- Labels are 1–4 words; put details after `~`.
- Icons: `@globe`, `@server`, `@database` (Lucide) or `@simple-icons:react`.
- Shapes: `(cylinder)` storage, `(person)` actor, `(note)`, `(circle)`, `(rounded)`, `(text)`.
- Ids are letters, digits, `_` or `-`, unique across the scene; arrows, labels and steps may only use ids defined in it.
## Explanation patterns
Pick one per drawing:
- **structure** ("what is it made of?"): components as nodes, groups for areas, labels for the important bits; `dir down` for hierarchies.
- **flow** ("how does it work?"): a left-to-right chain of nodes and arrows plus one step per stage.
- **comparison** ("X vs Y"): one group per option with parallel nodes in the same order; `!muted` for what is equal, `!accent` for the key difference.
- **metaphor** ("explain it simply"): one group for the real thing, one for an everyday counterpart, dashed arrows between matching elements.
- **picture** ("what does it look like?"): a `draw` block of the thing itself when boxes and arrows would hide the idea, such as atoms, forces, cells, orbits, geometry or machines.
Quality rules: 3–12 nodes; `!accent` on at most one or two elements; icons sparingly; 3–7 steps of one or two sentences each.
## Circuits
Find part types and pin names first (needs code execution):
```bash
node <skill-folder>/scripts/render.mjs --parts "distance sensor"
node <skill-folder>/scripts/render.mjs --parts arduino-uno
``질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.