
Turns your employee handbook into something you can actually query in plain language. Ask "can I work from Portugal for two weeks" or "what's the parental leave policy" and get back a clear answer with the exact source citation. Works standalone if you paste in your handbook text, but gets more powerful when connected to a knowledge base or HRIS for automatic lookups and employee-specific details like PTO balances. The output format is clean and includes who to contact for edge cases, which matters because policy questions are rarely black and white. Saves you from ctrl-F through a 50-page PDF every time someone asks about expense reimbursement.
$ npx -y skills add anthropics/knowledge-work-plugins --skill policy-lookup --agent claude-codeInstalls into .claude/skills of the current project.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Look up and explain company policies in plain language. Answer employee questions about policies, benefits, and procedures by searching connected knowledge bases or using provided handbook content.
/policy-lookup $ARGUMENTS
Search for policies matching: $ARGUMENTS
┌─────────────────────────────────────────────────────────────────┐
│ POLICY LOOKUP │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Ask any policy question in plain language │
│ ✓ Paste your employee handbook and I'll search it │
│ ✓ Get clear, jargon-free answers │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Knowledge base: Search handbook and policy docs automatically │
│ + HRIS: Pull employee-specific details (PTO balance, benefits) │
└─────────────────────────────────────────────────────────────────┘
Important guardrails:
## Policy: [Topic]
### Quick Answer
[1-2 sentence direct answer to their question]
### Details
[Relevant policy details, explained in plain language]
### Exceptions / Special Cases
[Any relevant exceptions or edge cases]
### Who to Contact
[Person or team for questions beyond what's documented]
### Source
[Where this information came from — document name, page, or section]
If ~~knowledge base is connected:
If ~~HRIS is connected:
Sponsors