「base」の検索結果

Analyze sales-call transcripts to extract why deals are won and lost across six dimensions — product, messaging, GTM/sales, pricing, competition, and customer context. Produces aggregated patterns with verbatim buyer quotes, frequencies, and recommendations. Writes to marketing/win-loss/win-loss.md as the evidence base under positioning, messaging, and ICP. Triggers - "win loss analysis", "why are we losing deals", "why do we win", "analyze sales calls", "churn analysis", "deal review"

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

Use when verifying information (fact, number, quote, event, statement) against authoritative primary sources, or cross-checking a number via one-level metric decomposition (Z = P × Q). Triggers: "verify X", "is this true", "find the original source", "where is this number from", "two sources disagree", "is it true X never did Y". Covers five scenarios: (1) basic truthfulness check, (2) completeness / out-of-context quoting, (3) one-level reasoning verification, (4) negative-statement handling, (5) multi-source conflict side-by-side output. Dig into whitelisted primary sources only (user-supplied files, official websites & databases, authoritative industry sources); cited reports / charts / datasets must be downloaded and read locally to count as verified — if download is blocked, hand the link to the user. If nothing can be found, plainly state "cannot verify" rather than guessing, patching, or citing secondary paraphrases. Always reply in the user's question language.

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

Generate or redesign evidence-based README files for apps, libraries, CLIs, monorepos, and agent skills. This skill should be used for /readme-write, /readme, generate readme, write readme, improve readme, 帮我写 README, 美化 README, README を書いて, README 작성해 줘, напиши README, or their equivalents in any language. Confirm reader and visual preferences before generation; every README includes a source-backed flowchart, and every language edition keeps identical content apart from the language. Git-driven updates are routed to the companion readme-update skill.

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

VNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db / dispatch_tracker.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX governance state. Triggers include: editing intelligence injection code, querying central DB for cross-project insights, debugging "intelligence not appearing in T0 state", modifying schema in `schemas/quality_intelligence.sql` or `schemas/runtime_coordination_v*.sql`, working with `scripts/quality_db_init.py` or `scripts/lib/coordination_db.py`.

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

VNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX governance state. Triggers include: editing intelligence injection code, querying central DB for cross-project insights, debugging "intelligence not appearing in T0 state", modifying schema in `schemas/quality_intelligence.sql` or `schemas/runtime_coordination_v*.sql`, working with `scripts/quality_db_init.py` or `scripts/lib/coordination_db.py`.

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

Multi-provider deliberation panel for COMPLEX, multi-view questions — architecture, strategy, market research, and codebase sweeps. Runs a 4-stage deliberation across the provider fleet (diverge → contrarian red-team → adversarial verify → cited synthesis), the same multi-perspective rigour the plan-gate already applies to plan reviews, generalised to arbitrary questions. Use when one model's answer isn't enough and you want convergence THROUGH disagreement + verification, not a single opinion.

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

Quality validation specialist covering functional, performance, and security testing to ensure production readiness through evidence-based testing.

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

How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.

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

Load files, object storage, dataframes, or external databases into MotherDuck using an appropriate bulk ingestion path.

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

Discover MotherDuck databases, tables, columns, shares, and sample data to understand an available dataset.

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

Use the MotherDuck CLI for terminal queries, authentication, and file-based Dive or Flight workflows.

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

估计中国 A 股"国家队"(中央汇金)的宽基 ETF 持仓变动趋势——追踪上交所沪深300/上证50/中证500/中证1000/中证A500/科创50 的 ETF 份额变化,叠加各自指数走势,生成六合一总图与各指数单图。Estimates China's "national team" (Central Huijin) broad-base ETF positioning by tracking Shanghai Stock Exchange ETF share changes. Use when the user asks about 国家队持仓 / 国家队仓位 / 中央汇金持仓 / 国家队加仓 / 国家队减仓 / ETF份额变化 / 看看国家队 / national team holdings / Central Huijin positions.

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

