4,175 件 ・ 関連度順
概要と使いどころ
Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
日本語の概要は準備中です。原文の説明を表示しています。
Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
日本語の概要は準備中です。原文の説明を表示しています。
Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.
日本語の概要は準備中です。原文の説明を表示しています。
Design document writing conventions. Use when writing or reviewing technical design documents.
日本語の概要は準備中です。原文の説明を表示しています。
This workflow, known as RIPER-5, is designed exclusively for handling complex software engineering tasks such as system design, architectural refactoring, bug diagnosis, performance optimization, and multi-component integration.
日本語の概要は準備中です。原文の説明を表示しています。
E2E Testing Standards Guide. Use this rule when you need to write or execute E2E tests, including test naming conventions, test workflows, and test behavior templates. This rule should be used for end-to-end integration testing scenarios to ensure test standardization and maintainability. Example: When writing new E2E tests, use this rule to ensure proper test format and workflow compliance.
日本語の概要は準備中です。原文の説明を表示しています。
提交或推送前的安全检查，扫描 API Key、访问令牌等敏感信息。
日本語の概要は準備中です。原文の説明を表示しています。
OMC agent catalog, available tools, team pipeline routing, commit protocol, and skills registry. Auto-loads when delegating to agents, using OMC tools, orchestrating teams, making commits, or invoking skills.
日本語の概要は準備中です。原文の説明を表示しています。
Whenever diagrams or mermaid is mentioned
日本語の概要は準備中です。原文の説明を表示しています。
按 Conventional Commits 规范编写提交信息。在创建 git commit 时使用。
日本語の概要は準備中です。原文の説明を表示しています。
自监控指标、告警代码标准
日本語の概要は準備中です。原文の説明を表示しています。
Code review behavioral standards. Reference during code review to ensure consistent quality checks from a QA perspective.
日本語の概要は準備中です。原文の説明を表示しています。
Use when turning copy, notes, articles, or topics into customizable-length English stick-figure videos (in 10-second multiples: 30s, 60s, 3min, 5min, default 60s), kinetic line-animation explainers, motivational shorts, or Gemini Omni Flash prompt packages.
日本語の概要は準備中です。原文の説明を表示しています。
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs. Use when creating, editing, or reviewing files in the lat.md/ directory.
日本語の概要は準備中です。原文の説明を表示しています。
Search file contents using regex pattern across directories. Cross-platform pure Python implementation (no external tools needed). Returns matching lines with file paths and line numbers.
日本語の概要は準備中です。原文の説明を表示しています。
Execute shell commands for system operations, directory creation, and script execution. When you need to run system commands, execute scripts, install packages, or manage processes. Note - if commands fail consecutively, try different approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Load a newly created skill from skills/ directory to make it immediately available
日本語の概要は準備中です。原文の説明を表示しています。
Find files by glob pattern recursively. Results sorted by modification time (newest first). Auto-skips .git, node_modules and other common ignore directories.
日本語の概要は準備中です。原文の説明を表示しています。
Install skill from URL or Git repository to local skills/ directory. When you need to add new skill from GitHub or install SKILL.md from URL. Supports Git repos and single SKILL.md files.
日本語の概要は準備中です。原文の説明を表示しています。
Click page elements by CSS selector or text content. When you need to click buttons, links, or select options. PREREQUISITE - must use browser_navigate to open target page first.
日本語の概要は準備中です。原文の説明を表示しています。
A Python library for reading, writing, and analyzing geospatial vector data; use it when you need spatial operations (buffer/overlay/join), CRS reprojection, or map visualization on formats like Shapefile/GeoJSON/GeoPackage or PostGIS.
日本語の概要は準備中です。原文の説明を表示しています。
A multi-stage workflow for writing long-form medical reviews; used when the user needs to build an outline based on PubMed literature, write chapter by chapter, perform supplementary searches, and format citations; input is the review topic and project directory, output is a c...
日本語の概要は準備中です。原文の説明を表示しています。
Collects candidate biomedical literature across multiple databases, adapts search logic by database, preserves source metadata, and organizes results into a structured, screening-ready candidate pool. Always use this skill when a user wants cross-database literature collection, search strategy construction, candidate paper aggregation, or first-pass evidence organization before deduplication, screening, layered reading, or review planning. Requires real and verifiable literature records only. Every formal literature item must include a real link and DOI when available; never fabricate citations, titles, authors, years, journals, abstracts, PMIDs, or DOIs. If a DOI is unavailable or cannot be verified, state that explicitly rather than inventing one.
日本語の概要は準備中です。原文の説明を表示しています。
Detects methodological gaps across study design, analysis, validation, bias control, reproducibility, and implementation readiness within a biomedical research area. Use this skill when a user wants to identify what current studies are still methodologically missing, which weaknesses are most consequential, and what upgrade path would produce a stronger next-step study. Always separate design gaps, analysis gaps, validation gaps, and reproducibility gaps. Never treat technical complexity as methodological rigor.
日本語の概要は準備中です。原文の説明を表示しています。