skool-challenge-launcherDesign a public-safe 7-day Skool challenge. Use when the user wants to invite member action, collect comments, produce visible proof, test demand, or turn re...
Install via ClawdBot CLI:
clawdbot install zack-dev-cm/skool-challenge-launcherGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 12, 2026
Aim at freelancers who do repetitive tasks. Ask them to audit one repeated task for a week and share a redacted before/after workflow. This yields proof of process improvement without exposing client data.
Target small business owners struggling to create content. Challenge them to repurpose one blog post into 3 social media variations and share template requests. Collects demand for a content repurposing course.
For course creators stuck on module delivery. Each day tackle a common blocker (e.g., module structure, engagement). Members submit blocker reports, and you release a reusable template on Day 5.
Challenge SaaS power users to find and share one underused feature per day with a redacted screenshot or text summary. Collects user feedback and generates social proof for feature adoption.
Launch the challenge for free; on Day 7, offer a free course module vote. The winner module becomes a paid course, pre-validated by member demand.
Use Day 5 to release a reusable template. Collect feedback and sell advanced templates or template bundles after the challenge.
End the challenge with a CTA for a free trust call (e.g., '30-min review of your workflow'). Convert active participants to paid coaching or consulting clients.
💬 Integration Tip
The challenge is self-contained within Skool posts; no external tools required. For automation, consider using Skool's scheduling feature or a simple Zapier to post daily prompts.
Scored May 12, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.