「contribution」の検索結果

Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.

日本語の概要は準備中です。原文の説明を表示しています。

Assesses a research paper outline (.qmd file) against structured criteria from Kosuke Imai's empirical research guide. Evaluates the abstract and section outline for: research question clarity, stated contributions, hypotheses and testable implications, data description, planned results and inferential approach, and robustness checks. Detects causal papers from the abstract and conditionally assesses identification strategy only when causal framing is present. Produces a structured markdown report with PASS/PARTIAL/FAIL assessments and actionable suggestions. Use when asked to assess, evaluate, review, or check a paper outline, abstract-and-outline, or research plan in a .qmd file.

日本語の概要は準備中です。原文の説明を表示しています。

Writes expert academic paper summaries for social science research, particularly political science and applied statistics. Use when asked to summarize, review, or create a reading summary of an academic paper, PDF, or research article. Accepts a file (PDF or text format) or a directory of papers. Produces a structured markdown summary — approximately 400–600 words — covering primary contributions, major questions and answers with point estimates, methods and data, and limitations and robustness. Includes BibTeX citation retrieved from Google Scholar and keyword metadata.

日本語の概要は準備中です。原文の説明を表示しています。

"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.".

日本語の概要は準備中です。原文の説明を表示しています。

"Analyze unit economics to evaluate per-unit profitability and business model scalability. Use this skill when the user needs to assess whether each transaction, customer, or product unit is profitable, evaluate startup viability, or optimize contribution margins — even if they say 'does our business model work', 'what's our margin per order', or 'can we scale profitably'.".

日本語の概要は準備中です。原文の説明を表示しています。

This skill provides expert-level guidance for VS Code extension development. Use when implementing new extension features, debugging extension code, designing WebView UIs, implementing Language Server Protocol features, or optimizing extension performance. Covers activation events, contribution points, VS Code API patterns, security best practices, testing strategies, and publishing workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare an outside contribution to Pulp or Forge that a maintainer can land with minimal rework — routing (Core vs Forge), local build and test on a plain Mac, the checks that are worth running without Shipyard/Tart/VMs, and the handoff format. Use when contributing without write access or without the maintainer CI fleet.

日本語の概要は準備中です。原文の説明を表示しています。

Maintainer side of an outside contribution — find what has arrived (fork PR, issue, or patches sent out-of-band), adopt it into an in-repo branch with authorship intact, review it against the repo's bar, and ship it through the normal merge path. Use when landing work from someone without write access or without the CI fleet.

日本語の概要は準備中です。原文の説明を表示しています。

Writing biosketches that build reviewer confidence — personal statement, contributions, and honest positioning.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze franchise and multi-location unit economics including per-location P&L construction, four-wall EBITDA margins, prime cost optimization, contribution margin analysis, break-even modeling, and store-level ROI calculations.

日本語の概要は準備中です。原文の説明を表示しています。

Calculate and model paid-media CPA, CPL, CPC, CPM, ROAS, MER, break-even targets, contribution margin, LTV:CAC, impression-share opportunity, budgets, forecasts, and experiment economics. Use for PPC math, ad calculator, break-even analysis, ROAS calculator, CPA calculator, budget forecast, LTV CAC, or MER.

日本語の概要は準備中です。原文の説明を表示しています。

Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection. Use for research storytelling, contribution framing, paper comparison, figure planning, or research retrospectives. Not an acceptance predictor or a routine grammar/citation formatter.

日本語の概要は準備中です。原文の説明を表示しています。

Design the engagement model for an Experience Cloud community: reputation levels, ideation, and content contribution strategy. Triggers: 'community engagement strategy', 'gamification Experience Cloud', 'reputation levels setup', 'ideation community portal', 'member recognition program'. NOT for blocking, flagging or approving what members post — use admin/experience-cloud-moderation. NOT for measuring logins, page views or engagement after launch — use data/community-analytics-data. Also covers: the Network reputation elements that carry the ladder (enableReputation, reputationLevels/level/label/lowerThreshold, reputationPointsRules/pointsRule/eventType/points), the 16 documented reputation eventType values and their default points, ManagedTopics / ManagedTopic (Navigational vs Featured, position 0-24), NetworkMember.ReputationPoints seeding, and why FeedItem cannot carry the engagement dashboard.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect the effective Spec Kit artifact inventory and composition stacks via `specify artifact`. USE FOR: listing commands/templates/scripts/hooks, explaining which preset or extension layer supplies an artifact, inspecting resolution precedence and hidden layers, checking hook registration, or resolving a stack lookupId to its validated contribution. DO NOT USE FOR: installing or changing presets/extensions (use speckit-preset or speckit-extension), resolving only a preset-managed filename (use speckit-preset), or running an artifact.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts U.S. capital call notices for PE, VC, or fund-managed LLCs aligned to LPA/operating agreement procedures and side letters. Use when drafting a capital call notice, drawdown notice, capital contribution demand, unfunded commitment call, or LP/GP capital call letter.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly-cadence engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. NOT for per-session or per-task reflection (see mk:memory / Phase 6 Reflect).

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive workflow for contributing to open-source projects with quality checks

日本語の概要は準備中です。原文の説明を表示しています。

Expert-level volcanology covering volcanic processes, eruption styles, volcano monitoring, volcanic hazards, igneous petrology, and volcanic contributions to climate.

日本語の概要は準備中です。原文の説明を表示しています。

Use when modeling CAC, LTV, payback, contribution margin, or burn-multiple per customer — SaaS, marketplace, or transactional. Triggers on 'are we unit-economic', 'what is our LTV/CAC'.

日本語の概要は準備中です。原文の説明を表示しています。

Load this skill before implementing a fix for a barrier that may originate in a shared component, design system, renderer, or external dependency rather than this project's own code. Decide whether the responsible fix is local, an existing installed capability, or an upstream contribution before writing a workaround. Absolutely always record any temporary local divergence with an owner and removal condition. Under no circumstances open, comment on, or submit anything in an external project without explicit human approval.

日本語の概要は準備中です。原文の説明を表示しています。

[Git] Use when generating developer KPI, performance, contribution value, story point, man-day, or code-quality reports from local git commit history.

日本語の概要は準備中です。原文の説明を表示しています。

Record the statements a journal requires and a reader checks — authors with their CRediT contributions, ethics approval that names the body and the reference number, how consent was taken, funding with grant numbers, conflicts of interest, data availability with an address or a reason, and the use of generative AI — as a validated record that the submission folder prints and the manuscript never carries. Use when a run is heading for submission, when an author asks who should be listed, when consent, approval or data sharing has to be stated, or when the venue's AI policy comes up.

日本語の概要は準備中です。原文の説明を表示しています。

Search, summarize, and synthesize economics literature. find research gaps, position your contribution.

日本語の概要は準備中です。原文の説明を表示しています。