281 件 ・ 関連度順
概要と使いどころ
Review the changed code for reuse, simplification, efficiency and altitude cleanups in this repository, then apply the fixes. Quality only — it does not hunt for bugs; use /code-review for that. The method, its scripts and its cases live in this directory, so the skill works without any user-level skill pack.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.
日本語の概要は準備中です。原文の説明を表示しています。
Docker best practices: image security, build efficiency, runtime hardening, Compose, local tooling (Colima, OrbStack). Use when writing or reviewing Dockerfiles and Compose files.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes event-driven opportunities with catalyst identification, pricing efficiency assessment, and risk/reward evaluation. Use when analyzing event-driven situations, evaluating catalysts, or assessing event timing.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes special dividend catalysts with balance sheet capacity, tax efficiency, and shareholder return comparison analysis. Use when modeling special dividends, evaluating capital return catalysts, or assessing dividend capacity.
日本語の概要は準備中です。原文の説明を表示しています。
Structures 100-day and long-term value creation plans with revenue growth, margin improvement, and capital efficiency initiatives. Use when building value creation plans, tracking improvement initiatives, or preparing operating partner reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates transportation assets with ridership analysis, fare structure assessment, and operating efficiency benchmarking. Use when analyzing transportation projects, evaluating mass transit, or assessing toll road economics.
日本語の概要は準備中です。原文の説明を表示しています。
Deconstructs unit economics with CAC, LTV, payback period, gross margin, and contribution margin analysis. Use when analyzing unit economics, validating SaaS metrics, or assessing business model efficiency.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates and scores Claude prompts and system prompts using a six-dimension Scorecard with anchored 1-5 rubrics. Trigger on: "review my prompt," "score this prompt," "rate my prompt," "evaluate this prompt," "improve my prompt," "what's wrong with my prompt." Also trigger on: "why isn't my prompt working," "my prompt produces bad output," "help me fix this prompt," "is this prompt any good." Scorecard covers Objective Clarity, Context Specificity, Reasoning Fit, Output Precision, Behavioral Calibration, and Architectural Efficiency, plus a five-question Output Evaluation Rubric for assessing actual output. Also use when the user pastes a system prompt and asks for feedback. Activate whenever structured quality assessment of a single prompt is the primary need. Do NOT use for project-level audits involving Custom Instructions architecture, knowledge file organization, or multi-file Project structure (use rootnode-project-audit if available).
日本語の概要は準備中です。原文の説明を表示しています。
Review user experience and interface design using Nielsen's heuristics, WCAG 2.1 accessibility guidelines, keyboard and screen reader audit, user flow analysis, cognitive load assessment, and form usability evaluation. Use when conducting a usability review before release, assessing WCAG 2.1 accessibility compliance, evaluating user flows for efficiency, reviewing form design, or performing a heuristic evaluation of an existing interface.
日本語の概要は準備中です。原文の説明を表示しています。
Design practical electromagnetic devices including electromagnets, DC and brushless motors, generators, and transformers by bridging theory to application. Use when sizing a solenoid or toroidal electromagnet for a target field or force, selecting motor topology and computing torque and efficiency, designing a transformer for a given voltage ratio and power rating, or analyzing losses from copper resistance, core hysteresis, and eddy currents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to optimize code, make a path faster, make this as fast as possible, reduce allocations, repair a regression, profile a target, grill every inefficiency, or run a subsystem or repo-wide performance campaign against a measured floor; when a performance requirement, slowness report, Core Web Vitals miss, or profiling evidence identifies a bottleneck; or for an "extremely optimize" performance campaign, optimizing suspected hot paths without waiting for benchmarks, or estimating hot and complexity-neutral cold paths while refusing complexity theater. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Structure-based docking with AutoDock Vina, Vinardo, and AutoDock4 through the Meeko toolchain. Use this skill to define a docking box, prepare receptors and ligands as PDBQT, run single or batch docking, rescore, and interpret affinities, poses, and ligand efficiency. Covers box definition from a reference ligand or pocket residues, protonation and tautomer decisions, flexible side chains, exhaustiveness and seeds, redocking validation, and virtual screening over compound libraries. Also trigger on vina, smina, gnina, mk_prepare_ligand, mk_prepare_receptor, mk_export, scrub.py, PDBQT, autogrid4, docking box, or binding-pose prediction.
日本語の概要は準備中です。原文の説明を表示しています。
Clean up a diff for reuse, simplicity and efficiency, then apply the fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when optimizing token usage, KV cache efficiency, or context window management for LLM agents. Keywords: context optimization, KV cache, prompt caching, token budget, semantic pruning, lost-in-the-middle.
日本語の概要は準備中です。原文の説明を表示しています。
Expert prompt engineer specializing in designing, optimizing, and managing prompts for large language models. Masters prompt architecture, evaluation frameworks, and production prompt systems with focus on reliability, efficiency, and measurable outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Institutional Theory (DiMaggio and Powell, 1983) to analyze how coercive, mimetic, and normative isomorphic pressures shape organizational structures and practices. Use this skill when the user needs to explain why organizations in the same field look alike, evaluate whether a practice was adopted for legitimacy vs efficiency, analyze regulatory or social pressures on strategy, or when they ask 'why do all firms in this industry do the same thing', 'is this best practice or just conformity', or 'how do regulations shape our structure'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Efficient Market Hypothesis (Fama, 1970) to evaluate information incorporation in asset prices across weak, semi-strong, and strong forms. Use this skill when the user needs to assess market efficiency, determine if a trading strategy can generate abnormal returns, evaluate event studies, or when they ask 'can technical analysis work', 'does the market already know this', or 'is this anomaly exploitable'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply organizational ambidexterity theory to balance exploration and exploitation activities. Use this skill when the user needs to diagnose whether an organization is over-exploiting or over-exploring, design structures that support both innovation and efficiency, or evaluate the tension between short-term performance and long-term renewal.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Lean and Six Sigma principles to eliminate waste and reduce process variation. Use this skill when the user needs to improve operational efficiency, identify the seven wastes (TIMWOOD), run DMAIC improvement projects, or streamline workflows — even if they say 'our process is too slow', 'where are we wasting resources', or 'how do we reduce defects'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply DuPont Analysis to decompose Return on Equity (ROE) into profitability, efficiency, and leverage components. Use this skill when the user needs to diagnose why ROE is high or low, compare financial performance drivers across companies, or identify which operational lever to pull — even if they say 'why is our ROE declining' or 'how do we improve returns'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze financial health using ratio categories: profitability, liquidity, leverage, efficiency, and valuation. Use this skill when the user needs to assess a company's financial performance, compare companies, evaluate creditworthiness, or prepare financial due diligence — even if they say 'is this company financially healthy', 'analyze these financial statements', or 'compare these two companies'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze supply chain operations using the SCOR model across Plan, Source, Make, Deliver, and Return processes. Use this skill when the user needs to optimize supply chain efficiency, evaluate supplier performance, improve logistics, or design an end-to-end supply chain strategy — even if they say 'our deliveries are slow', 'supply chain costs are too high', or 'we keep running out of stock'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Calculate and analyze Customer Acquisition Cost (CAC) and Customer Lifetime Value (LTV) to evaluate unit economics and marketing efficiency. Use this skill when the user needs to assess whether their customer acquisition is profitable, optimize marketing spend allocation, or evaluate business model viability — even if they say 'are we spending too much on ads', 'what's each customer worth', or 'is our growth sustainable'.".
日本語の概要は準備中です。原文の説明を表示しています。