Word・Excel・PowerPoint・PDF、議事録、マニュアル（3,328 件）
概要と使いどころ
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
日本語の概要は準備中です。原文の説明を表示しています。
Use when looking up documentation
日本語の概要は準備中です。原文の説明を表示しています。
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
日本語の概要は準備中です。原文の説明を表示しています。
通过 Context7 MCP 使用最新的库和框架文档，而非训练数据。当用户提出设置问题、API参考、代码示例或命名框架（例如 React、Next.js、Prisma）时激活。
日本語の概要は準備中です。原文の説明を表示しています。
High-precision semantic search and content retrieval via Exa API. Use when: (1) Deep research requiring semantic understanding, (2) Code documentation and examples lookup, (3) Company/professional research, (4) AI-powered comprehensive research tasks, (5) URL content extraction with structured output. Triggers: "research", "find papers", "code examples", "company info", "LinkedIn profiles", "deep analysis". Differentiator: Exa excels at semantic/neural search while grok-search is better for real-time news and general web content.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch current library and API documentation from Context7 when a coding answer needs authoritative, up-to-date examples or version-specific behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Enhanced web search and real-time content retrieval via Grok API with forced tool routing. Use when: (1) Web search / information retrieval / fact-checking, (2) Webpage content extraction / URL parsing, (3) Breaking knowledge cutoff limits for current information, (4) Real-time news and technical documentation, (5) Multi-source information aggregation. Triggers: "search for", "find information about", "latest news", "current", "fetch webpage", "get content from URL". IMPORTANT: This skill REPLACES built-in WebSearch/WebFetch with Grok Search tools.
日本語の概要は準備中です。原文の説明を表示しています。
不一书个人工作台生成器。通过一场引导式访谈，帮用户（包括完全不懂代码的人）做出一个属于自己的手机端个人工作台—— 左侧常驻功能栏、右侧卡片流，打开就是今日计划、打卡、记账、体重、日程、单词、树洞等自己每天真正要用的东西， 可以部署上线并添加到手机桌面，像一个 App 一样用。 当用户说"初始化不一书个人工作台生成器"、"初始化 bys-personal-dashboard"、"我想做一个自己的个人工作台"、 "抖音上那种个人工作台我也想要一个"、"把我的日常安排做成一个手机页面"时必须触发； 即使用户只是丢来一张别人的工作台截图说"我也想要这种"，也应触发。 已有工作台后说"给我的工作台加个XX功能"、"工作台换个配色"、"工作台改一下"时，走迭代流程而不是重新初始化。 用户没说"工作台"这个词时，用三个特征判断：①在手机上用 ②每天都会打开 ③装的是用户自己的私人数据 （体重、账目、打卡、待办、日记）。三个同时成立就该触发，比如"我想把体重记账待办整理到一个地方、 手机上能点开"——这就是工作台，只是用户不知道这个叫法。三个缺任何一个都不要触发。 功能只有一个也算——"我老忘记吃药，想每天在手机上勾一下"就是种子需求，别因为"听起来只是个小功能"就不触发。 判据是数据属于谁，不是数据存在哪：用户自己的记账 Excel 想做成手机上每天看的页面，是工作台；公司销售数据做报表，不是。 不用于：用完就走、不存个人数据的小工具页（抽奖转盘、计算器、放在活动大屏或直播间给别人看的倒计时）、 后台管理系统、 给团队用的多人协作工具、个人博客/作品集/对外展示的个人官网（那些是给别人看的，不是自己每天用的）、 公司或业务数据的报表看板（用 xlsx 之类的技能）、与个人工作台无关的普通 HTML 编码问题。
日本語の概要は準備中です。原文の説明を表示しています。
Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).
日本語の概要は準備中です。原文の説明を表示しています。
Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).
日本語の概要は準備中です。原文の説明を表示しています。
Check a text fragment for potential secrets (API keys, tokens, passwords) BEFORE sending to chat / committing / publishing. Second protection layer on top of the pre-commit hook — manual gate, user explicitly calls on potentially sensitive text.
日本語の概要は準備中です。原文の説明を表示しています。
Classifies raw pilot request → structured JSON {task_type, class, artifact, budget_estimate, confidence, routing_tag, resolution_path, schema_version, result_type, expected_result_kind, result_kind_resolution, hypothesis_relation}. Keyword-fast (<200ms) or Haiku fallback (<60s). Does NOT create WP or call executor.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Guides discovery of local skills and enforces minimal documentation style.
日本語の概要は準備中です。原文の説明を表示しています。
Write clear, plain-spoken code comments and documentation that lives alongside the code. Use when writing or reviewing code that needs inline documentation like file headers, function docs, architectural decisions, or explanatory comments. Works well for both human readers and AI coding assistants who see one file at a time.
日本語の概要は準備中です。原文の説明を表示しています。
Generate hierarchical AGENTS.md structures for codebases. Use when user asks to create AGENTS.md files, analyze codebase for AI agent documentation, set up AI-friendly project documentation, or generate context files for AI coding assistants. Triggers on "create AGENTS.md", "generate agents", "analyze codebase for AI", "AI documentation setup", "hierarchical agents".
日本語の概要は準備中です。原文の説明を表示しています。
Generate semantic + keyword match score. Compares resume content against job description to calculate a fit score and identify gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically deconstruct written content into verifiable claims, validate each using search/documentation, and facilitate informed discussion through structured interviewing.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates multi-agent workflows by delegating ALL tasks to spawned subagents via /spawn command. Parallelizes independent work, supervises execution, tracks progress in UUID-based output directories, and generates summary reports. Never executes tasks directly. Triggers on keywords: orchestrate, manage agents, spawn agents, parallel tasks, coordinate agents, multi-agent, orc, delegate tasks
日本語の概要は準備中です。原文の説明を表示しています。
Standardized reference documentation section structure for agents - project guidance, conventions, related agents, and Skills. Use when implementing or updating agent documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
日本語の概要は準備中です。原文の説明を表示しています。
AI-powered diary generation for agents - creates rich, reflective journal entries (400-600 words) with Quote Hall of Fame, Curiosity Backlog, Decision Archaeology, and Relationship Evolution. Generates personal, emotional entries from the agent's perspective. Works best with Claude models (Haiku, Sonnet, Opus).
日本語の概要は準備中です。原文の説明を表示しています。
Safely sync navigator's agent-browser fork with upstream vercel-labs/agent-browser, analyze changes, and generate integration documentation
日本語の概要は準備中です。原文の説明を表示しています。
Full-coverage formatted Excel report generation with Dutch market compatibility
日本語の概要は準備中です。原文の説明を表示しています。