Skip to content
Back to search

Prakhar-Claude-skills

Claude Code skills: plain-English explainers, flow diagram pages, and a dev-server session recorder

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/prakhar383--prakhar-claude-skills/badge.svg)](/listings/prakhar383--prakhar-claude-skills)

HTML

<a href="/listings/prakhar383--prakhar-claude-skills"><img src="/api/listings/prakhar383--prakhar-claude-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You need [Claude Code](https://docs.claude.com/en/docs/claude-code/overview) and [Git](https://git-scm.com). `flow-explainer` also needs [Node.js](https://nodejs.org) 18 or newer (nothing to `npm install`: the script has no dependencies).

Windows (PowerShell)

git clone https://github.com/prakhar383/Prakhar-Claude-skills.git
cd Prakhar-Claude-skills
powershell -ExecutionPolicy Bypass -File .\install.ps1

macOS or Linux

git clone https://github.com/prakhar383/Prakhar-Claude-skills.git
cd Prakhar-Claude-skills
chmod +x install.sh
./install.sh

Then start a new Claude Code session. Type `/` and you should see `explainer`, `explainer-short`, `flow-explainer` and `watch-run` in the list.

Install options

| You want | Windows | macOS / Linux | |---|---|---| | Only some tools | `.\install.ps1 explainer,flow-explainer` | `./install.sh explainer flow-explainer` | | Install into one project only | `.\install.ps1 -Project "C:\code\my-app"` | `./install.sh --project ~/code/my-app` | | Replace a copy you installed before | `.\install.ps1 -Force` | `./install.sh --force` |

Names you can pass: `explainer`, `explainer-short`, `flow-explainer`, `terminal-watcher`.

**For all projects or for one?** By default the tools go into your home folder (`~/.claude/`, on Windows `C:\Users\<you>\.claude\`), so they work in every project on that computer. With the project option they go into that project's `.claude/` folder instead. Commit that folder if you want your team, or Claude Code on the web (which works from the repository), to have them too.

**Updating later:** `git pull` in this folder, then run the installer again with `-Force` / `--force`. A knowledge map you have filled in (see below) is kept.

Install by hand

Copy the folders yourself if you prefer:

| From this repo | To | |---|---| | `skills/explainer/` | `~/.claude/skills/explainer/` | | `skills/explainer-short/` | `~/.claude/skills/explainer-short/` | | `skills/flow-explainer/` | `~/.claude/skills/flow-explainer/` | | `terminal-watcher/agents/terminal-watcher.md` | `~/.claude/agents/terminal-watcher.md` | | `terminal-watcher/commands/watch-run.md` | `~/.claude/commands/watch-run.md` |

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 119 lines
  1. # Prakhar's Claude Code skills
  2. Four home-made tools for [Claude Code](https://docs.claude.com/en/docs/claude-code/overview),
  3. built for someone who owns a software product but does not read code. They make Claude
  4. explain things in plain English, draw them as diagrams, and record manual testing sessions.
  5. | Tool | What it does | How you start it |
  6. |---|---|---|
  7. | [explainer](skills/explainer/) | Explains how something works, or what a plan will change, in plain English. Adds a diagram, a table, or pros and cons with real, sourced numbers only when they help. | Ask "explain…", "how does X work?", "walk me through…", or type `/explainer` |
  8. | [explainer-short](skills/explainer-short/) | The quick version: a two or three line answer, with at most one bullet list, small table or tiny chart. | Ask "quick question…", "in short…", "tl;dr", or type `/explainer-short` |
  9. | [flow-explainer](skills/flow-explainer/) | Draws any topic as a hand-drawn style flow diagram page (flowchart, swimlane, who-talks-to-whom, org chart) and opens it in your browser. | Ask "draw the flow of…", "diagram this", "flowchart", or type `/flow-explainer` |
  10. | [terminal-watcher](terminal-watcher/) | Starts your app, records everything the dev server prints while you click around, then writes a report of load times, errors and wasted API calls. | Type `/watch-run` (optionally `/watch-run detailed` or `/watch-run testing the checkout`) |
  11. The three explainer skills work together: an `explainer` answer can be turned into a
  12. `flow-explainer` page by saying "make it a page", and `explainer-short` offers the full
  13. `explainer` when a question is too big for three lines.
  14. ---
  15. ## Install
  16. You need [Claude Code](https://docs.claude.com/en/docs/claude-code/overview) and
  17. [Git](https://git-scm.com). `flow-explainer` also needs [Node.js](https://nodejs.org) 18 or
  18. newer (nothing to `npm install`: the script has no dependencies).
  19. ### Windows (PowerShell)
  20. ```powershell
  21. git clone https://github.com/prakhar383/Prakhar-Claude-skills.git
  22. cd Prakhar-Claude-skills
  23. powershell -ExecutionPolicy Bypass -File .\install.ps1
  24. ```
  25. ### macOS or Linux
  26. ```bash
  27. git clone https://github.com/prakhar383/Prakhar-Claude-skills.git
  28. cd Prakhar-Claude-skills
  29. chmod +x install.sh
  30. ./install.sh
  31. ```
  32. Then start a new Claude Code session. Type `/` and you should see `explainer`,
  33. `explainer-short`, `flow-explainer` and `watch-run` in the list.
  34. ### Install options
  35. | You want | Windows | macOS / Linux |
  36. |---|---|---|
  37. | Only some tools | `.\install.ps1 explainer,flow-explainer` | `./install.sh explainer flow-explainer` |
  38. | Install into one project only | `.\install.ps1 -Project "C:\code\my-app"` | `./install.sh --project ~/code/my-app` |
  39. | Replace a copy you installed before | `.\install.ps1 -Force` | `./install.sh --force` |
  40. Names you can pass: `explainer`, `explainer-short`, `flow-explainer`, `terminal-watcher`.
  41. **For all projects or for one?** By default the tools go into your home folder
  42. (`~/.claude/`, on Windows `C:\Users\<you>\.claude\`), so they work in every project on
  43. that computer. With the project option they go into that project's `.claude/` folder
  44. instead. Commit that folder if you want your team, or Claude Code on the web (which works
  45. from the repository), to have them too.
  46. **Updating later:** `git pull` in this folder, then run the installer again with
  47. `-Force` / `--force`. A knowledge map you have filled in (see below) is kept.
  48. ### Install by hand
  49. Copy the folders yourself if you prefer:
  50. | From this repo | To |
  51. |---|---|
  52. | `skills/explainer/` | `~/.claude/skills/explainer/` |
  53. | `skills/explainer-short/` | `~/.claude/skills/explainer-short/` |
  54. | `skills/flow-explainer/` | `~/.claude/skills/flow-explainer/` |
  55. | `terminal-watcher/agents/terminal-watcher.md` | `~/.claude/agents/terminal-watcher.md` |
  56. | `terminal-watcher/commands/watch-run.md` | `~/.claude/commands/watch-run.md` |
  57. ---
  58. ## Set up after installing (five minutes, optional but worth it)
  59. 1. **Teach the explainer your project.** Open Claude Code in the project and say:
  60. *"fill in the explainer knowledge map for this project"*. Claude replaces the template
  61. in `skills/explainer/references/knowledge-map.md` with where your project keeps its
  62. docs, plans and code, and the traps that cause wrong answers. Until then the explainer
  63. still works; it just searches more.
  64. 2. **Tell the explainers how you like things explained** (optional). Create
  65. `~/.claude/explanation-preferences.md` with a few lines, for example "British English",
  66. "always give one real example", "no jargon without a meaning in brackets". Both
  67. explainers read it, and add a dated note to it when an explanation fails and a second
  68. try works, so it gets better over time.
  69. 3. **Choose where diagrams are saved** (optional). Pages go to `~/Flow-Explainer/` unless
  70. you set the `FLOW_EXPLAINER_DIR` environment variable to another folder.
  71. 4. **Point `/watch-run` at your app** (optional). It works out your app folder, dev command
  72. and port on its own. To fix them, edit the "Settings for this project" table at the top
  73. of `commands/watch-run.md`.
  74. ---
  75. ## What is in this repo
  76. ```
  77. skills/
  78. explainer/ SKILL.md, references/knowledge-map.md (template), references/worked-example.md
  79. explainer-short/ SKILL.md, references/examples.md
  80. flow-explainer/ SKILL.md, scripts/make-page.mjs, assets/ (page templates), references/spec-format.md
  81. terminal-watcher/
  82. agents/terminal-watcher.md the recorder agent that writes the report
  83. commands/watch-run.md the /watch-run command that runs the session
  84. install.ps1, install.sh installers
  85. ```
  86. Each tool's folder has its own README with examples.
  87. ## Not included
  88. These skills were first written for one private project. Anything specific to that project
  89. (its folder paths, internal names and figures) has been replaced with neutral examples or
  90. fill-in settings. A project-only skill for triaging errors from that project's monitoring
  91. screen is not published here.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.