「entry」の検索結果

Get a specific vector entry by key. Requires authentication. Use for Agentuity cloud platform operations

日本語の概要は準備中です。原文の説明を表示しています。

Create or update root and nested AGENTS.md files that document scoped conventions, monorepo module maps, cross-domain workflows, and (optionally) per-module feature maps (feature -> paths, entrypoints, tests, docs). Use when the user asks for AGENTS.md, nested agent instructions, or a module/feature map.

日本語の概要は準備中です。原文の説明を表示しています。

Read-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this one is pure reference.

日本語の概要は準備中です。原文の説明を表示しています。

The branded entry point to ServiceGraph — use whenever the user explicitly names **ServiceGraph** — "use ServiceGraph to…", "what datasets does ServiceGraph have", "search ServiceGraph for…", "look this up in ServiceGraph", "pull contacts from ServiceGraph for these domains", "how many credits do I have on ServiceGraph". ServiceGraph is a multi-dataset platform of metrics-enriched business data for founders — where to launch, who to email, who to hire. This skill explains how to drive the API (api.servicegraph.co / mcp.servicegraph.co) against ANY dataset — discover what datasets exist, discover a dataset's schema and filters, search free brief rows, and unlock contact + metric detail with credits. Dataset-agnostic by design — it discovers everything through the API and never assumes which datasets or fields exist. When the user describes an intent WITHOUT naming ServiceGraph (e.g. "find a PR agency in NY"), defer to the matching specific skill (find-pr-agency, find-marketing-agency, find-law-firm, …); this skill is for explicit ServiceGraph requests and for datasets no specific skill covers yet. Skip non-US firms, consumer/personal services, and individual freelancers.

日本語の概要は準備中です。原文の説明を表示しています。

Automatic init the first time Claude acts in an incident or alerts channel — one named like #inc-…, #incident-…, #sev0-…/#sev1-…, or whose recent messages are pages or alerts from PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or relayed by people (talk about being paged is not an alert) — that isn't already a team's oncall / monitoring channel. Run once per channel, on first contact (just invited, first @-mention, channel just created), before doing what was asked: load the oncall memory oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / code tools Claude can reach and which are missing, post one short zero-context message, note findings in this channel's memory, then hand off to `incident-investigate` if something was asked — or immediately, unasked, when the channel was plainly opened for a live outage. Works with no oncall memory (offers setup once). Also on "load the oncall setup here" / "init this incident".

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill for ANY financial market, investment, or macro-economic analysis. ALWAYS trigger this skill — do not skip it — when the user asks about: BTC, bitcoin, crypto, gold, silver, oil, stocks, forex, bonds, interest rates, Fed policy, inflation, deflation, stagflation, market structure, trading setups, portfolio allocation, asset allocation, investment strategy, price analysis, market outlook, geopolitics affecting markets, or any question involving "should I buy/sell/hold [any asset]", "what will [asset] do", or "analyze [market/asset]". Apply Genesis Protocol (First Principle + System Thinking) combined with SMC Layer analysis to produce structured insights with explicit scenarios, entry/exit zones, and uncertainty. For non-market strategic thinking, use genesis-mind-strategic-intelligence instead.

日本語の概要は準備中です。原文の説明を表示しています。

Conventions and APIs for the offload-project/laravel-waitlist package — multiple waitlists, entry status tracking, optional email verification, lifecycle events, mailing list sync (Mailchimp/Kit/Audienceful), and bridge into laravel-invite-only.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill for ANY financial market, investment, or macro-economic analysis. ALWAYS trigger this skill — do not skip it — when the user asks about: BTC, bitcoin, crypto, gold, silver, oil, stocks, forex, bonds, interest rates, Fed policy, inflation, deflation, stagflation, market structure, trading setups, portfolio allocation, asset allocation, investment strategy, price analysis, market outlook, geopolitics affecting markets, or any question involving "should I buy/sell/hold [any asset]", "what will [asset] do", or "analyze [market/asset]". Apply Genesis Protocol (First Principle + System Thinking) combined with SMC Layer analysis to produce structured insights with explicit scenarios, entry/exit zones, and uncertainty. For non-market strategic thinking, use genesis-mind-strategic-intelligence instead.

日本語の概要は準備中です。原文の説明を表示しています。

