self-generating-skills

Draft SKILL.md files for reusable Pi skill directories from prompts.

Updated May 4, 2026
One-click install
npx skills add https://github.com/panamini/pi-tooling --skill self-generating-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-generating-skills
Source: https://github.com/panamini/pi-tooling/tree/main/skills/self-generating-skills
Command: npx skills add https://github.com/panamini/pi-tooling --skill self-generating-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert repeated AI-guided tasks into reusable Pi skills instead of re-documenting the same workflow each time.

Core Features & Use Cases

  • Skill drafting from a prompt: Translates a user request for a new skill into a new skills/<skill-name>/SKILL.md entrypoint.
  • Authoring checklist for quality: Ensures each generated skill includes a precise description, clear scope, verification steps, required tools/files/commands, and safety notes for destructive actions.
  • Update loop and deduplication: After successful reuse, folds in learned edge cases and removes non-generalizable context, then checks for overlap with existing skills using the curator workflow.

Quick Start

Run the skill-drafting command: /skill-draft "my-skill-name" "a short description of when to use it".

Frequently Asked Questions about self-generating-skills

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

FAQPage Schema
How do I convert repeated AI workflows into reusable skills?

To convert repeated AI workflows into reusable skills, draft a new SKILL.md file on demand using a skill-drafting command that translates your task description into a standardized Pi skill directory entrypoint.

What do I need to include in a SKILL.md file for skill authoring?

Skill authoring requires YAML frontmatter with name and description, a clear usage description, triggers and non-triggers, verification steps, and safety guidance for destructive actions to ensure proper workflow templating.

Does generating a new skill require any specific dependencies or components?

Generating a new skill does not require external dependencies or components, as the self-generating-skills process drafts the SKILL.md file entirely on demand within your existing project structure.

What is the best way to handle deduplication when standardizing recurring tasks as skills?

For deduplication when standardizing recurring tasks, fold in learned edge cases after successful reuse, remove non-generalizable context, and check for overlap with existing skills using the curator workflow.

How does workflow templating work for authoring and revising recurring tasks?

Workflow templating for authoring recurring tasks works by applying an authoring checklist that ensures each generated skill includes a precise description, clear scope, required tools, and safety notes before deployment.

When should I not use automation to generate a new skill directory?

You should not use automation to generate a new skill directory for workflows that are highly specific, contain non-generalizable context, or lack clear verification steps and safety boundaries for destructive actions.