When I first explored Kiro Powers, the Datadog Power immediately stood out. I’m a DevOps Engineer focused on Observability and Monitoring. I have experience with Datadog, New Relic and PostHog, so this piqued my attention. I was also participating in a hackathon that used Datadog, so I got to try that Power in a real workflow—not just as a demo. That experience triggered a simple thought: I also use PostHog heavily in another project, and I couldn’t find a PostHog Power. Since PostHog already has an MCP server, it felt like a perfect candidate for my first Power project.
TLDR; You can try my first Kiro Power for Posthog: posthog-kiro-power
What are Kiro Powers?
Kiro Powers are on-demand capability bundles for your AI agent. Instead of always loading every tool and every set of best practices into context, a Power is activated when it’s relevant—so the agent can load the right context and tools at the right time.
A Power typically packages:
- MCP servers / tool connections (so the agent can interact with real systems)
- Steering / guidance files (best practices and workflow patterns)
- Optional hooks (validation or automation depending on the Power)
That “load on demand” part is the key idea for me. Powers are meant to keep the agent focused without overwhelming it with irrelevant context.
If you want the official docs: Kiro Powers
Building the Power with Kiro’s Build a Power
The first step for me was using the Power that helps you Build a Power. This power guides you through the structure and basic setup.
My approach was simple:
- I told Kiro I wanted to create a Power for PostHog MCP
- I provided the PostHog MCP URL/docs as context (link below)
- I also mentioned I already had the Datadog Observability Power installed, and asked if we could use it as a template since both are observability-oriented
Normally, I use spec-driven development with Kiro. But in this case, I didn’t. This was small and specific, and I knew exactly what I wanted—so I treated it more like a guided conversation than a formal spec.
“An unexpected error occurred, please retry.”
There’s a common Kiro error that people mention a lot:
“An unexpected error occurred, please retry.”
I’d seen it discussed in the Discord community, but I’d never hit it myself until I installed my own Power.
Because this was my first Power, I initially assumed I’d made a mistake in the implementation or missed a required configuration step. I ended up going down a rabbit hole trying to figure out what was wrong.
In the end, it was much simpler: it was a misconfiguration / bad state in the Power setup. What fixed it was:
- Uninstalling a couple of Powers I wasn’t using
- Reinstalling cleanly
- Re-trying the install
- Click on ‘Try this Power’
Installing it, testing it, and open sourcing it
For a testing installation, I decided to import power from a folder and it worked fine. I just have to add my PostHog API key and it was ready to go.
Testing was straightforward because my application was already wired up with PostHog. Once the Power was installed, I could ask Kiro to inspect what I already had in PostHog dashboards, existing insights, and the general shape of my data. It actually came back and propose to use Feature Flags with PostHog, which is a really good suggestion, as I am using feature flags in a very basic way.
I also asked Kiro to look at my PostHog setup and propose a plan for adding LLM monitoring, because I’m currently missing that. It gave me a concrete direction, and implementing that is the next feature I want to add after writing this blog post.
This Kiro Power is key as I can focus my development to be more data-driven by just asking Kiro to look into my data on PostHog and use it as context or new features.
How to try it?
In order to install it, you just need the GitHub URL https://github.com/llamojha/posthog-kiro-power/tree/main/powers/posthog, plus your PostHog API key in the MCP config.
Lessons learned and what’s next
Initially, it felt a bit intimidating having to ‘build a power’. This all changed once I tried. Having the ‘Build a Power’ power to help me and guide me building helped a lot. It felt like a conversation with Kiro and it was very straightforward. I fully recommend you try to build a Power even if it’s just to find out how it works.
If you already know the tool you want to wrap—an MCP server, a CLI, or a workflow you use often—then creating a Power is mostly about packaging it cleanly and making it easy for the agent to load when relevant.
Next steps
This was a fun and smooth experience so I’m eager to keep building. I have a couple of ideas on what to do next:
- I’ve used New Relic as well, so I’m looking into the New Relic MCP side and creating a New Relic Power
- I also want to build a more complex Power. Bundle up Hooks and Steerings and test how far the Power concept can go in a larger workflow.
If someone from PostHog is reading this, please feel free to copy my work and make an official PostHog Kiro Power <3.
What was your experience with Kiro Powers? Have you built your own? Share your experience in the comments or join the Kiro Discord
Links