Skip to content
Back to search

rajitjosh

MarketplaceWorks with Claude CodeGitHub

rajitjosh's Claude Code skills for Frappe/ERPNext and product videos.

Safety scan

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

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

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

HTML

<a href="/listings/rajitjosh--claude-skills"><img src="/api/listings/rajitjosh--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.

In Claude Code:

/plugin marketplace add rajitjosh/claude-skills
/plugin install rajitjosh-skills@rajitjosh
/plugin install bench-wizard-frappe@rajitjosh

With the [`skills`](https://github.com/vercel-labs/skills) installer, for Claude Code, Codex, Cursor and others:

npx skills add rajitjosh/claude-skills

Or copy a folder from `skills/` into `~/.claude/skills/`.

A skill loads by itself when your request matches it ("make a walkthrough video of …"), or by name: `/recording-walkthrough-videos`.

---

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.

.claude-plugin/marketplace.json · Manifest · 26 lines
  1. {
  2. "name": "rajitjosh",
  3. "description": "rajitjosh's Claude Code skills for Frappe/ERPNext and product videos.",
  4. "owner": {
  5. "name": "rajitjosh"
  6. },
  7. "plugins": [
  8. {
  9. "name": "rajitjosh-skills",
  10. "source": "./",
  11. "description": "Frappe/ERPNext dashboards, plus walkthrough and promo videos of any web app."
  12. },
  13. {
  14. "name": "bench-wizard-frappe",
  15. "source": {
  16. "source": "github",
  17. "repo": "rajitjosh/bench-wizard"
  18. },
  19. "description": "What a Frappe/ERPNext custom app must change for a new Frappe version (frappe-upgrade-impact). Lives in Bench Wizard.",
  20. "strict": false,
  21. "skills": [
  22. "./bench_wizard/claude-plugin/skills/frappe-upgrade-impact"
  23. ]
  24. }
  25. ]
  26. }
README.md · README · 274 lines
  1. # claude-skills
  2. Skills for [Claude Code](https://claude.com/claude-code) (and other agents that read `SKILL.md` skills) from work on
  3. Frappe/ERPNext apps: dashboards, upgrades, and walkthrough and promo videos of any web app.
  4. | Skill | Use it for |
  5. |---|---|
  6. | [`recording-walkthrough-videos`](#recording-walkthrough-videos) | A captioned (optionally voiced) walkthrough video of a web app flow, scripted as a Playwright test so a broken flow fails the run: mp4 with chapters and a poster, subtitles, step-by-step stills and `steps.md` for setup docs, and share copy. Notes for Frappe desk and Vuetify apps. |
  7. | [`making-product-promo-videos`](#making-product-promo-videos) | A 30-90 s promo film of the real product, built in HyperFrames from clean Playwright captures: the script approved first, crops and highlights from the page's real boxes, music picked and synced by measurement, every number from a recorded run, delivered with a poster, share copy and cutdowns. |
  8. | [`frappe-premium-dashboard`](#frappe-premium-dashboard) | A polished, animated dashboard inside a Frappe/ERPNext custom app, not a stock Workspace: the delivery route (Vue 3 with frappe-ui, a Desk page or a web page), a permission-checked and cached data layer, layout, design tokens, charts, and motion that respects reduced-motion. |
  9. | [`frappe-upgrade-impact`](https://github.com/rajitjosh/bench-wizard/tree/main/bench_wizard/claude-plugin) | What a Frappe/ERPNext custom app must change for a new Frappe version, with a scanner for core APIs, overrides, fields and the known breaking changes. It lives in [Bench Wizard](https://github.com/rajitjosh/bench-wizard), which runs it from its Upgrade page; this marketplace lists it from there. |
  10. ## Install
  11. In Claude Code:
  12. ```
  13. /plugin marketplace add rajitjosh/claude-skills
  14. /plugin install rajitjosh-skills@rajitjosh
  15. /plugin install bench-wizard-frappe@rajitjosh
  16. ```
  17. With the [`skills`](https://github.com/vercel-labs/skills) installer, for Claude Code, Codex, Cursor and others:
  18. ```
  19. npx skills add rajitjosh/claude-skills
  20. ```
  21. Or copy a folder from `skills/` into `~/.claude/skills/`.
  22. A skill loads by itself when your request matches it ("make a walkthrough video of …"), or by name:
  23. `/recording-walkthrough-videos`.
  24. ---
  25. ## recording-walkthrough-videos
  26. A step-by-step video of a real flow in your app, with a caption for every step. The flow is a Playwright test: every
  27. step is asserted, so a broken flow fails the run instead of shipping a misleading video.
  28. ![A walkthrough frame: the field being explained is outlined, and the caption box sits out of its way](docs/images/wt-caption.jpg)
  29. *The field being explained is outlined (`spot()`), and the caption moves out of its way by itself.*
  30. ![A chapter card opening a part of the walkthrough](docs/images/wt-card.jpg)
  31. *Each part opens with a chapter card; each card becomes a chapter of the mp4.*
  32. ### What you get
  33. ```
  34. out/<flow>-2026-11-20-1430/
  35. <flow>.mp4 the video: H.264, plays everywhere, chapters embedded, the poster as frame 0
  36. <flow>.jpg the poster (the thumbnail chat apps show)
  37. <flow>.vtt subtitles matching the captions
  38. <flow>.chapters.vtt chapters for web players
  39. youtube-chapters.txt "0:00 Set up a new bench" lines to paste under a link
  40. steps.md every step: heading, text, timestamp, still (the start of a setup doc)
  41. stills/01.png … one screenshot per step, without its caption
  42. contact-sheet.png one frame every 5 s, to check the whole video at a glance
  43. share-copy.md a chat post and an email version, written by the agent
  44. ```
  45. ### What you need
  46. - The app running on a **dev or staging** site (never production: the recording writes real records), and a seeded
  47. demo login.
  48. - Node 22 or newer (`nvm use 24`), Playwright 1.65 or newer (for the animated cursor and click highlight), and system
  49. `ffmpeg` with `ffprobe`.
  50. - For a voiceover, a one-time offline setup of Kokoro (see the header of
  51. [`voice.py`](skills/recording-walkthrough-videos/voice.py)).
  52. ### How to ask
  53. Write a sentence ("make a video of how HR raises OT on staging"), or fill in the request; the agent asks only for what
  54. is missing and offers every choice you didn't make, with a recommendation:
  55. ```
  56. Walkthrough video: OT calculation on Payroll Entry
  57. Who will see it: internal only
  58. Site: https://staging.example.com
  59. Login: use out/.auth.json (demo user hr.demo)
  60. Audience: end users
  61. Flows: open OT Calculation for one employee; update the hours; create salary slips
  62. Layout: panel
  63. Pace: relaxed
  64. Voiceover: yes, voice af_heart
  65. Extras: Word doc from the steps
  66. ```
  67. "Who will see it" matters: lists, logs and file names on screen show real names. For a public video the agent runs an
  68. app instance that sees only demo data.
  69. ### What happens
  70. ```mermaid
  71. flowchart LR
  72. R[Request] --> S[Storyboard<br/>3-6 parts,<br/>you sign off]
  73. S --> W[Script<br/>one Playwright test,<br/>every step asserted]
  74. W --> D[Dry run<br/>DEMO_FAST=1]
  75. D -->|fails| W
  76. D --> V{Voice?}
  77. V -->|yes| K[Synthesize lines<br/>offline]
  78. V -->|no| REC[Record]
  79. K --> REC
  80. REC --> C[Check<br/>contact sheet,<br/>stills, mp4]
  81. C --> H[Hand over<br/>mp4, vtt, steps.md,<br/>share-copy.md]
  82. ```
  83. Every dry run repeats the flow's writes (backups, records), so the agent says what each run adds and iterates on one
  84. part at a time.
  85. ### Commands
  86. The agent runs these; they are here so you can re-record yourself.
  87. ```bash
  88. # dry run: every hold 300 ms, no slow motion: selector and data failures show in seconds
  89. DEMO_FAST=1 npx playwright test -c <dir>/demo.config.ts
  90. # record
  91. DEMO_LAYOUT=overlay DEMO_PACE=1 npx playwright test -c <dir>/demo.config.ts
  92. # one part only, while fixing it
  93. DEMO_FROM=3 DEMO_STOP=3 DEMO_FAST=1 npx playwright test -c <dir>/demo.config.ts
  94. ```
  95. | Setting | Values |
  96. |---|---|
  97. | `DEMO_LAYOUT` | `overlay` (default): the app full screen, a caption box placed automatically · `panel`: 1920x1080, the app at full size beside a text column that never covers it |
  98. | `DEMO_PACE` | `0.7` brisk · `1` normal · `1.4` relaxed (scales clicks and caption holds together) |
  99. | `DEMO_VOICE` | `af_heart` (default voice), `am_michael`, `bf_emma` · leave unset for no voice |
  100. ### The script, in short
  101. ```ts
  102. const demo = await Demo.start(page, context, "out/ot-2026-11-20-1430"); // first, before login and seeding
  103. // …log in and seed through the API…
  104. await demo.open("/app/payroll-entry");
  105. const app = demo.app; // every locator goes through this, so both layouts work
  106. demo.begin(); // the mp4, subtitles and steps.md start here
  107. if (runPart(1)) {
  108. await demo.card("Part 1", "Open OT Calculation", ["Done once a month by HR"]);
  109. await app.getByRole("button", { name: "OT Calculation" }).click();
  110. await expect(app.getByText("Employee")).toBeVisible();
  111. await spot(app.locator('[data-fieldname="employee"]'));
  112. await demo.say("Part 1", "Pick the employee", "Only employees with OT this month are listed.");
  113. await spot(app.locator('[data-fieldname="employee"]'), false);
  114. await demo.poster(); // the thumbnail: the strongest settled screen
  115. }
  116. await demo.finish("ot");
  117. ```
  118. [`kit-selftest.demo.ts`](skills/recording-walkthrough-videos/kit-selftest.demo.ts) tests the kit (30 tests); the skill
  119. also carries notes for [Frappe desk](skills/recording-walkthrough-videos/frappe.md) and
  120. [Vuetify apps](skills/recording-walkthrough-videos/vuetify.md).
  121. ### Sharing
  122. Over 25 MB in total, or for an email list, share Drive links rather than attachments, restricted to your domain when the
  123. screens show client data. Drive and browsers ignore embedded chapters, so paste `youtube-chapters.txt` under the link.
  124. ---
  125. ## making-product-promo-videos
  126. A short film of the real product: real screens, real numbers from a recorded run, cut to music. The script is the
  127. contract, approved before anything is captured or built.
  128. ![Four beats of a promo: a version picked with its card ringed, safety switches in dark mode, a port clash fixed, and an upgrade table with its target column ringed](docs/images/promo-beats.jpg)
  129. *Four beats of one film. The label column on the left says what happened; the ring marks the one result, placed from
  130. the element's real box on the page.*
  131. ![The end card: the app icon, its name, a one-line positioning and the repository link](docs/images/promo-endcard.jpg)
  132. *The end card: the product's own icon, its name and the link.*
  133. ### What you get
  134. ```
  135. renders/<name>-2026-11-20-1700/
  136. film.mp4 1920x1080, music and sound, the poster as frame 0
  137. film.jpg the poster
  138. share-copy.md a chat post and an email version, with the real numbers
  139. film-vertical.mp4 optional 15-20 s cutdowns for social (1080x1920 or 1080x1080), each with its poster
  140. ```
  141. ### What you need
  142. - The app running on a dev or staging site, with demo data that has clean names (no "test" anywhere on screen).
  143. - [HyperFrames](https://github.com/heygen-com/hyperframes) (`npx hyperframes auth login`, free) and the `heygen` CLI
  144. for the music catalog. Node 22 or newer, Playwright 1.65 or newer, system `ffmpeg`.
  145. ### How to ask
  146. ```
  147. Make a 60-second promo video of <product> from its real screens.
  148. App runs at <dev URL>. Audience: <who>. End card link: <link>.
  149. ```
  150. ### What happens
  151. Every step ends with a gate; the next step doesn't start until it holds.
  152. ```mermaid
  153. flowchart TD
  154. P0[0 · Read the project<br/>flow, real numbers, palette, icon, audience] --> P1[1 · Three storylines<br/>you pick one]
  155. P1 --> P2[2 · SCRIPT.md<br/>you approve it]
  156. P2 --> P3[3 · Capture<br/>clips, 2x stills, element boxes]
  157. P3 --> P4[4 · Music<br/>track, start offset, locked hits]
  158. P4 --> P5[5 · Sound effects<br/>each with a cause on screen]
  159. P5 --> P6[6 · Build in HyperFrames<br/>check + review]
  160. P6 --> P7[7 · Preview<br/>you approve, audio measured]
  161. P7 --> P8[8 · Deliver<br/>poster, share copy, cutdowns]
  162. P3 -. numbers changed .-> P2
  163. ```
  164. What keeps it honest and readable:
  165. - **Real screens and numbers.** Every number on screen comes from the recorded run. Numbers in the script are
  166. placeholders until the capture, and the agent tells you when the real ones differ.
  167. - **Highlights from the page, never by eye.** The capture records each component's real box with the still:
  168. ```ts
  169. await clip.shot("upgrade-table", {
  170. crop: page.locator(".upgrade-card table"), // what the panel shows
  171. ring: page.locator("td.moves-to"), // the one result to ring
  172. });
  173. ```
  174. - **Music by measurement.** Candidates from the catalog, then `hyperframes beats` and `hyperframes audio`: bars that
  175. divide the 5-6 s feature beats, a start offset that lands the strongest hits on the reveal and the payoff (within
  176. ±0.15 s), the tail after the end card.
  177. - **Reading over motion.** Text never snaps to every beat, zooms never push context out of frame, and reading shots
  178. hold still.
  179. [`kit-selftest.capture.ts`](skills/making-product-promo-videos/kit-selftest.capture.ts) tests the capture kit.
  180. ---
  181. ## frappe-premium-dashboard
  182. A dashboard inside a Frappe/ERPNext custom app that looks and moves like a modern SaaS product: a hero, rolling-digit
  183. KPIs, a card grid and custom charts. Stock Workspaces, Number Cards and Dashboard Charts can't produce this, so it
  184. builds a custom page in your custom app and never touches core files.
  185. ### How to ask
  186. ```
  187. Build a sales dashboard in <custom app> with 4-6 KPIs per tab (orders, revenue, top customers),
  188. filters by company and date, for the Sales Manager role.
  189. ```
  190. ### What happens
  191. 1. **Pick the delivery route** (the agent asks if unclear):
  192. | Route | When |
  193. |---|---|
  194. | A. Vue 3 SPA with frappe-ui (default) | A full-screen app feel, tabs, rich interaction and motion |
  195. | B. Desk Page | It must live inside `/app` with the navbar |
  196. | C. Web page (`www/`) | Read-only, shareable with portal users |
  197. 2. **Data layer first:** whitelisted API methods with permission checks, tested with `bench execute`.
  198. 3. **Components, then tabs:** rolling KPI digits, chart cards, ranked bars, filters, detail panel, skeletons, wired to
  199. shared filter state.
  200. 4. **Motion last**, with a reduced-motion path; checked at desktop and 375 px width, as a restricted user, at 60 fps.
  201. You get the file tree of changes, the API module, the components and CSS tokens, the `hooks.py` entries and a short
  202. README (route, roles, how to add a card, how to tune motion).
  203. ---
  204. ## License
  205. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

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