leaflet

v1.0.0

Build, debug, and integrate Leaflet web maps, including map setup, tile layers, markers, popups, GeoJSON overlays, bounds fitting, event handling, and plugin...

0· 119·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
The name and description match the SKILL.md guidance: building, debugging, and integrating Leaflet maps. Nothing in the skill asks for unrelated binaries, credentials, or system access.
Instruction Scope
Runtime instructions focus on map setup, debugging heuristics, framework lifecycle, CRS guidance, and safe popup/content handling. The skill does not instruct the agent to read system files, access unrelated environment variables, or transmit data to hidden endpoints. It explicitly warns not to hardcode private tokens.
Install Mechanism
No install specification and no code files — this is instruction-only, so nothing is downloaded or written to disk by the skill itself.
Credentials
No required environment variables, credentials, or config paths are declared. The skill's guidance about tile URLs and attributions is appropriate for a mapping helper.
Persistence & Privilege
always is false and there are no elevated privileges requested. The agents/openai.yaml allows implicit invocation (allow_implicit_invocation: true), which is a normal platform setting and not a disproportionate privilege for this skill.
Assessment
This skill is instruction-only and appears coherent and low-risk: it doesn't request secrets, install code, or access system paths. Before using, review any generated code for external tile URLs and third-party plugin usage (verify licensing, attribution, rate limits and whether a provider requires a private token). Never paste private API keys or machine-specific paths into prompts; if you need private tiles or tokens, keep them out of shared examples and restrict them to your application configuration. Finally, vet any suggested third-party plugins for maintenance and security before adding them to production.

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

latestvk972vhg8xcs3y4eeh16s2pvyks83b07f

License

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

Runtime requirements

🍃 Clawdis

Comments