agentsclimarketplace

Ascii

Skill yarikleto/claude-teacher-plugin/skills/ascii

DEFAULT diagram skill — simplest tier. Use when user invokes /ascii OR when suggesting a quick visual. Creates ASCII art rendered inline in terminal — zero friction. Escalate to /excalidraw for complex static diagrams (5+ components, multi-layer). Escalate to /demo for animated/dynamic concepts (protocol handshakes, algorithm traces, state transitions).From its SKILL.md

Install
npx -y skills add yarikleto/claude-teacher-plugin --skill ascii

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

6.9 KB, as published. Nobody here has run it

ASCII

Create ASCII art diagrams with detailed educational explanations. All output is pure Unicode box-drawing art — renders in any modern terminal, no external tools needed.

Invocation

/ascii <concept description>

Style Selection

Concept TypeStyleExample Use
Time-ordered (protocol flows, request/response)Sequence diagramTCP handshake, HTTP request
States/decisions (transitions, branching)FlowchartConnection lifecycle, error handling
Byte-level/structural (memory, packets, formats)RFC-style grid or tableTCP header, packet layout
Relationships/architecture (components, deps)Box-and-line with layersSystem architecture, module deps
Comparisons (A vs B)Side-by-side or before/afterActive vs passive mode
Hierarchies (trees, org charts)Tree with branchesDirectory structure, class hierarchy

Character Toolkit

Visual hierarchy through line weight:

WeightCharactersUse For
Double═ ║ ╔ ╗ ╚ ╝ ╠ ╣ ╦ ╩ ╬Outer boundaries, system borders, emphasis
Single─ │ ┌ ┐ └ ┘ ├ ┤ ┬ ┴ ┼Standard boxes, connections
Rounded╭ ╮ ╰ ╯Softer/informal elements
Dashed┄ ┆ or - - -Optional, conditional, weak relationships
Heavy━ ┃ ┏ ┓ ┗ ┛Bold emphasis

Arrows: → ← ↑ ↓ ↔ standard, ▶ ◀ ▲ ▼ filled, ⇒ ⇐ double

Fill/shading: ░ light, ▒ medium, ▓ dark, █ full

Elision: ⋮ vertical omission, ⋯ horizontal omission

Style Recipes

Sequence Diagram

  Client              Server
    │                    │
    │   SYN (seq=x)      │
    │───────────────────▶│
    │                    │
    │  SYN-ACK (seq=y)   │
    │◀───────────────────│
    │                    │
  • Vertical lifelines per actor, names at top
  • Horizontal arrows with labels above
  • Consistent column spacing and arrow lengths

Flowchart

  ┌─────────┐
  │  Start  │
  └────┬────┘
       │
       ▼
  condition? ──no──▶ Action B
       │                 │
      yes                │
       │                 │
       ▼                 │
  Action A               │
       │                 │
       ◀─────────────────┘
  • Avoid ASCII diamond shapes — use condition? with branching labels instead
  • Label branches on the arrows

RFC-Style Protocol Header

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Source Port          |       Destination Port        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  • Each -+- = one bit, centered field names
  • Use pure ASCII for this style — IETF convention

Architecture / Layer Diagram

╔═══════════════════════════════╗
║      Presentation Layer       ║
║  ┌────────┐    ┌───────────┐  ║
║  │  CLI   │    │  REST API │  ║
║  └───┬────┘    └─────┬─────┘  ║
╠══════╪════════════════╪═══════╣
║      ▼   Service Layer▼       ║
║  ┌────────────────────────┐   ║
║  │      Core Logic        │   ║
║  └───────────┬────────────┘   ║
╚══════════════╪════════════════╝
               ▼
         ┌──────────┐
         │ Database │
         └──────────┘
  • Double-line for system boundaries
  • Single-line for components inside
  • Horizontal dividers between layers

Process

  1. Analyze the concept — what type of information is it?
  2. Pick style using the selection table
  3. Create the diagram in a text code block:
    • Max width 78 characters
    • Generous whitespace — padding inside boxes
    • Standardize box widths where possible
    • Center vertical connectors under boxes
    • Break complex concepts into multiple smaller diagrams
  4. Research the concept using WebSearch before creating the diagram — verify accuracy against official docs, RFCs, or standards. Include source links.
  5. Write educational explanation:
    • What it shows — walk through the diagram
    • Why it works this way — reasoning behind the design
    • Key concepts — define terms that might be new
    • Common pitfalls — what people often misunderstand
    • Sources — links to official docs, RFCs, or standards used
  6. Save to docs/ — automatically save the diagram and explanation to docs/<concept-name>.md for future reference.

Quality Rules

  • Never mix pure ASCII (+ - |) with Unicode box-drawing in the same diagram
  • Align everything carefully — misaligned ASCII art is worse than no diagram
  • Use 2+ space gaps between unrelated elements
  • Keep consistent arrow lengths in sequence diagrams
  • If a diagram exceeds ~40 lines or ~10 nodes, split it up

DB Integration

After creating the diagram and explanation:

  1. Save to project-local docs/<concept-name>.md (for project-specific concepts)
  2. Save to global ~/.local/share/claude-education/docs/<concept-name>.md (for general concepts)
  3. Append to session log ~/.local/share/claude-education/sessions/[date].jsonl:
    {"time": "[now]", "event": "ascii", "topic": "[concept-slug]", "saved_to": "global|project|both"}
    
  4. If the concept corresponds to a tracked topic, update last_reviewed in its topic file

Integration with Other Skills

This skill is part of the claude-teacher plugin:

  • /quiz-me — if a student gets a visual concept wrong during a quiz, suggest illustrating it.
  • /challenge — challenges may need diagrams as part of the answer.
  • /progress — diagrams count toward topic engagement.
  • Diagrams saved to docs/ become the student's personal reference library.
  • The tutor (via CLAUDE.md) will suggest /ascii when visual explanation helps.

Keep looking

Skills are one crate of 611,178. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.