「how to use」の検索結果

Works out a company's go-to-market motion (product-led, sales-led or hybrid) from its website and pricing, then maps the funnel stage by stage: a definition, strategy, leading inputs the team controls, lagging outputs with targets, cadence and owner for each stage, MQL, SQL and PQL criteria, post-sale stages, closed-lost re-entry paths and backward funnel maths from a revenue target. Triggers: "funnel strategy", "funnel stages", "pipeline stages", "PLG vs SLG", "lead qualification criteria", "map our sales process", "how do leads flow". Feeds /goals. Not for setting the target itself (use /goals).

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

Create a new IWE skill with proper frontmatter, gates, scaffold and verification. Use when the pilot says: /skill-creator or «создай скилл <name>». The skill enforces WP Gate precondition, Routing Gate, IntegrationGate hard-check, collects parameters in 4 short steps, generates a scaffold SKILL.md from a template, shows a draft, writes files, and reminds about verify-skill.sh.

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

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).

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

Use after an Anabasis v2 comparison, checkpoint or system change, and before any sentence claims that a harness, a model or a patch improved something. States what one reading may be said to show: the identities it was made under, the counts kept apart, whether it was repeated, which part of a harness it belongs to, whether a mechanism was live in the run, and whether the measurement is valid as distinct from whether it was exploited. Ends in one fixed report.

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

Show details about a specific storage bucket. Requires authentication. Use for Agentuity cloud platform operations

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

Create, use, and manage Agent Skills for Claude. Use when working with Skills, creating custom capabilities, or understanding how Skills extend Claude's functionality. Covers Skill architecture, file structure, and best practices.

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

Extract and display the final message from a Claude agent JSONL file. Use when the user wants to see an agent report, view agent output, extract agent results, check what an agent produced, or read the final response from a subagent. Triggers on requests like "show me agent report", "what did agent X produce", "extract agent output", "view agent results", or "get the report from agent ad42ecb".

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

Initialize or improve AGENTS.md files that define how coding agents operate in a repo. Use when asked to set up or replace an agent init command (Codex, Claude), standardize multi-agent behavior, or audit an existing AGENTS.md for clarity, commands, boundaries, and repo-specific context. For Claude Code, also create CLAUDE.md as a symlink to AGENTS.md.

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

View current or given task plan. Use when the user calls to "view", "show" or "see" the "task", "plan", "spec", or "specification".

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

Work with a Grafana instance — search and read dashboards, run datasource queries (Prometheus, Loki, PostgreSQL, etc.), inspect alert rules and silences, post annotations, and manage folders. Use this whenever the user mentions a Grafana dashboard, panel, or alert; pastes a Grafana URL; asks "what does this dashboard show", "query this metric in Grafana", "is this alert firing", "silence this alert", or wants to create/export a dashboard — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

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

Generate and maintain the system recap block in a PR description - a GitHub-rendered visual summary of which system primitives a change touches, how risky it is, and what changed. Prefer mermaid sequence diagrams for the change; pick another graph type when it explains the diff better. Use when planning a non-trivial change (plan mode), when creating or updating a pull request (recap mode), or when the user asks for a visual recap, visual plan, system review, or PR recap.

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

Use when you want a research analysis of how a company, creator, or newsletter markets itself across channels, voice, and tactics.

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

LLM brand manipulation — build a consensus web so ChatGPT, Claude, Perplexity, and Google AI Overviews mention your brand when people ask about your category. Uses surround sound methodology, entity SEO, and LLM citation science. Use when "get mentioned in AI", "LLM brand presence", "surround sound", "AI search visibility", "Perplexity ranking", "ChatGPT mentions", "AI Overview inclusion", "entity authority", "brand mentions in AI", or any request to influence how AI systems perceive and recommend your brand.

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

Brand positioning workshop — define messaging framework, voice/tone, differentiation strategy, and taglines. Use when "brand positioning", "messaging framework", "brand voice", "how should we position ourselves", "differentiation", "tagline", or any request to define or refine brand identity and messaging.

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

Create crafted, accurate visualizations of anatomy, neurobiology, pharmacology, drugs, cells, and molecular biology. Show real biological structures and make their mechanisms visible, using literal anatomy or a clearly identified mechanical metaphor. Build interactive isometric SVG figures with sourced numbers, accessible motion, optional WebGL, a framed card and live readout. Use for biological explainers, educational illustrations, documentation and interactive figures.

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

Design the MixerSceneIntent, approval state, JSON schema, CLI examples, audit entries, and tests for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use whenever a task mentions mixer scenes, Ui24R snapshots/cues, operator-approved mixer control, show-director contract updates, schema updates, dry-run CLI shape, or follow-ups that revise this contract.

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

How to add a page to the tdmcp VitePress docs site so it builds, gets a clean URL, and lands in the right nav — including the repo's partial-translation convention (only the artist guide is EN+PT; reference/legal pages are English). Use when authoring the privacy policy or any new docs page for tdmcp.

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

Use for a weekly operating review (Friday wrap or Monday plan) — review progress against the 90-day priorities, surface stalled open loops, and set next week's focus. This is the PERSONAL operating review; distinct from /audit (checks the kit's connections/freshness) and /level-up (finds one automation to build). Trigger on "/weekly", "weekly review", "weekly planning", "how did this week go", "plan my week".

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

Rates any SKILL.md on a 0-100 scale across 10 dimensions with a SHIP / REWORK / SCRAP verdict. Evaluates trigger precision, instruction clarity, output predictability, edge case coverage, anti-hallucination guardrails, developer experience, composability, open-source readiness, wow factor, and real-world utility. No flattery — calibrated against Anthropic's own skill-creator rubric. Use this skill whenever someone says "score this skill", "rate my skill", "is this skill good", "skill review", "skill audit", "roast my SKILL.md", "grade this", "will this skill work", "evaluate my skill", "how good is this", or pastes a SKILL.md and asks for feedback. Also trigger when comparing two skills, benchmarking a skill collection, or asking "what's wrong with this skill" — even without the word "score".

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

Display input/output args, return object and cost time of a Python method invocation in a live process. Use this to observe function behavior at runtime — see what arguments go in, what comes back, and how long it takes. This is the most frequently used diagnostic command.

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

Solve competitive programming and LeetCode-style problems with educational explanations. Use when asked to "solve this problem", "help with this leetcode", "competitive programming solution", "solve this algorithm problem", "coding challenge solution", "how to solve this coding problem", or any algorithmic problem-solving request.

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

Simulates a realistic VC Investment Committee: three partner archetypes debate a startup's merits, concerns, and deal terms, scored across 28 dimensions. Use when the user asks to simulate an IC, or how partners would debate their startup, and gives a deck, a company description, or a specific fund. A full run takes about 15–20 minutes, so for a passing question such as 'would a VC fund us?' or 'are we fundable?', answer briefly in chat and offer the simulation instead of starting it. When it runs, partners' views come from the scored simulation, never improvised.

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

Create standout, technically ambitious interfaces that feel extraordinary through cinematic transitions, advanced motion, heavy rendering, or other high-ambition implementation work. Use when the user wants to wow, impress, go all-out, or push a feature beyond conventional UI polish—not when simple visual confidence or routine cleanup is enough.

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

Show the latest or selected plugin-managed Kimi job for the current repository. Use when the user explicitly asks for Kimi job status or progress.

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