expert-instruction — Claude Code skill: features and installation
The expert-instruction Claude Code skill helps design system instructions for AI agents. It covers agent roles, behavioral limits, response formats, and tool-use guidance.
MIT 106 installs ★ 29 updated 2026-08-17
npx skills add oakoss/agent-skills --skill expert-instruction -a claude-codeWhat expert-instruction does
The skill helps shape persistent instructions that govern an agent across conversations. It covers identity and capabilities, behavioral boundaries, response structure, tool selection, and handoffs to a human. Multi-step workflows and guardrails are part of the material too.
It calls out common prompt problems, including conflicting rules, vague personas, and missing tool-error handling. Its guidance recommends keeping system prompts below 2000 tokens and moving extra detail into reference documents. It also covers adversarial testing and tracking prompt versions.
This is for an agent’s lasting behavior, not tuning a single query or configuring training. The README points to the prompt skill for general techniques such as few-shot prompting and structured output.
What it helps with
- define an agent’s role and domain boundaries
- set tool selection rules and fallback behavior
- specify a consistent response structure
- decide when the agent should hand work to a human
- find conflicting rules in a system prompt
Example prompts for the agent
- Write a system prompt for a support agent with a clear role, limits, and response format.
- Set rules for when the agent should call tools and how it should respond to tool errors.
- Review this system prompt for conflicting instructions and out-of-scope requests.
How to install expert-instruction
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill expert-instruction -a claude-code2Manually: put the files in place
~/.claude/skills/expert-instruction/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/expert-instruction/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill expert-instruction -a codex2Manually: put the files in place
.agents/skills/expert-instruction/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill expert-instruction -a cursor2Manually: put the files in place
.cursor/skills/expert-instruction/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install oakoss/agent-skills skills/expert-instruction2Manually: put the files in place
.github/skills/expert-instruction/SKILL.md1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill expert-instruction -a gemini-cli2Platform CLI
gemini skills install https://github.com/oakoss/agent-skills --path skills/expert-instructionManually: put the files in place
.devin/skills/expert-instruction/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill expert-instruction -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about expert-instruction
How do I install expert-instruction in Claude Code?
Run npx skills add oakoss/agent-skills --skill expert-instruction -a claude-code. The skill file is at ~/.claude/skills/expert-instruction/SKILL.md.
What does expert-instruction do?
It helps create persistent system instructions for AI agents, covering identity, constraints, output structure, tool use, and behavior across multiple turns.
How is expert-instruction different from the prompt skill?
expert-instruction focuses on an agent’s ongoing behavior and boundaries. The README directs general prompt techniques, including few-shot and structured output, to the prompt skill.
Source text
SKILL.md · MIT
---
name: expert-instruction
description: |
System prompt design and instruction crafting for AI agents. Covers persona definition, constraint specification, output formatting, tool use instructions, multi-turn behavior, and guardrail design.
Use when writing system prompts for AI products, designing agent personas, specifying behavioral constraints, crafting tool-use instructions, or building multi-step agent workflows.
license: MIT
metadata:
author: oakoss
version: '1.0'
user-invocable: false
---
# Expert Instruction Design
## Overview
Expert instruction design focuses on crafting system prompts that define how an AI agent behaves, what it can and cannot do, and how it responds across interactions. Unlike general prompt engineering (which optimizes individual queries), this skill covers the **persistent behavioral layer** that shapes an agent's identity, capabilities, and constraints.
**When to use:** Writing system prompts for AI products, defining agent personas for customer-facing tools, specifying behavioral guardrails, crafting tool-use guidance, or designing multi-step agent workflows.
**When NOT to use:** One-off prompt optimization (use the `prompt` skill), fine-tuning or training-time configuration, infrastructure-level safety (use model provider safety features), or tasks that do not involve LLM agent behavior.
## Quick Reference
| Pattern | Purpose | Key Points |
| ------------------------ | ---------------------------------------- | ------------------------------------------------ |
| Identity block | Define who the agent is | Role, expertise, communication style |
| Capability declaration | State what the agent can do | Explicit tool list, domain boundaries |
| Constraint specification | Define behavioral boundaries | Hard limits, soft preferences, escalation rules |
| Output format rules | Ensure consistent response structure | Templates, progressive disclosure, length limits |
| Tool use instructions | Guide when and how to use tools | Selection criteria, error handling, sequencing |
| Multi-turn behavior | Handle conversation continuity | Context tracking, topic switching, memory |
| Guardrails | Prevent harmful or out-of-scope behavior | Content boundaries, instruction hierarchy |
| Escalation triggers | Define when to hand off to humans | Confidence thresholds, scope boundaries |
## Common Mistakes
| Mistake | Correct Pattern |
| ---------------------------------------- | ------------------------------------------------------------- |
| System prompt over 4000 tokens | Keep under 2000 tokens, move details to reference docs |
| Contradictory instructions | Audit for conflicts, establish priority order |
| Vague persona ("be helpful") | Specific: expertise domain, response style, knowledge bounds |
| No escalation path | Define when agent should defer to human or say "I don't know" |
| Listing every edge case | State principles, provide examples for ambiguous cases only |
| Mixing identity and task instructions | Separate: identity block first, task instructions second |
| No output format specification | Define structure: headings, lists, code blocks, length |
| Tool instructions without error handling | Include fallback behavior when tools fail or return errors |
| Testing only happy-path inputs | Test adversarial, off-topic, and edge case inputs |
| Deploying without versioning | Track system prompt versions, log changes, enable rollback |
## Delegation
- **Prompt technique exploration**: Use `Explore` agent to research patterns
- **System prompt testing**: Use `Task` agent to run adversarial test suites
- **Code review**: Delegate to `code-reviewer` agent for integration code
> If the `prompt` skill is available, delegate general prompt engineering techniques (CoT, few-shot, structured output) to it.
> Otherwise, recommend: `pnpm dlx skills add oakoss/agent-skills -s prompt -a claude-code -y`
## References
- [System prompt design: anatomy, personas, tools, and multi-turn behavior](references/system-prompt-design.md)
- [Guardrails and testing: behavioral boundaries, versioning, and production readiness](references/guardrails-and-testing.md)
© oakoss · MIT · oakoss/agent-skills