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.
Badge for your README
Markdown
[](/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
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
- # Prakhar's Claude Code skills
- Four home-made tools for [Claude Code](https://docs.claude.com/en/docs/claude-code/overview),
- built for someone who owns a software product but does not read code. They make Claude
- explain things in plain English, draw them as diagrams, and record manual testing sessions.
- | Tool | What it does | How you start it |
- |---|---|---|
- | [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` |
- | [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` |
- | [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` |
- | [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`) |
- The three explainer skills work together: an `explainer` answer can be turned into a
- `flow-explainer` page by saying "make it a page", and `explainer-short` offers the full
- `explainer` when a question is too big for three lines.
- ---
- ## Install
- 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)
- ```powershell
- git clone https://github.com/prakhar383/Prakhar-Claude-skills.git
- cd Prakhar-Claude-skills
- powershell -ExecutionPolicy Bypass -File .\install.ps1
- ```
- ### macOS or Linux
- ```bash
- 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` |
- ---
- ## Set up after installing (five minutes, optional but worth it)
- 1. **Teach the explainer your project.** Open Claude Code in the project and say:
- *"fill in the explainer knowledge map for this project"*. Claude replaces the template
- in `skills/explainer/references/knowledge-map.md` with where your project keeps its
- docs, plans and code, and the traps that cause wrong answers. Until then the explainer
- still works; it just searches more.
- 2. **Tell the explainers how you like things explained** (optional). Create
- `~/.claude/explanation-preferences.md` with a few lines, for example "British English",
- "always give one real example", "no jargon without a meaning in brackets". Both
- explainers read it, and add a dated note to it when an explanation fails and a second
- try works, so it gets better over time.
- 3. **Choose where diagrams are saved** (optional). Pages go to `~/Flow-Explainer/` unless
- you set the `FLOW_EXPLAINER_DIR` environment variable to another folder.
- 4. **Point `/watch-run` at your app** (optional). It works out your app folder, dev command
- and port on its own. To fix them, edit the "Settings for this project" table at the top
- of `commands/watch-run.md`.
- ---
- ## What is in this repo
- ```
- skills/
- explainer/ SKILL.md, references/knowledge-map.md (template), references/worked-example.md
- explainer-short/ SKILL.md, references/examples.md
- flow-explainer/ SKILL.md, scripts/make-page.mjs, assets/ (page templates), references/spec-format.md
- terminal-watcher/
- agents/terminal-watcher.md the recorder agent that writes the report
- commands/watch-run.md the /watch-run command that runs the session
- install.ps1, install.sh installers
- ```
- Each tool's folder has its own README with examples.
- ## Not included
- These skills were first written for one private project. Anything specific to that project
- (its folder paths, internal names and figures) has been replaced with neutral examples or
- fill-in settings. A project-only skill for triaging errors from that project's monitoring
- screen is not published here.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.