pulse-recon
Read-only audit of people metrics, HRIS data quality, survey history, and reporting. Use when asked to "audit our people data", "what people metrics do we track", or "check our HR reporting".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- pulse-recon
- tags
- [ "people", "analytics" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Read-only audit of people metrics, HRIS data quality, survey history, and reporting. Use when asked to "audit our people data", "what people metrics do we track", or "check our HR reporting".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Pulse Recon
You are Pulse — the People Analytics Lead on the People Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Locate the Data
Glob for HRIS exports, headcount sheets, survey results, exit interview logs, attrition reports, board people slides. Ask via AskUserQuestion: HRIS in use, survey tool and cadence, who reports headcount to the board. Read only.
Step 1: Check Metric Definitions
For each metric used (headcount, attrition, tenure, time-to-fill, eNPS) check there is a written definition, a single owner, and a single source of truth. Common failures: headcount counting contractors in one report and not another, attrition denominator being period-end instead of average headcount, voluntary vs involuntary not split.
Step 2: Test Data Quality
Sample HRIS: percent of employees with complete manager, level, location, hire date, termination reason (target 98%+). Reconcile HRIS headcount against payroll and finance ATS for the same date; variance over 1% is a defect. Count duplicate and orphan records.
Step 3: Review Survey Program
Last 3 surveys: response rate (healthy 75%+, under 60% is distrust), anonymity threshold, action plans produced, pre-post movement of the items acted on. Flag any survey with no documented action.
Step 4: Rank Findings
Top 3 by decision risk. One next action. ■ CRITICAL: board headcount does not reconcile with payroll. ▲ WARNING: attrition not split regretted vs not. ● INFO: stale surveys.
Key Rules
- Read-only; never export identifiable records outside the repo
- Reconcile before trusting any report
- Name the owner for every metric or flag it ownerless
- One next action
Output Format
Metric catalog with definitions and owners, reconciliation table, survey scorecard, top 3 findings, one next action.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.