Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Humanize Beagle
v1.0.0Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifi...
⭐ 0· 16·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (rewrite AI-generated developer text) match the instructions: reading a prior review, applying safe fixes, prompting for needs-review fixes, and using included style references. Declared dependencies (docs-style, review-ai-writing) align with the intended workflow.
Instruction Scope
Instructions operate on the repository (git status, stash, edit files, commit/PR artifacts skipped) which is expected for a docs-rewrite tool. Two minor scope notes: (1) it reads .beagle/ai-writing-review.json (expected but users should confirm contents), and (2) it assumes availability of git and jq though no binaries are declared—run with --dry-run first and ensure tools exist.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is downloaded or written outside normal repo edits. Low install risk.
Credentials
Requires no environment variables, no credentials, and no config paths. Actions are limited to repository files and included reference docs, so requested access is proportionate.
Persistence & Privilege
always is false and disable-model-invocation is true (skill cannot autonomously call models). The skill will modify repository files and performs git stash/changes when invoked by the user—this is expected behavior and scoped to the repo.
Assessment
This skill appears coherent and low-risk, but take these practical precautions before using it: 1) Commit or stash any important work (the skill will create its own stash and may apply automatic edits). 2) Run with --dry-run first to inspect proposed changes. 3) Ensure git and jq are available on the runner. 4) Inspect .beagle/ai-writing-review.json and the included reference files to confirm they contain only expected review data (not secrets). 5) Verify you trust the referenced dependency skills (review-ai-writing, docs-style) since this skill may invoke or rely on them. If you want maximum control, use --category and needs-review interactive flow rather than letting safe fixes auto-apply across the whole codebase.Like a lobster shell, security has layers — review code before you run it.
latestvk9737031f2r3sy131c4f5ghayn84nyte
License
MIT-0
Free to use, modify, and redistribute. No attribution required.