AGENT SKILLS · ミッション装備
実際に使われている Agent Skills
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 22,440
- リポジトリ
- 3446
- 最終同期
- 2026/10/28
catalystbyzohocatalyst-datastore
Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Requires MCP connection — check for CatalystbyZoho tools before any operation. Trigger on 'Data Store', 'ZCQL', 'create table', 'executeZCQLQuery', 'table permissions', 'ROWID', 'boolean column', 'boolean always true', 'truthy string', 'boolean stored as string', or 'DataStore data types'. You MUST load this skill whenever writing code that reads or writes Data Store data — ZCQL
- 1時間の導入数
- 1
- GitHub Stars
- 69
- 更新日
- 10月8日
catalystbyzohocatalyst-functions
Catalyst serverless functions — all 7 types (Basic I/O, Advanced I/O, Event, Cron, Job, Integration, Browser Logic), handler signatures, catalyst-config.json, Security Rules, API Gateway routing, file uploads, busboy, Express middleware, environment variables, function URL, and function testing. Requires MCP connection — check for CatalystbyZoho tools before any operation. Trigger on 'write a function', 'catalyst function', 'API Gateway', 'Security Rules', 'function not found', 'function returns
- 1時間の導入数
- 1
- GitHub Stars
- 69
- 更新日
- 10月8日
catalystbyzohocatalyst-zoho-mcp
Catalyst Zoho MCP — manage Catalyst infrastructure (tables, buckets, cache) via CatalystbyZoho MCP tools using natural language. Trigger on 'Zoho MCP', 'MCP tools', 'catalyst MCP', 'CatalystbyZoho', 'create table with AI', 'MCP setup', 'MCP config', 'global MCP server', 'infrastructure as conversation', 'MCP first', 'avoid Catalyst console', or 'use MCP instead of console'.
- 1時間の導入数
- 1
- GitHub Stars
- 69
- 更新日
- 10月8日
orcasecurityorca-cloud-cost-optimizer
Cloud cost optimization analysis using Orca Security asset data. Discovers all cloud assets (AWS, GCP, Azure) through Orca MCP tools, compares current configurations against cheaper alternatives using live public pricing, and produces a prioritized cost reduction report with exact asset evidence. Use when the user asks about cloud cost optimization, reducing cloud spend, rightsizing instances, saving money on cloud infrastructure, cost reduction opportunities, unused resources, oversized VMs, re
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-compliance-gap
Deep-dive compliance gap analysis for any framework — failing controls ranked by impact, quick wins, account breakdown, and remediation plan. Use when user asks about compliance gaps, failures, or status (e.g., "compliance gaps", "PCI DSS status", "where are we failing", "SOC 2 compliance", "quick wins").
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-config-origin
Traces any Orca alert back to who deployed it, what tool was used, what introduced the issue, and a full timeline of events. Use when user asks about origin, deployment, or ownership of an alert (e.g., "who created this", "where did this come from", "trace back orca-3380725", "who deployed", "what tool was used").
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-cve-blast-radius
CVE blast-radius analysis — given a single CVE-ID, find every affected asset across all accounts, rank by real exposure (internet-facing, attack-path participant, crown jewel) instead of static CVSS. Use when user asks about a specific CVE's environmental impact (e.g., "blast radius of CVE-2024-1234", "where are we affected by Log4Shell", "which assets have CVE-2021-44228", "who is exposed to CVE-XXXX").
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-impact-analysis
Analyzes the full impact of fixing an Orca alert — what closes, what breaks, and what the environment looks like after the fix. Use when user asks about impact, consequences, or blast radius of fixing an alert (e.g., "what's the impact of fixing orca-3380725", "if I fix this what breaks", "what else closes").
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-inactive-identities-cleanup
Inactive-identity cleanup - finds inactive identities (users, groups, and non-human identities) across an account, business unit, or tag in every cloud provider Orca supports (AWS, Azure incl. Entra ID, GCP incl. Google Workspace, Alibaba Cloud, OCI, Tencent Cloud), ranks them by identity risk score (highest risk first), and drives remediation through a non-destructive path (disable) or a destructive path (delete) that always requires explicit confirmation. Asks for the inactivity time frame (e.
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-k8s-connector-troubleshoot
Diagnoses Kubernetes Connector (K8s Tunnel Client / Helm chart orca-tunnel) install and connectivity failures from raw customer input — error text, helm status, kubectl describe, or pod logs — and walks through step-by-step remediation. Use when a user reports the K8s Connector won't install, won't connect, keeps disconnecting, or the cluster shows connected but no scan data appears.
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-mfa-enforcement
Finds users who can sign in without MFA across an account, business unit, or tag, ranks them by identity risk, and drives guided enrollment or gated enforcement. Use for MFA or 2FA gaps, root-account MFA, and MFA coverage evidence for an audit.
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
orcasecurityorca-morning-briefing
Daily security briefing summarizing new critical alerts, attack paths, compliance drift, exposure changes, and aging unactioned alerts from the last 24-72 hours. Use when user asks for a briefing, summary, or overview (e.g., "morning briefing", "what happened", "security summary", "daily report", "what needs attention").
- 1時間の導入数
- 1
- GitHub Stars
- 55
- 更新日
- 10月15日
spritecook-build-ui-kits
Create or refine game UI kits with SpriteCook's concept, component-sheet, extraction, and finalization tools. Use for a requested screen or matching set of reusable controls, including work from an existing SpriteCook concept. Pair with spritecook-workflow-essentials.
- 1時間の導入数
- 1
- GitHub Stars
- 45
- 更新日
- 10月15日
spritecook-generate-sprites
Still-image generation guide for SpriteCook. Use with spritecook-workflow-essentials when generating pixel art or detailed/HD assets, choosing models, and keeping style consistency with reference assets.
- 1時間の導入数
- 1
- GitHub Stars
- 45
- 更新日
- 10月15日
spritecook-upload-assets
Import an image the user selected for SpriteCook into their asset library through the MCP upload tools, for references, editing, animation, or reuse. Use when the requested SpriteCook workflow needs that image uploaded.
- 1時間の導入数
- 1
- GitHub Stars
- 45
- 更新日
- 10月15日
spritecook-use-assets-in-godot
Godot workflow for SpriteCook assets. Use when the user wants to turn SpriteCook spritesheet PNGs, animation assets, or character animation runs into Godot SpriteFrames resources and AnimatedSprite2D/AnimatedSprite3D animation nodes. Covers both manual spritesheet-to-Godot setup and the optional SpriteCook MCP Godot export endpoint.
- 1時間の導入数
- 1
- GitHub Stars
- 45
- 更新日
- 10月15日
spritecook-use-dual-grid-tilesets
Implementation guide for using SpriteCook top-down 15-piece tilesets with a dual-grid autotile renderer. Use when explaining or coding how to map a 4x4 15-piece tileset image into terrain using SpriteCook's dual-grid mask system.
- 1時間の導入数
- 1
- GitHub Stars
- 45
- 更新日
- 10月15日
spritecook-workflow-essentials
Shared workflow rules for SpriteCook. Use together with SpriteCook generation, UI-kit building, animation, import, background-removal, and asset-organization workflows for credits, downloads, asset manifests, safe auth handling, and recommended defaults.
- 1時間の導入数
- 1
- GitHub Stars
- 45
- 更新日
- 10月15日
qwencloudqwencloud-model-selector
Recommend the best Qwen model and parameters. TRIGGER when: choosing between Qwen models, comparing Qwen model pricing, understanding Qwen model capabilities, asking which models are available on Token Plan, viewing cost history, when an execution skill needs model selection advice, or user explicitly invokes this skill by name (e.g. use qwencloud-model-selector). DO NOT TRIGGER when: non-Qwen model discussions (OpenAI, Gemini, etc.), general AI questions unrelated to Qwen.
- 1時間の導入数
- 1
- GitHub Stars
- 44
- 更新日
- 9月21日
qwencloudqwencloud-payment
Manage payment methods, bind card, spending limit. TRIGGER when: user asks about payment methods, bind card, spending limit, payment status. DO NOT TRIGGER when: billing history, usage queries, subscription status (use qwencloud-usage), support tickets.
- 1時間の導入数
- 1
- GitHub Stars
- 44
- 更新日
- 9月21日
qwencloudqwencloud-text
Generate text, have conversations, write code, reason, and call functions with Qwen models and third-party models available on QwenCloud. TRIGGER when: user asks to chat with Qwen, generate text, write code with Qwen, use Qwen function calling, call third-party models (deepseek, kimi, glm, etc.) via QwenCloud, or explicitly invokes this skill by name (e.g. use qwencloud-text). DO NOT TRIGGER when: using non-QwenCloud platforms (direct OpenAI API, Google Gemini API, etc.), general coding question
- 1時間の導入数
- 1
- GitHub Stars
- 44
- 更新日
- 9月21日
qwencloudqwencloud-vision
Understand images and videos with Qwen vision models. TRIGGER when: user wants to analyze, describe, or extract information from images or videos, OCR text extraction, chart/table reading, visual reasoning, multi-image comparison, screenshot understanding, video comprehension, or explicitly invokes this skill by name (e.g. use qwencloud-vision). DO NOT TRIGGER when: user wants to generate/create images (use qwencloud-image-generation), generate videos (use qwencloud-video-generation), text-only
- 1時間の導入数
- 1
- GitHub Stars
- 44
- 更新日
- 9月21日
looker-open-sourcecreating-looker-dashboard
Looker Developer Onboarding: Step 7 (Final Step). Creates a LookML dashboard in the project, imports it as a user-defined dashboard (UDD) in Looker, and iteratively refines it based on user feedback by syncing changes. Only execute this after Step 6 (Model Setup using creating-lookml-model).
- 1時間の導入数
- 1
- GitHub Stars
- 40
- 更新日
- 10月15日
looker-open-sourceexploring-data-for-looker
Looker Developer Onboarding: Step 1. Guides the agent to explore BigQuery data and define the onboarding goal. This is the first active step, to be executed immediately after reading the parent orchestrator looker-developer-onboarding.
- 1時間の導入数
- 1
- GitHub Stars
- 40
- 更新日
- 10月15日