Share your OpenClaw experience
If you've spent any time on the internet, you know OpenClaw has been making waves lately. We recently connected with the organizers of ClawCon Michigan and knew it was time to create a space for DEV to get in on the action!
Running through April 26, the OpenClaw Challenge invites you to share your OpenClaw experience with the community. Whether you've been running your own instance for weeks or you're just getting started, we want to hear about it.
There are two prompts for this challenge and six chances to win.
We hope you give it a try!
Our Prompts
OpenClaw in Action
Your mandate is to build something with OpenClaw and share it with the community.
OpenClaw in Action Submission Template
OpenClaw is endlessly hackable and we want to see what you do with it. Whether you're a developer, founder, healthcare professional, or someone who just figured out how to automate something that used to drive you crazy, we want you to show off your build.
Wealth of Knowledge
Your mandate is to publish a post about OpenClaw that will educate, inspire, or spark curiosity.
Wealth of Knowledge Submission Template
Not sure what to write about? Here are some suggestions:
-
Tutorial: Walk us through how you built a skill, automated a workflow, or integrated a new service with OpenClaw. The more practical and reproducible, the better.
-
How-to guide: Break down a specific OpenClaw feature or setup process in a way that helps others get started or go deeper.
-
Personal essay or opinion piece: Share your experience building with OpenClaw or make a case for something. What does OpenClaw get right that others don't? What has your experience taught you about where personal AI is headed?
Note: If you are primarily showing off a project, please submit to the OpenClaw in Action prompt instead!
Prizes
We'll select three winners for each prompt.
Six prompt winners will each receive:
🦞 Bonus for ClawCon Michigan Attendees
Are you attending ClawCon Michigan tonight (April 16)? Participate in this challenge and you'll receive an exclusive ClawCon Michigan DEV badge: our way of celebrating the IRL OpenClaw community that inspired us to craft this challenge.
All Participants with a valid submission will receive a completion badge.
How To Participate
In order to participate, you must publish a DEV post using the submission template associated with each prompt.
Please review our judging criteria, rules, guidelines, and FAQ page before submitting so you understand our participation guidelines and official contest rules such as eligibility requirements.
Important Dates
-
April 16: OpenClaw Writing Challenge begins!
-
April 26: Submissions due at 11:59 PM PDT
-
May 7: Winners Announced
We can't wait to read what you write. Questions about the challenge? Drop them in the comments below.
Good luck and happy clawing! 🦞
Top comments (19)
Claws out
If you're lookin to give your pinchers state, memory, tool calling, model routing, etc. crawl on over to our backboard open claw plugin... npm i openclaw-backboard
Fascinating. Will probably participate, but more on the writing side if anything. Good Luck everyone! Can't wait to see what everyone is going to write/create with OpenClaw! :D
Nice challenge and prizes!
Santa Claws arrived early this year.
Good luck everyone.
openclaw here we go
On it🔥
I Built a Personal AI Assistant with OpenClaw — Architecture, Code, and What Actually Works
🧠 Introduction
Most conversations about personal AI focus on capability:
But after building a working system with OpenClaw, I realized something different:
This post walks through:
🧱 System Overview
I designed a minimal but extensible system with 4 core layers:
1. Input Layer
Handles messy, real-world input:
2. Processing Layer
3. Memory Layer
4. Action Layer
⚙️ Core Implementation
🧩 1. Task Extraction Engine
The first challenge: turning messy input into structured tasks.
👉 This simple parser worked surprisingly well for real-life inputs.
🧠 2. Priority Scoring System
Instead of “AI magic,” I used a rule-based scoring system:
👉 Insight:
Simple heuristics outperformed complex logic for everyday use.
🗂️ 3. Memory Layer (Lightweight Storage)
I used a simple in-memory structure (can be replaced with DB):
🔔 4. Action Engine (Reminders & Nudges)
🔄 5. Putting It Together
🧪 Example Interaction
Input:
Output:
🔍 What Actually Worked
✅ 1. Simplicity scales better than complexity
The system became more reliable when I:
✅ 2. Messy input is the real challenge
Handling:
…was more valuable than improving model intelligence.
✅ 3. Prioritization is everything
Users don’t need more information.
They need:
⚠️ What Didn’t Work
❌ Over-engineering the system
Adding:
…reduced usability.
❌ Fully autonomous behavior
The system worked best when:
🚀 Extending This System with OpenClaw
Here’s where OpenClaw becomes powerful:
🔗 Skill-based extensions
🔄 Composability
Each module can become a reusable skill:
💡 Key Insight
After everything, one thing became clear:
🏁 Final Thoughts
This wasn’t a massive AI system.
It didn’t:
But it did something more important:
It worked.
It handled real-life chaos:
And that’s where personal AI becomes meaningful.
📌 If You’re Building with OpenClaw
Start here:
Don’t chase perfection.
Build something that helps — even a little.
Because in real life, that’s more than enough.
The OpenClaw angle here is interesting — the Claude Skills ecosystem feels like it's at the same inflection point that npm packages had around 2013. One practical tip for submissions: think hard about skill composability. A skill that chains cleanly into other skills (well-defined inputs/outputs, clear failure modes) tends to be far more useful in real agent workflows than a monolithic "do everything" skill. Any chance the judging rubric weights reusability vs. novelty?
I'm completely in

Great initiative! Looking forward to exploring OpenClaw more.
Some comments may only be visible to logged-in visitors. Sign in to view all comments. Some comments have been hidden by the post's author - find out more