Rxtool

v1.0.0

Test, extract, replace, split, and explain regular expressions. Use when asked to test a regex pattern, extract matches from text, do regex replacements, spl...

0· 50·0 current·0 all-time
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
Name/description (regex testing/extraction/replacement/explanation) match the included code and runtime instructions. No unrelated environment variables, binaries, or config paths are requested. The presence of both rxtool.py and scripts/rxtool.py appears to be a packaging duplication but is consistent with the stated CLI usage.
Instruction Scope
SKILL.md instructs running the provided script(s) with pattern and text or via stdin. The instructions only reference regex patterns, text input, flags, and JSON output; they do not read or transmit unrelated files, environment variables, or external endpoints.
Install Mechanism
There is no install spec and all code is included in the bundle. No downloads, package managers, or archive extraction are used, which minimizes installation risk.
Credentials
The skill requires no environment variables, credentials, or privileged config paths. Runtime behavior reads stdin or accepts inline text only, which is proportional to a regex tool.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system changes or modify other skills. It uses standard CLI invocation and has no autonomous persistence beyond normal skill behavior.
Assessment
This skill appears coherent and self-contained: it runs local Python code to test/extract/replace/split/explain regexes and does not contact networks or ask for credentials. Things to consider before installing or running: (1) the package contains two identical script files (harmless but redundant); (2) be cautious when running untrusted regexes or feeding untrusted patterns into your environment — complex regexes can cause excessive CPU usage (ReDoS/catastrophic backtracking) or large outputs; and (3) if you plan to use it on sensitive data, remember it prints matches to stdout — avoid piping secrets into tools unless you control where the output goes. If you need the maintainer's identity or a homepage for auditability, request that before wide deployment.

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

latestvk9783ccv1pzmdzr4yxreqt7zwn83pwzw

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments