調査、論文、教育、資格学習（4,458 件）
Audit a manuscript's citations for fabricated sources, DOIs that resolve to the wrong work, in-text and reference-list mismatches, style, and claim support, verified against Crossref and OpenAlex. Use to check citations, references, a .bib file, or DOIs.
日本語の概要は準備中です。原文の説明を表示しています。
Researches one B2B SaaS competitor across 13 dimensions (company, product, ICP, pricing, reviews, content, launches, search and AI visibility, tech stack, hiring, go-to-market, social, paid ads) and writes a sourced dossier with an executive summary, a threat level, strengths and weaknesses, and a data gaps section. Run it once per competitor, then compare. Triggers: "competitor analysis", "competitor research on", "what is [competitor] doing", "compare us to", "competitive landscape", "battlecard prep". Run after /company-context and /icp-research. Not for researching your own company (use /company-context).
日本語の概要は準備中です。原文の説明を表示しています。
Builds an ideal customer profile from evidence: case studies, testimonials, customer logos, solutions pages, reviews and any sales notes you have. Produces market sizing layers, firmographic segments, a champion and an economic buyer persona, a negative ICP, intent signals, customer proof points and a voice-of-customer section in the buyers' own words, every claim sourced. Triggers: "ICP research", "ideal customer profile", "who are our customers", "customer segments", "buyer personas", "who should we target". Run after /company-context. Not for competitor analysis (use /competitor-research) or call transcript patterns (use /win-loss).
日本語の概要は準備中です。原文の説明を表示しています。
Humanizer 中文学术版——当用户要求润色论文、去除AI味、降低AIGC检测率，或说"帮我改改这段""这段读起来像AI写的"时触发。
日本語の概要は準備中です。原文の説明を表示しています。
Prepare to work on a GitHub issue or RFC. Use when the user says /start-work, asks to start an issue, begin an RFC implementation, or pick up a task. Creates the branch, gathers context, and checks learnings.
日本語の概要は準備中です。原文の説明を表示しています。
Add a new learning to the agent learnings file. Use when the user says /add-learning, asks to record a lesson, or when an implementation produced a reusable insight worth preserving for future agents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the primary outcome is creating publishable source-attributed content from URLs or supplied material, including research summaries, articles, briefs, and posts whose factual claims and quotations need reader-visible, verifiable citations.
日本語の概要は準備中です。原文の説明を表示しています。
Illustrative Claude Code skill configuration. Use when learning the basic SKILL.md shape; follow the canonical runtime reference for the current field inventory.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Sync a skill's content against the upstream library it covers — check whether the API descriptions, version references, and SOURCE: citations inside SKILL.md and its reference files still reflect what the library actually does today. Use when a library has released updates that may have changed the APIs the skill covers, when a skill references an old library version, when asked to sync, refresh, update, or check a skill against upstream docs, when the skill's content may have drifted from current library behavior, or when SOURCE: citations are stale. Accepts a SKILL.md path, skill directory, or plugin directory.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesis step in the multi-angle technical research pipeline. Receives structured outputs from all four research angles (api-state, ecosystem-research, impact-measurement, codebase-auditor), applies cross-angle signal weighting and conflict resolution, and produces a single synthesized Research section. Invoked by the technical-researcher orchestrator after all angle skills complete. Returns content to the orchestrator — does not write to the backlog.
日本語の概要は準備中です。原文の説明を表示しています。
Register a plan artifact via the MCP backlog server. Use when you produce a document or report that downstream agents or worktree-isolated environments need to retrieve — feature-context, codebase-analysis, architect, T0-baseline, TN-verification, or research artifacts. Triggers include "store an artifact", "register a plan artifact", "write a report to the backlog", "upload artifact content".
日本語の概要は準備中です。原文の説明を表示しています。
Research community usage patterns, real-world gotchas, and client compatibility for a specific known library, tool, or protocol feature. Use when a technical-researcher orchestrator needs community-sourced evidence about a named library or feature — bug reports, workarounds, compatibility gaps, and patterns from issue trackers and discussions. Distinct from the broad ecosystem-researcher agent — this skill targets a KNOWN entity and mines what real users have actually experienced, not what exists in a domain.
日本語の概要は準備中です。原文の説明を表示しています。
Quantitative cost measurement for technical research — token injection costs, payload sizes, context window consumption, and file-level counts from actual repo files. Use when a technical-researcher orchestrator needs the cost dimension of adding or changing something: how many tokens will it inject, how big are the artifacts, what is the context window impact? This is NOT blast-radius analysis (which files break) — it covers size, tokens, and performance cost only.
日本語の概要は準備中です。原文の説明を表示しています。
Manages the research/ knowledge base of verified tool and library research entries via knowledge-explorer.py. Commands — list (browse by category or SDLC layer), fetch-github (draft entry from GitHub repo), add (validate and route to category dir), update-append (append dated revision), generate-descriptions (repair missing or low-quality descriptions), migrate (convert inline-header entries to frontmatter). Use when browsing KB topics, adding or updating research entries, fetching GitHub repo metadata, generating descriptions in parallel via Haiku subagents, or migrating old-format entries to skill-spec frontmatter.
日本語の概要は準備中です。原文の説明を表示しています。
Bulk-refresh research entries in ./research/ using parallel research-curator agents. Use when /refresh-research is invoked, stale research needs updating, or bulk re-verification of research entries is requested. Inventories entries by review date and age, runs RT-ICA pre-flight, spawns agents in waves of 5, then validates, reviews, and commits through research-curator. Supports --all, --stale, --category, --layer, and --dry-run flags.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate research entry lifecycle in ./research/ — create, batch-import, refresh stale entries, and validate structure. Use when asked to add a tool, research a URL, document a library, refresh research, validate entries, or given any tool or library URL. Supports --batch (parallel multi-URL), --rerun (refresh one or all entries), and --validate (structural check with auto-fix of error-severity issues).
日本語の概要は準備中です。原文の説明を表示しています。
Builds a skill from official documentation through categorized research, citation review, integration, and final validation. Use when researching a tool or library before creating a skill, when "research for skill" or "create comprehensive skill" is requested, or when extensive multi-source documentation gathering is needed.
日本語の概要は準備中です。原文の説明を表示しています。
An AI analyst for buying B2B software. Investigates what vendors claim, checks the evidence, surfaces contradictions and unanswered questions, and produces a shareable Decision Brief with the questions to ask before you buy. Quick Eval by default; Deep Eval on request. Use when asked to evaluate, compare, vet, or research B2B software vendors.
日本語の概要は準備中です。原文の説明を表示しています。
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
日本語の概要は準備中です。原文の説明を表示しています。
Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory.
日本語の概要は準備中です。原文の説明を表示しています。
AgentDB Reinforcement Learning Training operates on 3 fundamental principles:
日本語の概要は準備中です。原文の説明を表示しています。