「wants」の検索結果

Turns an ICP or research goal into a plan for finding and scraping suitable directories. Use when the user has a target audience but is unsure where to find them, and wants source categories, queries, and an extraction workflow.

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

Assesses the quality, composition, and usefulness of a lead list. Use when the user provides a lead list and wants completeness, distribution, quality issues, and recommended next actions.

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

Ranks companies or accounts by strategic relevance and opportunity. Use when the user provides accounts and wants a priority score, tier, rationale, risks, and next action.

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

Qualifies and scores B2B prospects against a supplied ideal customer profile. Use when the user provides a lead list, company records, prospect data, or qualification criteria and wants prioritization, fit analysis, or disqualification reasons.

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

Creates a repeatable process for researching and comparing companies. Use when the user wants a structured, reusable company-research workflow with objectives, sources, fields, and validation.

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

Divides records into geographic or account-ownership territories. Use when the user provides records with location or account data and wants consistent territory assignments with unresolved locations flagged.

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

Turns company records into structured company research summaries. Use when the user provides company names or records and wants a consistent overview, market position, and relevance assessment.

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

Identifies missing information required to complete qualification, segmentation, or outreach preparation. Use when the user provides records and a goal and wants prioritized research gaps with sources.

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

Converts a job description into a structured candidate-sourcing workflow. Use when the user provides a role and wants candidate criteria, search terms, source recommendations, and a screening process. Must avoid sourcing on sensitive personal attributes.

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

Use when the user wants a ready-to-paste social post kit for an app, tool, or project launch or update — "make social posts", "launch posts", "post kit", "prep socials", "promote this". Produces one Markdown file with finished posts for X, Reddit, Instagram, LinkedIn, Threads, and short-form video, plus a pre-post checklist. Pull real facts from the project (repo, release, what it does, OS, links).

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

At the end of a long working session, produce a counterfactual trace note — a backward walk through the session that identifies the small number of load-bearing moments (observations, failures, accidents, decisions) without which the final outcome would not exist. Use this whenever the user asks to "close the session", "run the butterfly", "trace back", "what actually mattered here", asks for a session retrospective, or asks how the session arrived at its result. Also use it when a session ends with a significant outcome (a fix, a design decision, a shipped artifact) and the user wants a note capturing why it happened, not just what happened. Do NOT use for simple summaries of short sessions — this skill is for causal tracing, and it only earns its cost when the session was long enough to contain real forks.

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

Use when the user wants the full package on a repo, says run my project workflow, project check-in, or is overwhelmed opening an old or new folder. Runs the project onboarding checklist—explain-new-project, project-worth-my-time, and project-catch-up—in order or on demand.

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

Create an implementation plan and a GitHub Issue based on the task description provided as an argument. Use this when the user supplies a natural-language task description (not an issue number) and wants a new implementation-ready Issue. If the input is an existing issue number, use create-issue-from-issue-number (re-analyze) or update-issue (reflect comments) instead.

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

Create a new sub-agent definition file (agents/*.md) for the Claude Code plugin. Use this skill when the user wants to add a new specialized agent, define a new agent type, or create an agent that handles a specific domain of tasks. Trigger whenever the user mentions creating, adding, or defining a new agent or sub-agent.

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

Re-analyze an existing GitHub Issue using its current title and body as input, refresh the implementation plan against the latest code state, and update the Issue in place. Use this when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the Explore-based analysis. For reflecting comment-driven updates instead, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.

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

Virtual QA Lead that turns requirements into review-ready, TestRail-importable test cases in one conversation. Use it whenever the user has requirements, a spec, a user story, or acceptance criteria (PDF, DOCX, XLSX, TXT, MD, or pasted text) and wants test cases, a test plan, a checklist, test coverage, a regression suite, or a TestRail/Qase/Zephyr export, even without saying "test cases" ("write tests for this spec", "what should we check here?"). Especially useful when they attach their team's existing test cases to match. When the spec describes an API (endpoints, status codes, schemas, auth, OpenAPI/Swagger), Casely also builds a runnable Postman collection, so use it for "API tests", "Postman collection", or "tests I can run in Newman/CI". Triggers on the same request in any language.

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

Search the web with LLM-optimized results via the Tavily CLI. Use this skill when the user wants to search the web, find articles, look up information, get recent news, discover sources, or says "search for", "find me", "look up", "what's the latest on", "find articles about", or needs current information from the internet. Returns relevant results with content snippets, relevance scores, and metadata — optimized for LLM consumption. Supports domain filtering, time ranges, and multiple search depths.

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

Extract clean markdown or text content from specific URLs via the Tavily CLI. Use this skill when the user has one or more URLs and wants their content, says "extract", "grab the content from", "pull the text from", "get the page at", "read this webpage", or needs clean text from web pages. Handles JavaScript-rendered pages, returns LLM-optimized markdown, and supports query-focused chunking for targeted extraction. Can process up to 20 URLs in a single call.

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

Mid-run failure recovery for disease-market-sizing-orchestration. Inspects .cache/<slug>/ to determine which phase last completed and which phase to run next. Use when orchestration was interrupted and user wants to continue without restarting from phase 1.

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

Web search, content extraction, crawling, and deep research via the Tavily CLI. Use this skill whenever the user wants to search the web, find articles, research a topic, look something up online, extract content from a URL, grab text from a webpage, crawl documentation, download a site's pages, discover URLs on a domain, or conduct in-depth research with citations. Also use when they say "fetch this page", "pull the content from", "get the page at https://", "find me articles about", or reference extracting data from external websites. This provides LLM-optimized web search, content extraction, site crawling, URL discovery, and AI-powered deep research — capabilities beyond what agents can do natively. Do NOT trigger for local file operations, git commands, deployments, or code editing tasks.

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

Convert documents to Markdown using Microsoft's MarkItDown CLI (`markitdown`). Supports PDF, Word, PowerPoint, Excel, images (OCR), audio (transcription), HTML, YouTube, and URLs. Use when a user wants to convert a file or URL to Markdown, extract text from PDFs/images, transcribe audio/video, or batch-convert documents.

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

Conduct comprehensive AI-powered research with citations via the Tavily CLI. Use this skill when the user wants deep research, a detailed report, a comparison, market analysis, literature review, or says "research", "investigate", "analyze in depth", "compare X vs Y", "what does the market look like for", or needs multi-source synthesis with explicit citations. Returns a structured report grounded in web sources. Takes 30-120 seconds. For quick fact-finding, use tavily-search instead.

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

Crawl websites and extract content from multiple pages via the Tavily CLI. Use this skill when the user wants to crawl a site, download documentation, extract an entire docs section, bulk-extract pages, save a site as local markdown files, or says "crawl", "get all the pages", "download the docs", "extract everything under /docs", "bulk extract", or needs content from many pages on the same domain. Supports depth/breadth control, path filtering, semantic instructions, and saving each page as a local markdown file.

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

Discover and list all URLs on a website without extracting content, via the Tavily CLI. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where something is on a domain, or says "map the site", "find the URL for", "what pages are on", "list all pages", or "site structure". Faster than crawling — returns URLs only. Essential when you know the site but not the exact page. Combine with extract for targeted content retrieval.

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