aurora-norfolk
v1.0.0produce a practical 3-day northern lights planning and live-update workflow for tim in dereham, norfolk, with alert-day escalation, north norfolk coast compa...
⭐ 0· 82·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description align with the SKILL.md. Requested data sources (NOAA SWPC, Met Office, AuroraWatch UK) and the need to compare inland vs coast are appropriate for an aurora‑planning workflow. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
Runtime instructions are narrowly scoped to fetching space‑weather and local weather data, scoring components, producing 3‑day outlooks, and running live‑night checks. The skill explicitly permits only web_search, http_request, calculator, file_read, and file_write — which are the exact capabilities needed. It does instruct the agent to keep a small JSON state file (to suppress noisy repeats), which is proportionate to the workflow.
Install Mechanism
There is no install spec and no code files — the skill is instruction‑only, so nothing is downloaded or written beyond the agent's normal use of allowed tools.
Credentials
The skill requires no environment variables or credentials. This matches expectations: NOAA and AuroraWatch are public data; Met Office site‑specific data may sometimes require an API key, but the skill does not request any secrets. Overall the lack of requested credentials is proportionate.
Persistence & Privilege
always:false and normal autonomous invocation are set. The skill recommends storing a small JSON state file to suppress repeated alerts — this is reasonable and limited in scope. It does not request system‑wide configuration changes or other skills' credentials.
Assessment
This skill appears coherent and limited to public-data retrieval and a small local state file. Before installing, confirm the agent will have (1) web_search or http_request access to fetch NOAA, Met Office, and AuroraWatch data, and (2) permission to write a small JSON state file in the agent's storage. Note: some Met Office endpoints may require an API key or different access method; if those keys are needed later you should expect the agent to request them (they're not currently required). Because the agent can run autonomously, make sure you trust it to perform scheduled checks and to write state files; however, no broad credentials or external endpoints are requested by the skill itself.Like a lobster shell, security has layers — review code before you run it.
latestvk975j6cxr8jtdyv6fw0cw8pjsx83aynv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.