Research & Learning skills

発明相談、論文投稿前確認、共同出願、ライセンス可能性を知財担当へ渡すために初期整理する

The English summary is being prepared. Showing the original description.

研究評価指標（論文数、被引用数、h-index等）の収集・分析を行う

The English summary is being prepared. Showing the original description.

研究成果のプレスリリース、研究紹介、Web掲載、取材対応、英文概要の初稿と確認フローを作る

The English summary is being prepared. Showing the original description.

政策動向、研究力分析、公募情報、学内資源を統合し部局・研究グループ向けの研究戦略メモを作る

The English summary is being prepared. Showing the original description.

Continuous learning framework — learn from work, organize knowledge, build feedback loops. Use when: recording lessons, organizing knowledge, or setting up learning systems that persist across sessions.

The English summary is being prepared. Showing the original description.

Relentless delivery mode for complex, multi-step tasks. Use when: multi-file features, unclear root cause debugging, multi-angle research, architecture decisions with trade-offs. Activates parallel subagent dispatch and strict verification.

The English summary is being prepared. Showing the original description.

Write an analytical longform piece — a 4-phase pipeline from raw idea to finished text, with research-backed facts and a devil's-advocate pass before publishing. Invoke /longread <topic>. Triggers — "write a longread about X", "write an analytical breakdown of Y", "write an expert post", "turn this into an article".

The English summary is being prepared. Showing the original description.

Teacher mode — turn a session recap / article / docs / concept / piece of code / bug into an incremental mini-course with comprehension checks, quizzes, and an auto-saved summary note. Invoke /teach [topic or URL]. Triggers — "explain it like a teacher", "walk me through what we did", "turn this into a lesson", "quiz me", "teach me", "let's learn this together".

The English summary is being prepared. Showing the original description.

Bootstrap self-improving Symphony + Linear orchestration for a software repository. Use when Codex needs to inspect a repo, review or generate repo-local guidance, shape Linear issues, render a Symphony workflow, launch a high-leverage first execution wave, or run an orchestrator-led review, recovery, and learnings loop that makes future runs better.

The English summary is being prepared. Showing the original description.

Research process for comparing frontier harnesses (Claude Code, Codex, OpenClaw, autoresearch, Prime Agent) with the original/upstream implementation and performing GAP analysis before feature implementation. Triggered by "research" ("리서치"), "gap", "frontier", "harness", "case study" ("사례 조사"), "pattern exploration" ("패턴 탐색"), "comparative analysis" ("비교 분석") keywords.

The English summary is being prepared. Showing the original description.

Evidence-first multi-step research with bounded parallel collection, contradiction checks, and cited synthesis.

The English summary is being prepared. Showing the original description.

Ingest GEODE research/knowledge into the mango-wiki Obsidian vault (render + sync).

The English summary is being prepared. Showing the original description.

Auto-search and summarize latest AI/agent papers.

The English summary is being prepared. Showing the original description.

Root-causes one specific mistake the agent just made, such as not committing despite instructions to, by checking it against the loaded AGENTS.md, CLAUDE.md, skills, and Beads memories, delegating the investigation to a separate agent where the harness supports one; proposes concrete context improvements, and lets the user choose which to apply and how to remediate. Use when the user invokes `/learn` or `$learn`, with or without a description of the mistake, including `/learn /qs`-style shorthand naming the corrective command. For a broad end-of-session documentation sweep, use `documentation-updates` (`/reflect`) instead.

The English summary is being prepared. Showing the original description.

Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.

The English summary is being prepared. Showing the original description.

Researches and compares free and open source software projects in a supplied domain, using either user-named candidates or a discovered shortlist. Use when evaluating FOSS alternatives, comparing GitHub popularity, maintenance, licences, domain fit, trade-offs, or producing a linked HTML comparison report.

The English summary is being prepared. Showing the original description.

Fetch external sources (web/arXiv/GitHub) into scanner-gated wiki CANDIDATES, never canonical pages: guarded, capped, scanned. NOT for local knowledge (mk:wiki) or markdown fetch (mk:web-to-markdown).

The English summary is being prepared. Showing the original description.

Deep multi-source technical research with citations — tech evaluation, ecosystem/standards comparison. NOT for API docs (mk:docs-finder), codebase discovery (mk:scout), or project Q&A (mk:ask-me).

The English summary is being prepared. Showing the original description.

JSON-canonical session memory in .meowkit/memory (Markdown is a generated view). Capture learnings, patterns, costs; loads at Orient, persists at Reflect. NOT for retrospectives (mk:retro).

The English summary is being prepared. Showing the original description.

Capture, gate, query, and render long-term project knowledge through the gated `mewkit wiki` subsystem. Use to create a wiki, propose/approve candidates (scanner-gated), hand off a skill's terminal artifact as a scanned candidate, recall context, search the FTS index, or list pages. Agents may only PROPOSE candidates; canonical pages are written only via human approve. NOT for short-lived JSON memory (see mk:memory); NOT for fetching external sources (see mk:wiki-research); NOT for HTML snapshots (see mk:wiki-render).

The English summary is being prepared. Showing the original description.

Fetch external sources (web / arXiv / GitHub) and turn them into scanner-gated wiki CANDIDATES — never canonical pages. Every fetched byte is DATA; url-guarded, size-capped, redirect-re-validated, injection-scanned, and secret-scrubbed before a candidate is even created. Requires network. NOT for capturing local knowledge (see mk:wiki); NOT for one-shot page-to-markdown (see mk:web-to-markdown).

The English summary is being prepared. Showing the original description.

JSON-canonical session memory. Use when capturing session learnings, extracting patterns, or tracking costs — persists to .meowkit/memory JSON stores; matching Markdown files are generated views. Activates during Phase 0 (Orient) to load context and Phase 6 (Reflect) to persist it. NOT for weekly-cadence engineering retrospectives (see mk:retro); NOT for arbitrary file storage.

The English summary is being prepared. Showing the original description.

Creates structured multi-file implementation plans before build. Scope-aware: trivial tasks exit early, simple tasks get fast plans, complex tasks get full research + phase files + validation. Enforces Gate 1. Activated by /mk:plan or /mk:cook. NOT for ticket complexity analysis against an existing codebase (see mk:planning-engine); NOT for CEO-level scope review of existing plans (see mk:plan-ceo-review).

The English summary is being prepared. Showing the original description.

Use when a decision needs deep multi-source technical research with cited evidence — technology evaluation, ecosystem comparison, standards/spec fact-finding, "how do others solve X". Triggers on "research X", "deep dive on X", "evaluate X vs Y", "find best practices for X". NOT for library/API doc lookup (see mk:docs-finder); NOT for one-shot URL fetch (see mk:web-to-markdown); NOT for internal codebase discovery (see mk:scout); NOT for project-only Q&A (see mk:ask-me); NOT for comparing solution designs (see mk:brainstorming); NOT for root-cause debugging (see mk:investigate); NOT for wiki ingestion of sources (see mk:wiki-research).

The English summary is being prepared. Showing the original description.