Use whenever the user wants to find, shortlist, vet, enrich, or research US professional-services firms — law, marketing, consulting, accounting, IT services, architecture, engineering, HR, PR, design, and similar B2B service providers. Triggers on requests like "find me a PPC agency in California", "shortlist three boutique IP law firms", "build a longlist of 50 mid-size IT consultancies", or "here are 12 agency domains — pull contact info and confirm which are US-based", even when the need is described indirectly without naming a category. Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog with filters for industry, services, location, size, ratings, and third-party listings. Skip when the user is asking for personal/consumer services for themselves (an individual's own legal, tax, or medical needs), non-US firms, individual freelancers, retail/ecommerce/SaaS-product companies, recruiting-an-employee tasks, or general web research that doesn't need a structured firm directory.

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

Maintain user-owned GPG and SSH public-key parsing, profile API registration, identity database persistence, format compatibility, and maintained OpenPGP dependencies. Excludes portal signing-key publication and admin private-key export.

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

Maintain portal public signing-key discovery at .well-known/jwks.json, reusable admin API directive parsing, opt-in admin private-key export, KMS key serialization, asymmetric issuer selection, base-path routing, and JWT verification tests. Excludes upstream OAuth provider JWKS consumption.

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

Maintain the pure-Go SQLite password identity store, reusable parser, immutable account evidence, idempotent enrollment, portal injection, and login E2E tests. Excludes local JSON database internals and MFA/profile feature implementation.

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

Perform a holistic, human-reviewer-style critique of the currently staged Git changes (or, with `--unstaged`, of the unstaged and untracked changes, with `--branch`, of a branch against its base, or, with `--commit`, of a single commit) and emit an approve/reject verdict with prioritized, severity-tagged, line-cited findings. Use when the user wants the staged diff, a branch, or a commit "reviewed", "critiqued", or "code-reviewed".

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

Resolve the Git merge conflicts of a working directory -- of an in-progress merge, rebase, cherry-pick, revert, stash apply, or of conflict markers left by patch -- carefully and semantically, never losing any change, escalate unresolvable hunks as-is, continue the in-progress operation, and emit a RESOLVED, PARTIAL, NONE, or FAILED verdict. Use when the user calls to "resolve" or "fix" merge conflicts.

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

Edit Specification: Use when the user wants to "edit" the SpecBook-based specification (SPEC) in one shot from a query, with optional grilling, SpecBook validation, looping, and Git worktree isolation.

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

Merge a Git source branch, including its still uncommitted changes, into a target branch through a regular merge, a rebase with fast-forward, or a squash merge, resolving merge conflicts semantically, check that the source branch landed, and emit a MERGED, CONFLICT, or FAILED verdict. Use when the user calls to "merge", "integrate", or "land" a branch.

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

Export the SpecBook-based specification (SPEC) into ready-to-consume renderings like HTML, PDF, normalized Markdown, or JSON. Use when the user wants to "export", "render", or "materialize" the specification.

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

Edit Source Code: Use when the user wants to "edit" the code base in one shot from a query or a bare analyzer issue id like "P1", fusing crafting, refactoring, and resolving with optional grilling, verification, looping, and Git worktree isolation.

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

Iteratively edit and refine a named plan for a task through a conversational loop. A new plan is optionally composed along the chosen one of several proposed crafting, refactoring, resolution, or specification approaches. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or draft. Use when the user wants to plan a task purely through chat-driven refinement, or wants a plan to "craft" a new feature, "refactor" the code base, or "resolve" a problem (also from a bare analyzer issue id like "P1").

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

Builds, revises, restyles, and critiques deliberate, editable Feishu / Lark whiteboards from content, references, existing SVGs, or live boards. Use for whiteboards, infographics, diagrams, system maps, timelines, decision boards, posters, and visual explainers that need factual fidelity, strong hierarchy, intentional composition, and evidence-based review rather than a generic grid of equal cards. Routes creation, revision, and critique through separate playbooks; commits to a content-and-design contract before drawing; validates deterministic SVG defects; renders and inspects the actual artifact; and uses an independent final reviewer for material deliveries.

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