Write clear prompts with action, content scope, and intent
Every effective prompt needs three essentials: what you want done, which content to work with, and whether you want suggestions or direct action. Master these essentials and you'll get better results from Aiko Agent while avoiding common mistakes that lead to vague or incorrect responses.
Why prompts fail
Here’s a prompt that seems reasonable: “Help with this article’s SEO.” Aiko receives this and needs to guess: Which article? What kind of SEO help - generate metadata, analyze keywords, update existing fields? Should it make changes directly or show you options first? Every time Aiko has to guess, you risk getting results that don’t match what you need. And even when Aiko eventually gets it right, vague prompts lead to extra back-and-forth that takes more time and uses more resources. The solution is building prompts from three essential principles that eliminate guesswork.The three essentials
Every prompt you write to Aiko should answer three questions:- What action do you want Aiko to take?
- Which specific content should Aiko work with?
- What’s your intent - do you want suggestions to review, or direct implementation?
Principle 1: State the action clearly
Start your prompt with a specific verb that describes exactly what you want done. Vague requests like “help with this article” or “fix the SEO” force Aiko to interpret your intent, often inefficiently or incorrectly. The strongest action verbs describe concrete content operations. You can find a list of such action verbs in the table below.| Action | Use when |
| Find / List / Show | You want to discover or see content |
| Create | You’re making something new |
| Translate | You need a language variant |
| Generate | You want Aiko to produce text (SEO, summaries) |
| Assign | You’re adding taxonomy terms, contributors, or collections |
| Move | You’re changing workflow steps or collections |
| Update | You’re modifying existing content |
| Publish / Unpublish | You’re changing what’s available live |
| Delete | You’re removing content |
- ❌ Vague: “Help with the description for our campaign”
- ✅ Clear: “Generate a meta description for the Article item named Spring Campaign 2026”
- ❌ Vague: “I need the onboarding guide in German”
- ✅ Clear: “Translate the Getting Started Guide content item to a new German language variant”
Principle 2: Specify the content
After stating the action, tell Aiko exactly which content to work with using Kontent.ai terminology. Being specific about scope prevents Aiko from affecting too much content or too little.How to specify scope
Let’s look at some example prompt fragments identifying the scope using the Kontent.ai terminology for precise results. Single item by name“...the content item named Spring Campaign 2026” Single item, specific language
“...the German language variant of Product Overview” All items of a type
“...all Article content items” Items in a collection
“...all content items in the Blog collection” Items in a workflow step
“...content items in the Ready for Review workflow step” Combined filters
“...all Blog Post content items in the Marketing collection that are in the Draft workflow step”
Common terminology mix-ups to avoid
| Instead of | Use |
| “page” or “post” | content item |
| “tags” | taxonomy terms |
| “component” (used loosely) | Component has a specific meaning in Kontent.ai. If you mean something else, be specific: content item, element (which one?), or snippet. |
| content type vs. content item | A content type is a template. A content item is individual content based on that template. |
Principle 3: Declare your intent
The third essential tells Aiko whether you want suggestions for human review or direct action. This is your safety mechanism to ensure changes happen only when you’re ready.- Suggest first when you want control. Use phrases like “Suggest taxonomy terms for…” or “Recommend workflow changes for…” or “Show me options for…”. This gives you a chance to review before anything changes.
- Request direct action when you’re confident. Use phrases like “Create a new content item…” or “Update the pricing element…” or “Assign these taxonomy terms…” This tells Aiko to execute immediately.
- First prompt asks for suggestions.
- Second prompt implements after you verify.
Example conversation
Notice the language used in the prompts – action verb used, scope specified, and the use of Kontent.ai terminology. You: “Suggest taxonomy terms for the Article content item Cloud Migration Best Practices from the Topics taxonomy group.” Aiko: Responds with recommendations. You: “Assign those terms as suggested.” This two-step pattern gives you control. You see what Aiko will do before it happens, and you can adjust if the suggestions don’t match your expectations.Putting the three essentials together
Let’s see how combining all three principles transforms a vague request into an effective prompt.