Pa Status

v1.0.1

PA network health dashboard. Use when: checking if all PAs in the network are active, checking billing status, verifying calendar connections, or generating...

0· 46·1 current·1 all-time
byNetanel Abergel@netanel-abergel
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/description match the instructions: the skill reads data/pa-directory.json, checks last_seen, billing, calendar, and status fields, and generates a report. All required data is local and coherent with network-status functionality.
Instruction Scope
Instructions are narrowly scoped to reading data/pa-directory.json and generating a report. A notable runtime action is the 'Quick Ping (WhatsApp Reachability)' flow — it directs sending pings to PAs flagged as issues and to consult whatsapp-diagnostics and billing-monitor skills; that implies outbound messaging and inter-skill calls, which are outside this skill's own code but expected behavior for a monitoring workflow.
Install Mechanism
Instruction-only skill with no install spec and no external downloads, so nothing is written to disk by an installer or pulled from remote sources.
Credentials
The skill requests no environment variables or credentials. It does read PII (phone numbers, owner_email) from a local JSON file — this is expected for a reachability/billing dashboard but you should ensure the data file is stored and accessed securely and that automated pings are authorized.
Persistence & Privilege
always:false and no self-modifying or cross-skill config writes. The skill schedules a daily report in its documentation but does not request elevated or persistent platform privileges.
Assessment
This skill is internally coherent, but review before enabling: 1) Confirm data/pa-directory.json is stored securely (it contains phone numbers and emails). 2) Decide whether automatic WhatsApp pings are allowed — they will send messages to people and rely on other skills (whatsapp-diagnostics, billing-monitor) that may require credentials. 3) Verify where the daily report is delivered (admin recipient) to avoid exposing PII. 4) If you use scheduling/automation, restrict rate and recipients to avoid spam and ensure consent. If you want more confidence, inspect the other referenced skills (whatsapp-diagnostics, billing-monitor) to see what credentials they request.

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

latestvk979n2cw99t07wd33dg8ed4qtn842brb

License

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

Comments