Funnlp
v2.0.3Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Funnlp concepts, best practices, and implementation patterns.
⭐ 0· 117·1 current·1 all-time
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 promise a local reference for Funnlp concepts and the files (SKILL.md + a bash script) implement exactly that: static heredoc outputs. No unrelated credentials, binaries, or network access are requested.
Instruction Scope
SKILL.md explicitly states outputs are plain-text via heredoc and no network or credentials are used—matching the script. Minor inconsistencies: the script's VERSION variable is 2.0.2 while the metadata is 2.0.3, and the quickstart text generically mentions "Required tools and access credentials" (likely boilerplate) even though the skill requires none. These are small, non-security issues.
Install Mechanism
No install spec is provided (instruction-only). No downloads or package installs occur. Risk from installation is minimal because nothing is written to disk by an installer; the included script is plain bash source that can be inspected before execution.
Credentials
The skill declares no required environment variables, no primary credential, and the script does not read env vars or config paths. Requested permissions are proportionate (none).
Persistence & Privilege
always:false and user-invocable:true (defaults). The skill does not request persistent presence or modify other skills/config. Autonomous invocation is allowed by platform default but the skill's static nature limits risk.
Assessment
This appears to be a harmless, local reference tool: it prints static documentation and does not access network, credentials, or config. Before installing or running, you can (1) inspect the included scripts (they're plain bash) to confirm no unexpected behavior, (2) prefer running it in a restricted environment if you want extra caution, and (3) be aware of the minor metadata inconsistencies (version number and boilerplate mention of credentials) which look like harmless copy-paste artifacts. If you require cryptographic guarantees, check the repository/source release signatures or contact the author listed in the metadata.Like a lobster shell, security has layers — review code before you run it.
latestvk9762qm7m83q3p3vdnrvxszgex83g3cn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.