조사, 논문, 교육, 자격증 공부 (4.4천건)
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch daily arXiv announcements (cs.RO), filter by research relevance, generate a structured markdown digest, and sync matched papers to a Zotero collection with arXiv PDFs attached.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
10-team parallel deep analysis with cross-verification for any topic, repository, or technology. Use when user invokes /research or asks for comprehensive research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured SE task evaluation using 15 benchmark definitions from claude-code-harness research
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research-validated planning — research → plan → verify cycle for high-confidence implementation plans
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skill for adding or updating educational algorithm guides, ensuring consistent patterns and simple explanations suitable for an 8-year-old.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use ruLake as the agent's working memory. Auto-invoke /rulake-memory:memory-recall when the agent needs to look up something it might already know; auto-invoke /rulake-memory:memory-remember after the agent learns or decides something worth pinning. Closes the self-learning loop without requiring the agent author to wire it explicitly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate and save a session summary before ending conversation. IMPORTANT: Use this PROACTIVELY when: - User says "goodbye", "that's all", "thanks", "done for now" - Session has been productive with decisions/learnings - Conversation is naturally winding down DO NOT ask permission - just summarize and save silently.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Save important context to persistent memory for future sessions. PROACTIVELY USE THIS when you detect: - Decisions: "let's go with", "decided to", "chose", "went with" - Learnings: "I learned", "turns out", "TIL", "realized", "discovered" - Errors resolved: "fixed", "the problem was", "solution was" - Client info: names, emails, phone numbers, addresses, invoice amounts - Preferences: "I prefer", "I like", "don't like", "always use" - References: API keys locations, file paths, URLs, credentials - Patterns: "pattern", "convention", "always do", "standard approach" - Important commands run worth remembering Do NOT ask permission - just capture silently when these patterns appear.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Save a project fact, decision or gotcha so your next session already knows it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map unfamiliar code or research an approach before planning, read-only and fast.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Do market research, user research, and product validation on Reddit with semantic search across 50K+ subreddits, 20M+ posts, and 40M+ comments via reddapi.dev - search by meaning, not keywords, no Reddit OAuth or app registration needed. Use when the user wants to research what people say on Reddit, find user pain points and complaints, validate a product or niche idea, do competitor and market research, track subreddit trends over a date range, or discover which subreddits discuss a topic. Also use when the user mentions 'Reddit research', 'Reddit 调研', 'search Reddit', 'subreddit discovery', 'niche validation', 'pain points', 'user complaints', or 'Reddit trends'. Requires REDDAPI_API_KEY. For B2B lead scoring, see reddit-leads; for a bare API reference, see reddit-search-api.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generalize published Spectre and remote microarchitectural research into passive target prerequisites, defensive review, and approval-gated local validation. Use for shared runtimes, JavaScript isolates, edge workers, serverless platforms, browser sandboxes, remote timing, cache side channels, speculative type confusion, or Dynamic Process Isolation analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Finish an authorized security research task with a durable solved, abstained, or blocked outcome. Use when evidence is sufficient, a stop condition is reached, a tool budget is nearly exhausted, or the agent must commit its best supported answer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Suggests that adults with type 1 or type 2 diabetes using continuous subcutaneous insulin infusion (CSII) and continuous glucose monitoring (CGM) receive education, training, and ongoing support to achieve and maintain individualized glycemic goals. Trigger phrases include: 'Patient on pump plus CGM, arrange education' and 'Ensure CSII+CGM users get training and support'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Suggests encouraging patients to use appropriately adjusted embedded bolus calculators in CSII and to provide education regarding their use and limitations. Triggers include: 'Patient starting pump, discuss bolus calculator', 'Review bolus calculator education at pump initiation'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill recommends that a multidisciplinary team, including an experienced endocrinologist, incorporates patient values and preferences while providing education about treatment options for Cushing’s syndrome. Use when planning treatment for a CS patient requiring coordinated care; triggers include persistent hypercortisolism after transsphenoidal surgery, consideration of bilateral adrenalectomy, radiotherapy, or medical therapy, and need for shared decision‑making.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.