8,706 件 ・ 関連度順
概要と使いどころ
Read or convert documents (PDF, Office, OpenDocument, RTF, EPUB, CSV) in a research workflow: read directly or convert, pick the converter from document structure, and decide whether the Markdown is tracked or scratch. Use when a document must be read, quoted, summarized, searched, extracted, or added to a source library; scans go to $vlm-ocr.
日本語の概要は準備中です。原文の説明を表示しています。
Read Haskell package documentation, Haddock HTML, Hackage pages, or dependency source for cabal nix-style projects. Prefer locally built/cached docs and source from the cabal store, dist-newstyle, plan.json, and repo-cache; fall back to Hackage only for packages outside the project dependency set or when local docs are unavailable.
日本語の概要は準備中です。原文の説明を表示しています。
Search and read locally-stored Claude documentation covering Claude Code CLI, Claude API (Messages, tool use, vision, streaming, batch), Agent SDK (Python and TypeScript), prompt engineering, and all Anthropic platform docs. Use this skill whenever the user asks about Claude Code features (hooks, MCP servers, skills, plugins, settings, permissions, keybindings, sub-agents), the Anthropic API or any of its SDKs (Python, TypeScript, Go, Java), the Agent SDK (sessions, hooks, custom tools, MCP), model capabilities (context windows, extended thinking, pricing, rate limits, vision), prompt engineering best practices, or troubleshooting any Claude-related error. This skill provides instant access to official documentation files without web searches — always prefer it over web lookups for Claude and Anthropic topics.
日本語の概要は準備中です。原文の説明を表示しています。
Advanced Docker containerization expert for multi-stage builds, image optimization, security hardening, and Compose orchestration. Use when the task involves `working with Dockerfile`, `docker-compose.yml`, `containerization`, `multi-stage builds`, or `optimizing Docker images`.
日本語の概要は準備中です。原文の説明を表示しています。
Verify document completeness for each bureaucratic step of an EU/DACH relocation, flagging missing items and translation requirements. Use after creating a relocation plan and before beginning bureaucratic procedures, when preparing for a specific appointment (Buergeramt, Finanzamt), when unsure which documents need certified translation or apostille, after receiving a rejection or request for additional documents, or as a periodic check during the relocation process to ensure nothing has been overlooked.
日本語の概要は準備中です。原文の説明を表示しています。
Translate, complete, and audit Docusaurus localization under docs/i18n for both UI JSON catalogs and documentation Markdown/MDX pages. Use when adding or correcting locales, when a language switcher translates only theme labels while page content stays in the default language, or when verifying that non-default locales do not fall back to source documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Add or update NowStack Mobile docs in docs/. Use when documenting architecture, release workflows, Convex/web/mobile patterns, setup, APIs, or tooling — or via `/ns docs`.
日本語の概要は準備中です。原文の説明を表示しています。
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
日本語の概要は準備中です。原文の説明を表示しています。
Use the hyalo CLI instead of read/edit/grep/write when working with markdown (.md) files that have YAML frontmatter. This skill MUST be consulted whenever pi is working with markdown documentation directories, knowledgebases, wikis, notes, Obsidian-compatible collections, Zettelkasten systems, iteration plans, or any collection of .md files with frontmatter. Trigger this skill when: searching or filtering markdown files by content, tags, or properties; reading or modifying YAML frontmatter; managing tags or metadata across documents; toggling task checkboxes in markdown; getting an overview of a documentation directory; querying document properties or status fields; bulk-updating metadata across many markdown files; or when you find yourself repeatedly using read/edit/grep/write on .md files. Even if the user does not mention "hyalo" by name, use this skill whenever the task involves structured markdown documents with frontmatter. For pi sessions, ALWAYS use `--format text` for compact, LLM-friendly output.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
日本語の概要は準備中です。原文の説明を表示しています。
Update all project documentation including implementation docs, user guides, API docs, and architecture diagrams. Use when finalizing features to ensure comprehensive documentation.
日本語の概要は準備中です。原文の説明を表示しています。
This skill provides guidance for maintaining documentation consistency with implementation in the vscode-sidebar-terminal project. Use this skill when creating or updating documentation, verifying documentation accuracy, preparing releases, or when the codebase has changed and documentation may need updates. This skill should be used proactively after implementing features or bug fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Write documentation developers actually use: READMEs, API docs, ADRs, runbooks, and docs-as-code workflows. Use when writing or improving technical documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Generate OpenAPI 3.1 documentation from your API codebase. Auto-detects Express, Fastify, NestJS, Django, FastAPI, Flask, Rails, Spring, Go, and more. Triggers: you need API documentation, OpenAPI spec, Swagger docs, endpoint reference, or REST API docs.
日本語の概要は準備中です。原文の説明を表示しています。
Write a technical tax position memo that documents a tax filing position with authorities, facts, analysis, and conclusion. Use when a tax professional says "write a tax memo", "document this tax position", "research memo for the partner", "we need to support this deduction", "document the tax treatment", "write up the authority for this position", "technical memo on [tax issue]", "MLTN analysis", "reasonable basis memo", "document the IRC section that supports this", or needs to formally document a tax conclusion. Also trigger when someone has a tax question that needs a written conclusion backed by legal authority - even if they don't use the words "tax memo" or "tax position".
日本語の概要は準備中です。原文の説明を表示しています。
Document a machine learning model in a structured, transparent format for stakeholders, reviewers, and future maintainers. Use when the user says "document this model", "write a model card", "model documentation", "how should I document my ML model", "bias and fairness report", "model transparency", "what does this model do", "model handoff", "production model documentation", or needs to communicate what a model does, how it was built, where it works, and where it fails.
日本語の概要は準備中です。原文の説明を表示しています。
Write a clear, reviewable audit workpaper documenting procedures, evidence, and conclusions. Use when an auditor says "write a workpaper", "document this audit procedure", "tick and tie this", "I need to document my testing", "substantive testing workpaper", "controls testing documentation", "audit evidence memo", "prepare the workpaper for this balance", "document the audit steps I performed", or needs to capture any audit work in a format that supports review and sign-off. Also trigger when someone has completed audit testing and needs to write it up even if they don't use the word "workpaper".
日本語の概要は準備中です。原文の説明を表示しています。
**WORKFLOW SKILL** — Generate formatted documents from Markdown or structured content. USE FOR: creating PowerPoint presentations, Word documents, Excel spreadsheets, MS Project files, PDFs from Markdown/JSON/chat context using templates. DO NOT USE FOR: converting documents TO Markdown (use doc-to-markdown), general file I/O, web scraping.
日本語の概要は準備中です。原文の説明を表示しています。
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration configuration, compliance data collection, audit trail setup, regulatory documentation workflow, Field Audit Trail configuration, Setup Audit Trail, Event Monitoring, Discovery Framework, FSC KYC objects, Identity Document setup, Party Identity Verification. NOT for security implementation, NOT for designing AML/KYC architecture (use architect/aml-kyc-process-architecture), NOT for configuring who can access deal or client data (use admin/compliant-data-sharing-setup).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a BA or admin needs to document the Salesforce data model: creating field inventories, object relationship maps, ER diagrams, or analyzing field usage across objects. Triggers: 'data dictionary', 'document our data model', 'object relationship map', 'field inventory', 'ER diagram for Salesforce'. NOT for designing the model or choosing lookup vs master-detail — use data/data-model-design-patterns. NOT for generating the Mermaid or PlantUML diagram — use architect/salesforce-erd-and-diagramming. More trigger keywords: field inventory CSV, describe API, getGlobalDescribe, DescribeFieldResult, sObject describe, schema snapshot, schema drift, blank field descriptions, undocumented fields, field ownership, data dictionary review cadence.
日本語の概要は準備中です。原文の説明を表示しています。
Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST API rate limits, OpenAPI sObjects, API contract record, error contract, errorCode catalog, 410 GONE retired API version, HTTP 300 external ID upsert, idempotency key, deprecation notice, composite subrequest limit. NOT for building the endpoint or writing the Apex REST service — use apex/apex-rest-services. NOT for upgrading the API version on your own Apex, LWC or sfdx-project.json — use devops/api-version-management.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Mastra framework guide. Teaches how to find current documentation, verify API signatures, and build agents and workflows. Covers documentation lookup strategies (embedded docs, remote docs), core concepts (agents vs workflows, tools, memory, RAG), TypeScript requirements, and common patterns. Use this skill for all Mastra development to ensure you're using current APIs from the installed version or latest documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Audit one local prospectus PDF, DOC, or DOCX through PDRouter and download the annotated document with AutoDoc NEXT2.0.
日本語の概要は準備中です。原文の説明を表示しています。