rules-lookup

List and retrieve official Pi.dev developer rules for compliance checks.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/zerwiz/wayofpi --skill rules-lookup-zerwiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rules-lookup
Source: https://github.com/zerwiz/wayofpi/tree/main/.pi/skills/rules-lookup
Command: npx skills add https://github.com/zerwiz/wayofpi --skill rules-lookup-zerwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork when creating or changing Pi assets by helping you consult the official developer rules first, so you can avoid architecture mistakes, security violations, and invalid configurations.

Core Features & Use Cases

  • Rule Discovery: Lists the available rule documents so you know which policy applies to skills, extensions, packages, models, or CLI behavior.
  • Targeted Rule Reading: Retrieves the exact rule content needed to verify compliance before you build or modify assets.
  • Use Case: A developer preparing a new skill can check the skills and security rules before implementation to ensure the design, permissions, and packaging approach are compliant.

Quick Start

Ask the skill to list the available developer rules and then read the rule that matches the asset you want to create or modify.

Frequently Asked Questions about rules-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Pi.dev developer rules before creating a skill?

To check Pi.dev developer rules before creating a skill, you can use this tool to list available rule documents and retrieve the exact content needed to verify compliance, permissions, and packaging standards. It removes guesswork by consulting official policies before implementation.

What developer rules apply to Pi extensions and system configurations?

Developer rules for Pi extensions and system configurations cover policy documents for skills, packages, models, and CLI behavior. You can discover the specific applicable rules by requesting a listing of available official documents to ensure your architecture and security approach is compliant.

Can I verify security and compliance standards for Pi packages without guesswork?

You can verify security and compliance standards for Pi packages by retrieving targeted rule content. This consults official developer rules to validate permission scoping and security review workflows, ensuring your assets avoid architecture mistakes and invalid configurations.

When do I need to consult official rules for modifying Pi assets?

You should consult official rules for modifying Pi assets whenever you are preparing changes to skills, extensions, or system configuration. Reading the matching rule content beforehand validates your design and ensures the modifications meet required compliance and security standards.

What is the best way to validate architecture before building new Pi.dev skills?

The best way to validate architecture before building Pi.dev skills is to retrieve the specific skills and security rules first. This performs an architecture validation check against official developer standards, preventing design mistakes before you start implementation.