policy-lookup

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

11.0K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill policy-lookup

0

installs

0

this week

11.0K

stars

Installation Guide

How to use policy-lookup on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add policy-lookup
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill policy-lookup

Fetches policy-lookup from anthropics/knowledge-work-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/policy-lookup

Restart Cursor to activate policy-lookup. Access via /policy-lookup in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

/policy-lookup

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.

Usage

/policy-lookup $ARGUMENTS

Search for policies matching: $ARGUMENTS

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                    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) │
└─────────────────────────────────────────────────────────────────┘

Common Policy Topics

  • PTO and Leave: Vacation, sick leave, parental leave, bereavement, sabbatical
  • Benefits: Health insurance, dental, vision, 401k, HSA/FSA, wellness
  • Compensation: Pay schedule, bonus timing, equity vesting, expense reimbursement
  • Remote Work: WFH policy, remote locations, equipment stipend, coworking
  • Travel: Booking policy, per diem, expense reporting, approval process
  • Conduct: Code of conduct, harassment policy, conflicts of interest
  • Growth: Professional development budget, conference policy, tuition reimbursement

How to Answer

  1. Search ~~knowledge base for the relevant policy document
  2. Provide a clear, plain-language answer
  3. Quote the specific policy language
  4. Note any exceptions or special cases
  5. Point to who to contact for edge cases

Important guardrails:

  • Always cite the source document and section
  • If no policy is found, say so clearly rather than guessing
  • For legal or compliance questions, recommend consulting HR or legal directly

Output

## 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 Connectors Available

If ~~knowledge base is connected:

  • Search employee handbook and policy documents automatically
  • Cite the specific document, section, and page number

If ~~HRIS is connected:

  • Pull employee-specific details like PTO balance, benefits elections, and enrollment status

Tips

  1. Ask in plain language — "Can I work from Europe for a month?" is better than "international remote work policy."
  2. Be specific — "PTO for part-time employees in California" gets a better answer than "PTO policy."

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.741 reviews
  • N
    Nia FarahDec 20, 2024

    policy-lookup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • C
    Chaitanya PatilDec 4, 2024

    policy-lookup has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • P
    Piyush GNov 23, 2024

    Solid pick for teams standardizing on skills: policy-lookup is focused, and the summary matches what you get after install.

  • H
    Hiroshi MartinNov 19, 2024

    Registry listing for policy-lookup matched our evaluation — installs cleanly and behaves as described in the markdown.

  • S
    Sofia HaddadNov 11, 2024

    policy-lookup reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • S
    Shikha MishraOct 14, 2024

    We added policy-lookup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • D
    Daniel ChawlaOct 10, 2024

    policy-lookup fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • C
    Carlos RamirezOct 2, 2024

    I recommend policy-lookup for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • J
    Jin KapoorSep 25, 2024

    policy-lookup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • R
    Rahul SantraSep 21, 2024

    policy-lookup fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 41

1 / 5

Discussion

Comments — not star reviews
  • No comments yet — start the thread.