Agent skill

Prompt Engineering

by niki914 in niki914/zafiro

Guidelines to writing prompts, docs, or tasks for AI to read or execute, with strict context isolation.

MITAuto-check passedAI & LLM Engineering

Install Prompt Engineering

skills CLI
$ npx skills add niki914/zafiro --skill prompt-engineering -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install niki914/zafiro prompt-engineering --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/niki914/zafiro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prompt-engineering .claude/skills/prompt-engineering && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prompt-engineering
GitHub stars
231
Token cost
~666 tokens
SKILL.md length
267 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Guidelines to writing prompts, docs, or tasks for AI to read or execute, with strict context isolation.

  • Tasks that involve Prompt engineering
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prompt Engineering is an agent skill from niki914/zafiro. Guidelines to writing prompts, docs, or tasks for AI to read or execute, with strict context isolation.

Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering Prompt engineering. The repository describes itself as: Open-source BYOK AI agent for Android. Full phone control, native Shell & Python 3, with Skills and MCP support. Built with Material 3 Expressive. Works via Shizuku (root… The licence is MIT.

When your agent uses it

  • Tasks that involve Prompt engineering

Example prompts

  • “Use the prompt-engineering skill to guideline to writing prompts, docs, or tasks for AI to read or execute, with strict context isolation”
  • “/prompt-engineering”

What it can do on your machine

Read from SKILL.md and the folder at commit d50b2ab. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are diff).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prompt Engineering loads about 666 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 267 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~666

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from niki914/zafiro at commit d50b2ab, republished under its MIT licence (© niki914). 267 words, ~666 tokens.

