eforge-playbook

Name: eforge-playbook
Availability: InStock
Author: eforge-build

Manage eforge playbooks for Run, List, Promote, Demote, Create, and Edit workflows.

69|4|Updated Mar 15, 2026

Search Tags:#automation #playbooks #workflows #scopes #shadowing #eforge

Ready to run

npx skills add https://github.com/eforge-build/eforge --skill eforge-playbook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eforge-playbook
Source: https://github.com/eforge-build/eforge/tree/main/packages/pi-eforge/skills/eforge-playbook
Command: npx skills add https://github.com/eforge-build/eforge --skill eforge-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation, editing, and management of recurring workflows by providing a structured interface to manage eforge playbooks across user, project-team, and project-local scopes, enabling consistent automation of Build steps.

Core Features & Use Cases

Manage playbooks for Run, List, Promote, Demote, Create, and Edit workflows via a unified skill.
Supports scope-driven shadowing and promotion/demotion to share or localize templates across teams and projects.
Validates and saves playbooks with frontmatter and a standardized body, ensuring repeatable deployments and governance.

Quick Start

Describe the recurring workflow you want to capture, then create the playbook with /eforge:playbook create.

Frequently Asked Questions about eforge-playbook

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

FAQPage Schema

How do I create reusable automation playbooks for recurring team workflows?▼

You can create reusable automation playbooks by describing your recurring workflow and using the create command to validate and save templates with frontmatter and a standardized body. This ensures repeatable deployments and governance across your team.

How does playbook scope shadowing work for project-local and team-level automation?▼

Playbook scope shadowing allows you to localize templates at the project-local level while inheriting shared project-team configurations. You can promote or demote playbooks across these scopes to control whether workflows are shared or localized to specific projects.

What is the best way to manage and edit recurring build step workflows?▼

Managing recurring build step workflows is handled through a unified interface that supports list, run, edit, create, promote, and demote actions. This structure ensures consistent automation and governance for your recurring deployment workflows.

Do I need the eforge daemon API to run and validate playbooks?▼

Yes, running and validating playbooks relies on the eforge daemon API. The Skill uses this API to validate frontmatter-defined names and descriptions, ensuring your saved playbooks meet the required standardized format before execution.

Can I promote a personal playbook to a shared project-team scope?▼

Yes, you can promote a personal playbook to a shared project-team scope. The Skill supports promotion and demotion workflows, allowing you to transition templates between user, project-team, and project-local scopes to share or localize automation.

What format is required when saving eforge playbooks for repeatable deployments?▼

Saving eforge playbooks requires a standardized format with frontmatter defining the name and description, followed by a standardized body. The Skill validates this structure against the eforge daemon API to ensure repeatable deployments and consistent governance.