calendly-api
Calendly scheduling automation using REST API v2 for managing event types, availability, bookings, webhooks, and scheduling workflows
requirements-triage
複数の要件や要望を体系的に分析・評価し、実装する項目を決定するスキル。 MoSCoW分類、優先度スコアリング、影響分析を提供する。 プロジェクト初期段階での要件整理から、開発中の追加要望への対応まで幅広く活用できる。 Anchors: • Software Requirements (Karl Wiegers) / 適用: 要件優先順位付け / 目的: リソース最適配分 • Lean Analytics (Alistair Croll) / 適用: ビジネス価値評価 / 目的: 戦略的決定支援 • Prioritization Frameworks / 適用: MoSCoW, RICE, Kano / 目的: 体系的な優先順位決定 Trigger: Use when triaging multiple requirements, prioritizing features, defining scope, or making resource allocation decisions. requirements triage, priority scoring, MoSCoW classification, scope management, feature prioritization, 要件トリアージ, 優先順位付け
ghe-checkpoint
POST a progress checkpoint to the CURRENTLY ACTIVE thread. Saves work state without changing phases. Requires an already-claimed in-progress thread. USE THIS SKILL WHEN: - User says "post a checkpoint" or "save my progress" - User says "update the issue" or "record current state" - User says "checkpoint" or "save checkpoint" - User completed a milestone and wants to record it - User encountered a blocker and wants to document it - User is about to take a break and wants to save state - Meaningful state change occurred during work PRECONDITION: User must already have an active (claimed, in-progress) thread. DO NOT USE THIS SKILL WHEN: - User wants to SEE status (use ghe-status) - User wants to START work on new issue (use ghe-claim) - User wants to FINISH current phase and MOVE to next (use ghe-transition) - User wants reports (use ghe-report) - No active thread exists (must claim first) EXAMPLES: <example> Context: User working on DEV wants to save progress user: "Post a checkpoint" assistant: "I'll use g
output-formatting
様々な形式での出力フォーマッティングスキル。Markdown、JSON、YAML、表形式など、 構造化された見やすい出力を作成します。 Anchors: • The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: コード品質と可読性 / 目的: 読みやすく保守可能な出力設計 • Technical Writing (Google Developer Documentation Style Guide) / 適用: ドキュメント構造 / 目的: 明確で一貫性のある技術文書フォーマット Trigger: Use when formatting output, creating structured documents, generating tables, or converting between formats. output format, markdown, json, yaml, table, document structure, formatting, presentation
freecad-automation
AI-powered automation agent for FreeCAD CAD operations including natural language processing, batch processing, parametric design, and marine engineering applications. Use for CAD automation, drawing generation, FEM preprocessing, and integration with offshore analysis tools.
task-decomposition
複雑なタスクを目的・成果・制約から分解し、実行可能な作業単位に落とし込むスキル。 依存関係、優先順位、検証条件まで整理して、実行計画を一貫した形で提示する。 Anchors: • PMBOK Guide / 適用: WBS作成 / 目的: 分解粒度と成果物の整合 • User Story Mapping (Jeff Patton) / 適用: 価値分解 / 目的: 価値順序の可視化 • The Pragmatic Programmer / 適用: 反復計画 / 目的: 実行可能性の担保 Trigger: Use when breaking down complex work, clarifying ambiguous tasks, or planning phased execution. task decomposition, work breakdown, WBS, dependency mapping, phased planning
development-loop
Complete development lifecycle: brainstorm → TDD planning → ralph implementation → review → feedback loop until approved
command-placement-priority
コマンドの配置場所と優先順位（プロジェクト/ユーザー/MCP、名前空間、競合解決）を整理し、配置判断と移行方針を支援するスキル。 配置基準、優先順位ルール、移行フローを一貫して整理する。 Anchors: • The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 配置判断の実務 / 目的: 運用の一貫性確保 • Priority Resolution Protocol / 適用: 同名競合の解決 / 目的: 優先順位の明確化 Trigger: Use when determining command placement, resolving command priority conflicts, or migrating commands between project/user/MCP layers. command placement, priority resolution, namespace design, project vs user commands, MCP integration
notification-integration-gha
GitHub Actions通知統合スキル。Slack、Discord、MS Teams、Emailへの ビルド/デプロイ状態通知を自動化。成功/失敗メッセージのカスタマイズと インタラクティブ要素をサポート。 Anchors: • The Pragmatic Programmer (Hunt and Thomas) / 適用: 自動化とフィードバックループ / 目的: 迅速なフィードバックによる問題早期発見 • Site Reliability Engineering (Google) / 適用: モニタリングとアラート設計 / 目的: 適切な粒度と重要度の通知 • GitHub Actions best practices / 適用: ワークフロー設計とシークレット管理 / 目的: セキュアで保守性の高い設定 Trigger: Use when setting up notifications, configuring webhooks, adding Slack/Discord/Teams/Email alerts to workflows, troubleshooting notification failures, or implementing status reporting. slack notification, discord webhook, teams alert, github actions notify, workflow status, deployment notification
troubleshooting-guides
問題解決を効率化するトラブルシューティングガイドの設計スキル。 診断フロー、問題分類、解決手順書を体系的に設計します。 Anchors: • 『Don't Make Me Think』（Steve Krug）/ 適用: ユーザビリティ設計 / 目的: 問題自己解決力向上 • SRE原則 / 適用: 障害対応 / 目的: トラブル診断効率化 Trigger: トラブルシューティングガイド作成時、問題診断フロー設計時、エラー説明書作成時に使用
sentry-setup-ai-monitoring
Setup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically detects installed AI SDKs and configures the appropriate Sentry integration.
mermaid-diagram-to-image
Convert Mermaid diagrams to images (PNG, SVG, PDF) using mermaid-cli. This skill should be used when Claude generates Mermaid diagram syntax and wants to create a visual representation for the user, or when converting existing Mermaid diagrams to image formats.
context-window-optimization
コンテキストウィンドウの制約内で情報を最適整理するためのスキル。 トークン計測、優先順位付け、圧縮、検証の一連フローを提供する。 Anchors: • High Performance Browser Networking / 適用: 計測とレイテンシ意識 / 目的: 予算内最適化 • Designing Data-Intensive Applications / 適用: リソース制約下の設計 / 目的: 効率的な構造化 • Progressive Disclosure パターン / 適用: 段階的情報開示 / 目的: 過剰読み込みの回避 Trigger: Use when optimizing context window usage, measuring token budgets, prioritizing context elements, or applying compression techniques. context window optimization, token budget, context prioritization, compression, summarization
backlog-management
プロダクトバックログの作成・整理・優先順位付けを行うためのスキル。 ユーザーストーリー作成、DEEP原則の適用、健全性分析を通じて実装可能な状態を維持します。 Anchors: • Agile Estimating and Planning / 適用: 見積もりと優先度 / 目的: 計画精度の向上 • User Stories Applied / 適用: ストーリー作成 / 目的: 要件の明確化 • The Product Owner's Handbook / 適用: バックログ運用 / 目的: 価値最大化 Trigger: Use when managing product backlogs, refining user stories, prioritizing items, or assessing backlog health.
docs-creating-accessible-diagrams
WCAG-compliant Mermaid diagrams using verified accessible color palette. Use when creating diagrams, flowcharts, or any color-dependent visualizations requiring accessibility compliance for color blindness.
interviewing-plans
Use when a plan, PRD, or spec has vague requirements, undefined terms, or missing details - conducts structured interview using AskUserQuestion to surface hidden assumptions, challenge ambiguities, and produce implementation-ready specs. Also use proactively when encountering plans that say things like "make it faster" or "improve UX" without concrete definitions.
feature-prioritization-framework
RICE scoring framework for ruthless feature prioritization. Evaluates features against strategic objectives, customer value, and resource constraints. Produces prioritized product roadmap with clear rationale for what to build first, defer, or kill.
mindm-mindmap
High-level MindManager mindmap operations via the mindm-mindmap CLI or python -m mindmap.actions. Use when a map must be read (mindmap, selection, grounding info), serialized to Mermaid, or created from Mermaid.
meeting-prep
Prepare comprehensive briefings for upcoming meetings
