Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Automate punching time in/out on WPS Time / NetTime (wpstime.com NetTime). Use for phrases like setup punchclock/configure punchclock/set up time clock, clock in/clock out, start break/end break, start lunch/end lunch, check status/status. Runs a Playwright flow, captures a screenshot, and replies with a brief confirmation.
Automate punching time in/out on WPS Time / NetTime (wpstime.com NetTime). Use for phrases like setup punchclock/configure punchclock/set up time clock, clock in/clock out, start break/end break, start lunch/end lunch, check status/status. Runs a Playwright flow, captures a screenshot, and replies with a brief confirmation.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Run the bundled Playwright script to log into WPS Time NetTime using macOS Keychain credentials, perform the requested punch action (or status check), take a screenshot, and report results.
Map user intent to the script --action:
setup punchclock / configure punchclock / set up time clock โ run setup flow
clock in โ clock-in clock out โ clock-out start break โ start-break end break โ end-break (implemented as Clock In (end break) in script) start lunch โ start-lunch end lunch โ end-lunch (implemented as Clock In (end lunch) in script) status / check status โ status
Run the interactive setup script to store credentials in macOS Keychain: cd {baseDir}/scripts node ./setup.mjs This stores credentials locally under Keychain services: wpstime-punchclock.company (secret = company/common id) wpstime-punchclock (account = username, secret = password)
Only use if the user explicitly asks for chat-based setup and accepts that the password will appear in chat history/logs. Workflow: Warn clearly: the password will be sent via chat and may be stored by the chat platform + gateway logs. recommend Option A instead. If they still confirm, collect 3 fields in separate turns: companyId username password Store into macOS Keychain on the SAME machine running the gateway using security add-generic-password -U: security add-generic-password -U -s "wpstime-punchclock.company" -a "company" -w "<companyId>" security add-generic-password -U -s "wpstime-punchclock" -a "<username>" -w "<password>" Never echo the password back. After storing, run status to verify login works.
Run the punch script (headless by default): node {baseDir}/scripts/punchclock.mjs --action <action> Optional flags: --headless 0 for debugging --outDir <path> to control screenshot output Parse stdout JSON. On success: read performed, screenshotPath, and (optionally) pull key fields from snippet. On failure: report error and do not claim the punch succeeded. Reply to the requesting channel with: one-line confirmation (what was performed) effective status/time if present (best-effort) attach the screenshot at screenshotPath If the user asks to clock in/out but they may already be in that state, prefer running status first or immediately after to confirm and avoid double-punch confusion.
Do not store secrets in files or prompts. Use Keychain. Preferred services (used by setup.mjs): Service wpstime-punchclock.company โ secret = company/common id Service wpstime-punchclock โ account = username, secret = password Backward-compat (older OpenClaw setups): openclaw.wpstime.company openclaw.wpstime If missing, the punch script throws an error. When that happens, guide the user to run: cd {baseDir}/scripts node ./setup.mjs Then retry the requested action.
If you need the longer operational runbook, read: references/PUNCHCLOCK_RUNBOOK.md
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.