j.playbook

Invokes a named Jenga playbook by ID, skipping natural-language matching to run its skill chain.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-playbook-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.playbook
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-playbook
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-playbook-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you already know exactly which Jenga playbook you want, going through natural-language intent detection and playbook matching is unnecessary overhead. This Skill lets you invoke a playbook directly by its ID, jumping straight to chain confirmation and execution. ## Core Features & Use Cases - Direct ID Invocation: Resolves a playbook by ID via load-playbooks.sh lookup, bypassing detect-nl-intent.sh and match-playbook.sh entirely. - Catalog Listing: Invoked with no argument, it renders a Markdown table of all available built-in and project playbooks with their step chains. - Distinct Error Handling: Distinguishes not_found (with a 'did you mean' catalog nudge) from invalid (reporting the validation reason verbatim) and setup failures. - Use Case: You know the brainstorm-to-mirror playbook exists and want to run it now — invoke it by ID and confirm the rendered chain instead of describing your intent in free text. ## Quick Start Ask the agent to run the j.playbook skill with the playbook ID 'brainstorm-to-mirror' to confirm and execute that playbook chain directly.

Frequently Asked Questions about j.playbook

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

FAQPage Schema
How do I run a Jenga playbook directly by its ID?▼

Invoke the j.playbook skill with the playbook ID as its argument, for example 'j.playbook brainstorm-to-mirror'. It resolves the ID via load-playbooks.sh lookup, then renders and confirms the chain before executing it sequentially.

How do I list all available Jenga playbooks?▼

Invoke j.playbook with no argument. It calls load-playbooks.sh in full-catalog mode and renders a Markdown table with Id, Name, Source (Built-in or Project), and Steps columns.

What is the difference between j.playbook and the /jenga natural-language flow?▼

The /jenga flow uses detect-nl-intent.sh and match-playbook.sh to propose a playbook from free text. j.playbook skips both when you already know the exact ID, reusing the same confirmation and execution steps afterward.

What happens if the playbook ID I give does not exist?▼

The skill reports that no such playbook was found and may list available IDs from the full catalog as a 'did you mean' nudge. If the file exists but failed validation, it reports the exact validation reason instead of a generic not-found message.

Can j.playbook handle playbooks with nested or conditional steps?▼

Yes. Composed steps, conditionals, and forward_from/resolve resolution are handled identically to the natural-language path, with no special-casing for direct invocation.