6,444 件 ・ 関連度順
Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", "Research similar trials for [intervention]", or when developing FDA submission documentation for investigational products.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture quality critique dimensions for peer review. Load when invoking solution-architect-reviewer or performing self-review of architecture documents.
日本語の概要は準備中です。原文の説明を表示しています。
Critique dimensions and scoring for research document reviews
日本語の概要は準備中です。原文の説明を表示しています。
Architecture quality critique dimensions for peer review. Load when performing architecture document reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Type-specific validation checklists, six quality characteristics, and quality gate thresholds for documentation assessment
日本語の概要は準備中です。原文の説明を表示しています。
Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing.
日本語の概要は準備中です。原文の説明を表示しています。
Agent safety boundaries - input validation, output filtering, scope constraints, and document creation policy
日本語の概要は準備中です。原文の説明を表示しています。
Critique dimensions, severity framework, verdict decision matrix, and review output format for documentation assessment reviews
日本語の概要は準備中です。原文の説明を表示しています。
DIVIO/Diataxis four-quadrant documentation framework - type definitions, classification decision tree, and signal catalog
日本語の概要は準備中です。原文の説明を表示しています。
Documentation collapse anti-patterns - detection rules, bad examples, and remediation strategies for type-mixing violations
日本語の概要は準備中です。原文の説明を表示しています。
Shared density-resolution contract for wave skills. Canonical detail on the D12 cascade, density resolver call, ad-hoc override workflow, and DocumentationDensityEvent telemetry emission. Referenced from nw-discover / nw-discuss / nw-design / nw-devops / nw-distill / nw-deliver.
日本語の概要は準備中です。原文の説明を表示しています。
BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation
日本語の概要は準備中です。原文の説明を表示しています。
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "organize the project rules", "clean up scattered documentation", "把规则迁移到 skills 目录", "优化 skill 路由", "提高 description 命中率", or "减少薄壳重复维护". Activate when a SKILL.md is too large, rules are duplicated across agent entry files, task routing or trigger_examples miss natural user language, or templates / thin shells / validation scripts need drift-resistant maintenance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when brand VISUAL rules have to be created or updated — brand personality, color system, typography, logo usage, imagery and visual tone, component rules, accessibility contrast, standard asset sizes, and file naming. It is the source document every design skill and the Brand Hub reads. Trigger on 'brand guideline', 'brand book', 'style guide', 'brand standards', 'our designs all look different', 'update the brand palette'. Also use when the user has a logo and nothing written down. Not for — how the brand SOUNDS in writing, see `35-brand-voice-global`; positioning and the message, see `58-positioning-global`; briefing one asset, see `42-image-brief-global`; scoring a design, see `47-design-review-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to define, document, or enforce how the brand SOUNDS in writing — three personality traits, a five-dimension tone table, vocabulary to use, avoid, and ban, sentence rules, before and after rewrites, platform adaptation, and a copy approval checklist. Every content skill reads it before writing. Trigger on 'brand voice', 'tone of voice', 'voice guidelines', 'banned words list', 'this copy does not sound like us', 'every writer sounds different'. Also use when the user cannot say why a draft feels wrong. Not for — the visual side of brand, see `46-brand-guideline-global`; positioning and the message, see `58-positioning-global`; approving one specific piece, see `62-marketing-review-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use for 小北在读研 / XiaoBei academic paper-to-PPT workflows: generate thesis-defense or project-report decks from uploaded papers, literature, reports, technical documents, and optional PPTX visual templates. Produces a source-grounded outline, an imagegen visual scheme, one complete bitmap per slide, an imagegen provenance manifest, and an image-only PPTX. Do not use when the user needs editable slide text or native editable charts.
日本語の概要は準備中です。原文の説明を表示しています。
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
日本語の概要は準備中です。原文の説明を表示しています。
Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.
日本語の概要は準備中です。原文の説明を表示しています。
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language. Use when the user asks to generate a changelog, write release notes, summarize recent commits, prepare CHANGELOG.md, or document what changed between versions.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate questions using high-trust primary sources and traceable citations. Use when the user asks for research, current documentation or API facts, source verification, or evidence-backed comparison.
日本語の概要は準備中です。原文の説明を表示しています。
Configure repository-local tracker, triage, and domain-document conventions needed by the Matt Pocock engineering skills.
日本語の概要は準備中です。原文の説明を表示しています。