3,384 件 ・ 関連度順
概要と使いどころ
Review touched Incan source for Python-quality readability, idiomatic Incan structure, dogfooding integrity, public API polish, and source-level anti-patterns. Use for `.incn` stdlib, examples, language-surface implementations, or when the user asks whether Incan code reads like well-written Python rather than Rust-shaped scaffolding.
日本語の概要は準備中です。原文の説明を表示しています。
Medical/scientific paper writing workflow skill. Manages the full pipeline from literature search to submission-ready manuscript. Creates and manages a project directory with IMRAD-format section files, literature matrix, reference management, and quality checklists. Supports both English and Japanese papers. Triggers: 'write paper', 'paper-write', 'start manuscript', '論文を書く', '論文執筆', '論文プロジェクト', 'manuscript', 'research paper', '原稿作成'.
Use when auditing CRM data quality, finding duplicate records, identifying stale leads, cleaning pipeline data, or improving data hygiene. Triggers: 'clean my CRM', 'audit CRM data', 'find duplicates', 'CRM hygiene', 'data quality check', 'stale leads', 'pipeline cleanup'.
日本語の概要は準備中です。原文の説明を表示しています。
Convert deep research output (Claude Research, ChatGPT Deep Research, Gemini, Codex — any long-form MD/Word/text) into a consulting-quality HTML report: pyramid structure, numbers promoted to KPIs/charts, comparisons turned into framework tables, citations preserved. Use when the user provides research/investigation results and says レポートにして/HTMLにまとめて/資料にして/きれいにして, mentions ディープリサーチの結果/調査結果/リサーチ結果, or asks to research a topic AND deliver a report. NEVER invents numbers or facts not present in the source (盛らない原則).
Discover and install agent skills from the open ecosystem (skills.sh), optimized for Japanese users. Use when the user asks 'how do I do X', 'is there a skill for X', or in Japanese 「〜できる？」「〜のスキルある？」「スキルを探して」「〜を自動化したい」「〜を効率化したい」. Always converts Japanese intent into short English search keywords before searching (the registry matches English keywords only), and verifies skill quality and safety before recommending installation.
上线放行决策 / 阻断不达标交付时使用。适用于版本发布前门禁、CI/CD 自动门禁、阶段性质量评估。融合 SonarQube Quality Gate、DORA Change Failure Rate、Google Beyoncé Rule。
日本語の概要は準備中です。原文の説明を表示しています。
[Deprecated] quality gate now covers tests + canary. Use `cm-quality-gate` instead.
日本語の概要は準備中です。原文の説明を表示しています。
[Deprecated] quality gate now covers tests + canary. Use `cm-quality-gate` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a skill isn't triggering as expected, before adding a new skill (to check for a name collision), during periodic cleanup of an accumulated skills directory, or when asked to review skill quality — checks frontmatter validity, description quality against Skill Discovery Optimization conventions, body size, and cross-scope name collisions.
日本語の概要は準備中です。原文の説明を表示しています。
Score deep research agents on benchmark tasks using factual verification, report-quality scoring, and process evaluation before model or workflow changes ship.
日本語の概要は準備中です。原文の説明を表示しています。
Generates render and output configuration for Remotion videos. Focuses ONLY on output settings, codec, format, quality, resolution. Input is target platform/quality requirements. Output is RENDER_CONFIG.md with Remotion render settings.
日本語の概要は準備中です。原文の説明を表示しています。
Structured review process for Remotion video implementations. Analyzes spec compliance, detects common timing/easing issues, validates asset quality, and provides prioritized revision lists. Use when reviewing Remotion code against design specs or performing quality assurance on video compositions. Trigger phrases "review video code", "check spec compliance", "audit Remotion implementation".
日本語の概要は準備中です。原文の説明を表示しています。
Architect a feature with the Carmack Council before writing code. Use when explicitly asked to plan a feature, do a "council plan", "carmack plan", or invoke /council-plan. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js), Brandur Leach (Postgres), Vercel Performance, Simon Willison (LLM pipeline), Karri Saarinen (UI quality), Vitaly Friedman (UX quality). Interactive feature discovery followed by parallel subagent dispatch. Produces a sequenced, attributed implementation plan with no code. Stack: Next.js App Router / React / TypeScript / tRPC / Prisma / Neon / Clerk.
日本語の概要は準備中です。原文の説明を表示しています。
Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write test specs for new code). Powered by Carmack × Beck quality-testing.md reference doc. Stack: Next.js App Router / TypeScript / Vitest / Cypress / tRPC / Prisma / Neon.
日本語の概要は準備中です。原文の説明を表示しています。
Apply modern web development best practices for security, compatibility, and code quality. Use when the task involves `apply best practices`, `security audit`, `modernize code`, `code quality review`, or `check for vulnerabilities`.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive SEO analysis for any website or business type. Performs full site audits, single-page deep analysis, technical SEO checks (crawlability, indexability, Core Web Vitals with INP), schema markup detection/validation/generation, content quality assessment (E-E-A-T framework per Dec 2025 update extending to all competitive queries), image optimization, sitemap analysis, and Generative Engine Optimization (GEO) for AI Overviews, ChatGPT, and Perplexity citations. Analyzes AI crawler accessibility (GPTBot, ClaudeBot, PerplexityBot), llms.txt compliance, brand mention signals, and passage-level citability. Industry detection for SaaS, e-commerce, local business, publishers, agencies. Triggers on: "SEO", "audit", "schema", "Core Web Vitals", "sitemap", "E-E-A-T", "AI Overviews", "GEO", "technical SEO", "content quality", "page speed", "structured data".
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate user-facing interfaces against Nielsen's 10 Usability Heuristics. Complements /mycelium:service-check (Downe = service-level quality, Nielsen = interface-level quality).
日本語の概要は準備中です。原文の説明を表示しています。
Apply MCAF non-functional-requirements guidance to capture or refine explicit quality attributes such as accessibility, reliability, scalability, maintainability, performance, and compliance. Use when a feature or architecture change needs explicit quality attributes and trade-offs.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".
日本語の概要は準備中です。原文の説明を表示しています。
Structures credit underwriting with financial ratio analysis, cash flow quality assessment, and downside scenario modeling. Use when underwriting credit, analyzing borrower quality, or writing credit opinions.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses underlying asset pools with stratification, concentration analysis, historical performance, and credit quality distribution. Use when analyzing collateral pools, stratifying asset characteristics, or evaluating pool quality.
日本語の概要は準備中です。原文の説明を表示しています。
Measures implementation shortfall with paper portfolio comparison, delay cost attribution, and execution quality assessment. Use when measuring implementation shortfall, analyzing execution quality, or attributing trading costs.
日本語の概要は準備中です。原文の説明を表示しています。
Rates responses and plans against quality rubrics. Used for plan validation, response quality audits, and multi-agent consensus.
日本語の概要は準備中です。原文の説明を表示しています。
QA validation and fix loop workflow — validates implementation completeness then iterates fix cycles until all acceptance criteria pass and quality gates clear
日本語の概要は準備中です。原文の説明を表示しています。