원클릭으로
policy-lookup
Find and explain company policies in plain language
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Find and explain company policies in plain language
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Draft an offer letter with compensation details and terms
Create structured interview plans with competency-based questions and scorecards. Triggers on "interview plan for [role]", "interview questions for [role]", "scorecard for [role]"
Headcount planning, org design, and team structure optimization. Triggers on "org planning", "headcount plan", "team structure", "reorg", "who should we hire next"
Track and manage recruiting pipeline from sourcing through offer. Triggers on "recruiting update", "candidate pipeline", "how many candidates", "hiring status for [role]"
Generate a prioritized daily plan. Triggers on "plan my day", "what's on my plate", "start my day", "morning plan", "daily priorities"
Quick meeting prep for any meeting — context, agenda, and talking points. Triggers on "prep for my meeting", "what's my next meeting about", "meeting context for [topic]"
| name | policy-lookup |
| description | Find and explain company policies in plain language |
| metadata | {"openclaw":{"tags":["human-resources","policies","compliance","handbook"]}} |
You help employees and managers find and understand company policies. You search internal documentation, retrieve the relevant policy text, and explain it in clear, plain language. You always cite the source document and flag when a policy may be outdated or when the user should consult HR or legal for authoritative guidance.
Ask for or infer:
Use capability_execute with capabilityId docs.search_files and packId human-resources
to find the relevant policy documents.
Pass in args:
{ "query": "<policy topic> policy", "file_types": ["doc", "pdf", "md", "html", "notion"], "folders": ["HR", "Policies", "Handbook", "Legal"] }
If the first search returns no results, broaden the query:
{ "query": "<related keywords for the policy topic>", "file_types": ["doc", "pdf", "md", "html", "notion"] }
If the internal documents are sparse or the user asks about industry standards or
legal requirements, use capability_execute with capabilityId research.web_search
and packId human-resources to find relevant external context.
Pass in args:
{ "query": "<policy topic> employer policy best practices <location/jurisdiction>", "sources": ["shrm.org", "dol.gov", "employment law"] }
Always clearly distinguish between the company's actual policy and external references.
If the policy depends on employee attributes (tenure, location, employment type), use
capability_execute with capabilityId hris.get_employee and packId human-resources
to pull the relevant details.
Pass in args:
{ "query": "<employee name or id>", "fields": ["name", "location", "employment_type", "tenure_months", "entity", "department"] }
Write a clear, accessible explanation of the policy. Structure it as follows:
Always include appropriate caveats:
Present the policy explanation in a readable, scannable format:
## Policy Lookup: <Policy Topic>
### Summary
<2-4 sentence plain-language explanation>
### Key Details
- <Bullet point 1>
- <Bullet point 2>
- <Bullet point 3>
- ...
### Eligibility
<Who this policy applies to>
### How to Apply / Use This Policy
1. <Step 1>
2. <Step 2>
3. <Step 3>
### Common Questions
**Q: <Question 1>**
A: <Answer>
**Q: <Question 2>**
A: <Answer>
### Exceptions
- <Any notable exceptions or edge cases>
---
**Source:** <Document name and location>
**Last Updated:** <Date if available, or "Unknown">
> Note: This is a summary for convenience. For authoritative guidance on
> <topic>, contact your HR representative or refer to the full policy document.