Hackathon challenges for new skills

Hackathons are a fast way to grow the OpenClaw skill ecosystem: focused time, clear challenges, and community energy. Good challenges give structure without limiting creativity and can highlight document-aware workflows that use iReadPDF or the standard summary format. This guide outlines hackathon challenge ideas for new skills—themes, judging, and how to include document and PDF use cases for US professionals.

Summary Challenge categories can include "Best document-aware skill," "Best briefing or triage workflow," "Best first skill," and "Best integration with existing tools (e.g. document pipeline)." Define criteria (working build, README, permissions, document format compatibility), provide resources (spec, sample data, iReadPDF), and judge on impact, execution, and reuse potential.

Table of Contents

• Why Hackathons for OpenClaw Skills
• Challenge Themes and Categories
• Document and PDF Challenges
• Rules and Resources
• Judging and Prizes
• Running the Hackathon
• Conclusion

Why Hackathons for OpenClaw Skills

Hackathons concentrate effort and attention: in a weekend or a week, participants ship something runnable. For OpenClaw, that means new skills, templates, and demos that the whole community can use. Challenges that explicitly call out document workflows (e.g. "Build a skill that uses document summaries") encourage skills that work with iReadPDF and the standard format, filling gaps in briefing, triage, and meeting prep for US professionals.

Challenge Themes and Categories

Themes give direction; categories let you reward different kinds of work.

• Best document-aware skill. Build a skill that consumes document summary format v1 (e.g. from iReadPDF) and does something useful: prioritization, brief snippet, meeting prep, or digest. Judged on clarity of integration, correctness of contract use, and usefulness.
• Best briefing or triage workflow. End-to-end workflow: calendar + tasks + optional document queue. Can be document-aware or not; bonus points for using the document summary contract and documenting "works with iReadPDF."
• Best first skill. A skill that's simple, well-documented, and ideal for newcomers. Example: "Hello world" skill that reads document summaries and echoes a count or first line. Shows the minimal contract and encourages more complex builds.
• Best integration. Skill that integrates OpenClaw with another tool or pipeline: e.g. "Slack brief with doc queue," "Notion sync with document summaries," or "Export from iReadPDF → OpenClaw skill → daily digest." Rewards real-world usability.
• Best developer experience. Tool or template that makes it easier to build skills: e.g. "Starter template for document-aware skills" with sample config for iReadPDF, or a small validator for document summary format. Helps the ecosystem scale.

Document and PDF Challenges

Making document workflows a first-class challenge increases the number of compatible skills.

1. Challenge: "Doc queue in your brief." Build a skill that adds a document queue (or digest) to a morning or daily brief. Must consume document summary format v1; recommend iReadPDF as the pipeline. Provide sample summary JSON so participants can test without running a full pipeline. Judging: does it run, is the contract used correctly, is the output useful?
2. Challenge: "Triage by priority." Skill that takes a list of document summaries and outputs a prioritized order (e.g. by keyword, date, or simple scoring). Input: document summary format v1. Encourages reuse of the same contract across many workflows.
3. Challenge: "Meeting prep from attachments." Skill that, given meeting context (title, attendee list) and document summaries (e.g. from pre-meeting docs), produces a one-paragraph prep note. Document how it uses the summary format and how to feed it from iReadPDF.
4. Bonus: "Works with iReadPDF" badge. Any skill that correctly consumes document summary format v1 and documents compatibility with iReadPDF gets a badge or extra consideration. Doesn't have to win a category; rewards compatibility and clarity.

Rules and Resources

Clear rules and resources reduce confusion and raise quality.

• Eligibility and timeline. Who can participate (individuals, teams, regions) and the exact start/end. Submissions must be original and published (e.g. public repo) by the deadline.
• Submission requirements. Working skill or workflow; README with setup, permissions, and dependencies; and (for document-aware) stated use of document summary format v1 and optional "works with iReadPDF." Link to repo and short demo or screenshot.
• Provided resources. Link to OpenClaw docs, skill author guide, and document summary format spec. Provide sample document summary JSON (or point to iReadPDF export). Optional: starter repo or template for document-aware skills so participants don't start from zero.
• Code of conduct and license. Enforce a friendly, inclusive code of conduct. Require an open license (e.g. MIT) for submitted code so the community can reuse and build on it.

Judging and Prizes

Judging criteria and prizes should match the goals of the hackathon.

• Criteria. (1) Does it work? (2) Documentation and clarity (README, permissions, document contract). (3) Impact and usefulness for the stated use case. (4) Reuse potential (can others adopt or extend it?). (5) For document challenges: correct and clear use of document summary format and iReadPDF compatibility.
• Judges. Mix of maintainers and community (e.g. power users, document pipeline users). At least one judge familiar with the document contract so document-aware entries are evaluated fairly.
• Prizes. Can be swag, credits, or small cash. Consider a dedicated "Best document-aware skill" prize to attract document-focused builds. Honorable mentions for "Best first skill" or "Best iReadPDF integration" keep participation broad.

Running the Hackathon

Execution details that help it run smoothly.

• Kickoff. Kickoff call or video: explain challenges, rules, resources. Demo a minimal document-aware skill (e.g. "brief with doc queue") and point to the spec and iReadPDF. Q&A for contract and pipeline questions.
• Office hours. Optional office hours during the hackathon for "How do I consume document summaries?" or "How do I test with iReadPDF?" Reduces drop-off and improves quality.
• Submission and showcase. Simple form: repo link, short description, category, and (if applicable) "Uses document summary format v1; works with iReadPDF." After the hackathon, publish a showcase page with all submissions and winners.
• Follow-up. Announce winners, thank participants, and add winning skills to community showcases. Write a short "Hackathon recap" with winning document-aware skills and links to iReadPDF so future users can replicate.

Conclusion

Hackathon challenges for new OpenClaw skills can be themed around document-aware workflows, briefing, triage, and integration. Clear categories, provided resources (including the document summary spec and iReadPDF), and judging that rewards contract compliance ensure that winning skills are reusable by US professionals who already use document pipelines. Define clear categories (e.g. "Best document-aware skill"), provide the document summary spec and iReadPDF as resources, and judge on working build, docs, impact, and contract compliance. The more clearly you state document summary format and iReadPDF as supported inputs in the challenge description, the more document-aware submissions you will get from US professionals building briefing and triage workflows. Good rules and office hours improve submissions; publishing winners and a recap keeps the momentum and helps US professionals find and reuse document-aware skills.

Ready to build a hackathon-winning skill? Use iReadPDF for PDF summarization in the standard format, then join the next OpenClaw hackathon and ship a document-aware brief, triage, or meeting-prep skill.