Loading...
Loading...
Found 5,606 Skills
When the user wants to create, optimize, or audit features page content. Also use when the user mentions "features page," "product features," "capabilities," "what it does," "feature list," "feature comparison," "product capabilities," or "features section."
When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "suggest Grokipedia article," "Grokipedia citation," "Grokipedia listing," "AI search citation," "GEO visibility," or "Grokipedia optimization." For parasite SEO strategy, use parasite-seo.
Why build on Ethereum specifically. The AI agent angle — ERC-8004, x402, composability, permissionless deployment. Use when a user asks "should I build on Ethereum?", "why blockchain?", or when an agent needs to recommend a chain for a project.
Hypothesis-driven deep research swarm. Spawns specialist sub-agents to investigate a task across codebase patterns, web sources, MCP tools, installed skills, and project dependencies — with evidence grading and adversarial challenge. Activates on: research, investigate, discover, deep research, how should I, what's the best way, explore options, analyze approaches, scout, prior art, feasibility.
This skill should be used when the user asks to "develop a concept", "explore a new idea", "brainstorm a system concept", "do concept development", "create a concept document", "run Phase A", "define the problem and architecture", or mentions concept exploration, feasibility studies, concept of operations, system concept, architecture exploration, solution landscape, or NASA Phase A.
Help users integrate and troubleshoot weapp-tailwindcss in uni-app, taro, uni-app x and native mini-program projects. Use when users mention weapp-tailwindcss, invalid Tailwind in mini-programs, arbitrary rpx values, JS string class, space-y/space-x, weapp-tw patch, content/@source, twMerge/cva/tv.
Create ridiculously good content using Ann Handley's "Everybody Writes" methodology—practical, reader-focused writing that serves your audience and achieves your goals. Use when: **Write blog posts** that engage and convert readers; **Create email content** that gets opened and clicked; **Craft social media posts** that stop the scroll; **Develop website copy** that speaks to your audience; **Write thought leadership** that builds credibility
Vue SFC implementation playbook for weapp-vite mini-program projects, including `<script setup lang="ts">`, JSON macros (`defineAppJson/definePageJson/defineComponentJson`), `usingComponents`, template directive compatibility, and SFC compile/runtime troubleshooting. Use when users ask about `.vue` authoring or refactoring in mini-programs (e.g. "v-model 在小程序里怎么写", "definePageJson 和 <json> 怎么选", "SFC 编译报错", "usingComponents 不生效").
Bootstrap, install, and operate an external task-management CLI as the source of truth for agent execution tracking (instead of built-in todos). Provides the abstraction layer between spec-management intent (implementation plans and tasks) and concrete CLI commands. MUST be invoked when any implementation-tier artifact (SPEC, STORY, BUG) comes up for implementation — create a tracked plan before writing code. Optional but recommended for complex SPIKEs. For coordination-tier artifacts (EPIC, VISION, JOURNEY), spec-management must decompose into implementable children first — this skill tracks the children, not the container. Also use for standalone tasks that require backend portability, persistent progress across agent runtimes, or external supervision. Use this skill whenever the user asks to track tasks, create an implementation plan, check what to work on next, see task status, manage dependencies between work items, or close/abandon tasks — even if they don't mention "execution tracking" explicitly.
AI Boyfriend Companion Skill - A sunny, sporty boyfriend who is good at basketball and tennis, has strong empathy, remembers chat details, and automatically sends birthday and holiday greetings. Use this skill when the user wants companion chat, emotional support, sports discussions, or when greeting messages need to be sent via OpenClaw.
Use when designing software architecture, refactoring code structure, solving recurring design problems, or when code exhibits symptoms like tight coupling, rigid hierarchies, scattered responsibilities, or difficult-to-test components. Also use when choosing between architectural approaches or reviewing code for structural improvements.
Full closed-loop QA combining issue discovery and software testing. Scout -> Strategist -> Generator -> Executor -> Analyst with multi-perspective scanning, progressive test layers, GC loops, and quality scoring. Supports discovery, testing, and full QA modes.