prompt-engineering

Construct XML-wrapped Jerry prompts with NPT constraints and 7-criterion scoring.

30|6|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/geekatron/jerry --skill prompt-engineering-geekatron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-engineering
Source: https://github.com/geekatron/jerry/tree/main/skills/prompt-engineering
Command: npx skills add https://github.com/geekatron/jerry --skill prompt-engineering-geekatron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Prompt Engineering skill provides a structured approach to building high-quality prompts for the Jerry Framework, enabling reliable routing, data sourcing, and governance through XML-wrapped prompts and standardized scoring.

Core Features & Use Cases

  • Interactive 5-element prompt anatomy: guides users through routing, scope, data source, quality gate, and output path to produce ready-to-use prompts.
  • NPT constraint generation support: enables creation of NPT-009/NPT-013 blocks for governance YAML, rule files, and skill docs.
  • Prompt quality scoring: applies the 7-criterion rubric to identify gaps and drive improvements.
  • Template-driven routing guidance: accelerates prompt construction for spikes, implementations, orchestration, and architecture tasks.

Quick Start

Follow the 5-element walkthrough to generate an XML-wrapped prompt ready for Jerry integration.

Frequently Asked Questions about prompt-engineering

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

FAQPage Schema
How do I structure prompts for Jerry workflows to get deterministic results?

Structured Jerry prompts use XML-wrapped construction covering five elements: routing, domain scope, data sources, quality gates, and explicit output paths. This anatomy ensures deterministic results and reliable execution.

What is the 7-criterion rubric for prompt quality scoring?

The 7-criterion rubric for prompt quality scoring evaluates generated prompts against specific governance and structural constraints. It identifies gaps in routing, scope, and output definitions to drive iterative improvements.

How do I generate NPT-009 and NPT-013 constraint blocks for governance YAML?

Generate NPT-009 and NPT-013 constraint blocks by using structured prompt engineering support to produce governance YAML, rule files, and skill docs that enforce specific routing and quality gate requirements.

Can I use template-driven routing for spike and architecture task prompts?

Yes, template-driven routing guidance accelerates prompt construction for spikes, implementations, orchestration, and architecture tasks by providing structured XML-wrapped templates tailored to each workflow type.

What are the limitations of XML-wrapped prompt construction in Jerry?

XML-wrapped prompt construction requires strict adherence to the 5-element anatomy and NPT constraints to function properly. Without complete routing, scope, and quality gate definitions, Jerry prompts may yield non-deterministic results.