2,691 件 ・ 関連度順
概要と使いどころ
Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.
日本語の概要は準備中です。原文の説明を表示しています。
Development methodology rules (Clean Architecture, TDD flow, 3-Strike rule, decision priority) that govern planning, implementation, and review. Load before designing, staging, implementing, or reviewing code changes.
日本語の概要は準備中です。原文の説明を表示しています。
再発しやすい危険な実装パターンを、安全側に倒れる標準パターン・禁止事項・共通層・静的ルール候補へ 変換するスキル。ORM強制、deny-by-default認可、サービス経由I/O、永続化確認後の成功表示などを設計する。 レビューで危険コードを見つけるのではなく、危険コードを書きにくくする設計標準を作ることが目的。 Use when turning repeated defect patterns into safe architectural defaults, forbidden-to-safe mapping tables, common layer designs, and enforceable static analysis rules.
Drafts the instructions field of a declarative agent that orchestrates a set of custom skills, under a character cap (default 8,000), from the skills' names and descriptions: role and scope, one routing rule per skill, workflow order, gates written as workflow holds, global rules, output format and what the agent never does. Returns the text in a fenced block with its character count labelled counted or estimated, plus a skill inventory, routing table, gate table, rules trace and open questions for the owner. Use when the user asks to "write the instructions for my agent", "draft a system prompt that ties these skills together", "tighten these agent instructions to fit the cap", "how should the agent route between these skills" or "revise my agent's orchestration text". Do not use to review a single SKILL.md, use skill-file-reviewer instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Google TypeScript Style Guide reference for writing, reviewing, and refactoring TypeScript code. Use this skill whenever you are writing TypeScript code, reviewing TypeScript code, refactoring TypeScript, configuring ESLint or linter rules for TypeScript, or when the user asks about TypeScript coding conventions, naming conventions, type system best practices, or import/export patterns. Also trigger when the user mentions 'Google style', 'gts', 'TypeScript style guide', or asks 'how should I name this', 'should I use interface or type', 'how to handle null/undefined' in a TypeScript context. TypeScriptを書く・レビューする・リファクタリングする、ESLintの設定をする、「命名規則」「型の使い方」「import/exportのルール」「interfaceとtypeどっち」「anyを使っていい？」「nullチェックどうする」「Google式」「コーディング規約」「スタイルガイド」などの質問にも対応します。TypeScriptのコードに関する質問や作業であれば積極的にこのスキルを使ってください。
Protocol for two LLM agents (Claude, Codex or any other) to agree and work from one shared folder: message format, channels, roles, evidence rules, wake-up alarm and anti-patterns. Triggers: /llm-pact, agree with codex, connect a second agent, pair rules, agent consensus, two-agent protocol.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure an always-loaded rules file such as CLAUDE.md or MEMORY.md: build a top block of key rules plus numbered categories, move rule bodies verbatim with a script that proves zero byte loss, fold heavy mechanics into trigger-plus-pointer form, then guards, a canary window and fleet rollout. For scheduled maintenance, not ad-hoc trimming. Triggers: "/canon-revision", "revise the canon".
日本語の概要は準備中です。原文の説明を表示しています。
Rebuild the canon mirror for a second coding agent (AGENTS.md) after a rules-file version bump: show the changelog delta, write in only the new rules, then enforce the size cap, version stamp, structural anchors, a copy into the shared folder and the linter run. Triggers: "/codex-mirror", "update the codex mirror", "AGENTS.md is stale".
日本語の概要は準備中です。原文の説明を表示しています。
Load the operations codex that governs everyone acting as or for the owner (the owner, human assistants and AI agents) before outreach, replies in their chats, scheduling, purchases, hiring or household ops. Covers where the rules live in the vault, how to pull the right slice, and the rule that the newest entry wins per topic. Triggers: "/bible", "what do the rules say".
日本語の概要は準備中です。原文の説明を表示しています。
Single-mainline governance for deployless repositories. Use after a deployless audit when a repo needs trunk-based branch rules, branch protection, contribution guidance, review gates, merge queue policy, AI PR intake rules, or agent-ready mainline practices.
日本語の概要は準備中です。原文の説明を表示しています。
Agentic design-to-build pipeline that turns a Figma design into a built WordPress site using the Figma MCP server (read side) and the Elementor MCP server (write side) attached as MCP Apps on an NV oOS assistant. Covers the 7-stage pipeline (Scope → Read → Plan → Tokenize → Build → Verify → Handoff), the normative stage rules (get_design_context first, tokenize before build, drafts only, never publish, Figma read-only), the build-manifest contract (schema + example in reference/build-manifest.md), the design-file contract (frame/section/variable naming in reference/design-file-contract.md), assistant wiring (figma + elementor MCP Apps, OAuth + application passwords, host allowlist), safety rules, and troubleshooting. Use when asked to build or create a site, page, or landing page from a Figma design, to wire Figma MCP or Elementor MCP for design-to-build work, to approve or produce a build manifest, or to debug a failed design-to-build run.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "set up conversion values so tROAS optimizes profit not orders", "map margin onto my purchase value", "build value rules for lead / phone / signup conversions", or "stop bidding to revenue when I care about profit"; defines and QAs the conversion VALUE model — per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count sanity check — as a value-model spec plus a pre-launch value QA sheet. Not for whether the tag fires or UTMs are clean — use conversion-signal-qa; not for cross-platform double-count de-dup — use attribution-reconciler; not for scoring R1/R2 — that is a scored veto in ad-account-auditor. 付费广告转化价值建模/利润出价/价值规则QA
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel's voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry's voice-dossier; not for finished copy or blog posts — use content-writer; not for the message hierarchy itself — use message-system-architect; not for claim adjudication — use offer-claims-registry. 品牌语气/词汇表/命名税/禁用词/品牌语言规范
日本語の概要は準備中です。原文の説明を表示しています。
Detects over-permissive Firestore/Storage rules (allow read, write: if true / auth-only without ownership), missing auth checks on writes, and admin SDK private key exposure to client bundles.
日本語の概要は準備中です。原文の説明を表示しています。
スプリントレトロスペクティブを実行する。KPT整理→改善アクション→CLAUDE.md/rules/agentsへの自動フィードバックで組織を進化させる
Choose between standard mileage rate and actual expenses for business vehicle deductions. Covers the IRS mileage rate, method lock-in rules, mileage log requirements, commuting rules, luxury auto limits, and heavy vehicle exceptions. Trigger on "mileage deduction", "standard mileage rate", "vehicle expenses", "car deduction", "business miles", "mileage tracking".
日本語の概要は準備中です。原文の説明を表示しています。
Universal AI design correction rules — SUPERSEDED. The `impeccable` skill now provides 27 deterministic anti-pattern rules plus a 12-rule LLM critique pass, which are more comprehensive and runtime-enforced via the `impeccable` CLI. This file is kept for backward compatibility — the `impeccable` skill's design laws and anti-patterns take precedence.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and optimize repositories for AI coding agents. Creates minimal AGENTS.md, CLAUDE.md symlink, docs/REQUIREMENTS.md, docs/BUSINESS-RULES.md, feedback loops, and deterministic enforcement (Claude Code hooks, OpenCode plugins). Use when user wants to make a repo AI-friendly, set up AGENTS.md/CLAUDE.md, document requirements/business rules for AI, add pre-commit hooks for AI workflows, or optimize codebase structure for coding agents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Coralogix — coralogix observability platform for log analytics, metrics, tracing, security, and alerting. Covers log querying with DataPrime, metric exploration, alert management, parsing rules, and data usage insights. Use when searching Coralogix logs, investigating application errors, managing alert rules, or analyzing log ingestion patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Cursor — cursor AI-powered editor management and team analytics. Covers team seat management, usage tracking, model configuration, rules file analysis, project settings review, and workspace configuration. Use when managing Cursor team licenses, reviewing AI feature adoption, or analyzing Cursor workspace and rules configurations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Config Cat — configCat feature flag management, remote configuration, A/B testing, targeting rules, and percentage-based rollouts. Covers flag listing, targeting rule management, environment overrides, audit log review, and SDK integration status. Use when managing feature flags, reviewing targeting rules, analyzing flag usage, or auditing configuration changes in ConfigCat.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Bunny Cdn — bunny.net CDN management covering pull zones, storage zones, edge rules, cache configuration, and bandwidth analytics. Use when managing Bunny CDN pull zones, analyzing traffic patterns, configuring edge rules, monitoring cache hit ratios, or managing Bunny storage for origin content.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Azure Cdn — azure CDN management covering profiles, endpoints, custom domains, caching rules, origin groups, and performance analytics. Supports Microsoft, Verizon, and Akamai CDN providers within Azure. Use when managing Azure CDN endpoints, analyzing cache performance, configuring delivery rules, or troubleshooting content delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Config Deep — aWS Config deep rule and compliance management. Covers Config rules, conformance packs, aggregators, advanced queries, remediation actions, configuration history, and multi-account compliance dashboards. Use when auditing AWS resource compliance, managing Config rules, reviewing conformance pack results, or querying resource configurations across accounts.
日本語の概要は準備中です。原文の説明を表示しています。