Prompt Engineering Canon
Canonical prompt-engineering operating procedure distilled from Google's 68-page Prompt Engineering whitepaper (Lee Boonstra, Feb 2025): when to use zero/few-shot, system/contextual/role prompting, chain-of-thought, step-back, self-consistency, ToT, ReAct, output-format control, and exact temperature/top-K/top-P starting values. Trigger whenever writing, reviewing, or debugging a prompt for an LLM, choosing sampling configuration, or deciding which prompting technique fits a task.
Install
npx skills add Archive228/lab-skills --skill prompt-engineering-canongit clone --depth 1 https://github.com/Archive228/lab-skills.git /tmp/lab-skills
mkdir -p ~/.claude/skills
cp -r /tmp/lab-skills/skills/prompt-engineering-canon ~/.claude/skills/prompt-engineering-canonPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Prompt Engineering Canon Operating procedure for writing effective LLM prompts, distilled from Google's Prompt Engineering whitepaper (Lee Boonstra, Feb 2025). Gives you: a technique-selection decision framework (zero-shot through ReAct), exact sampling-config starting values (temperature / top-K / top-P), and the whitepaper's full best-practices list compressed into rules and a checklist. Written against Gemini in Vertex AI, but the techniques are model-agnostic (the paper names Gemini, GPT, Claude, Gemma, LLaMA). ## When to use Use this skill when you are: - Writing or rewriting a prompt for any LLM task: classification, extraction, summarization, Q&A, translation, code generation/explanation/translation/debugging, reasoning. - Choosing sampling configuration (temperature, top-K, top-P, token limit) via an API or Vertex AI Studio. - Debugging bad LLM output: wrong answers on reasoning tasks, inconsistent classifications, malformed JSON, repetition loops. - Deciding whether a task needs examples, reasoning steps, multiple samples, or external tools. Do NOT reach for the heavier techniques by default: chain-of-thought costs extra output tokens (money + latency), and self-consistency multiplies that by the number of samples. Start simple (zero-shot), escalate only when the simple prompt fails. ## Decision framework ### Configure sampling first
Details
- Skill name
prompt-engineering-canon- Repository
- Archive228/lab-skills
- Path
skills/prompt-engineering-canon/SKILL.md- License
- MIT
- Repo updated
- 12 August 2026
FAQ
What does the Prompt Engineering Canon skill do?
Canonical prompt-engineering operating procedure distilled from Google's 68-page Prompt Engineering whitepaper (Lee Boonstra, Feb 2025): when to use zero/few-shot, system/contextual/role prompting, chain-of-thought, step-back, self-consistency, ToT, ReAct, output-format control, and exact temperature/top-K/top-P starting values. Trigger whenever writing, reviewing, or debugging a prompt for an LLM, choosing sampling configuration, or deciding which prompting technique fits a task.
How do I install the Prompt Engineering Canon skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Archive228/lab-skills --skill prompt-engineering-canon. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Prompt Engineering Canon popular?
It lives in Archive228/lab-skills, which has 10 GitHub stars and 2 forks.
Related skills
Agent Design Fundamentals
10Archive228/lab-skills
Decision rules for whether to build an LLM agent and how to architect it, distilled from OpenAI's "A Practical Guide to Building Agents": build/no-build criteria, model selection, tool design, single-agent vs multi-agent orchestration (manager pattern vs decentralized handoffs), layered guardrails, and human-in-the-loop triggers. Use when designing, reviewing, or refactoring an agent system — before choosing an architecture, adding more agents, defining tools, or shipping an agent to production without guardrails.
Agent Evals
10Archive228/lab-skills
Build and maintain evaluation suites for AI agents: bootstrap 20-50 tasks from real failures, pick code-based vs model-based vs human graders by agent architecture (coding, conversational, research, computer-use), write unambiguous tasks with reference solutions, and keep suites alive via ownership and transcript reading. Use when creating evals from zero, adding graders or eval cases, debugging suspicious eval scores, or deciding pass@k vs pass^k metrics for an agent product.
Agent Failure Preflight
10Archive228/lab-skills
Pre-deployment failure-mode gate for agentic AI systems, distilled from Microsoft AI Red Team's Taxonomy of Failure Modes in Agentic AI Systems v2.0 (grounded in 12 months of red-team engagements). Run it before shipping or materially changing an agent — adding tools/MCP servers/plugins, enabling persistent memory, adding sub-agents or orchestration, enabling computer use, or expanding permissions — to verify concrete controls against memory poisoning, HitL bypass, goal hijacking, supply-chain compromise, session context contamination, capability disclosure, and multi-agent cascade failures.
Reverse Engineer Js
9vladmdgolam/agent-skills
Reverse-engineer minified or obfuscated JavaScript bundles. Primary tool: humanify (humanifyjs) — uses an LLM to rename mangled identifiers back to meaningful names. Default model: gemini-3.8-flash. Use when the user says 'deobfuscate this bundle', 'humanify this', 'rename minified vars', 'reverse engineer this JS', 'what does bundle.js do', or is working in a project with a deobfuscated `og/` or `modules/` folder fed by humanify. Covers humanify CLI invocation, the pseudo-TTY workaround for cursorTo crashes, single-module extraction from a bundle, and chaining with beautifiers.
Prompt Cache Optimization
10Archive228/lab-skills
Maximize OpenAI prompt-cache hit rate to cut time-to-first-token latency by up to 80% and input token cost by up to 90%: prefix-stability rules, cache-aware prompt layout, prompt_cache_key routing, allowed_tools, Responses API vs Chat Completions, Flex vs Batch, extended 24h caching, and Realtime retention_ratio. Use when designing or reviewing prompt/message layout for any repeated OpenAI API workload, when cached_tokens is low or zero, when TTFT or input spend is high at scale, or when choosing truncation/compaction strategy for long conversations. Scope: models before GPT-5.6 (per the sourc
Semantic Compression
5therealmoronto/claude-semantic-compression
Apply semantic logic compression (Ovchinnikov method) when crafting prompts for LLMs or describing complex conditional logic. Use this skill whenever the user asks to: write or optimise a prompt for an LLM, compress or rewrite a task description, describe multi-condition business logic (if/and/or/not chains), or asks why an LLM misunderstood their instructions. Also trigger when the user says ‘compress the logic’, ‘write a prompt for’, ‘the LLM doesn't understand’, ‘simplify the conditions’, or similar intents. Also trigger when the user wants to use output modifiers such as →code or →no-meta,
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.