agentsclimarketplace

Opt editor install

Skill reopt-ai/reopt-skills/skills/opt-editor-install

Agent skills for the reopt ecosystem — CLI workflows, Brandapp SDK install/review, and @reopt-ai/opt-* component package setup. Installs into Claude Code, Cursor, Codex, Cline, Gemini CLI, and more via skills.sh.

Install
npx -y skills add reopt-ai/reopt-skills --skill opt-editor-install

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

  • 1 stars1 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.

What its author says it does

Copied from the file, not written here

Install or upgrade @reopt-ai/opt-editor in a consumer project. Auto-branches by current install state. Triggers on "opt-editor install", "opt-editor init", "opt-editor setup", "editor install", "editor init", "opt-editor upgrade", "opt-editor update", "editor upgrade", "editor update".

SKILL.md

4.1 KB, as published. Nobody here has run it

opt-editor Install

This is NOT the opt-editor you know. Read node_modules/@reopt-ai/opt-editor/dist/docs/ before writing code.

When to apply

Consumer project depends on @reopt-ai/opt-editor. Triggers: "install", "init", "setup", "upgrade", "update" — with or without an opt- / editor prefix.

Invocation

/opt-editor-install              # Auto-branch (missing → init, installed → upgrade)
/opt-editor-install --with-ai    # Init + AI streaming integration
/opt-editor-install 1.0.0        # Upgrade to a specific version
/opt-editor-install --dry-run    # Analyze only

Step 1 — Pin agent rules into AGENTS.md / CLAUDE.md

Source: the module's own agent-rules file once it ships one (@reopt-ai/opt-editor does not, as of 1.1.2). Fallback: agent-rules.md bundled with this skill. Wrap content between:

<!-- BEGIN:reopt/opt-editor-agent-rules -->
…content from source…
<!-- END:reopt/opt-editor-agent-rules -->

Idempotent: replace only between markers.

Step 2 — Consumer-side setup (this skill owns; docs cannot)

  1. Public npm registry — no token or scoped .npmrc entry is required. Inspect the project .npmrc and npm config get @reopt-ai:registry; if the scope still resolves to GitHub Packages, remove only the legacy project entry @reopt-ai:registry=https://npm.pkg.github.com. Preserve unrelated registry/auth settings, and ask before changing user/global npm config.

  2. Prereqs — Node 18+, React 19+, bun or npm. AI integration uses optional peers ai >= 7 and zod >= 3; do not install them for a non-AI editor.

  3. App wiring — properties of the consumer app:

    • Editor CSS import at the app root.
    • Catalog file (catalog.ts or similar) — block-definition registry.
    • AI endpoint (when --with-ai): a Vercel AI SDK–compatible route.
  4. Doctornpx @reopt-ai/opt-cli doctor runs the audit (unified design CLI; there is no opt-editor-cli).

Step 3 — Route to module docs

Task signalRead
Start here — doc indexdist/docs/index.md
Getting started / install / upgradedist/docs/01-getting-started.md
API (components, hooks, store, serialization, types)dist/docs/02-api/
AI streaming integrationdist/docs/02-api/04-ai-stream.md, dist/docs/03-recipes/03-ai-streaming.md
High-level AI ops / agent-mode tools (EditorOperation, OperationCompiler)dist/docs/03-recipes/08-editor-operations.md
Diff-mode suggestion review (mode="diff")dist/docs/03-recipes/09-diff-review-integration.md
Recipes (basic, custom blocks, markdown, image, …)dist/docs/03-recipes/
Troubleshootingdist/docs/05-troubleshooting.md

Pipeline (auto-branch)

#StepInitUpgrade
1Detect current state
2Public-registry preflight + legacy override cleanup
3Install / update package
4CSS import check
5Catalog generation
6Editor component generation
7Breaking-change edits
8Deprecated fixes (opt-in)
9Doctor (environment audit) + summary

Detailed procedure lives in module docs — start at dist/docs/index.md, then dist/docs/01-getting-started.md. Read before acting.

Safety

  • Never upgrade without an impact scan (run --dry-run first).
  • Confirm before overwriting existing files.
  • Apply breaking-change edits in logical groups — never bulk-apply.
  • Do not finish until tsc --noEmit passes.
  • Always provide a rollback path.

Verify

  1. npx @reopt-ai/opt-cli doctor passes.
  2. npx tsc --noEmit passes.
  3. Editor mounts and StaticRenderer renders a stored EditorSpec (its content) without console warnings.

Keep looking

Skills are one crate of 328,083. 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.