1,024 件 ・ 関連度順
概要と使いどころ
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
日本語の概要は準備中です。原文の説明を表示しています。
Premium UI/UX design audit and refinement skill. Conducts systematic visual audits of existing apps and produces phased, implementation-ready design plans. Use this skill whenever the user asks to audit a UI, improve an app's visual design, make an interface feel more polished or premium, review design consistency, fix visual hierarchy, or refine spacing/typography/color. Also trigger when the user says "design review", "make it look better", "UI polish", "visual refinement", "design pass", "audit the design", or references making an app feel more professional. This skill is purely visual — it does not touch functionality, logic, or features. It elevates what exists.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a spec or requirements for a multi-step task, before touching code
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a written implementation plan to execute in a separate session with review checkpoints
日本語の概要は準備中です。原文の説明を表示しています。
Use when a bounded Yardlet task needs a concrete implementation plan before code changes
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, or review the dygo framework CLI in Go with Cobra. Use for commands, flags, help, prompts, plans, output contracts, completion, and project-aware CLI behavior. Do not use for operating a deployed business through the reserved dygo-cli operator skill.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
日本語の概要は準備中です。原文の説明を表示しています。
Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.
日本語の概要は準備中です。原文の説明を表示しています。
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Create concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.
日本語の概要は準備中です。原文の説明を表示しています。
Ground GEODE design and evaluation work in Stanford CS329A Parts 2 and 5. Use for test-time compute, planning, multi-step reasoning, deep research, LATS, independent subplans, best-of-N, repair depth, measurement replication, verifier authority, and GEODE/Eco²/SIL/Crucible comparisons.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares jurisdiction-specific charitable solicitation registration packages for U.S. nonprofits. Covers multi-state nexus analysis, exemption eligibility, URS filing strategy, financial disclosures, and professional fundraiser documentation. Use when a nonprofit plans fundraising campaigns, online donation drives, direct mail, telephone solicitation, or any cross-state charitable solicitation.
日本語の概要は準備中です。原文の説明を表示しています。
Produces structured U.S. legal audit summaries that distill compliance findings into executive-ready risk prioritization and remediation plans, covering likelihood/impact scoring, consequence analysis, and corrective actions with timelines and owners. Use for legal audits, compliance audits, regulatory audits, compliance gap analyses, risk assessments, audit report summaries, or remediation roadmaps. Trigger keywords: audit summary, compliance findings, audit report, risk prioritization, remediation plan, regulatory exposure, corrective action plan.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts an asbestos abatement plan compliant with OSHA 29 CFR 1926.1101 and EPA NESHAP 40 CFR 61 Subpart M. Extracts facility details from uploaded surveys and contractor documents to produce a regulatory filing and operational guide. Use when preparing pre-abatement regulatory submissions, contractor work plans, or facility owner compliance documentation for asbestos removal projects.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a post-judgment asset and enforcement report synthesizing debtor asset investigations, exemption analysis, fraudulent transfer assessment, and prioritized collection strategies. Use when preparing judgment enforcement plans, debtor asset profiles, collection status reports, or post-trial recovery analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ticket complexity and dependencies against the codebase before sprint planning. NOT for writing plans (mk:plan-creator); NOT for scope review (mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Structured multi-file implementation plans before build; scope-aware, enforces Gate 1. NOT for ticket sizing (mk:planning-engine) or plan CEO-review (mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Structured second-pass reasoning after a review or plan verdict: pre-mortem, inversion, red team, Socratic lens, etc. NOT for initial review (mk:review) or new plans (mk:plan-creator).
日本語の概要は準備中です。原文の説明を表示しています。
Workflow navigator: scans project state (plans, reviews, tests, git) and recommends the next pipeline step. Use for 'what next?' or 'where am I?'. NOT for complexity routing (mk:scale-routing).
日本語の概要は準備中です。原文の説明を表示しています。
Serve a markdown file/directory as a calm, book-like reader via a local HTTP server (127.0.0.1 only); good for long-form docs like RFCs and plans. Supports Mermaid, dark/light mode, and a nav sidebar.
日本語の概要は準備中です。原文の説明を表示しています。
Answer factual project questions (codebase, architecture) with cited evidence. NOT for brainstorming, trade-offs (mk:party), debugging (mk:investigate), review (mk:review), or plans (mk:plan-creator).
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Use when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).
日本語の概要は準備中です。原文の説明を表示しています。