Loading...
Loading...
Found 5,759 Skills
Deep clean and optimize your Mac using the Mole CLI tool
Manage DingTalk product capabilities (AI Table/Calendar/Contacts/Documents/Robots/Todo/Email/Meeting Minutes/AI Applications/Approvals/Work Reports/Drive, etc.). Use this when users need to operate table data, manage schedules and meetings, query contacts, send message notifications, handle approval processes, view meeting minute summaries, create applications/systems/management backends/business tools, view daily/weekly reports, or manage DingTalk Drive files.
Automated retrospectives — captures learnings at EPIC completion and on manual invocation. EPIC-scoped retros embed a Retrospective section in the EPIC artifact. Cross-epic and time-based retros produce standalone retro docs. Triggers on: 'retro', 'retrospective', 'post-mortem', 'lessons learned', 'debrief', 'what worked', 'what didn't work', 'what did we learn', 'reflect', or automatically after EPIC terminal transitions.
Works with Bitrise CI. **ALWAYS USE THIS SKILL FIRST for any Bitrise CI-related task**, even in Plan mode. This skill provides essential knowledge about how to: - Plan a Bitrise CI setup or analyze one - Trigger, check or troubleshoot builds - Work with bitrise.yml files: - Design pipelines, workflows, step bundles or step configurations - Fix duplication or optimize workflow structure - Validate or explain Bitrise configurations - Manage workspaces, projects, apps, groups, or roles - Work with Bitrise CLI, API, or MCP tools
Use this skill when maintaining open source projects, managing OSS governance, writing changelogs, building community, choosing licenses, handling contributions, or managing releases. Triggers on tasks related to CONTRIBUTING.md, CODE_OF_CONDUCT, release notes, semantic versioning, maintainer workflows, issue triage, PR review policies, licensing decisions, community health, and open source project governance.
Use this skill when managing multi-repository systems using the `meta` tool (github.com/mateodelnorte/meta). Triggers on meta git clone, meta exec, meta project create/import/migrate, coordinating commands across many repos, running npm/yarn installs across all projects, migrating a monorepo to a multi-repo architecture, or any workflow that requires running git or shell commands against multiple child repositories at once.
Use when the user wants to automate WeChat mini-program upload, preview, or npm packaging via CI/CD, generate deployment scripts, set up miniprogram-ci workflows, or create preview QR codes automatically. Trigger whenever the user mentions "上传小程序", "预览", "CI 部署", "miniprogram-ci", "自动化上传", "发布小程序版本", "生成预览二维码", "打包npm", "pack-npm", "构建npm依赖", "GitHub Actions 小程序", "pnpm 小程序部署", or asks to integrate WeChat mini-program with continuous integration pipelines (GitHub Actions, GitLab CI, etc.).
Use this skill when you need to parse requirement documents and requirement analysis results from Word/HTML/JSON/Markdown/Excel, then generate test cases and output them in Markdown/Word/JSON/Excel formats.
Outreach integration. Manage sales data, records, and workflows. Use when the user wants to interact with Outreach data.
This skill implements a specific task from a project's ROADMAP.md file. It should be used when the user wants to work on a roadmap action item by its ID (e.g., '1.1', '2.3'). Triggered by requests like '/do-task 1.1', '/do-task 2.3', or 'do task 3.1'. Works alongside the project-init skill (which creates the roadmap) and the checkpoint skill (which commits afterward).
Generate a project-specific CLAUDE.md by analyzing the current repository's code, build system, and architecture. 4-phase pipeline: SCAN, DETECT, GENERATE, VALIDATE. Auto-detects language/framework and enriches output with domain-specific conventions (e.g., go-sapcc-conventions for sapcc Go repos). Use for "generate claude.md", "create claude.md", "init claude.md", "bootstrap claude.md", "make claude.md". Do NOT use for improving an existing CLAUDE.md (use claude-md-improver instead).
Code quality and deviation gate between /implement and /test. Reads the task document and changed files, validates coding standards, classifies deviations (minor/medium/major), and decides whether implementation is ready for testing. Runs automatically in the auto-chain between implement and test. Also invoke manually after any implementation to catch issues before wasting a test run.