Looks up and explains company policies on PTO, benefits, remote work, travel, and conduct in plain language. Auto-activates on questions like 'what's our PTO policy'; invoke via /policy-lookup.
From human-resourcesnpx claudepluginhub cy-wali/knowledge --plugin human-resourcesThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
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: