╔══════════════════════════════════════╗ ║ ▓▓▓ FROM CHATBOT TO AGENT ▓▓▓ ║ ╚══════════════════════════════════════╝

Getting Started with
Agentic AI

Stop chatting. Start automating.

A hands-on guide for technical people who know chatbots but haven't explored agents, SOPs, and rapid prototyping yet.

▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪

01 The Mind Shift: What Kiro CLI Actually Is

You've used a chatbot — you type a question, it answers, you copy-paste the result somewhere. That's a conversation. An agentic CLI like Kiro CLI?Kiro is actually a full IDE built by AWS — but it's ultra-flexible and can do much more than just coding. Kiro CLI is its command-line interface, which is what we focus on here. There's also a Kiro UI for those who prefer a graphical interface, with a focus on software development. is something fundamentally different: it's an AI that can take actions on your computer — read your files, run shell commands, call APIs, write code, and loop autonomously until a task is done.

Chatbot Mode

  • You ask, AI answers in text
  • Copy-paste results manually
  • No access to your system
  • One question at a time
  • You do all the work

Agentic Mode

  • You describe a goal
  • AI reads, writes, executes
  • Accesses your files, CLI, APIs
  • Multi-step autonomous loops
  • AI does the work, you review

Think of it this way: A chatbot is like texting a friend for advice. An agentic CLI is like hiring an assistant who sits at your terminal, reads your files, writes scripts, runs them, checks the output, fixes errors — and hands you the finished result.

Kiro CLI is built by AWS and runs right in your terminal. It connects to frontier AI models and has access to tools — the ability to read and write files, execute shell commands, fetch, read and understand web content, and more. The key insight: the AI doesn't just know things, it can do things. You describe what you want, and it figures out the steps, executes them, and learns from its mistakes along the way.

You describe
a task
Agent
plans
Agent uses
tools
Loops until
done
You review
the result
▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪

02 Kiro CLI Quickstart

Let's get Kiro CLI running on your machine in under 5 minutes. You'll need macOS or Linux (Windows users: use Windows Subsystem for Linux (WSL) or the Kiro GUI). See the official installation docs for full details.

Install

# One-liner install (macOS / Linux)
curl -fsSL https://cli.kiro.dev/install | bash

Log In

# Start Kiro CLI — it will prompt you to log in on first run
kiro-cli
# Select "Use for Free with Builder ID"
# A browser window opens — sign in, and you're ready to go.
▸ PRO TIP Typing kiro-cli every time gets old fast. Add an alias so you can just type k:
echo 'alias k="kiro-cli"' >> ~/.zshrc && source ~/.zshrc
On Linux, replace .zshrc with .bashrc.

Your First Agentic Task

Here's where it gets exciting. Instead of asking the AI a question and copy-pasting the answer, you give it a task — and it does the work for you. Try this:

# Inside Kiro CLI, just type your task in plain English:
> Create a simple Python web scraper that fetches the top
  headlines from AWS News and prints them to the terminal

Watch what happens — the agent thinks through the problem, tries different approaches, writes the code, and then runs it to verify it works:

▸ I'll create a minimal Python web scraper for AWS News headlines.
Fetching content from: https://aws.amazon.com/about-aws/whats-new/
✓ Fetched 2119 bytes

▸ The page is dynamically loaded. Let me try the RSS feed instead:
Fetching: https://aws.amazon.com/about-aws/whats-new/recent/feed/
✗ Unsupported content type: application/rss+xml

▸ The RSS feed exists — I'll create a scraper that uses it directly:
Creating: aws_news_scraper.py (10 lines, stdlib only)
Running: python3 aws_news_scraper.py

Announcing new metal sizes for Amazon EC2 M8gn instances
Amazon Bedrock now supports server-side tool execution
AWS Observability now available as a Kiro power
Announcing AWS Elemental Inference
...

▸ Done! Created aws_news_scraper.py — uses only Python's
standard library. Run: python3 aws_news_scraper.py
Credits: 0.26 • Time: 42s
▸ KEY CONCEPT Notice what happened: the agent tried to fetch the page, hit a wall (dynamic content), adapted its strategy (switched to RSS), wrote the code, and ran it to confirm it works — all on its own. You typed one sentence. The agent made decisions, wrote a working script, and verified the result. That's the difference between chatting and agentic work.

Useful Slash Commands

/context      # See & configure where Kiro reads context from
/context show # Show which steering files, rules & skills are active
/tools        # Show available tools the agent can use
/mcp          # List active plugin servers (more on this in Section 03)
/model        # Switch AI model mid-conversation (with tab completion)
/clear        # Clear conversation history and start fresh
/help         # Full command reference
▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪

03 Supercharging with MCP Servers & Skills

