3,488 件 ・ 関連度順
概要と使いどころ
Generates publication-quality figures for ML papers from research context. Given a paper section or description, extracts system components and relationships to generate architecture diagrams via Gemini. Given experiment results or data, auto-selects chart type and generates data-driven figures via matplotlib/seaborn. Use when creating any figure for a conference paper.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate research rigor. Assess methodology, experimental design, statistical validity, biases, confounding, evidence quality (GRADE, Cochrane ROB), for critical analysis of scientific claims.
日本語の概要は準備中です。原文の説明を表示しています。
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a PR or feature needs both specification and code-quality review
日本語の概要は準備中です。原文の説明を表示しています。
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review
日本語の概要は準備中です。原文の説明を表示しています。
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates
日本語の概要は準備中です。原文の説明を表示しています。
Expert multi-AI code review with inline PR comments — use for thorough quality and security analysis
日本語の概要は準備中です。原文の説明を表示しています。
Review of a PR, branch, or your own uncommitted work across eight dimensions — security, correctness, test coverage, API/compatibility, usability, documentation, code quality, performance. Sizes the diff, reviews inline or fans out reviewers off a shared brief, verifies findings against code, reports a grouped list with a shape verdict, fixes on approval. Use for "review this PR", "/pr-review 3011", or a pre-flight self-review before submitting; add "thorough" for adversarial verification.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-writer + python-architect + editorial-owner + growth-hacker loop to produce a patch-ready advisory. Does NOT review code quality, security, or test coverage. Does NOT auto-merge or auto-push doc edits.
日本語の概要は準備中です。原文の説明を表示しています。
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and writing with quantitative scoring and actionable feedback.
日本語の概要は準備中です。原文の説明を表示しています。
Add, revise, or review Marin tests for an explicit behavior change, regression, or test-quality request.
日本語の概要は準備中です。原文の説明を表示しています。
Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits the journey from the SERP click to the on-page goal: click-through factors (title, meta, rich results), then post-click signals that keep users and drive conversions: above-the-fold relevance and intent match, page speed / Core Web Vitals, readability, clear CTAs, mobile usability, and what causes pogo-sticking back to Google. Use when the user has decent rankings but poor CTR or poor on-page conversion, wants better dwell time / engagement, less bounce, or a page experience aligned with search intent. Trigger on: "SXO", "search experience optimization", "good rankings but low CTR", "high bounce rate from search", "pogo-sticking", "improve dwell time", "SEO and conversion", "ranking but not converting", "engagement signals", "make this page convert search traffic". For pure landing-page conversion in ads use /google-ads-landing; for content quality use /seo-page.
日本語の概要は準備中です。原文の説明を表示しています。
Audit, diagnose, plan, and safely operate connected LinkedIn Ads accounts through the NotFair MCP, with an export-based fallback. Use for LinkedIn advertising, sponsored content, lead-generation forms, job-title or company targeting, campaign groups, creatives, conversions, lead quality, budgets, bids, or approved LinkedIn campaign changes.
日本語の概要は準備中です。原文の説明を表示しています。
Image SEO audit — make a site's images discoverable in Google Images and stop them from dragging down Core Web Vitals. Audits alt text quality and coverage, descriptive file names, modern formats (WebP/AVIF), dimensions and compression, responsive srcset, lazy-loading, explicit width/height (CLS), image sitemaps, and ImageObject structured data. Use this skill whenever the user asks about image SEO, alt text, Google Images ranking, image optimization for search, image file size hurting page speed, WebP/AVIF, or image structured data. Trigger on: "image SEO", "alt text", "rank in Google Images", "optimize my images for search", "image alt tags", "WebP", "image compression SEO", "image sitemap", "ImageObject schema", or any image-discoverability / image-performance question. For overall page speed use /seo-analysis; for generating new images use the brand image skills.
日本語の概要は準備中です。原文の説明を表示しています。
Code quality checks, formatting, and metrics via qlty CLI
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user asks for a PowerPoint presentation, a .pptx file, or slides for a talk/pitch/report — creating a new deck from scratch, editing an existing .pptx, or reading/summarizing an existing deck's content. Covers slide layout, color/typography choices, and a content-quality checklist for professional-looking output. Does not cover rendering slides to images for visual QA (see the 'Not supported' section).
日本語の概要は準備中です。原文の説明を表示しています。
统筹兼顾：当多个目标、指标或利益方相互制约、优化一项会伤害另一项时，识别全部辩证关系对，检查片面性，为每对关系定出当前阶段的侧重与底线，评估系统性影响，并设失衡预警。触发信号包括 trade-off、目标冲突、速度 vs 质量、短期 vs 长期、"顾此失彼"；只有单一目标、用户已定取舍、或属硬性二选一时不触发。 English: Overall planning. When several goals, metrics, or stakeholders constrain each other and optimizing one harms another, map every dialectical pair, check for one-sidedness, set the current emphasis and floor for each pair, assess system-wide effects, and define imbalance alarms. Triggers include trade-offs, goal conflicts, speed vs quality, short vs long term; skip for single-goal work, decisions the user already made, or hard either/or constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
日本語の概要は準備中です。原文の説明を表示しています。
发布前质量关卡：合规风险检测（敏感词、绝对化用语、平台规则） + 产物质量审核（完整性、可读性、平台适配度）。一次检查，两道把关。 当用户说"检查合规"、"质量检查"、"能不能发"、"有没有敏感词"、 "审核一下"、"发布前检查"、"质量够不够"时使用。 合并了原 skill-check-compliance 和 skill-review-deliverable 的能力。
日本語の概要は準備中です。原文の説明を表示しています。
平台原生搜索流量优化：把内容做成能被平台搜索到的样子。 校验并优化标题/正文关键词布局、话题标签搜索权重、封面/首帧文字关键词、 搜索流量 vs 推荐流量的取舍。覆盖小红书、抖音、知乎、公众号、B站、微博。 当用户说"SEO 检查"、"搜索优化"、"关键词布局"、"搜不到我的内容"、 "怎么被搜到"、"话题标签怎么选"、"搜一搜优化"、"发布前校验"时使用。 网页/博客的 Meta/OG/Slug/E-E-A-T 校验作为可选模式保留（见 references）。
日本語の概要は準備中です。原文の説明を表示しています。
Audit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write). Agents must discover the docs themselves, install deps, ask for credentials if needed, and attempt real execution. The skill captures each agent's trace — tool calls, retries, wall time, errors — and scores on Setup Friction, Speed, Efficiency, Error Recovery, and Doc Quality, then emits an HTML report with an A–F grade and concrete fixes. Use when the user asks to audit agent experience, test a skill, audit docs for agents, check if a SDK is agent-friendly, validate a SKILL.md, measure agent DX, or benchmark how painful onboarding is for an AI agent. Triggers: 'audit agent experience', 'test this skill', 'audit docs for agents', 'is my SDK agent-friendly', 'run a DX audit', 'agent experience test', 'test my docs', 'how do agents do with my product'.
日本語の概要は準備中です。原文の説明を表示しています。
Review chart choice, labeling, accessibility, and storytelling quality for existing visualizations. Use as an explicit/manual helper for critique and cleanup, not as the main owner for scientific figure production or general chart generation.
日本語の概要は準備中です。原文の説明を表示しています。