Humanize Ai Text 1.0.0.1
v1.0.0Humanize AI-generated text to bypass detection. This humanizer rewrites ChatGPT, Claude, and GPT content to sound natural and pass AI detectors like GPTZero,...
⭐ 0· 59·1 current·1 all-time
byjayden@jaydenlm
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (humanize AI text to bypass detectors) match the included scripts (detect.py, transform.py, compare.py) and patterns.json. The required surface (no env vars, no external binaries) is proportional. Minor packaging inconsistency: _meta.json.ownerId differs from the registry owner ID in the metadata — likely benign but worth verifying the publisher.
Instruction Scope
SKILL.md and the scripts instruct the agent to read/write local text files, scan for patterns, and rewrite content to reduce detector signals. The instructions do not request unrelated files, system credentials, or network endpoints. However, the explicit runtime objective is to bypass AI detectors — a clear misuse vector (academic dishonesty, terms-of-service evasion) even though it stays within the technical scope described.
Install Mechanism
No install spec or external downloads. All code is packaged in the skill and operates locally; there are no remote fetches, archive extraction, or registry installs to review.
Credentials
No environment variables, credentials, or config paths are required. The scripts only read local files (text and patterns.json) and write outputs; requested access is minimal and proportional.
Persistence & Privilege
The skill does not request always:true and has no mechanism to persist or modify other skills or global agent settings. It runs on demand and only interacts with files the user provides.
Assessment
This skill is technically coherent: the scripts implement exactly what the README says and operate only on local files (no network calls or credentials). Before installing, consider: 1) Ethical/legal risk — the tool explicitly helps evade AI-detectors (could violate school/employer policies or service TOS). 2) Source verification — no homepage and the metadata ownerId mismatch is a minor red flag; prefer code from a known, trusted publisher. 3) Audit patterns.json and the scripts yourself (they're small and human-readable) to confirm there are no hidden behaviors. 4) Test in a sandbox or limited environment first. If you intend legitimate uses (e.g., improving writing quality), document that and avoid using the tool to bypass policy or rules.Like a lobster shell, security has layers — review code before you run it.
latestvk973c0211kj5jkvp8nt13xrjb184mcgj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.