Out of the box, Kiro CLI can read files, run commands, and fetch web pages. That's already powerful, but the real magic starts when you plug in MCP servers?Model Context Protocol (MCP) is an open standard — originally introduced by Anthropic — that lets AI agents connect to external tools and data sources. Think of MCP servers as plugins: each one gives your agent new abilities. There's a growing directory of MCP servers for everything from AWS docs to GitHub to databases. and Skills?Skills are instruction bundles that teach an agent how to do specific tasks well. The concept was introduced by Anthropic for Claude Code and is now an open standard adopted by multiple tools — including Kiro. Anthropic maintains a collection of ready-made skills at github.com/anthropics/skills. — giving the agent entirely new capabilities like searching AWS documentation, working with Excel files, or querying databases.

What is MCP?

Model Context Protocol (MCP) is an open standard that lets AI agents connect to external tools and data sources. Think of MCP servers as "plugins" for your agent — each one gives it a new set of abilities. One server might let it search official AWS documentation, another might let it interact with your GitHub repositories, another might connect it to a database.

Adding an MCP Server

Let's add the AWS Documentation MCP server so Kiro can search official AWS docs directly. First, quit Kiro CLI if it's running (type /quit), then install the uv Python package manager which is needed to run the MCP server:

# Install uv — a fast Python package runner. Many MCP servers
# are Python tools, and "uvx" (part of uv) runs them without
# manual installation.
curl -LsSf https://astral.sh/uv/install.sh | sh

Now register the MCP server with Kiro:

# Add the AWS Documentation MCP server globally
kiro-cli mcp add \
  --name "awslabs.aws-documentation-mcp-server" \
  --scope global \
  --command "uvx" \
  --args "awslabs.aws-documentation-mcp-server@latest" \
  --env "FASTMCP_LOG_LEVEL=ERROR" \
  --env "AWS_DOCUMENTATION_PARTITION=aws"

The config is stored in ~/.kiro/settings/mcp.json — you can also edit that file directly if you prefer. Now restart Kiro CLI and try it out:

# Start Kiro CLI and use your new tool:
kiro-cli

> What storage classes are available in S3 in
  the AWS region in Switzerland?

The agent now searches the official AWS documentation (not its training data) and gives you an accurate, up-to-date answer about S3 storage classes available in the Zurich region. That's the power of MCP — you're extending what the agent can access and know.

▸ SECURITY NOTE When configuring MCP servers, use environment variable references (${API_TOKEN}) for any secrets. Never hardcode credentials in the config file, and don't commit mcp.json to version control.

Skills: Teaching Kiro New Tricks

While MCP servers give the agent access to external tools and data, Skills teach the agent how to do specific tasks well. A Skill is a bundle of instructions, best practices, and sometimes MCP servers that Kiro loads when it detects a relevant task. Think of it as giving the agent a playbook for a particular job.

For example: out of the box, Kiro can't work with Excel files. But with the xlsx Skill, it learns how to read, create, and modify spreadsheets using the right libraries and patterns. See the official Skills documentation for details.

Adding a Skill

Anthropic maintains a collection of ready-made Skills at github.com/anthropics/skills. Let's add the Excel skill so Kiro can work with spreadsheets.?Skills are stored as SKILL.md files in ~/.kiro/skills/<name>/ (global) or .kiro/skills/<name>/ (project-local). You could copy the files there manually — but it's much easier to just ask the agent to do it for you, as shown below. Inside Kiro CLI, just tell it what you want:

# Inside Kiro CLI, ask it to install the skill:
> add the xlsx skill from
  https://github.com/anthropics/skills/tree/main/skills/xlsx
  as described in https://kiro.dev/docs/cli/skills/

Kiro will read the documentation, download the skill files, and configure everything. Afterwards, you can ask Kiro to read, create, and modify Excel files directly — it knows the right approach because the Skill tells it how.

The pattern: MCP servers give the agent access to new data and tools (like AWS docs, GitHub, databases). Skills teach it how to do specific jobs well (like creating spreadsheets, writing documents, generating presentations). Together, they turn a basic agent into a specialist for your workflow.

▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪

04 Strands Agent SOPs: The Game Changer

So far you've seen how to give an agent a single task. But what about entire workflows — the multi-step processes you do manually every day? Think about it: reviewing documents, processing reports, checking logs, summarizing meetings. Normally, automating these requires writing code. What if you could just describe the workflow in plain English and have an agent execute it?

That's exactly what Agent SOPs (Standard Operating Procedures) do. Built by AWS and battle-tested by thousands of Amazon teams, SOPs are markdown files that describe a workflow step by step. You feed the SOP to an agent, and it follows the instructions — reading files, running commands, making decisions — just like a human would follow a checklist. Now they're open source.

The real killer feature: SOPs let you fully automate processes that would normally require writing code. You can turn any manual workflow into an automation just by describing it. No programming needed to start. Later, you can replace individual steps with code snippets to make them more reliable — but you don't have to.

SOPs borrow a simple convention from internet standards (RFC 2119) — special keywords that control how strictly the agent must follow each instruction:

MUST = the agent has to do this, no exceptions    SHOULD = strongly recommended, but agent can adapt    MAY = optional, agent decides

SOP Structure at a Glance

SOP FORMAT
## Goal
What should be achieved when the SOP is done?
## Inputs & Parameters
What information does the agent need? (file paths, URLs, settings...)
## Constraints
MUST / SHOULD / MAY rules that set boundaries for the agent.
## Procedure
The step-by-step instructions. Can include natural language, code, or both.
## Validation
How should the agent check that it did the job correctly?
## Output
What should the final result look like? (file format, structure...)

Why SOPs are Perfect for Rapid Prototyping

Start fully agent-driven — Write your workflow in plain English. No code needed. The AI follows the steps and uses its reasoning to fill in the gaps. You have a working prototype in minutes.
Spot the weak points — Run it a few times. When the agent makes inconsistent decisions at a specific step, you know exactly where to add more precision.
Inject code snippets — Replace the vague steps with concrete code (also AI-generated if you like). The SOP becomes a hybrid: natural language for the flexible parts, code for the deterministic parts.
Iterate to reliability — Keep tightening. Each iteration makes the workflow more reliable without requiring a full rewrite.
▸ THE KEY INSIGHT SOPs give you a spectrum between "fully autonomous agent" and "rigid script." You start at the autonomous end and slide toward determinism only where you need it. This is far faster than writing code from scratch — and you can share the SOP with anyone, because it's just a readable markdown file.
▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪

05 Creating & Using Your First SOP

The best way to start is to take something you already do — a prompt you type regularly — and turn it into a reusable SOP. Let's do that step by step.

From Everyday Prompt to Reusable SOP

Say you often ask an AI: "Fix the grammar issues and improve the flow of this text." That works, but you get different quality each time. Let's turn it into a consistent, reusable SOP:

text-polish.sop.md
## Goal
Improve the grammar, clarity, and flow of a given text file
while preserving the author's voice and intent.

## Parameters
- MUST input_file: Path to the text file to improve
- MAY tone: Target tone (default: "professional")

## Constraints
- MUST preserve the original meaning and intent
- MUST keep technical terms unchanged
- SHOULD prefer shorter sentences over long ones
- MUST NOT add new information not present in the original

## Procedure
1. Read the entire input_file
2. Identify grammar errors, awkward phrasing, and unclear passages
3. Rewrite problem areas for clarity and flow
4. Ensure paragraph transitions are smooth
5. Save the improved version as {input_file}-polished.md
6. Create a short changelog listing the key changes made

## Validation
- MUST verify no technical terms were altered
- MUST verify the polished text is similar in length (±20%)

## Output
Two files: the polished text and the changelog

Running SOPs in Kiro CLI?cd into the directory where your .sop.md file lives, then start kiro-cli from there. Inside Kiro, tab completion works for SOP filenames — just start typing and press Tab.

# Inside Kiro CLI:
> run text-polish.sop.md with draft-blogpost.md

Kiro reads the SOP, follows each step, creates the polished file and the changelog. Every time you run it, the result is consistent because the constraints and validation steps keep the agent on track.

Creating SOPs Conversationally

You don't even have to write the SOP by hand. You can ask Kiro to create one for you. But first, you need to teach it the SOP format. Just tell Kiro to fetch the formatting rule directly from GitHub:

> Read this rule and apply it: https://raw.githubusercontent.com/strands-agents/agent-sop/refs/heads/main/rules/agent-sop-format.md
# → Kiro downloads the rule and learns the SOP format.

Now Kiro knows how to write properly structured SOPs. Just describe the workflow you want:

> Create an SOP that takes a folder of CSV files, validates
  that each file has the required columns (date, amount,
  category), merges them into one file, and creates a
  summary with totals per category.

Kiro will generate a properly structured SOP with parameters, constraints, procedure, and validation — ready to use or refine.

▸ PRO TIP Never edit SOPs by hand. Instead, ask Kiro to make changes: "add a step to flag duplicate entries", "make the output format Excel instead of CSV". Kiro understands the SOP structure and will update it correctly, keeping all the formatting, constraints, and validation rules intact. SOPs are your versioned, shareable automation recipes — just markdown files you can check into Git.
▸ LEVEL UP Want to never run that rule again? Ask Kiro:
> Turn the Agent SOP format rule at https://raw.githubusercontent.com/strands-agents/agent-sop/refs/heads/main/rules/agent-sop-format.md into an Agent Skill following the spec at https://agentskills.io/specification. Put the full rule content into the SKILL.md body — don't split into reference files. Save it to my global skills directory as agent-sop-format/SKILL.md. Now Kiro knows how to write SOPs in every session, in every project — permanently. You just used the agent to upgrade itself.
▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪

