3,223 件 ・ 関連度順
概要と使いどころ
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
日本語の概要は準備中です。原文の説明を表示しています。
Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never commits, never touches consent paths. Disjoint from the commit skill (Phase 11 executor): the planner proposes a split; the executor lands one consented commit. Use when a working tree has accumulated heterogeneous changes that should not land as one commit.
日本語の概要は準備中です。原文の説明を表示しています。
Marc Andreessen-mode decision and productivity skill. A blunt, market-first operator that pressure-tests ideas, ventures, features, and career bets through Andreessen's actual frameworks — market dominates team and product; the only milestone that matters is product/market fit; bias to build over deliberate. Use when the user says 'andreessen', 'pmarca mode', 'should I build this', 'is there a market', 'are we at product/market fit', 'pmf check', 'pressure-test this idea', 'be brutal about this venture', 'market-first take', or wants a no-disclaimers, no-hedging, confidence-leveled verdict on whether something is worth pursuing. Also provides the 3x5-card + Anti-Todo personal productivity routine. Runs on a fixed anti-sycophancy operating prompt: leads with the strongest counterargument, never validates premises, uses explicit confidence levels, never apologizes for disagreeing. Not for polite brainstorming — this skill exists to tell you the market is dead when it is.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise comparison, position bias, evaluation pipelines, or automated quality assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
日本語の概要は準備中です。原文の説明を表示しています。
Replace this with a precise trigger description. State the Amazon PPC workflow, user intent, required data, and when Codex or Claude should use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use for prioritization, or when there are more tasks than capacity: "what should we do first?", "rank this backlog", "cut scope for the MVP", "RICE score these". Picks a method (RICE, ICE, MoSCoW, impact-effort), scores items and sets a cut line. Skip for choosing between two designs.
日本語の概要は準備中です。原文の説明を表示しています。
Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Use for first principles thinking, or when the user questions an inherited default: "why do we do it this way?", "is this cost really necessary?", "should we copy what competitors do?". Strips analogies and rebuilds from fundamentals. Skip for convention-following checklists.
日本語の概要は準備中です。原文の説明を表示しています。
Use for ethical thinking, or when a plan could harm or unfairly burden people: "should we do this?", "is this fair?", "privacy or bias risk", "who gets hurt?". Maps stakeholders, harms, power and consent. Skip for legal advice, neutral fact lookups and implementation-only work.
日本語の概要は準備中です。原文の説明を表示しています。
Use for SWOT analysis, or when the user wants to assess where a team, product or company stands: "strengths and weaknesses", "should we enter this market?", "review our position", "competitor comparison". Turns findings into actions. Skip for detailed planning or pure market sizing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user describes a problem, decision or stuck situation but names no method: "how should I approach this?", "help me think this through", "we can't decide", "where do I start?". Picks the best-fit thinking method and runs it. Skip for plain execution tasks or when a method is named.
日本語の概要は準備中です。原文の説明を表示しています。
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
日本語の概要は準備中です。原文の説明を表示しています。
Pressure-test an existing plan or design artifact until it is coherent enough for the next workflow step or plainly blocked. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, rolling-wave project shape, or slice contract; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.
日本語の概要は準備中です。原文の説明を表示しています。
Mark a rolling-wave slice done on explicit user authority, regardless of its current lifecycle status or missing implementation, finalization, review, verification, or child-project state. Use when the user says a slice is done, complete, finished, accepted, or should be marked done; capture available material learnings, update project state, and output roadmap progress without requiring earlier workflow steps.
日本語の概要は準備中です。原文の説明を表示しています。
Create or maintain a source-grounded kpopper knowledge model as a versioned plugin. Use when a reusable domain model should ship independently of any one project.
日本語の概要は準備中です。原文の説明を表示しています。
Generates an experiment-overview snapshot of all research questions under research/reports/. Invoke when a new point-in-time report across all RQs should be produced.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "scrub JSON values", "mask config fields", "add a Git clean filter", "remove volatile values from tracked config", or "stop config churn".
日本語の概要は準備中です。原文の説明を表示しています。
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
日本語の概要は準備中です。原文の説明を表示しています。
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。