Individual skill

prompt-engineering-guidance

Team-level guidance for prompt engineering — standards, review processes, prompt libraries, versioning, and rollout practices. Use when standardizing how an organization writes and maintains prompts.

skills/prompt-engineering-guidance/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 54
Repository last updated: Oct 10, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
ai-agents-automation Repository topic
ai-skills Repository topic
awesome Repository topic
awesome-list Repository topic
chatgpt Repository topic
claude-skills Repository topic
meta-ai Repository topic
muse-ai Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,856 bytes

Read excerpt


# Prompt Engineering Guidance (Team Practice)

Individual prompt skill doesn't scale; teams need shared standards. This skill covers the 
organizational side: conventions, review, libraries, versioning, and rollout — so prompts become 
maintained assets instead of tribal knowledge.

## Overview

Treat prompts like code: they live in version control, go through review, have tests, and follow 
style conventions. A prompt library gives teams reusable, vetted components (classifiers, 
extractors, summarizers) instead of everyone reinventing them. Rollout practices — staging, 
canary, rollback — apply because prompt changes are behavior changes. The goal is a team where 
anyone can find, understand, and safely modify any prompt.