6,111 件 ・ 関連度順
概要と使いどころ
Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses. Each mode has a defined structure and quality bar. Use whenever a business asks to articulate strategy, set goals, analyse competition, plan for growth, do a SWOT, write OKRs, or build a lean business plan. Produces actionable documents, not generic frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Document and type a Sentry API endpoint. Write or fix @extend_schema decorators, specify response TypedDicts, type request parameters, correct type drift between the declared schema and the runtime response, and validate the generated spec. Use when asked to "document an endpoint", "add OpenAPI docs", "add/fix @extend_schema", "type an endpoint response", "fix the response type", "fix type drift", "reuse a response type", "split an overloaded endpoint", "specify the response schema", "add a TypedDict response", "migrate a legacy api-docs path", "fix a parameter type", or "make an endpoint public" / "promote an endpoint" (promotion is one section here).
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Confluence expert for spaces, knowledge bases, documentation, page layouts, macros, templates, and Jira-Confluence integration. Use for documentation strategy, space architecture, content organization, and collaborative knowledge management.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "analyze this codebase", "document this service", "generate technical docs", "I inherited this code", "help me understand this system", "create docs for this project", "what does this system look like", "onboard me to this codebase", "this codebase has no docs", "visualize the architecture from code", or any explicit request to produce structured documentation or architecture diagrams from an existing codebase. Specifically optimized for AWS workloads (CDK, CloudFormation, Terraform) with source-of-truth citations. Do NOT activate for code reviews, single-function explanations, generating new code, or general coding tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Produce the Part 3 Four Core Documents: business, segmentation, positioning, DMFlow. "produce the four core documents"
日本語の概要は準備中です。原文の説明を表示しています。
Build students' capacity to compare accounts across multiple historical sources — identifying agreements, contradictions, and gaps. Use when students treat individual documents as complete answers rather than partial perspectives.
日本語の概要は準備中です。原文の説明を表示しています。
Risk-based vendor assessment framework for IT service providers, technology vendors, and third-party partners under DORA, NIS2, GDPR. Provides three-phase process (Initial Screening / Detailed Assessment / Final Evaluation), six-dimension risk scoring (Financial/Operational/Compliance/Security/Reputational/Strategic) with weighted matrices, full DORA Art. 28-30 contractual checklist, NIS2 Art. 21(2) security measures enumeration, GDPR Art. 28 documentation checks, red flags per dimension, trigger-based review criteria, and document templates. Use when: (1) Evaluating new vendors or technology providers, (2) Conducting critical ICT third-party due diligence under DORA, (3) Performing supply chain security assessment under NIS2, (4) Creating vendor onboarding documentation, (5) Establishing ongoing vendor monitoring, (6) Assessing concentration risk, or (7) Generating executive vendor risk reports.
日本語の概要は準備中です。原文の説明を表示しています。
Edit, query, and transform Word documents (.docx) with the SuperDoc CLI. Use when the user asks to read, search, modify, format, comment, track changes, or review changes in .docx files. Triggers on any task involving Word documents — text replacement, redlining, contract markup, template filling, bulk edits, content extraction, or document review.
日本語の概要は準備中です。原文の説明を表示しています。
No Inference / Source-Locked Verification. Forces Claude to answer ONLY from user-provided materials and/or online sources actually accessed — no inference, no assumptions, no gap-filling. Every factual, legal, numerical, or procedural claim must be anchored to a cited source. Use whenever Claude reviews documents, summarises evidence, checks accuracy, drafts submissions, creates timelines, extracts facts, checks citations, analyses rules, prepares legal arguments, compares documents, verifies claims, produces chronologies, works from uploaded materials, performs legal research, checks case status, or does anything where evidential fidelity matters. Also trigger on: 'source-locked', 'no inference', 'only from the materials', 'don't assume', 'stick to the evidence', 'verify this', 'check this is right', 'work from the documents'. Overrides Claude's default tendency to fill gaps. If evidential accuracy matters, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Detects prompt injection hidden in documents from the other side (pleadings, skeletons, bundles, served evidence, opponents' emails and attachments) before an AI reads them, so the model is not turned against your client. Checks word by word that the text an extractor hands the model was visibly drawn on the page: white, near-white, covered, clipped, off-page, tiny, transparent and invisible-mode text in PDF (ink test plus OCR); Word formatting resolved as Word does (styles, shading, theme colours, scaling, off-page frames, fallbacks, unused headers); HTML/CSS, RTF, email with attachments and zips, xlsx/pptx and legacy formats. Flags Unicode smuggling, text addressed to an AI and authorities found only in hidden text. Fails closed. Optional Read-tool hook. Use BEFORE any AI summary or analysis of an opposing or third-party document. Triggers: 'scan for injection', 'is this document safe', 'check the other side's skeleton', 'injection guard'.
日本語の概要は準備中です。原文の説明を表示しています。
Compliant, retrieval-grounded research over investor-State dispute settlement (ISDS) awards and decisions. Use when the user asks about ICSID / investment-treaty arbitration cases, awards, or doctrines (fair and equitable treatment, expropriation, jurisdiction, costs, annulment, etc.) and wants answers grounded in the actual document text with pinpoint citations. Identifies the correct document on the case page, confirms it against the PDF's own first pages, retrieves primary documents on demand from ICSID, PCA, etc., never scrapes or hosts a corpus in violation of applicable terms, and cites only retrieved text.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a formal, structured AI Act compliance assessment report suitable for legal files, audit trails, and regulatory inquiries. This skill should be used when the user asks to "generate an AI Act report", "create a compliance assessment report", "document the AI Act analysis", "create a Prüfbericht", "export as Word document", or wants to consolidate prior AI Act skill outputs into a formal documented assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Works out which documents you have to hand over to the other side in a civil case in England & Wales, and builds the formal list. The part it gets right that trips people up is which disclosure regime applies — Practice Direction 57AD (the Disclosure Pilot, now permanent in the Business and Property Courts, with its Models A–E) or standard disclosure under CPR Part 31 everywhere else. It picks the regime, chooses a Model per issue, structures the Disclosure Review Document, and drafts the disclosure certificate for the party to sign personally. Built for litigation juniors, in-house counsel, and small teams without a precedent bank. Use when the user says 'disclosure list', 'PD 57AD', 'Model C', 'extended disclosure', 'List of Documents', 'N265', or needs to work out what must be disclosed.
日本語の概要は準備中です。原文の説明を表示しています。
Parse and extract data from Chinese identity documents for KYC (Know Your Customer) compliance. Adapts the original kyc-doc-parse skill for Chinese ID cards, business licenses, and domestic compliance requirements. Triggers on "A股KYC", "身份文件解析", "parse Chinese ID", "KYC document", "客户身份识别", or "extract [document type]".
日本語の概要は準備中です。原文の説明を表示しています。
Generate or update documentation for the AI Hero API by reading the source code at ~/repos/ai/course-builder. Use when user wants to document, update docs for, or understand the AI Hero API endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Translator development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using translate/detect/dictionary APIs, Custom Translator, glossaries, document jobs, or Docker containers, and other Azure Translator related development tasks. Not for Azure AI Language (use azure-language-service), Azure Speech in Foundry Tools (use azure-speech), Azure AI Document Intelligence (use azure-document-intelligence), Azure AI Immersive Reader (use azure-immersive-reader).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure DocumentDB development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Mongo-compatible APIs, vector search, cross-region replication, change streams, or the HTTPS Data API, and other Azure DocumentDB related development tasks. Not for Azure Cosmos DB (use azure-cosmos-db), Azure Table Storage (use azure-table-storage), Azure SQL Database (use azure-sql-database), Azure SQL Managed Instance (use azure-sql-managed-instance).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Content Understanding in Foundry Tools development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when building Content Understanding analyzers, RAG document flows, agentic workflows, REST/SDK calls, or GA migrations, and other Azure Content Understanding in Foundry Tools related development tasks. Not for Content Safety in Foundry Control Plane (use azure-content-safety), Azure Speech in Foundry Tools (use azure-speech), Azure AI Vision (use azure-ai-vision), Azure AI Document Intelligence (use azure-document-intelligence).
日本語の概要は準備中です。原文の説明を表示しています。
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain a structured LLM-generated wiki for any codebase. Use when the user asks to analyze/understand/document a codebase, build a code wiki, create project documentation from source, or update an existing .llm-wiki. Triggers on phrases like "build wiki", "analyze this codebase", "document this project", "update wiki", "llm-wiki", or when entering an unfamiliar project that has no .llm-wiki yet.
日本語の概要は準備中です。原文の説明を表示しています。
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting. Use when users request technical documentation, API docs, API references, code examples, or developer documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
日本語の概要は準備中です。原文の説明を表示しています。