pac-pi-skill

Enforce standardized skill directory structure and SKILL.md frontmatter in repositories.

2|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/ladislas/mypac --skill pac-pi-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pac-pi-skill
Source: https://github.com/ladislas/mypac/tree/main/skills/pac-pi-skill
Command: npx skills add https://github.com/ladislas/mypac --skill pac-pi-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides engineers to author, rename, or refactor a Pi skill within the repo by enforcing a uniform layout, frontmatter contract, and local directory structure.

Core Features & Use Cases

  • Enforces that a skill directory under skills/ contains SKILL.md with a matching name frontmatter.
  • Provides a clear, step-by-step process for gathering requirements, drafting, and reviewing skill changes, ensuring consistency across the codebase.
  • Helps maintain repo-wide references and reduces drift when skills are renamed or restructured, by outlining update checks and best practices.

Quick Start

Follow this workflow to author or update a repo-owned skill under skills/, ensuring the directory, frontmatter, and optional references remain consistent.

Frequently Asked Questions about pac-pi-skill

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

FAQPage Schema
How do I enforce a standardized skill structure within a repository?

To enforce a standardized skill structure within a repository, validate that directories under skills/ contain a SKILL.md file with a matching name frontmatter. This ensures the directory, frontmatter, and layout conform to the repo's skill contract.

What is the best way to refactor a skill directory and update its YAML frontmatter?

The best way to refactor a skill directory and update its YAML frontmatter is to follow a structured workflow that outlines update checks and best practices. This reduces drift when skills are renamed or restructured across the codebase.

How do I author a new Pi skill without causing naming drift in the repo?

To author a new Pi skill without causing naming drift, gather requirements, draft the SKILL.md, and review changes using a step-by-step process. This enforces a uniform layout and frontmatter contract across the codebase.

Does a skill directory need a matching SKILL.md frontmatter name?

Yes, a skill directory requires a matching SKILL.md frontmatter name. Enforcing this frontmatter contract ensures the local directory structure conforms to the repository's skill contract.

Why does my repository layout fail the skill contract validation?

Repository layout fails the skill contract validation when the directory name and SKILL.md frontmatter do not match. Validating the frontmatter and layout ensures the directory conforms to the required skill structure.