Download SKILL.mdSave it as .claude/skills/prompt-engineering/SKILL.md (or your agent's skills folder).
name
prompt-engineering
description
Guidelines to writing prompts, docs, or tasks for AI to read or execute, with strict context isolation.
trigger
write a prompt|improve wiki|update documentation|dispatching agents|

prompt-engineer

Translate user commands into precise prompts or documentation edits. Eliminate context pollution ruthlessly.

<prompt_engineering_standards>

  • AX First: System architecture must be designed for AI consumption.
  • Clear Delimiters: Use explicit XML tags to isolate context, delimit instructions, and prevent injection. Skip XML wrappers when the content already has its own unambiguous boundary (e.g., a markdown heading, a code fence) — adding XML on top adds ceremony without improving isolation.
  • CoT & Verification: Perform internal step-by-step reasoning before outputting. Implement reverse-verification (e.g., "What specific error occurs if this info is missing?").
  • Mandatory Pre-flight Checklist: BEFORE outputting a file diff, executing a tool, or delegating a task, internally verify: 1. Is the payload/memory written strictly in English? 2. Are credentials (Token/PAT) completely scrubbed? Halt execution if validation fails.
  • Few-shot Examples: Provide 3-5 examples including Negative Examples to establish clear boundaries.
  • Zero Silent Drops: Log drops/errors explicitly. No backpressure blackholes.
  • Semantic Precision: Eliminate abstract adjectives; use executable metrics. </prompt_engineering_standards>

<stateless_document_modification> To prevent "version baggage" and "context pollution" when modifying documentation:

  • Treat every update as a clean-slate rebuild. Replace old facts with new facts directly. Never explain history, deltas, or reasoning in the text.
  • Delete obsolete content entirely — no ghost context, no "(Updated)" labels. No version tags or timestamps in headers unless explicitly requested.
Examples

Bad (meta-tagging noise):

diff
- # Auth Module
+ # Auth Module (v2 Updated)

Good: no title change needed.

Bad (conversational baggage):

diff
- Auth validates tokens.
+ Auth validates tokens and sessions. (Note: it no longer only validates tokens.)

Good:

diff
- Auth validates tokens.
+ Auth validates tokens and sessions.

</stateless_document_modification>

<agent_dispatch_rules>

  • Task content for subagents MUST be in English and strictly adhere to <prompt_engineering_standards>. Preserve native hardcoded strings from the source code.
  • Output in the same language the user used in the request.
  • Always pass explicit contextual constraints. Never override user requirements with generic implementations. </agent_dispatch_rules>

© niki914, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/prompt-engineering of niki914/zafiro.

Open the folder on GitHubat commit d50b2ab

Compare with similar skills

Prompt Engineering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prompt Engineering compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prompt Engineering this skillniki914/zafiro231—~666Automated safety check: PassMIT
Prompt Improverseverity1/claude-code-prompt-improver1.9k1 repos~1.7kAutomated safety check: PassMIT
Prompt Engineering Patternsynulihao/AgentSkillOS61714 repos~1.7kAutomated safety check: PassNone
Patch CreationPiebald-AI/tweakcc2.5k—~1.6kAutomated safety check: PassMIT
Senior Prompt Engineermaslennikov-ig/claude-code-orchestrator-kit2603 repos~1.4kAutomated safety check: PassCustom licence
Codex Fable5baskduf/FableCodex437—~1.6kAutomated safety check: PassAGPL-3.0

Similar skills

  • Prompt Improver

    severity1/claude-code-prompt-improver

    This skill enriches vague prompts with targeted research and clarification before execution.

    1.9k GitHub starsUsed in 1 repo~1.7k tokens
    AI & LLM EngineeringAuto-check passed
  • Prompt Engineering Patterns

    ynulihao/AgentSkillOS

    Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production.

    617 GitHub starsUsed in 14 repos~1.7k tokens
    AI & LLM EngineeringAuto-check passed
  • Patch Creation

    Piebald-AI/tweakcc

    Create and register new patches for tweakcc. An agent skill from Piebald-AI/tweakcc.

    2.5k GitHub stars~1.6k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Senior Prompt Engineer

    maslennikov-ig/claude-code-orchestrator-kit

    Provides reference guides and Python scripts for prompt optimization, RAG evaluation, and agent orchestration when building or tuning LLM systems.

    260 GitHub starsUsed in 3 repos~1.4k tokens
    AI & LLM EngineeringAuto-check passed
  • Codex Fable5

    baskduf/FableCodex

    Apply a Claude Fable 5 inspired operating style inside Codex.

    437 GitHub stars~1.6k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check passed
  • Reference for designing and tuning production LLM prompts: few-shot examples, chain-of-thought, structured outputs, templates and system prompts.

    40k GitHub stars~1.3k tokensUpdated 5 days ago
    AI & LLM EngineeringAuto-check passed

More from niki914/zafiro

  • Release New Version

    niki914/zafiro

    A skill your agent uses when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and…

    231 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Add Worktree

    niki914/zafiro

    A skill your agent uses when the user wants to start work in a new git worktree — "new worktree", "spin up a worktree/branch for this", "work on X in another worktree", "branch this off".

    231 GitHub stars~669 tokensUpdated yesterday
    Auto-check passed
  • Install a skill from a public GitHub repository onto this device.

    231 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Skill Creator

    niki914/zafiro

    Create new skills, modify and improve existing skills, and measure skill performance.

    231 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Termux

    niki914/zafiro

    Load this skill for anything involving Termux (com.termux) — first-time SSH setup, connecting to Termux, or a Termux connection that stopped working.

    231 GitHub stars~688 tokensUpdated yesterday
    Auto-check passed
  • Test Triage

    niki914/zafiro

    Use before writing, adding, or modifying any unit test in this repo — before creating a Test.kt file or a @Test function, and before touching an existing test after a refactor.

    231 GitHub stars~935 tokensUpdated yesterday
    Auto-check passed

Questions about Prompt Engineering

What does Prompt Engineering do?

Guidelines to writing prompts, docs, or tasks for AI to read or execute, with strict context isolation. Prompt Engineering is an agent skill from niki914/zafiro. Guidelines to writing prompts, docs, or tasks for AI to read or execute, with strict context isolation.

When should I use Prompt Engineering?

Prompt Engineering fits situations like: tasks that involve Prompt engineering.

How do I install Prompt Engineering in Claude Code?

Run `npx skills add niki914/zafiro --skill prompt-engineering -a claude-code`. Or copy the skill folder (.agents/skills/prompt-engineering in niki914/zafiro) into .claude/skills/prompt-engineering in your project. Claude Code loads it when a task matches its description.

How do I install Prompt Engineering in Codex?

Run `npx skills add niki914/zafiro --skill prompt-engineering -a codex`. Or copy the skill folder (.agents/skills/prompt-engineering in niki914/zafiro) into .agents/skills/prompt-engineering in your project. Codex loads it when a task matches its description.

Can I use Prompt Engineering in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add niki914/zafiro --skill prompt-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prompt-engineering, .gemini/skills/prompt-engineering, .github/skills/prompt-engineering and .opencode/skills/prompt-engineering in your project.

What does Prompt Engineering need to run?

SKILL.md names no scripts, command-line tools or credentials: Prompt Engineering is instructions for the agent only.

Does Prompt Engineering access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prompt Engineering safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prompt Engineering use?

Prompt Engineering is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prompt Engineering use?

About 666 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prompt Engineering?

Skills that share tags, products or a category with Prompt Engineering: Prompt Improver (severity1/claude-code-prompt-improver, 1.9k stars), Prompt Engineering Patterns (ynulihao/AgentSkillOS, 617 stars), Patch Creation (Piebald-AI/tweakcc, 2.5k stars) and Senior Prompt Engineer (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prompt Engineering?

niki914 (a GitHub user) maintains it in niki914/zafiro, which has 231 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: niki914/zafiro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.