← Products

AI
⚙ Needs: an LLM app or agent to prompt — the skill is a promp…

Senior prompt engineer — system prompts, agent instructions and structured output patterns

Craft production prompts: system prompt architecture, instruction hierarchy, few-shot examples, structured outputs, evaluation loops, and ready-made templates

At a glance
What
Craft production prompts: system prompt architecture, instruction hierarchy, few-shot examples, structured outputs, evaluation loops, and ready-made templates
Cost
Free
Needs
an LLM app or agent to prompt — the skill is a prompt-crafting methodology the agent follows, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @davila7
⌁

Install

Prerequisites: an LLM app or agent to prompt — the skill is a prompt-crafting methodology the agent follows, not software Install "Senior prompt engineer — system prompts, agent instructions and structured output patterns" for me. It gives my agent @davila7's prompt-engineering toolkit: system-prompt architecture, instruction hierarchy, few-shot example design, structured-output patterns (JSON schemas, constrained formats), evaluation loops, and ready-made templates. NOTE: prompting practices evolve with models — treat templates as starting points and evaluate against your target model. MIT-licensed. Repository: https://github.com/davila7/claude-code-templates/blob/main/cli-tool/components/skills/development/senior-prompt-engineer/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "senior-prompt-engineer". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent the target model and the task to prompt for; nothing else — it's a prompt-crafting methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.