Loading...
Loading...
Found 5,760 Skills
Build tool for Go projects. Use when the user wants to create, edit, or understand Way-specific Magefiles, build targets, or automate Go project tasks.
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
Interact with Microsoft Teams - send messages, read channels, manage reactions
Interact with Slack workspaces using bot tokens - send messages, read channels, manage reactions
Manage Obsidian vault for persistent knowledge storage, search, and retrieval
Slack Web APIを操作するスキル。メッセージの投稿・取得、スレッドの取得、投稿の検索、ユーザー情報の取得、自分宛てDM送信を実行。 使用タイミング: (1) Slackにメッセージを投稿したい (2) チャンネルのメッセージ履歴を取得したい (3) スレッドの返信を取得したい (4) 自分の投稿を検索したい (5) ユーザー情報を取得したい (6) 自分にDMを送りたい トリガーキーワード: Slack、メッセージ送信、スレッド取得、チャンネル履歴、ユーザー取得、DM送信
Design-to-code pipeline: extract copy from URLs, extract design tokens from images, then build React components or HTML preview variants. Use when: extracting content from websites, extracting design systems, generating frontend code, previewing design variants, sending to Figma via MCP. Triggers on "extract copy", "extract design", "build frontend", "generate variants", "export design", "send to Figma".
Comprehensive toolkit for generating best practice Helm charts and resources following current standards and conventions. Use this skill when creating new Helm charts, implementing Helm templates, or building Helm projects from scratch.
Sns Topic Config - Auto-activating skill for AWS Skills. Triggers on: sns topic config, sns topic config Part of the AWS Skills skill category.
Configure perform API fuzzing to discover edge cases, crashes, and security vulnerabilities. Use when performing specialized testing. Trigger with phrases like "fuzz the API", "run fuzzing tests", or "discover edge cases".
Execute chaos engineering experiments to test system resilience. Use when performing specialized testing. Trigger with phrases like "run chaos tests", "test resilience", or "inject failures".
Post-pipeline retrospective — parse logs, score process quality, find waste patterns, suggest skill/script patches. Use after pipeline completes or when user says "retro", "evaluate pipeline", "what went wrong", "pipeline review", "check pipeline logs".