Loading...
Loading...
Found 2,044 Skills
Connect and use third-party apps through Mermail Composio from Claude, Codex, or another external MCP client. Use when a user wants to inspect connection status, connect or reconnect GitHub, Slack, Apollo, Notion, Google Calendar, or another supported toolkit, discover a provider action and schema, or execute an allowed third-party read or write. Never route Gmail or Outlook email work through Composio; keep email in Mermail.
This skill should be used when the user asks for a "sensitivity reader", "authenticity reader", "cultural review", "is this portrayal okay", "real people in my novel", "defamation", "can I use song lyrics", "epigraph permission", "permissions", "quote permission", "fair use", "AI disclosure", "do I need to disclose AI", "send to my editor", "editorial round", "Word file for my editor", "editor review copy", "co-author", "collaborate on a book", "shared world", "back up my book", "does this echo my source", "similarity check", "check overlap with my earlier books", or wants to run human editorial, ethics, permissions, or collaboration workflows around a story project. NOT for contracts or selling rights (use publishing), or reader feedback rounds and review copies for readers, including the GitHub review-copy setup (use feedback-triage).
Deep EVM smart contract security audit system. Use when asked to audit a contract, find vulnerabilities, review code for security issues, or file security issues on a GitHub repo. Covers 500+ non-obvious checklist items across 19 domains via parallel sub-agents. Different from the security skill (which teaches defensive coding) — this is for systematically auditing contracts you didn't write.
Identify EMERGING trends by connecting dots across unrelated sources. Monitor niche communities, academic research, GitHub, patents, funding, regulatory changes. Predict what will trend in 3-6 months based on weak signals.
This skill should be used when the user asks to "migrate to Buildkite", "convert pipelines from Jenkins", "convert GitHub Actions workflows", "convert CircleCI config", "convert Bitbucket Pipelines", "convert GitLab CI", "migrate CI/CD to Buildkite", "switch from Jenkins to Buildkite", "move from GitHub Actions", "plan a CI migration", "convert my CI config", "bk pipeline convert", or "what's the Buildkite equivalent of". Also use when the user mentions migration planning, CI conversion, pipeline conversion, converting workflows, or asks about translating CI/CD configuration from another provider to Buildkite.
Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure/fix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.
Create or improve a complete Runpod template project from an application request, local code, or GitHub repository, with a documented Dockerfile and app-specific files for Pods or queue/load-balanced Serverless. Use runpod-templates for finding or operating existing official templates, runpod-mcp/runpodctl to register an already-built image as a template, flash for its code-first workflow, and companion-clis for standalone image build/push commands.
A Git workflow assistant toolkit. Use this skill when the user asks to generate a commit message, commit or push code changes, create or switch branches based on a Chinese description, create or update a PR/MR for a target repository, merge a PR/MR by number and update the main branch, tag a branch with a version and push it, tag an already merged stable branch and create a GitHub/GitLab Release by default (the release phase after pr-merge), slim down the current Git repository into a shallow clone, or pull and categorize GitHub starred repositories. It also handles vague requests such as "write a commit message," "commit this," "create a branch for XX," "open a PR," "merge the PR," "create a tag," "publish a release," "publish a version," "slim down the repository," and "categorize my starred repositories."
Optimize local build, test, and check commands with measured wall-time evidence. Use for "speed up my build", "why is just check slow", or /build-optimize. Route GitHub Actions work to /ci-optimize.
Write tests for the added lines that a pharn-ci report (the pharn-dev/pharn-ci GitHub Action or the `pharn-ci check` CLI, 0.1.x with Report v1 or 0.2.x with Report v2) lists as uncovered, so a pull request's diff coverage meets its threshold. Use when pharn-ci fails with DIFF_COVERAGE_BELOW_THRESHOLD, or the person asks to cover the lines pharn-ci reports, raise diff coverage, get the pharn-ci coverage check passing, or exclude a file from, lower or switch off the pharn-ci coverage gate (it explains what that changes and asks first). Adds tests only - never lowers the threshold, excludes files, edits the pharn-ci config or workflow (including the test-integrity and accept-label inputs), adds coverage-ignore comments, skips or focuses tests, weakens test scripts, or applies the accept label. Not for adding pharn-ci to a repository (pharn-ci-install) or the PHARN CLI (pharn-cli).
Daily report creation skill. Summarizes GitHub and Jira activities, creates a draft, and posts as an Issue. Use when: - Asked to "create daily report" or "write daily report" - Asked to "summarize today's activities" - Requested to create a daily report or journal
Research and extract an engineer's coding style, patterns, and best practices from their GitHub contributions. Creates structured knowledge base for replicating their expertise.