Loading...
Loading...
Found 7,027 Skills
Schedule sales meetings efficiently — booking pages, round-robin routing, calendar integration, reminders, no-show recovery, and meeting page conversion. Use when setting up booking links, configuring round-robin scheduling, reducing no-shows, optimizing meeting pages, choosing a scheduling tool, Mixmax scheduling, or Mixmax meetings. For Yesware-specific help, use /sales-yesware. Do NOT use for lead routing rules (use /sales-lead-routing), cadence design (use /sales-cadence), or calendar-based CRM automation (use /sales-integration).
Reply.io platform help — multichannel sequences (email, LinkedIn, calls, SMS, WhatsApp), Jason AI SDR, B2B database, email warmup, deliverability tools, unified inbox, analytics, Salesforce/HubSpot integration, agency features. Use when asking 'how do I do X in Reply.io', setting up Reply.io sequences, configuring Jason AI, connecting Reply.io to Salesforce or HubSpot, using Reply.io warmup, or troubleshooting Reply.io deliverability. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Reply.io to other tools via Zapier (use /sales-integration).
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
Write, rewrite, review, and organize developer-facing documentation for web software projects. Use when creating or improving README files, docs homepages, quickstarts, tutorials, how-to guides, API/reference pages, conceptual explanations, migration guides, or troubleshooting content for frontend, backend, full-stack, SDK, API, or framework-based web products. This skill applies strong information architecture, task-first page structure, clear voice, runnable examples, version and prerequisite hygiene, accessibility rules, and docs-as-code maintenance habits. Do not use it for marketing copy, legal text, or non-technical customer-support articles.
Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document
Search markdown knowledge bases, notes, and documentation using QMD. Use when users ask to search notes, find documents, or look up information.
Setup and workflow for using sqry semantic code search as an MCP server with OpenAI Codex CLI. Covers installation, MCP configuration via `~/.codex/config.toml`, and recommended patterns for code analysis tasks. Install this skill to give Codex access to sqry's 34 AST-based code analysis tools.
Create a detailed execution plan for implementing features or refactors in a codebase by leveraging existing research in the specified `research` directory.
Configure, deploy, and manage Senpi Trading Runtime (OpenClaw plugin @senpi-ai/runtime) for automated on-chain position tracking with DSL trailing stop-loss protection. Use when a user needs to create or modify runtime YAML files, configure DSL (Dynamic Stop-Loss) exit engine parameters (phases, tiers, time-based cuts), set up the position_tracker scanner to monitor a wallet's positions on Hyperliquid, install/list/delete runtimes via CLI, or inspect DSL-tracked positions. The runtime does NOT create strategy wallets; create/get the strategy wallet via Senpi MCP first, then link that existing wallet in runtime YAML. Triggers on mentions of senpi, Senpi runtime, DSL exit, stop-loss tiers, position tracker, trailing stop, openclaw senpi, dsl_preset, or strategy YAML configuration."
Use when managing AI Hub account, API keys, balance, usage, or API endpoints. Use when user says "AI Hub", "add AI credits", "create API key", "check AI usage", "auto-recharge", "AI Hub endpoint", "AI Hub base URL", "how to use AI Hub API", "LLM API", "AI API", "OpenAI compatible", "Anthropic API", "GPT", "Claude", "Gemini", "DeepSeek", or "Grok" in the context of Zeabur.
Quick pragmatic review of .NET test code for anti-patterns that undermine reliability and diagnostic value. Use when asked to review tests, find test problems, check test quality, or audit tests for common mistakes. Catches assertion gaps, flakiness indicators, over-mocking, naming issues, and structural problems with actionable fixes. Use for periodic test code reviews and PR feedback. For a deep formal audit based on academic test smell taxonomy, use exp-test-smell-detection instead. Works with MSTest, xUnit, NUnit, and TUnit.
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.