hike-route-planner
v1.0.0Plan complete hiking itineraries and leader-ready route briefs for day hikes, mountain walks, coastal treks, and beginner group outings. Use when a user asks...
⭐ 0· 76·2 current·2 all-time
by@decin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and included files (SKILL.md + local plan template) align: the skill is instruction-only and intended to produce formatted hike plans. It does not declare unrelated binaries, env vars, or installs.
Instruction Scope
Instructions stay within the planner scope (read local template, gather constraints, produce route/risks/gear/costs). They explicitly forbid automatic template changes and require clarifying missing inputs. However, the workflow mandates verifying real‑time facts (weather, trail closures, transit schedules) but does not specify data sources or how to fetch them — this is vague and may lead the agent to perform web requests or call external APIs at runtime.
Install Mechanism
No install spec and no code files beyond docs; nothing will be downloaded or executed on install. This minimizes installer-related risk.
Credentials
The skill requires no environment variables, credentials, or config paths, which is proportionate for an instruction-only planner. One caveat: because it asks to verify live data (weather, transport), users who want authoritative external checks may need to supply API keys or grant network access — these are not declared by the skill.
Persistence & Privilege
always is false and the skill does not request persistent/system-level privileges. The template is local and only updated when the user explicitly asks, so no covert modification of other skills or system settings is apparent.
Assessment
This skill appears to be what it says: an instruction-only hike planner that uses the included local template. It's low-risk because it doesn't install code or request credentials. Things to consider before installing: (1) the skill asks the agent to "verify" real-time facts (weather, trail closures, transit) but doesn't declare how — expect the agent to perform web lookups or require API keys if you need authoritative data; (2) if you do not want the agent making outbound requests, clarify in prompts that it should mark live checks as "not verified" and only use conservative estimates; (3) if you plan to update the template via the linked Feishu page, confirm how template sync/authentication will be handled (the skill does not include any Feishu credentials). If you want strict control, test the skill in a sandboxed agent or instruct it to avoid live internet checks unless you provide specific trusted data sources or API credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97286k084zs8vsw7p07x6ke2s83e9a6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.