Tech Prompt Engineering
Debug and harden production LLM prompts — handle prompt injection, output format drift, instruction forgetting in long contexts, and cross-model portability issues. Use this skill when the user ships an LLM-powered feature to production and needs to diagnose why outputs are inconsistent, unsafe, or regressed after model updates — NOT for basic 'write a better prompt' questions.
Install
npx skills add asgard-ai-platform/skills --skill tech-prompt-engineeringgit clone --depth 1 https://github.com/asgard-ai-platform/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/tech-prompt-engineering ~/.claude/skills/tech-prompt-engineeringPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Production Prompt Engineering ## Overview This skill addresses the failure modes that appear ONLY in production LLM applications: prompt injection, output format drift, silent regression across model versions, instruction decay in long contexts, and hallucination under pressure. It is NOT a tutorial on few-shot or chain-of-thought — assume the agent already knows basic prompting techniques. ## When to Use **Trigger conditions:** - A production LLM feature is misbehaving (inconsistent, unsafe, format-drifting) - Designing a system prompt for a multi-tenant application - Hardening prompts against injection or jailbreak attempts - Diagnosing regression after a model version update **When NOT to use:** - Basic "how do I write a prompt" — the agent already knows few-shot, CoT, role-play - One-off content generation (just write the prompt directly) - RAG architecture design (use a RAG-specific skill) ## Framework ``` IRON LAW: Treat User Input as Hostile by Default In production, user input WILL be used to attempt prompt injection. The only reliable defense is structural separation: 1. System prompt carries ALL rules and behavior (never trust user input to override) 2. User input is NEVER concatenated directly into instructions 3. Output is validated against an expected schema BEFORE being used downstream A prompt that works in dev with clean input will fail in production with adversarial input. ``` ## Production Failure Modes
Details
- Skill name
tech-prompt-engineering- Repository
- asgard-ai-platform/skills
- Path
tech-prompt-engineering/SKILL.md- License
- MIT
- Repo updated
- 6 June 2026
FAQ
What does the Tech Prompt Engineering skill do?
Debug and harden production LLM prompts — handle prompt injection, output format drift, instruction forgetting in long contexts, and cross-model portability issues. Use this skill when the user ships an LLM-powered feature to production and needs to diagnose why outputs are inconsistent, unsafe, or regressed after model updates — NOT for basic 'write a better prompt' questions.
How do I install the Tech Prompt Engineering skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add asgard-ai-platform/skills --skill tech-prompt-engineering. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tech Prompt Engineering popular?
It lives in asgard-ai-platform/skills, which has 248 GitHub stars and 30 forks.
Related skills
Algo Ad Bidding
248asgard-ai-platform/skills
Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.
Algo Ad Budget
248asgard-ai-platform/skills
Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.
Algo Ad Ctr
248asgard-ai-platform/skills
Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.
3 Statements
110microsoft/cat-agent-skills
Completes existing income statement, balance sheet and cash flow templates while preserving layout, grounding historical inputs and linking forecast formulas with reconciliation checks. Use for "fill in a 3-statement template", "complete an IS/BS/CF framework", "populate my integrated financial model", "link statements in this template", or "finish the forecasts in my three-statement workbook". Do NOT use for blank-slate models or general workbook edits (use xlsx), DCF valuation (use dcf-valuation), or buyout modeling (use lbo-model).
Tech MCP Server Dev
248asgard-ai-platform/skills
Build MCP (Model Context Protocol) servers including tool definition, schema design, authentication, error handling, and Claude Code integration. Use this skill when the user needs to create an MCP server, expose APIs or databases to AI agents, design tool schemas, or integrate with Claude Code — even if they say 'build an MCP server', 'connect Claude to our database', 'expose our API to AI', or 'create a tool for Claude Code'.
Agent Evaluation Designer
110microsoft/cat-agent-skills
Use this skill whenever the user wants to evaluate, test, or validate an AI agent, decide whether an agent is ready to ship or go live, choose how to grade an agent's answers (exact match, similarity, meaning, keywords, quality, or custom), design a test set of questions and expected answers, or interpret evaluation results into a go/no-go decision. Invoke it before the user hand-builds tests or declares an agent "done.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.