381 件 ・ 関連度順
概要と使いどころ
Research a specific technology, library, system, protocol, or tool to answer a concrete technical question with source-traceable evidence. Use when current implementation details, version behavior, configuration, compatibility, or authoritative technical facts must be verified rather than recalled. Also use when explicitly asked to incorporate verified findings into an existing skill.
日本語の概要は準備中です。原文の説明を表示しています。
Verify one falsifiable factual claim against evidence appropriate to the claim. Use when a concrete assertion about software, documentation, configuration, releases, or repository behavior must be classified as VERIFIED, REFUTED, or INCONCLUSIVE.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the PLAN artifact from SAM Stage 2 needs contextualization against actual codebase state — grounds the design plan in reality by performing scope analysis (NEW/MODIFY/COMPLETE classification), conflict detection between plan assumptions and codebase patterns, and resource mapping to concrete file paths and integration points. Produces an updated ARTIFACT:PLAN registered via MCP with a Contextualization section appended.
日本語の概要は準備中です。原文の説明を表示しています。
Organizational Development Manager (R31): guides the subject from an organizational change request (self/team/organization) to a concrete first step from SE/SM/PE. Step 0 — system type classifier (MIM.M.030, 7 questions). Step 3 — routing-table (MIM.M.031).
日本語の概要は準備中です。原文の説明を表示しています。
Maps your company's GTM motion (PLG, SLG, or Hybrid) to concrete funnel stages with inputs, outputs, and qualification criteria per stage. Detects motion type from website + Exa research, then produces pre-close + post-close stage definitions, the FETE mapping (Fit / Engagement / Tier / Eligibility), and closed-lost re-entry paths. Triggers - "funnel strategy", "funnel stages", "pipeline stages", "sales process", "lead qualification", "GTM motion mapping", or any work defining how leads flow through the business. Upstream - recommended company-context, icp-research. Downstream - feeds lifecycle-marketing, outreach-emails, content-strategy. NOT for lead scoring logic (use /lead-scoring) or lifecycle email campaigns (use /lifecycle-marketing).
日本語の概要は準備中です。原文の説明を表示しています。
Лёгкий советник «раздвигающий шторки» — premortem-сессия которая находит дыры в плане с разных углов, предлагает варианты решений по каждой и помогает юзеру быстро принять осознанные решения. История запусков сохраняется в ./docs/premortem/. Use when user types «премортем», «premortem», «найди дыры в плане», «посмотри со стороны на план», «what could kill this plan». Do NOT use for: vague ideas without a concrete plan; one-right-answer questions; creative editing of a draft; already-irreversible decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Match a free-text intent against the accumulated help of all ASE skills, generate all adequately fitting `/ase:ase-xxx-xxx` commands -- ranked best-fitting first, each with concrete options and arguments -- and let the user execute one of them, refine the intent, or cancel. Use when the user knows what they want but not which skill or flags realize it, or mentions "intent" or requests "help".
日本語の概要は準備中です。原文の説明を表示しています。
Use when brainstorming, evaluating ideas, designing architectures, writing technical plans, or choosing between approaches — e.g. "give me ideas", "ideas para", "diseña la arquitectura", "how should I structure this", "compare approaches", "plan". Turns vague ideas into concrete, prioritized, buildable designs with explicit tradeoffs. Use before writing code, not after.
日本語の概要は準備中です。原文の説明を表示しています。
Session wrap-up: consolidates every descriptive markdown file (README.md, AGENTS.md, HANDOFF.md, docs/*) into ONE canonical CLAUDE.md, then reconciles it against the current code state so a fresh session or new teammate can pick up immediately. CLAUDE.md keeps a mandatory PROGRESS block at the top answering two questions: where are we now and what's the next concrete action. Trigger when the user says: "wrap", "wrap up", "/wrap", "tidy docs", "sync docs", "update docs", "archive", "this phase is done", or the Chinese equivalents "收尾", "同步文档", "整理文档", "整理一下", "更新文档", "存档", "梳理一下", "这阶段做完了". A bare "tidy" / "整理" with prior dev context counts. Do not under-trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Use Browserbase when an agent needs hosted browser sessions, remote automation, session recording, and scalable browser infrastructure without managing Chromium fleets directly. This skill packages the Browserbase API and SDK into a concrete workflow for running, monitoring, and extracting results from cloud browser sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Uses mitmproxy2swagger to turn captured mitmproxy flows or HAR exports into a first-pass OpenAPI document that an agent can refine, validate, and hand off to downstream tooling. Invoke it when the API already exists but the contract does not, and you need a concrete spec before generating clients, mocks, tests, or reviewable docs.
日本語の概要は準備中です。原文の説明を表示しています。
Better Auth is an open source authentication framework for TypeScript apps. It gives agents a concrete way to wire sign-in, sessions, passkeys, OAuth providers, and plugins into modern web stacks with real package and docs support.
日本語の概要は準備中です。原文の説明を表示しています。
Use REUSE when an agent needs file-level licensing clarity instead of guessing from a single top-level LICENSE file. The agent checks compliance, adds or verifies SPDX headers, pulls missing license texts into LICENSES/, and produces a concrete remediation list or SPDX export.
日本語の概要は準備中です。原文の説明を表示しています。
Benchmark external agent frameworks, auto-detect source type, scan for prompt injection, and convert findings into a concrete TDD upgrade backlog for agent-studio evolution.
日本語の概要は準備中です。原文の説明を表示しています。
Use before EZ_math_model declares quality_audit, packaging, or final delivery complete, especially when pass/fail claims must be backed by files, commands, counts, or concrete evidence.
日本語の概要は準備中です。原文の説明を表示しています。
File a librarian query result back into the library as a new page with provenance tracking. Karpathy's "good answers can be filed back into the wiki as new pages" insight made concrete. The library compounds from explorations, not just from external sources.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior needs concrete proof before review, merge, or shipment.
日本語の概要は準備中です。原文の説明を表示しています。
Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that propose technical changes, justifying design decisions in ADRs, constructing substantive code review feedback, or building a research argument or technical proposal.
日本語の概要は準備中です。原文の説明を表示しています。
Create a typed assignment branch and draft PR for one student. Use when the advisor has a concrete hypothesis and the student has no open `status:wip` or `status:review` assignment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to audit typography across a codebase. Produces a file:line report with concrete fixes ordered by impact and flags unverifiable rules. Not for building a type system or token scale.
日本語の概要は準備中です。原文の説明を表示しています。
Search the local Odylith projection store after concrete anchors exist.
日本語の概要は準備中です。原文の説明を表示しています。
Use when concrete anchors already exist and the local Odylith projection store needs search.
日本語の概要は準備中です。原文の説明を表示しています。
Use when concrete Odylith failure evidence needs a Casebook bug with grounded repro details.
日本語の概要は準備中です。原文の説明を表示しています。
Capture a new Odylith Casebook bug from concrete failure evidence and grounded repro details.
日本語の概要は準備中です。原文の説明を表示しています。