06 SOPs with Code: The Full Power

The text-polish SOP above was fully agent-driven — every step was natural language. That's great for a prototype. But for steps that need to produce the exact same result every time, you can embed actual code snippets right in the SOP. The agent then runs that code instead of improvising.

Here's a real-world example: an SOP that downloads YouTube video transcripts and generates structured summaries. Notice how some steps are natural language (the agent reasons) and some are concrete code (deterministic execution):

Below is a condensed view. You can view the full SOP file here.

yt-summary.sop.md
## Goal
Download a YouTube video transcript and generate a structured
summary of the main topics discussed.

## Parameters
- MUST youtube_url: The YouTube video URL
- MAY language: Transcript language (default: "en")

## Step 1: Download Transcript
← This step uses exact code (deterministic):
The agent MUST use yt-dlp (a command-line YouTube downloader) to get subtitles:
yt-dlp --write-subs --write-auto-subs --sub-lang en --skip-download "URL"

## Step 2: Clean VTT Content
← Also deterministic — the SOP includes a full Python script:
The agent MUST run the provided Python script to strip
VTT headers, timing tags, and remove repeated phrases.
Here's a snippet of what that looks like in the SOP:
# Excerpt from the cleaning script embedded in the SOP:
import re, os, sys

video_id = sys.argv[1]
vtt_file = [f for f in os.listdir('.')
            if f.endswith('.vtt') and video_id in f][0]

# Strip VTT timing headers, inline tags, and duplicates
# ... (full script in the SOP file)

with open('subtitle.txt', 'w') as f:
    f.write(' '.join(cleaned))
## Step 3: Generate Summary
← This step is agent-driven (flexible):
Read the entire transcript and create a summary using
this structure: TL;DR, The Big Idea, Key Takeaways,
Who Should Watch, Skip If.
The agent MUST derive a descriptive filename from
the video content with the YouTube video ID appended.

See the pattern? Steps 1 and 2 are deterministic — the agent runs the exact commands and scripts specified. Step 3 is agent-driven — the AI uses its reasoning to create a good summary. This hybrid approach gives you reliability where it matters and flexibility where you need it.

Running It in Kiro CLI?cd into the directory where your .sop.md file lives, then start kiro-cli from there. Inside Kiro, tab completion works for SOP filenames — just start typing and press Tab.

# Inside Kiro CLI:
> run yt-summary.sop.md with
  https://www.youtube.com/watch?v=NrbzlvjX0GQ

The agent downloads the transcript, cleans it with the exact script provided, then uses its intelligence to create a concise, well-structured summary. Same result structure every time, but with the AI's reasoning for the creative parts.

▸ IMPORTANT: DON'T EDIT SOPs BY HAND When you want to change an SOP, don't open the file and edit it directly. Instead, tell Kiro what to change:

> Update yt-summary.sop.md: add a step after the summary that generates a LinkedIn post highlighting 3 key insights from the video
Or provide an example of what you want:

> Here's an example output I liked — update the SOP so future summaries follow this format: [paste example]
Kiro understands the SOP structure and will make the change correctly, keeping all the formatting, constraints, and validation rules intact.
▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪

07 Resources & Next Steps

Quick Wins to Try Right Now

1. Install Kiro CLI and ask it to create the AWS News scraper from Section 02.
2. Add the AWS Documentation MCP server and ask an architecture question.
3. Install the xlsx Skill and ask Kiro to create a budget spreadsheet.
4. Turn a prompt you use weekly into an SOP (grammar fix, log analysis, data cleanup).
5. Run that SOP a few times, then harden one step with a code snippet.

▸ REMEMBER The goal isn't to write perfect code from day one. It's to automate first, discover where the gaps are, and only then invest effort in making things deterministic. SOPs are your bridge from "I asked a chatbot" to "I have a reliable automated workflow" — and you get there incrementally, not by starting over.
▸ ABOUT THIS PAGE Hi, I'm Christoph Schnidrig. A close friend asked me: "How do I actually get started with agentic AI — not just chatting, but having it do things and automate stuff? It's overwhelming when you go to YouTube." That question inspired this guide. Strands Agent SOPs in particular changed how I approach automation — I use them every day to turn manual workflows into reliable automations. This page is my attempt to share that starting point.
This page reflects my personal experience and opinions. I work at AWS, but this is not an official AWS publication. Kiro is an AI-powered IDE by AWS — free tier available, with paid plans for additional credits. Strands Agent SOPs and MCP are open source.