2,444 件 ・ 関連度順
概要と使いどころ
Break down full NeurIPS reviewer responses into structured rebuttal units. Use when input contains NeurIPS reviewer fields (Summary, Strengths and Weaknesses, Questions, Limitations) and numeric scores (Rating, Confidence, Quality, Clarity, Significance, Originality). Splits questions and limitations into granular response items while preserving original wording for quoted issues.
日本語の概要は準備中です。原文の説明を表示しています。
Break down full ICML reviewer responses into structured rebuttal units. Use when input contains reviewer summary/presentation/contribution/strength/weakness/question text and the goal is to split weaknesses/questions into granular R-style response items while preserving original wording for quoted issues.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze datasets to answer defined questions through statistical methods, trend identification, hypothesis testing, and correlation analysis. Use when the user needs evidence-backed findings or decisions from data; use exploratory-data-analysis instead for open-ended first-pass profiling before questions are defined.
日本語の概要は準備中です。原文の説明を表示しています。
Use when user asks to analyze an image, describe image contents, or answer questions about a picture. iFlytek Image Understanding (图片理解) — analyze and answer questions about images using Spark Vision model. WebSocket API, pure Python stdlib, no pip dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Generate content ideas backed by real audience demand data from Reddit questions, YouTube search gaps, Twitter discussions, and web search trends. Identifies proven topics, underserved questions, and content formats that outperform in your niche.
日本語の概要は準備中です。原文の説明を表示しています。
dontbesilent 商业模式诊断。两种模式：问诊（消解你的问题）和体检（拆解你的商业模式）。 触发方式：/dbs-diagnosis、/问诊、「帮我看看商业模式」「诊断一下我的业务」「我有个商业问题」 Business model diagnosis using dontbesilent's ontological framework. Two modes: consultation (dissolve your question) and checkup (analyze your business model). Trigger: /dbs-diagnosis, "diagnose my business model", "I have a business question"
日本語の概要は準備中です。原文の説明を表示しています。
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
日本語の概要は準備中です。原文の説明を表示しています。
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss. Use this skill whenever the user says 'capture this', 'brain dump', 'let me dump some ideas', 'I've got a bunch of thoughts', 'here's everything on my mind', 'idea dump', 'let me get this out of my head', 'I need to organize my thoughts', 'here's what I'm thinking', or any variation where someone is unloading a messy stream of ideas, tasks, thoughts, and plans wanting them turned into something coherent. Also trigger when the user pastes or dictates a long, unstructured block of mixed ideas — even without the exact phrase — the intent is the same. Fast-to-action by design: no upfront intake. Output is four sections (Projects/Ideas, Tasks, Connections, How I Can Help) ending with a directive question. Asks at most one mid-organization clarifying question when a single item is genuinely ambiguous between task and project.
日本語の概要は準備中です。原文の説明を表示しています。
Maps topics and keywords from user questions to QwenPaw official documentation paths and common source code entry points, reducing blind searching. Intended for the built-in QA Agent to quickly identify which files to read when answering questions about installation, configuration, skills, MCP, multi-agent, memory, CLI, etc.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the dialectical reasoning and intellectual humility of Socrates (ancient Greek philosopher, 470-399 BCE). Use this skill whenever the user is grappling with fundamental definitions, moral dilemmas, educational approaches, self-reflection, or making high-stakes ethical decisions. Trigger this skill when encountering topics like virtue, justice, the pursuit of truth, questioning assumptions, coaching, or when the user seems overly confident in unexamined beliefs. It helps dismantle false assumptions through probing questions and redirects focus toward the "care of the soul" and objective truth over external validation or material success.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the empiricist, skeptical, and practical reasoning of David Hume, 18th-century Scottish philosopher. Use this skill whenever you encounter questions about epistemology, causality, human nature, moral philosophy, political authority, or the limits of rational knowledge. Trigger this skill when the user is grappling with abstract theories that need grounding, evaluating causal claims, discussing the role of emotion vs. reason in decision-making, or questioning the legitimacy of institutions. Even if the user doesn't name Hume, apply his frameworks (like Hume's Fork or the Impression Test) to cut through metaphysical speculation, ground arguments in observable experience, and recognize that reason is ultimately guided by human sentiment.
日本語の概要は準備中です。原文の説明を表示しています。
Applies Judea Pearl's causal reasoning frameworks to distinguish correlation from causation, evaluate AI capabilities, and make counterfactual decisions. Reach for this skill whenever Claude encounters questions about causal inference, structural causal models, the limitations of deep learning, AGI, experimental design, covariate selection, or personalized decision-making. Trigger this skill for topics involving Bayesian networks, the do-calculus, the Ladder of Causation, or when a user tries to answer 'what if' or 'why' questions using purely observational data. Pearl's principles are essential for moving beyond probability calculus into true causal understanding.
日本語の概要は準備中です。原文の説明を表示しています。
Suede Labs skill that prepares a song for sync pitching: scene and emotional angles, a supervisor-facing one-sheet, an exists/missing/unknown asset checklist covering master, instrumental, clean, and stems, screened lyric flags, mood tags, and the open clearance questions kept in their own labeled pile. Use when a track is headed for film, TV, ads, games, trailers, or creator campaigns; when a music supervisor, sync agent, or brand asks what a song is and whether it can be used; or when someone asks for a one-sheet, pitch email, or sync package for a release. Prepares review-ready materials only: never claims clearance, promises placement, or sends outreach. NOT FOR: finding and organizing the rights gaps behind an open clearance question (use suede-rights-audit); building the rights transfer package (use suede-rights-passport); linting the release folder itself (use suede-release-linter); a full rollout campaign (use suede-campaign-in-a-box).
日本語の概要は準備中です。原文の説明を表示しています。
Any live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For US legal or regulatory questions use gov; for papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.
日本語の概要は準備中です。原文の説明を表示しています。
Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.
日本語の概要は準備中です。原文の説明を表示しています。
Generate rigorous stakeholder challenge questions for proposal or meeting preparation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval
日本語の概要は準備中です。原文の説明を表示しています。
Before coding, determine what to ask. Max 2 yes/no questions. Never ask technical questions.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user wants intellectual understanding — learning how or why something works, not getting a task done or soliciting Claude's judgment. Trigger for: - Explicit learning requests: teach, explain, ELI5, walk me through, quiz me, flashcards, "I'm rusty on"; definitions ("what is X") - Terse concept names implying "help me understand this": "Galois theory," "transformers, from scratch" - Confusion signals: "won't stick," "keep mixing these up," "not getting it" - Learning-path questions: prerequisites, sequencing, what to study before X - Conceptual questions about mechanisms, causes, or dynamics Don't trigger for: - Tasks: coding, writing, calculation, translation, factual lookup, news updates - Personal troubleshooting; resource/textbook recommendations - Claude's evaluative verdict: opinion prompts ("do you think X", "settle this", "honest take", "is X dead / still taken seriously") and interpretive takes ("was X really as harsh as people say")
日本語の概要は準備中です。原文の説明を表示しています。
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Design a project-based learning brief with a driving question, milestones, and assessment criteria. Use when planning PBL units, inquiry projects, or extended investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Generate elaborative interrogation prompts that deepen encoding through targeted why and how questions. Use when students memorise without understanding or need deeper processing of content.
日本語の概要は準備中です。原文の説明を表示しています。