ClawHub

reinvent4

v1.0.0

Help install, configure, run, troubleshoot, and extend MolecularAI REINVENT4 for generative molecular design. Use when the user mentions REINVENT4 or Reinven...

⭐ 0· 75·0 current·0 all-time
by@zoeprior
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the contents: SKILL.md and the three reference files all explain install, config, plugins, notebooks, and tests for REINVENT4. There are no unrelated required binaries, env vars, or config paths declared.
ℹ
Instruction Scope
Instructions correctly direct the agent to read local repo files (install.py, pyproject.toml, configs/) and to prefer dry-run/help checks (e.g., `python install.py --help`, `--dry-run`) before real installs. This scope is appropriate for an installer/helper, but it does include guidance to execute local installer scripts and CLI commands — running `python install.py` or `reinvent` executes code from the repository, so the agent/user should inspect those files before executing them in a production environment.
✓
Install Mechanism
This skill has no install spec and is instruction-only (no downloads or binary installs). That minimizes disk-write/remote-code risks from the skill itself.
✓
Credentials
No environment variables or credentials are required by the skill. The docs mention optional upstream requirements (e.g., `OE_LICENSE` for OpenEye-licensed tests) which are proportional to running those optional features and are not demanded by the skill itself.
✓
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or claim to modify other skills or system-wide agent settings.
Assessment
This skill is coherent and appears to be a safe guide for working with a local REINVENT4 checkout, but exercise the normal cautions for installer helpers: review the repository files (especially install.py and any setup scripts) before running them, prefer `--dry-run` and `--help` as suggested, run installs in an isolated environment or container if possible, and only supply optional licensed credentials (like OE_LICENSE) when you trust the source and need those features. If you are unsure about any command the skill proposes, ask the agent to show the exact command and the relevant lines from the local file before executing.

Like a lobster shell, security has layers — review code before you run it.

latestvk9755e1q9gvkh57n4k4pvem19583qnnj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments