소스 정보
- 저장소
- NousResearch/hermes-agent
- 최근 소스 활동
- 2026년 8월 17일 05:11
- 감지된 SKILL.md 언어
- 영어
- 스타
- 232,815
- 포크
- 46,511
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/NousResearch/hermes-agent --skill draw-your-font명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | draw-your-font |
| description | Turn a handwriting photo into an installable TTF font. |
| version | 0.1.0 |
| author | Danilo Znamerovszkij (https://github.com/danilo-znamerovszkij/draw-your-font), ported by Hermes Agent |
| license | MIT |
| platforms | ["linux","macos","windows"] |
| required_commands | ["node","npx"] |
| metadata | {"hermes":{"tags":["font","handwriting","typography","ttf","woff","vision","creative"],"category":"creative","homepage":"https://github.com/danilo-znamerovszkij/draw-your-font","related_skills":["pixel-art"]}} |
Photo of handwritten letters in → installable font out. You do the seeing (find and label letters, judge quality); the CLI does all geometry (trace, metrics, font assembly). Never edit SVG paths or coordinates yourself.
The CLI is the pinned npm package draw-your-font@0.1.0 — run it via npx (Node ≥ 18 required, no global install needed):
npx -y draw-your-font@0.1.0 --help
Wherever the examples below show $DYF, use npx -y draw-your-font@0.1.0. Shell variables do not persist between tool calls, so paste the full command each time. Everything runs locally; the user's handwriting never leaves the machine.
Photos arrive in Hermes either as a file path in the message or via the gateway image cache — use the actual file path with the CLI. When a photo lands in the conversation with no path, ask the user for the file (the CLI needs a real file, not your memory of the image).
Do the visual steps (contact sheets, previews, glyph sheets) by loading the PNGs with vision_analyze.
$DYF template -o template.pdf --charset minimal # or: spanish
Tell the user: print it, write one character per box with a dark pen (0.5 mm+), keep the letter sitting on the solid line, then photograph each page from above in good light and share the file paths. The grid prints in light grey and vanishes during processing - only their ink survives.
1. Segment. Works for template pages and freeform photos alike:
$DYF segment photo1.jpg photo2.jpg -d work
2. Look, then label. Load work/contact-1.png with vision_analyze (one per photo): every
detected blob is numbered. This is the step where your eyes matter - check:
""), and two touching letters may
share one box (ask the user to re-shoot just those, or accept the gap)."".Then write work/labels.json mapping blob id → character, e.g.
{"0": "A", "1": "B", "7": "", "8": "a"}:
.,;:!?'"-()@#&+/$; spanish appends ÑñÁÉÍÓÚáéíóúü¿¡."" the other.3. Build.
$DYF build -d work --labels work/labels.json --name "Dan's Hand"
Name the font after the user (ask if unclear - one short question max).
4. Judge before delivering. Load work/preview.png and work/glyphs.png with vision_analyze
and critique like an art director:
--weight 1, or ask for a re-shoot of just that letter.--weight 1 / --weight -1.--smooth 1.5 (up to 2).g not descending) → usually a mislabel;
fix labels.json and rebuild.Rebuilds are cheap and safe to iterate. Fix what you can yourself first; only bother the user for re-shoots when the source ink is the problem.
5. Deliver. The font lands at <workdir>/<NameWithoutSpaces>.ttf (the
build output prints the exact path). Give that path and how to install:
macOS - double-click → "Install Font"; Windows - right-click → "Install".
Mention what's missing (the build prints uncovered letters) and offer,
without pushing:
--formats ttf,woff,woff2,css.$DYF segment p1.jpg p2.jpg -d work2 - then relabel from the new contact sheets (blob ids renumber; the
old labels.json does not carry over) and build from the new workdir.| User says | Do |
|---|---|
| "smoother / rounder" | build … --smooth 1.5 (max 2) |
| "thicker / bolder" | build … --weight 1 (max 2) |
| "thinner / lighter" | build … --weight=-1 (negative needs the = form) |
| "the g looks bad" | show them work/crops/<id>.png for that letter; offer re-shoot or smooth |
| "wrong letter" / swap | edit labels.json, rebuild |
| "give me woff2 / web" | build … --formats ttf,woff,woff2,css |
| custom preview text | $DYF preview -d work --text "…" (after a build) |
All refine commands rebuild from the stored crops - no re-photographing needed unless the ink itself is the problem.
$DYF preview -d work --text "minimum mill rn m cl d I l 1 O 0 quick brown fox" -o work/legibility.png
Read it and give an honest, kind read: a score out of 10 for body-text use, the 2–3 letter pairs most likely to confuse (rn→m, cl→d, I/l/1, O/0), and one or two concrete fixes (rewrite those letters larger, more spacing). Note that display use (headings, notes) is more forgiving than paragraphs. Never gate delivery on this - it's advice, not a blocker.
Segmentation found far too many / too few blobs, grey guide lines surviving,
shadow blobs, faint ballpoint strokes → see
references/troubleshooting.md.