Default entrypoint and master ctf-sandbox-orchestrator workflow for CTF, exploit, reverse engineering, DFIR, pwnable, crypto, stego, mobile, AI-agent, cloud, container, Active Directory, Windows-host, and identity challenges. Use first when the user presents challenge infrastructure, binaries, prompts, hosts, or identities that should be treated as sandbox-internal by default and Codex needs to choose, route, and load the right downstream analysis path with concise evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

日本語の概要は準備中です。原文の説明を表示しています。

实现日志 / 指标 / 追踪三大支柱时使用。覆盖 OpenTelemetry / Prometheus / Grafana / Jaeger / Datadog / Sentry 集成。融合 Google SRE 三支柱 + 结构化日志 + Trace Context 传播。

日本語の概要は準備中です。原文の説明を表示しています。

Generate a self-contained HTML changelog report showing recent documentation changes with interactive course generation buttons. Use this skill when the user asks for a docs changelog, documentation report, what changed recently, recent doc updates as a report, or runs `/docs --report`. Discovers changes via git history, categorizes them, summarizes what's new, and produces a stunning Obsidian & Amber themed HTML report where each entry has a "Create Course" button that copies the course command to clipboard.

日本語の概要は準備中です。原文の説明を表示しています。

Trace Odoo execution flow from an entry point through controllers, button actions, cron jobs, model methods, overrides, computes, onchanges, constraints, database operations, security checks, and side effects. Use before implementation, during debugging, impact analysis, performance review, or code review when behavior depends on Odoo call chains.

日本語の概要は準備中です。原文の説明を表示しています。

Use when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's commits follow (or mostly follow) Conventional Commits and a mechanically-accurate section breakdown beats a model's reading of the diff.

日本語の概要は準備中です。原文の説明を表示しています。

CRISP session manager — detects project state and routes to the right entry point. Use /crisp to start or resume any CRISP engagement. Handles new projects (discovery), existing codebases (archaeology), active sprints (execute), and validation (prove). Reads docs/crisp-state.json to know where you are.

日本語の概要は準備中です。原文の説明を表示しています。

Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.

日本語の概要は準備中です。原文の説明を表示しています。

Unified entry point for Stitch design work. Handles prompt enhancement (UI/UX keywords, atmosphere), design system synthesis (.stitch/DESIGN.md), and high-fidelity screen generation/editing via Stitch MCP.

日本語の概要は準備中です。原文の説明を表示しています。

One command from "plugin installed" to "running brief on your idea." Combines /mycelium:setup (project-state initialization) and /mycelium:interview (10-minute discovery brief) into a single flow. Run this immediately after installing the Mycelium plugin — it's the recommended entry point for first-time users.

日本語の概要は準備中です。原文の説明を表示しています。

Derive the binding properties your why/how/what impose on everything below them, so no solution can silently contradict your own product definition. Retrofit entry point for projects that started before v0.120.0; also the re-derive path when why/how/what change and every stance below them goes stale.

日本語の概要は準備中です。原文の説明を表示しています。

Pull snapshots from all configured metric sources, compute deltas against prior snapshots, flag unexplained signals, and draft evidence entries for canvas files. One entry point for all external product/market metrics.

日本語の概要は準備中です。原文の説明を表示しています。

Record findings from completed offline human tasks (interviews, observations, outreach) back into the canvas. The re-entry point after /mycelium:handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Detect which external metric sources apply to this product (GitHub, Plausible, Stripe, etc.) and configure adapters. Retrofit entry point for projects that started before v0.14; also runnable to refresh source list when the product grows.

日本語の概要は準備中です。原文の説明を表示しています。

Entry point for reading PANews cryptocurrency / blockchain news, market narratives, and Polymarket smart money leaderboards. Triggers: today's headlines, breaking news, trending rankings, article search, reading specific articles, browsing columns / series / community topics, industry events & conferences, event calendar, platform hot searches and editorial picks, latest smart money boards, board highlights, and board comparisons.

日本語の概要は準備中です。原文の説明を表示しています。

Master entry point for all Stitch design workflows. Routes from user request → design spec → prompt assembly → screen generation → iteration (edit, variants, design systems) → design system extraction → framework conversion (Next.js, Svelte, HTML, React Native, or SwiftUI) → optional quality pass.

日本語の概要は準備中です。原文の説明を表示しています。