pl-skill-creator

Create, validate, and package portable Agent Skill packages across agent runtimes.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/rickvang/Persona-Library --skill pl-skill-creator-rickvang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pl-skill-creator
Source: https://github.com/rickvang/Persona-Library/tree/main/.agents/skills/pl-skill-creator
Command: npx skills add https://github.com/rickvang/Persona-Library --skill pl-skill-creator-rickvang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authoring a reusable Agent Skill package requires consistent structure, correct SKILL.md frontmatter, triggering validation, and runtime-specific packaging, which is error-prone when done ad hoc. This Skill turns an approved capability brief into a validated, distributable Skill package while keeping portable Skills separate from Persona-specific applications and workflows. ## Core Features & Use Cases - Package Authoring: Convert a bounded capability definition into a complete SKILL.md with supporting references, scripts, or assets using progressive disclosure. - Validation and Evaluation: Run structural validation plus positive and negative triggering tests, edge cases, fallbacks, and regression checks for target agent runtimes. - Boundary Governance: Enforce placement gates, change-impact reconciliation, and separation between reusable Skills, Persona applications, workflows, and Tool-use recipes. - Use Case: A team wants to publish a new reusable Skill for multiple agent runtimes. Use this Skill to define the contract, author the package, validate triggering behavior, and reconcile repository routes before release. ## Quick Start Use pl-skill-creator to turn this capability brief into a validated portable Skill package with triggering tests and evaluation evidence.

Frequently Asked Questions about pl-skill-creator

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

FAQPage Schema
How do I create a portable Agent Skill package?▼

Define the capability contract including purpose, triggers, inputs, outputs, and failure modes, then author SKILL.md with YAML frontmatter containing name and description. Validate structure and test positive and negative triggering before packaging for the target runtime.

What should a SKILL.md file contain?▼

A SKILL.md file must contain YAML frontmatter with at least a name and description used for discovery, followed by Markdown body instructions loaded into context on activation. Optional scripts, references, and assets directories support on-demand resources.

How do I validate Skill triggering behavior?▼

Run structural validation first, then test positive triggering with realistic requests and negative triggering with out-of-scope prompts. Include edge cases, fallbacks, permission limits, and regression cases for each requested agent runtime.

When should I not use a Skill authoring workflow?▼

Do not use it for discovering existing capabilities, composing multi-stage playbooks, executing tools, changing credentials, or writing one-off task instructions. Those belong to discovery, synthesis, or execution layers rather than package authoring.

Can one Skill package target multiple agent runtimes?▼

Yes, but keep one Skill identity and one core workflow, applying only the package conventions required by each requested target runtime. Avoid copying runtime-specific or Persona-specific judgment into the portable package.