open-slide-best-practices

open-slide-best-practices is a skill for Claude Code, Codex from skills-il/developer-tools. It costs 179 tokens per session (5,194 once invoked), scanned A, original, MIT.

A set of authoring rules for open-slide, a React-based tool for creating presentations on a fixed 1920×1080 canvas. It includes guidance for Hebrew, right-to-left (RTL) text, themes, design tokens, and inspector comments.

In plain words
What is it for?
Use it when creating or editing slides, building themes, or processing inspector comments in an open-slide project. It is especially relevant for Hebrew and bilingual presentations.
Why use it?
It helps prevent layout and typography problems when slides contain Hebrew or mixed Hebrew and English. It explains how to work within open-slide's file structure and visual system.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit Use it when creating or editing slides, building themes, or processing inspector comments in an open-slide project. It is especially relevant for Hebrew and bilingual presentations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/skills-il/developer-tools/open-slide-best-practices
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add skills-il/developer-tools --skill open-slide-best-practices
Clone the repo
git clone --depth 1 https://github.com/skills-il/developer-tools

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for open-slide-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/skills-il/developer-tools/open-slide-best-practices.svg)](https://agentmods.dev/skills/skills-il/developer-tools/open-slide-best-practices)
Your own site
<a href="https://agentmods.dev/skills/skills-il/developer-tools/open-slide-best-practices"><img src="https://agentmods.dev/badge/skills/skills-il/developer-tools/open-slide-best-practices.svg" alt="Measured on agentmods" height="20"></a>
Per session 179 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,194 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 26
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00179 $0.05194
Opus 5 $0.00089 $0.02597
Sonnet 5 $0.00036 $0.01039
Haiku 4.5 $0.00018 $0.00519

Measured 8d ago against content hash 1be93ba3479c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

open-slide-best-practices scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

open-slide-best-practices/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

open-slide Best Practices for Israeli Developers

Adapted from 1weiho/open-slide (MIT). Hebrew and RTL adaptations by skills-il.

Problem

open-slide ships an opinionated authoring system: a fixed 1920×1080 React canvas, a typed DesignSystem const, a themes folder, an inspector that drops @slide-comment markers in source, and five built-in skills (slide-authoring, create-slide, create-theme, apply-comments, current-slide). None of those touch Hebrew or RTL. Out of the box, a deck written by a coding agent comes out left-aligned, system-font only, with paddingLeft that fights the Hebrew reading order, and no guidance for mixed Hebrew+English text. Israeli developers waste hours retrofitting RTL, loading Hebrew Google Fonts, and discovering that the type scale (140–200px hero) which works in Inter looks cramped in Heebo at the same weight.

Instructions

When to use

Use this skill whenever you are writing or editing code under slides/<id>/ in an open-slide project, creating a theme under themes/, or processing inspector comments — especially when any of that content is in Hebrew or bilingual.

New project setup

When in an empty folder or workspace with no existing open-slide project, scaffold one using:

npx @open-slide/cli init my-slide
cd my-slide
npm run dev

Replace my-slide with a suitable project name. The scaffolder installs dependencies with npm and prints npm run dev as the next step; pnpm dev works too if you re-install with pnpm.

Node version. @open-slide/cli depends on commander@15, which declares "node": ">=22.12.0", and on chalk@6 (">=22"). On Node 20 the install still completes but npm prints EBADENGINE Unsupported engine for both. Use Node 22.12 or newer.

What the scaffold gives you:

Path What it is
slides/<id>/index.tsx One folder per slide. See the id rule below.
themes/ Theme markdown files
open-slide.config.ts Typed OpenSlideConfig export, empty by default. Framework-level options live here: base, slidesDir, themesDir, assetsDir, port, allowedHosts, build, and a deprecated locale.
.agents/skills/ and .claude/skills/ The five upstream skills, copied in at init time
npm run sync:skills Re-copies the bundled skills out of @open-slide/core after a core upgrade

Read the full file on GitHub · 207 lines

Files

What ships with it

10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 207 lines · 179 tokens per session scan A 1be93ba3479c

Subscribe to this mod's changes

open-slide-best-practices is a skill published in the GitHub repository skills-il/developer-tools (10 stars, last pushed 6d ago), licensed MIT. It adds 179 tokens to every session and 5,194 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

Remotion

Creates programmatic video with React via Remotion — compositions, sequences, and motion graphics animated with useCurrentFrame() and rendered to MP4. USE WHEN video, animation, motion graphics, video rendering, React video, render video, animate content, make a short, create animations, video overlay, explainer…

danielmiessler/LifeOS · 121 tokens

tamagui

Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with styled(), configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/"…

tamagui/tamagui · 90 tokens

remotion-best-practices

Best practices for Remotion - Video creation in React.

vercel-labs/json-render · 17 tokens

r3f-animation

React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.

zebbern/claude-code-guide · 43 tokens

remotion-best-practices

Best practices for Remotion - Video creation in React.

haydenbleasel/ultracite · 17 tokens

add-component

Add a new visualization component to Unovis end to end — the TypeScript core, the shared registry, the generated framework wrappers, a dev example, a gallery example, and docs. Use when asked to add/create a new component, chart type, plot, or diagram to the library, or to wire an existing core component through to…

f5/unovis · 74 tokens