This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing...
日本語の概要は準備中です。原文の説明を表示しています。
6,451 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing...
日本語の概要は準備中です。原文の説明を表示しています。
Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate FriendlyBet company-level strategy, CEO handoff, department orchestration, HR/agent-quality escalation, operating-model decisions, multi-agent synthesis, roadmap tradeoffs, decision rights, quality gates, and updates to the virtual company system. Use when Eyal asks to involve the company, CEO, leadership, strategy, operations, several departments, or named executive agents such as Strategy Director, Chief of Staff, or Operating System Lead.
日本語の概要は準備中です。原文の説明を表示しています。
Act as FriendlyBet's CEO and primary front door for every FriendlyBet request through automatic company preflight. Own end-to-end routing, planning, execution coordination, department orchestration, decision-rights enforcement, quality gates, board-style reporting, and escalation only for strategic, legal, brand, cost, risk, or taste decisions. Use by default in FriendlyBet threads, with full department planning for broad, ambiguous, strategic, cross-functional, or outcome-driven requests such as SEO, new features, multi-sport expansion, product direction, release execution, company operations, or agent coordination.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate operational workspace setup before implementation slices across scaffold, CI/CD, hosting, and data provisioning shards
日本語の概要は準備中です。原文の説明を表示しています。
Scan downstream specs for contradictions with locked decisions and apply approved fixes with consistency checks
日本語の概要は準備中です。原文の説明を表示しています。
Safely evolve shared contracts with consumer discovery, migration tests, versioning checks, and downstream spec cascade validation
日本語の概要は準備中です。原文の説明を表示しています。
Introduce genuinely new scope into the pipeline by classifying change type and cascading updates through downstream layers
日本語の概要は準備中です。原文の説明を表示しています。
Define security, attack surface, integration, and observability architecture with compliance escalation
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
日本語の概要は準備中です。原文の説明を表示しています。
Capture and classify new scope, write entry-point updates, and determine downstream cascade scope
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a new Gradle module in any Kotlin Android project. Walks the user through choosing one of three module types — library module (`com.android.library`), feature module (regular Android library that hosts a feature/UI, install-time only), or dynamic feature module (`com.android.dynamic-feature`, on-demand/conditional/instant delivery). Use whenever the user wants to add a module, modularize code, extract a util/data/ui layer, create a new feature, set up Play Feature Delivery, or asks "should this be a library or feature module?". Discovers the project's existing conventions (plugin aliases, namespaces, sibling modules, version catalog) instead of hardcoding any. Pushes back on bad combos (e.g. utility code in a dynamic feature). Stops at scaffolding; app-level wiring is out of scope.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。
Type-safe URL query state management with nuqs 2.x. Use when writing or reviewing code that uses useQueryState, useQueryStates, URL search params, query parameters, nuqs parsers, createLoader, createSearchParamsCache, createSerializer, or URL state in Next.js, React, Remix, React Router, or TanStack Router.
日本語の概要は準備中です。原文の説明を表示しています。
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
日本語の概要は準備中です。原文の説明を表示しています。
Bu Flutter template'inde uctan uca yeni feature iskelesi kurar — lib/feature/<ad>/ klasor yapisi, Freezed state + Cubit, StatelessWidget ya da StatefulWidget+ViewModel view, BlocProvider yerlesimi (global state_initialize mi lokal mi), TypedGoRoute, LocaleKeys cevirileri, AppPaddings/textTheme/colorScheme token'lari ve zorunlu <feature>.md modul dokumani. Kullanici "yeni feature ekleyelim", "su sayfayi projeye gore yaz", "cubit + state + view kur", "feature iskeleti cikar", "scaffold a feature" dediginde kullan.
日本語の概要は準備中です。原文の説明を表示しています。
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
日本語の概要は準備中です。原文の説明を表示しています。
Scans HOT.md and proposes which rules should graduate to SOUL.md (untouched 30+ days) or be removed entirely. Run weekly via cron, or invoke ad-hoc when HOT.md feels stale. Triggers: "clean up HOT", "graduate rules", "is HOT.md stale", "what HOT rules can I drop".
日本語の概要は準備中です。原文の説明を表示しています。
Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge graph and smart memory management using graphify + Obsidian-inspired patterns. Use when: setting up a knowledge graph, managing memory health, cross-linking notes, compiling wiki pages from scattered notes, adding structured frontmatter, or running memory health checks. Triggers on: 'knowledge graph', 'graphify', 'wiki', 'cross-link', 'memory health', 'frontmatter', 'compile notes', 'wikilinks'.
日本語の概要は準備中です。原文の説明を表示しています。
Configures autonomous heartbeat and cron-based proactive routines (e.g., morning briefing setup, unanswered-message scan cadence). Invoke when user is SETTING UP or MODIFYING a proactive routine, not when the routine itself fires. Cron crons execute their own logic — they do NOT load this skill. Triggers: "set up proactive check", "configure heartbeat", "add morning briefing", "tune cron cadence".
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Chronosphere — chronosphere cloud-native observability platform for metrics, tracing, and alerting at scale. Covers PromQL-based metric queries, trace analysis, monitor management, dashboards, and control plane configuration. Use when querying Chronosphere metrics, investigating service performance, managing alerting rules, or analyzing distributed traces.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Fargate — aWS Fargate task and service analysis covering ECS cluster inventory, Fargate task status, CPU and memory utilization, task definition review, networking configuration, service auto-scaling policies, and container health checks. Use for Fargate-specific workload optimization.
日本語の概要は準備中です。原文の説明を表示しています。