Parts 1-4 showed you what Kiro Crew can do. Investigate incidents. Automate weekly toil. Block dangerous commands. All using the built-in agent.
{% link https://dev.to/aws-builders/introducing-kiro-crew-awss-open-source-ai-agent-orchestrator-1e63 %}
{% link https://dev.to/aws-builders/how-kiro-crews-cron-jobs-replaced-4-hours-of-weekly-toil-37h %}
But here's what nobody's talking about: Kiro Crew has an App Store. And you can build your own apps for it. In five minutes.
Not plugins. Not scripts. Full apps with their own agents, skills, cron jobs, and dashboard pages. Package them. Publish them. Other users install with one click.
I built one. A Daily Standup Bot. It reads my git commits every morning and generates standup notes so I never have to write "worked on X" again. Let me show you how.
Table of Contents What the App Kit actually is What we're building Step 1: The manifest (app.json) Step 2: The agent Step 3: The skill Step 4: The dashboard page Step 5: The cron job Install and run What it looks like live Publishing to the App Store What else you could build Try it yourself
| Component | What it does | |-----------|-------------| | Agents | Custom AI agent with its own model, prompt, and tool access | | Skills | On-demand knowledge files that teach the agent specific capabilities | | MCP servers | New tools the LLM can call | | Cron jobs | Scheduled tasks the app owns | | UI pages | Custom pages in the dashboard sidebar | | Backend processes | HTTP servers reverse-proxied through the gateway |
An app that only ships a skill is one markdown file. An app that ships everything is a full project. You decide the scope.
The key difference from "just adding a skill": apps are installable, versioned, publishable, and isolated. Crew manages their lifecycle. Users install from the App Store with one click.
A Daily Standup Bot that: Reads git commits from the last 24 hours Formats them as "What I Did / What's Blocked / What's Next" Runs every weekday at 9 AM automatically Shows standup history in a custom dashboard page
That's agents, skills, a dashboard page, and a cron job. All declared in one file. Crew reads this and wires everything up.
Eight lines. The @kirocrew-core tool reference gives it access to spawn processes, read files, and interact with the system. The model: "auto" lets Crew pick the best available model.
Skills are markdown. They load on-demand when trigger words appear in the conversation. No code. No compilation. Just knowledge the agent uses when relevant.
You don't npm install @kirocrew/app-sdk. The dashboard provides it at runtime. Your app stays tiny. Build with Vite, mark Crew's SDK as external, output a single .mjs file.
Crew registers the cron on enable. Deregisters on disable. Every weekday at 9 AM, it spawns a session, runs the message through standup-agent, and stores the result. No daemon. No systemd timer. Just a line in your manifest.
After installation, "Standups" appears in the sidebar. The dashboard shows stat cards and an empty state waiting for the first standup.
The agent runs git log --since="24 hours ago" --oneline --no-merges, analyzes each commit, and produces: