'contributions' 검색 결과

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"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.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds a compact profile of a GitHub user or PR author — identity, activity, company, commit history, and trust signals. Use during pull request review or triage, especially for contributions from unfamiliar authors.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

We, like many other open source projects, are dealing with a surge in low quality contributions enab

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Complete guide to using and extending Hermes Agent — CLI usage, setup, configuration, spawning additional agents, gateway platforms, skills, voice, tools, profiles, and a concise contributor reference. Load this skill when helping users configure Hermes, troubleshoot issues, spawn agent instances, or make code contributions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Complete guide to using and extending Hermes Agent — CLI usage, setup, configuration, spawning additional agents, gateway platforms, skills, voice, tools, profiles, and a concise contributor reference. Load this skill when helping users configure Hermes, troubleshoot issues, spawn agent instances, or make code contributions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.