621 件 ・ 関連度順
概要と使いどころ
Run the NowStack Mobile setup checker as a strict read-only contract. Use for `/ns check`, configuration readiness, external account status, production preflight, or machine-readable setup evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a read-only NowStack Mobile launch audit across product, web, iOS, Android, backend, auth, payments, email, storage, analytics, stores, and operations. Returns an evidence-backed GO or NO-GO verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing Quarkus + LangChain4j project against this stack's agentic conventions — a read-only conformance or gap-analysis review. Use when the user asks to audit, review, check, assess, or validate a Quarkus project against the LangChain4j agentic conventions, or wants to know whether an existing project conforms to (or is ready to adopt) this stack. User-invoked only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to hunt in the organisation's own Microsoft Sentinel workspace — sweep the logs for IOC hits (IP, domain, hash, URL, account), hunt behavioural TTPs from MITRE ATT&CK techniques, run KQL against live data, or check which tables the workspace actually ingests. Discovers available tables first and only generates KQL for tables that verifiably exist, so hunts adapt to each environment's connectors. Commonly chained by the /*-investigation skills to answer "were we exposed?". Reads $SENTINEL_TENANT_ID, $SENTINEL_CLIENT_ID, $SENTINEL_CLIENT_SECRET, $SENTINEL_WORKSPACE_ID. Read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a Research Pilot project needs read-only gap detection or Evidence Need extraction from the Project Understanding Graph.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a Research Pilot project needs a read-only recommendation for the next workflow action.
日本語の概要は準備中です。原文の説明を表示しています。
Super Base Context — project doc loader & synchronizer. Triggers even without explicit "load docs"/"sync docs." READ MODE — load architecture/modules/coding/decision docs when work references project state: code work (write/modify/remove); design (features/APIs/schemas/architecture); review (modules, past solutions); tech selection; ADR research; migration/refactor planning; performance/security analysis; tests; code reviews; any spec/plan/design/ADR referencing project. WRITE MODE — NET DELTA vs. last doc sync: additions/modifications/REMOVALS/deprecations of previously-synced code or decisions (docs revert: delete BCU file/ADR), AND rollbacks. User signals: sync docs/done/ready to commit/pre-commit/record decision. Auto-fires before final task-completion reply. WRITE MODE does NOT fire on: brainstorming, generic/read-only Q&A, in-session try-and-undo with no net change, already-synced.
日本語の概要は準備中です。原文の説明を表示しています。
Linux security mechanism bypass playbook. Use when facing restricted bash/rbash, read-only or noexec filesystems, AppArmor, SELinux, seccomp filters, or audit logging that must be evaded during post-exploitation.
日本語の概要は準備中です。原文の説明を表示しています。
Use for a whole-corpus, read-only audit of tracked stablecoin static metadata and domain sidecars, especially after catalog changes or when factual or internal-consistency drift needs review.
日本語の概要は準備中です。原文の説明を表示しています。
Run bounded, read-only semantic advisory sidecar passes for candidate mapping, issue triage, upstream diffs, evidence verification triage, and meta audit hints. Enforces monthly spend limits with explicit fallback to worker-luna.
日本語の概要は準備中です。原文の説明を表示しています。
Review a Gaia curation PR or branch as a read-only merge gate. Use for canonical registry promotion, schema, evidence, prerequisite, nomenclature, installability, and generated-artifact checks. Route intake batches to /gaia-draft-curate and unrelated PRs to /review.
日本語の概要は準備中です。原文の説明を表示しています。
Triage and classify pending Gaia skill intake batches in registry-for-review/. Use for gaia push intake proposals, draft skill batches, and deciding whether proposals should proceed to canonical curation. This skill is read-only and never promotes skills itself.
日本語の概要は準備中です。原文の説明を表示しています。
Run any installed skill on several models at once — you, OpenAI Codex, OpenCode and whoever else the profile names — and show what each one made of it side by side. Every model gets the same prepared copy of the skill and works read-only. Use for "/multi:skill <name>", "run this skill on every model", "run <skill> through multi", or any skill whose answer you want from more than one model.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to query Volcengine CloudTrail audit logs, investigate login or resource operations, or manage CloudTrail trails and backfill delivery tasks. Trigger on 操作审计, 审计日志, CloudTrail, cloud_trail, trail, 跟踪, 历史补投, or backfill in a Volcengine context. Audit queries are read-only; trail and backfill mutations require an explicit preview and confirmation.
日本語の概要は準備中です。原文の説明を表示しています。
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
日本語の概要は準備中です。原文の説明を表示しています。
Deep code review driven by a short interview. Read-only reader agents analyze the chosen scope per angle, the lead verifies every finding, and each point is routed to the skill that fixes it. Never edits the code.
日本語の概要は準備中です。原文の説明を表示しています。
Check Anthropic API access and list available Claude models. Read-only. Trigger phrases: anthropic, claude models, anthropic api.
日本語の概要は準備中です。原文の説明を表示しています。
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.
日本語の概要は準備中です。原文の説明を表示しています。
Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason broadly or repair files.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only 跨平台 code／architecture／repo／release／Skill 審計器。用於清理前盤點、重複／依賴／分層／長責任、sync、release／資安、生成資產、Skill Token、GitHub 自動更新與舊版淘汰稽核；也是 R&D 的 measurement provider。
日本語の概要は準備中です。原文の説明を表示しています。
Read-only repository explorer. Use PROACTIVELY for cold-start exploration, broad cross-file localization, or when a direct search has failed and you need to find where something lives. Skip it when the issue already names the exact file or symbol, or a previous turn already returned usable file:line evidence. Returns only compact path:line citations; its reads and greps never enter the main conversation.
日本語の概要は準備中です。原文の説明を表示しています。
Review Caveman Cloud evidence read-only: costs, Cave Score, Cave Plan, workflows, traces, latency, errors, compression, routing, and verified savings. Use when the user asks what Caveman found, where LLM spend goes, why cost or quality changed, which workflows need attention, or asks for a trace or analytics review. Prefer Caveman MCP tools; fall back to CLI JSON.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, reviewing, or troubleshooting Salesforce formula fields. Triggers: 'formula field', 'cross-object formula', 'null handling', 'compile size', 'HYPERLINK', 'IMAGE', 'why is formula slow', 'formulaTreatBlanksAs', 'BlankAsZero', 'blank field handling', 'field-meta.xml formula', 'CustomField formula deploy', 'formula returns blank', 'formula field read-only on data load'. NOT for a formula field slowing a SOQL query or blocking an index — use apex/formula-field-performance-and-limits. NOT for Formula resources inside a Flow — use flow/flow-formula-and-expression-patterns.
日本語の概要は準備中です。原文の説明を表示しています。