{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-alexanys--awesome-openclaw-usecases-zh","slug":"alexanys--awesome-openclaw-usecases-zh","name":"awesome-openclaw-usecases-zh","type":"repo","url":"https://github.com/AlexAnys/awesome-openclaw-usecases-zh#readme","page_url":"https://unfragile.ai/alexanys--awesome-openclaw-usecases-zh","categories":["automation"],"tags":["ai-agent","ai-assistant","ai-automation","ai-tools","automation","awesome-list","chinese","claude","content-creation","devops","hermes","knowledge-management","llm","openclaw","personal-assistant","productivity","self-hosting","use-cases","workflow-automation","zh-cn"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_0","uri":"capability://planning.reasoning.multi.domain.ai.agent.use.case.curation.and.documentation","name":"multi-domain ai agent use case curation and documentation","description":"Curates and documents 49+ real-world OpenClaw agent implementation patterns across Chinese and international contexts, organized by domain (office automation, content creation, DevOps, knowledge management). The repository serves as a structured knowledge base that maps business problems to agent architecture patterns, enabling builders to reference proven implementations rather than designing from scratch. Uses markdown-based documentation with code examples, configuration templates, and deployment guides for each use case.","intents":["Find proven OpenClaw agent patterns for my specific business domain","Understand how to adapt international AI agent use cases to Chinese market requirements","Learn best practices for building autonomous agents in office automation and content creation","Reference working implementations before building my own agent architecture"],"best_for":["Chinese-speaking developers building LLM agents for enterprise automation","Teams migrating from manual workflows to AI-driven automation","Builders seeking domain-specific agent architecture patterns without starting from zero","Non-technical founders prototyping AI agent MVPs in Chinese market"],"limitations":["Documentation is primarily in Chinese — limited accessibility for non-Chinese speakers","Use cases are OpenClaw-specific — patterns may not directly transfer to other agent frameworks","No interactive testing environment — examples are static documentation rather than runnable demos","Limited real-time updates — use case relevance depends on community contribution velocity"],"requires":["GitHub account to access repository","Basic understanding of LLM agents and OpenClaw framework","Chinese language proficiency for full documentation comprehension","Local development environment matching use case requirements (Python 3.8+, Node.js, etc.)"],"input_types":["business problem description","domain context (office automation, content creation, DevOps, etc.)","existing workflow documentation"],"output_types":["markdown documentation with architecture diagrams","code templates and configuration examples","deployment guides and setup instructions","integration patterns with third-party services"],"categories":["planning-reasoning","knowledge-management","use-case-reference"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_1","uri":"capability://automation.workflow.office.automation.workflow.pattern.reference","name":"office automation workflow pattern reference","description":"Documents OpenClaw agent patterns for automating office tasks including document processing, email management, calendar scheduling, and task coordination. Provides architecture examples showing how agents integrate with office APIs (email, calendar, document storage), handle multi-step workflows, and manage state across office tools. Includes templates for common patterns like automated report generation, meeting scheduling, and document classification.","intents":["Automate repetitive office tasks without building custom integrations from scratch","Understand how to chain multiple office tools together in an agent workflow","Build agents that can read, process, and generate office documents autonomously","Implement autonomous scheduling and meeting coordination agents"],"best_for":["Enterprise teams looking to reduce manual office work through AI agents","Administrative automation specialists building internal tools","Developers integrating OpenClaw with office productivity suites (Feishu, DingTalk, etc.)","Teams managing high-volume document processing workflows"],"limitations":["Patterns assume integration with specific office platforms (Feishu, DingTalk, Outlook) — adaptation required for other systems","State management across long-running office workflows requires external persistence — not built into examples","Rate limiting on office APIs can cause bottlenecks in high-volume automation scenarios","Error handling for office API failures requires custom retry logic not covered in basic examples"],"requires":["OpenClaw framework installed and configured","API credentials for target office platform (Feishu, DingTalk, Microsoft 365, etc.)","Understanding of office API rate limits and authentication mechanisms","Python 3.8+ or Node.js 14+ depending on implementation language"],"input_types":["office document formats (docx, xlsx, pptx)","email content and metadata","calendar event data","task and project management data"],"output_types":["automated documents and reports","scheduled calendar events","classified and organized email","task completion notifications"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_2","uri":"capability://text.generation.language.content.creation.and.generation.workflow.templates","name":"content creation and generation workflow templates","description":"Provides OpenClaw agent patterns for autonomous content generation including blog post writing, social media content creation, video script generation, and multilingual content adaptation. Demonstrates how agents use prompt engineering, content templates, and iterative refinement loops to produce publication-ready content. Includes patterns for content planning, draft generation, review cycles, and multi-platform distribution.","intents":["Generate blog posts and articles at scale using AI agents","Create social media content calendars and posts autonomously","Adapt content across multiple languages and platforms automatically","Implement content review and refinement loops within agent workflows"],"best_for":["Content teams and agencies scaling production without proportional headcount increase","Solo creators and small publishers managing multiple content channels","Marketing teams automating content adaptation for different platforms and audiences","Multilingual content operations requiring consistent quality across languages"],"limitations":["Generated content quality varies significantly based on prompt engineering — requires human review before publication","Agents lack true creative originality — patterns are recombination of training data rather than novel ideas","Fact-checking and source verification require external tools — agents cannot independently verify claims","Brand voice consistency requires extensive prompt tuning and feedback loops per brand"],"requires":["OpenClaw framework with LLM backend (Claude, GPT-4, etc.)","Content management system or publishing platform API access","Template library for target content types","Human editorial review process for quality assurance"],"input_types":["content briefs and outlines","topic keywords and research materials","brand guidelines and voice specifications","source documents for adaptation"],"output_types":["blog posts and articles (markdown, HTML)","social media posts with platform-specific formatting","video scripts and transcripts","multilingual content variants"],"categories":["text-generation-language","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_3","uri":"capability://automation.workflow.devops.and.infrastructure.automation.agent.patterns","name":"devops and infrastructure automation agent patterns","description":"Documents OpenClaw agent patterns for infrastructure monitoring, log analysis, incident response, and deployment automation. Shows how agents integrate with monitoring tools, parse logs, trigger remediation workflows, and coordinate multi-service deployments. Includes patterns for anomaly detection, alert triage, and automated rollback decisions based on system metrics.","intents":["Automate incident detection and initial response without human intervention","Analyze logs and metrics to identify root causes of system failures","Coordinate complex multi-service deployments with automated validation","Implement autonomous infrastructure scaling based on system load"],"best_for":["DevOps teams managing complex microservices architectures","SRE teams automating incident response and remediation","Infrastructure teams reducing MTTR through autonomous troubleshooting","Organizations with 24/7 operations requiring automated on-call support"],"limitations":["Agents require extensive training on system topology and failure modes — generic patterns don't transfer across different architectures","Safety-critical decisions (rollbacks, scaling down) require human approval — full autonomy is risky","Log parsing and metric interpretation require domain-specific knowledge — agents struggle with novel failure patterns","Integration with monitoring tools (Prometheus, Datadog, etc.) requires custom connectors for each platform"],"requires":["OpenClaw framework with access to monitoring and logging APIs","Kubernetes, Docker, or other container orchestration platform","Monitoring stack (Prometheus, Grafana, Datadog, etc.)","CI/CD pipeline integration (Jenkins, GitLab CI, GitHub Actions, etc.)","Incident management system (PagerDuty, OpsGenie, etc.)"],"input_types":["system metrics and performance data","application logs and error traces","deployment manifests and configuration","incident alerts and notifications"],"output_types":["incident reports and root cause analysis","automated remediation actions","deployment validation results","scaling recommendations and actions"],"categories":["automation-workflow","tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_4","uri":"capability://memory.knowledge.knowledge.management.and.semantic.search.agent.patterns","name":"knowledge management and semantic search agent patterns","description":"Documents OpenClaw agent patterns for building knowledge bases, implementing semantic search, and enabling agents to retrieve and synthesize information from large document collections. Shows how agents use embeddings, vector search, and retrieval-augmented generation (RAG) to answer questions grounded in organizational knowledge. Includes patterns for document ingestion, chunking strategies, and multi-hop reasoning across knowledge sources.","intents":["Build searchable knowledge bases that agents can query autonomously","Enable agents to answer questions by retrieving and synthesizing relevant documents","Implement semantic search that understands intent rather than keyword matching","Create agents that can reason across multiple knowledge sources to answer complex questions"],"best_for":["Organizations with large document repositories needing intelligent search","Customer support teams building AI agents that reference knowledge bases","Research teams synthesizing insights from multiple documents","Enterprise teams implementing internal knowledge management systems"],"limitations":["Embedding quality depends on training data — domain-specific embeddings require fine-tuning","Vector search can return irrelevant results if chunking strategy is poor — requires careful document preprocessing","RAG agents hallucinate when knowledge base lacks relevant information — requires fallback mechanisms","Keeping embeddings synchronized with document updates requires continuous re-indexing"],"requires":["OpenClaw framework with embedding model access","Vector database (Pinecone, Weaviate, Milvus, etc.)","Document collection in structured format (PDF, markdown, HTML, etc.)","Embedding model (OpenAI, Sentence Transformers, etc.)","Python 3.8+ for document processing and indexing"],"input_types":["documents in various formats (PDF, docx, markdown, HTML)","user questions and queries","document metadata and tags"],"output_types":["retrieved document excerpts with relevance scores","synthesized answers with source citations","semantic search results ranked by relevance","multi-hop reasoning chains showing information synthesis"],"categories":["memory-knowledge","search-retrieval","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_5","uri":"capability://automation.workflow.personal.ai.assistant.and.productivity.agent.templates","name":"personal ai assistant and productivity agent templates","description":"Provides OpenClaw patterns for building personal AI assistants that manage tasks, schedules, communications, and information needs. Shows how agents integrate with personal productivity tools (note-taking, task management, calendar), maintain user context across conversations, and proactively suggest actions based on user patterns. Includes patterns for multi-turn conversations, preference learning, and personalized recommendations.","intents":["Build a personal AI assistant that understands my work context and preferences","Automate task management and priority setting based on deadlines and importance","Get proactive suggestions and reminders based on my calendar and workload","Maintain conversation context across multiple interactions with the assistant"],"best_for":["Individual knowledge workers seeking personal productivity augmentation","Executives and managers needing intelligent scheduling and priority management","Remote workers managing distributed teams and communications","Researchers and analysts needing information synthesis and organization"],"limitations":["Personal assistants require significant user context and preference data — cold start problem for new users","Privacy concerns with storing personal data — requires careful data handling and user consent","Preference learning requires feedback loops — agents improve slowly without explicit user training","Context window limitations prevent agents from maintaining full conversation history for long-term interactions"],"requires":["OpenClaw framework with persistent storage for user preferences","Integration with personal productivity tools (Notion, Obsidian, Todoist, etc.)","Calendar and email access (Gmail, Outlook, etc.)","User authentication and session management","Privacy-compliant data storage (encrypted, user-controlled)"],"input_types":["natural language queries and commands","calendar and schedule data","task and project information","email and communication context","user preferences and feedback"],"output_types":["task recommendations and prioritization","calendar suggestions and scheduling","information summaries and digests","proactive alerts and reminders","conversation responses with context awareness"],"categories":["automation-workflow","planning-reasoning","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_6","uri":"capability://tool.use.integration.telegram.bot.and.messaging.platform.integration.patterns","name":"telegram bot and messaging platform integration patterns","description":"Documents OpenClaw agent patterns for deploying agents as Telegram bots and other messaging platforms, including message parsing, command handling, state management across conversations, and rich media support. Shows how agents handle asynchronous messaging, manage user sessions, and integrate with external services through messaging interfaces. Includes patterns for inline keyboards, callback queries, and multi-user conversations.","intents":["Deploy OpenClaw agents as accessible Telegram bots without building custom interfaces","Handle multi-user conversations with state management per user","Integrate external services and APIs through messaging commands","Build interactive agents with buttons, menus, and rich formatting"],"best_for":["Teams deploying agents to non-technical users via familiar messaging apps","Developers building chatbots for Telegram and WeChat audiences","Organizations providing customer support through messaging platforms","Communities building collaborative bots for group coordination"],"limitations":["Message length limits on platforms restrict context window — long conversations require summarization","Asynchronous messaging adds latency compared to synchronous APIs — not suitable for real-time interactions","Rate limiting on messaging platforms can throttle agent responses — requires queue management","Rich media support varies by platform — patterns must account for platform-specific capabilities"],"requires":["OpenClaw framework with messaging platform SDK","Telegram Bot API token or WeChat API credentials","Message queue for handling asynchronous requests (Redis, RabbitMQ, etc.)","User session storage (database or cache)","Python 3.8+ or Node.js 14+ for bot implementation"],"input_types":["text messages","command strings (/command syntax)","callback queries from inline buttons","media files (images, documents)","user metadata and context"],"output_types":["formatted text messages with markdown","inline keyboards and buttons","media files and documents","callback responses","notifications and alerts"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_7","uri":"capability://planning.reasoning.multi.agent.coordination.and.workflow.orchestration.patterns","name":"multi-agent coordination and workflow orchestration patterns","description":"Documents OpenClaw patterns for coordinating multiple agents working together on complex tasks, including agent communication protocols, task delegation, result aggregation, and conflict resolution. Shows how agents can specialize in different domains and coordinate through message passing or shared state. Includes patterns for hierarchical agent structures, parallel task execution, and sequential workflow orchestration.","intents":["Decompose complex tasks across multiple specialized agents","Coordinate parallel execution of independent agent tasks","Implement hierarchical agent structures with delegation and supervision","Aggregate results from multiple agents and resolve conflicts"],"best_for":["Teams building complex autonomous systems requiring specialization","Organizations automating multi-step processes across departments","Developers implementing agent-based solutions to large-scale problems","Research teams exploring multi-agent reasoning and collaboration"],"limitations":["Coordination overhead increases latency — parallel execution requires careful synchronization","Agent communication can create circular dependencies or deadlocks — requires careful workflow design","Result aggregation from multiple agents requires conflict resolution logic — no universal solution","Debugging multi-agent systems is complex — requires comprehensive logging and tracing"],"requires":["OpenClaw framework with message passing or shared state support","Message broker or event bus (RabbitMQ, Kafka, etc.) for agent communication","Workflow orchestration tool (Airflow, Temporal, etc.) for complex coordination","Distributed tracing and logging (Jaeger, ELK stack, etc.)","Python 3.8+ or Node.js 14+ for multi-agent implementation"],"input_types":["task specifications and requirements","agent capability definitions","workflow definitions and orchestration rules","inter-agent messages and results"],"output_types":["aggregated results from multiple agents","workflow execution logs and traces","agent communication records","conflict resolution decisions"],"categories":["planning-reasoning","automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-alexanys--awesome-openclaw-usecases-zh__cap_8","uri":"capability://automation.workflow.self.hosted.and.privacy.preserving.agent.deployment.patterns","name":"self-hosted and privacy-preserving agent deployment patterns","description":"Documents OpenClaw patterns for deploying agents on self-hosted infrastructure with privacy guarantees, including local LLM integration, on-premise data processing, and air-gapped deployments. Shows how to run agents without sending data to cloud services, maintain data sovereignty, and comply with data residency requirements. Includes patterns for local embedding models, offline knowledge bases, and encrypted communication.","intents":["Deploy agents on-premise to maintain data sovereignty and privacy","Run agents with local LLMs without cloud API dependencies","Ensure compliance with data residency and regulatory requirements","Build agents that process sensitive data without external service exposure"],"best_for":["Organizations with strict data privacy and sovereignty requirements","Government and regulated industries (finance, healthcare) requiring on-premise deployment","Teams building agents for sensitive business processes","Developers seeking independence from cloud LLM providers"],"limitations":["Local LLMs have lower quality than cloud models — performance trade-off for privacy","Self-hosting requires significant infrastructure and operational overhead — not suitable for small teams","Offline knowledge bases require manual updates — no real-time information access","Air-gapped deployments prevent integration with external services — limits functionality"],"requires":["OpenClaw framework with local LLM support","Local LLM runtime (Ollama, LM Studio, vLLM, etc.)","Self-hosted vector database (Milvus, Weaviate, etc.)","On-premise infrastructure (Kubernetes, Docker, etc.)","Network isolation and security controls","Python 3.8+ or Node.js 14+ for deployment"],"input_types":["local documents and knowledge bases","user queries and commands","system configuration and deployment specifications"],"output_types":["agent responses and reasoning traces","deployment logs and monitoring data","audit trails and compliance records"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":46,"verified":false,"data_access_risk":"high","permissions":["GitHub account to access repository","Basic understanding of LLM agents and OpenClaw framework","Chinese language proficiency for full documentation comprehension","Local development environment matching use case requirements (Python 3.8+, Node.js, etc.)","OpenClaw framework installed and configured","API credentials for target office platform (Feishu, DingTalk, Microsoft 365, etc.)","Understanding of office API rate limits and authentication mechanisms","Python 3.8+ or Node.js 14+ depending on implementation language","OpenClaw framework with LLM backend (Claude, GPT-4, etc.)","Content management system or publishing platform API access"],"failure_modes":["Documentation is primarily in Chinese — limited accessibility for non-Chinese speakers","Use cases are OpenClaw-specific — patterns may not directly transfer to other agent frameworks","No interactive testing environment — examples are static documentation rather than runnable demos","Limited real-time updates — use case relevance depends on community contribution velocity","Patterns assume integration with specific office platforms (Feishu, DingTalk, Outlook) — adaptation required for other systems","State management across long-running office workflows requires external persistence — not built into examples","Rate limiting on office APIs can cause bottlenecks in high-volume automation scenarios","Error handling for office API failures requires custom retry logic not covered in basic examples","Generated content quality varies significantly based on prompt engineering — requires human review before publication","Agents lack true creative originality — patterns are recombination of training data rather than novel ideas","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5688197830389371,"quality":0.43,"ecosystem":0.6000000000000001,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.3,"quality":0.2,"ecosystem":0.15,"match_graph":0.3,"freshness":0.05}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:21.549Z","last_scraped_at":"2026-05-03T13:57:16.561Z","last_commit":"2026-05-03T01:18:01Z"},"community":{"stars":3984,"forks":437,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=alexanys--awesome-openclaw-usecases-zh","compare_url":"https://unfragile.ai/compare?artifact=alexanys--awesome-openclaw-usecases-zh"}},"signature":"9YCmN85f0VIclxguIolHo9BlbEVH4FZnR0DDbT+MDPoGIJa245l5g6n2zttVEE38OAfy26tE5y5a8AXHzWckAQ==","signedAt":"2026-06-22T19:51:43.097Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/alexanys--awesome-openclaw-usecases-zh","artifact":"https://unfragile.ai/alexanys--awesome-openclaw-usecases-zh","verify":"https://unfragile.ai/api/v1/verify?slug=alexanys--awesome-openclaw-usecases-zh","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}