agentica-prompts

Featured

Write reliable prompts for Agentica/REPL agents that avoid LLM instruction ambiguity

AI & Automation 531 stars 44 forks Updated 1 months ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
91
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Agentica Prompt Engineering Write prompts that Agentica agents reliably follow. Standard natural language prompts fail ~35% of the time due to LLM instruction ambiguity. ## The Orchestration Pattern Proven workflow for context-preserving agent orchestration: ``` 1. RESEARCH (Nia) → Output to .claude/cache/agents/research/ ↓ 2. PLAN (RP-CLI) → Reads research, outputs .claude/cache/agents/plan/ ↓ 3. VALIDATE → Checks plan against best practices ↓ 4. IMPLEMENT (TDD) → Failing tests first, then pass ↓ 5. REVIEW (Jury) → Compare impl vs plan vs research ↓ 6. DEBUG (if needed) → Research via Nia, don't assume ``` **Key:** Use Task (not TaskOutput) + directory handoff = clean context ## Agent System Prompt Template Inject this into each agent's system prompt for rich context understanding: ``` ## AGENT IDENTITY You are {AGENT_ROLE} in a multi-agent orchestration system. Your output will be consumed by: {DOWNSTREAM_AGENT} Your input comes from: {UPSTREAM_AGENT} ## SYSTEM ARCHITECTURE You are part of the Agentica orchestration framework: - Memory Service: remember(key, value), recall(query), store_fact(content) - Task Graph: create_task(), complete_task(), get_ready_tasks() - File I/O: read_file(), write_file(), edit_file(), bash() Session ID: {SESSION_ID} (all your memory/tasks scoped here) ## DIRECTORY HANDOFF Read your inputs from: {INPUT_DIR} Write your out...

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
6 months ago
Last Updated
1 months ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

agent-prompt

Prepare a grounded task or continuation prompt. Use when delegating fresh work or carrying progress, decisions, failures, and proof into a new agent session.

4 Updated today
fmind
AI & Automation Listed

agent-prompt-author

Write, revise, and diagnose system prompts, orchestrator instructions, subagent delegation contracts, tool descriptions, and harness text for LLM agents you build and ship. Use whenever someone wants an agent to behave differently by changing its text — "write a system prompt for X", "improve this orchestrator prompt", "my agent keeps ignoring this rule", "the prompt got worse after I edited it", "add a constraint so it stops doing Y", "write a tool description", "should I run GEPA or DSPy on this", "review this agent prompt", "is this prompt any good", "how much of this is still needed". Also use when a prompt has grown past ~200 lines, when a refinement loop has stopped helping, or before investing in automated prompt optimization. Do NOT use for one-off chat prompts, for CLAUDE.md and repo context files (opposite policy — see Route C), or for brand voice and creative style guides.

0 Updated 1 weeks ago
amylyra
AI & Automation Listed

subagent-prompt-design

Design and write well-formed prompts for SubAgents launched via the Agent/Task tool. Use this skill whenever you are about to delegate work to a SubAgent, write prompts for parallel fan-out exploration or multi-perspective review, decide which model tier a SubAgent should use, or structure the return format so the main context stays clean. If you are about to fire off a Task call without reading this first, stop and read it — a poorly written subagent prompt is worse than doing the work inline.

0 Updated yesterday
sardonyx0827