Loading...
Loading...
Found 91 Skills
Analyse GitHub repository activity including issues, PRs, contributors, and engagement
Conduct enterprise-grade research with multi-source synthesis, citation tracking, and verification. Use when user needs comprehensive analysis requiring 10+ sources, verified claims, or comparison of approaches. Triggers include "deep research", "comprehensive analysis", "research report", "compare X vs Y", or "analyze trends". Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
Should be used when doing clickhouse analysis and diagnostics review before any altinity-expert-clickhouse skill to test clickhouse connection and set general rules
Deep Research Methodology (8-Step Process): Transform vague topics into high-quality research reports. Automatically perform problem decomposition, data stratification, fact extraction, framework comparison, derivation and verification, and deliver structured reports. Trigger Words: - "Deep Research", "In-Depth Study", "In-Depth Analysis" - "Help me research", "Do a research", "Conduct a study" - "Comparative Analysis", "Concept Comparison", "Technology Comparison" - "Write a research report", "Produce a research report" Note: If the user needs a visual diagram instead of a report, please use the research-to-diagram skill.
Deep research and analysis tool. Generates comprehensive HTML reports on any topic, domain, paper, or technology. Use when user asks to research, analyze, investigate, deep-dive, or generate a report on any subject. Supports academic papers (arXiv), technologies, trends, comparisons, and general topics.
Track and check updates for all OpenClaw dependencies: managed skills (GitHub/ClewHub), bundled skills, workspace skills, npm packages, pip packages, and CLI tools. Use when user asks "check for updates", "dependency status", "are my skills up to date", "什么需要更新", "检查依赖", "检查更新", or wants a dependency health report. Triggers on: dependency check, skill updates, outdated packages, version drift.
Create structured documents from conversations, summaries, or content in open formats (markdown, PDF, text). Use when the user requests document creation, report generation, content export, conversation summaries, or structured documentation. Triggers include "create a document", "make a report", "summarize this conversation", "export to PDF/markdown", or any request to formalize content into a document. Works independently or integrates with design-assistant skill for polished visual output.
Use when the user asks to perform a code review, review code changes, analyze a diff, or audit code quality. Runs a structured review of git diff output covering security, correctness, performance, maintainability, and style. Produces a markdown report saved as a .md file named after the current branch.
Generate user demand research reports from real user feedback. Scrape and analyze feature requests, complaints, and questions from Reddit, X, and GitHub.
Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
Shows a summary of the most recent validator session for requests such as "show validator status", "summarize last validator run", or "what failed in the last validator session".