shaonlisted

# Shaon Claude Code skill for the `shaon` repo and binary. ## Tool Selection - Prefer the **MCP server** when a tool already covers the domain operation. - Fall back to the **CLI** for local-machine or interactive operations: `auth`, `payroll payslip view`, `reports show`, `cache refresh attendance-types`, `serve`, and `completions`. - Use this **skill** to pick the right surface, the right command/tool, and the right safety flow. ## Human-attested writes All write commands (`attendance report today/day/range`, `attendance auto-fill`, `attendance resolve`) submit under the user's identity against their real employer's system. When driving these, ALWAYS: 1. Run with `--dry-run` (the default) first. 2. Show the resulting preview to the user. 3. Require the user to explicitly confirm in the conversation before rerunning with `--execute`. Never autonomously rerun a write with `--execute`. Writes must be treated as user-authorized actions and must not be submitted without explicit user confirmation. ## CLI Entry Point If working from a repo checkout, prefer: ```bash scripts/run.sh <command> [args] ``` If installed globally: ```bash shaon <command> [args] ``` ## First-Time Setup Create `~/.shaon/config.toml`: ```toml subdomain = "mycompany" username = "123456789" payslip_folder = "/path/to/payslips" # optional payslip_format = "%Y-%m.pdf" # optional ``` Then authenticate: ```bash shaon auth ``` If stored credentials are stale and you want a deter