183건 · 관련도순
Investigate Python bugs by pausing execution, inspecting variables, and stepping through code. Choose pdb for local inspection or debugpy for remote connections, with guidance for failing tests, crash analysis, and already running processes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search runtime and scene management: verify queries, inspect scenes, debug app readiness, and diagnose recall or scene-config issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds, with the lead triaging findings and creating targeted follow-up tasks. Scales from Focused (2 researchers, 1-2 rounds) to Comprehensive (4 researchers, 3-4 rounds with cross-verification). Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate setup, configuration, execution, monitoring, and troubleshooting of AutoResearchClaw — the 23-stage autonomous research pipeline that generates conference-grade papers. Use when the user mentions ResearchClaw, wants to write a research paper autonomously, needs to set up or debug the pipeline, or says research paper, autonomous research, or paper generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pure API reference for reddapi.dev - authentication, all endpoints (vector search, semantic search, trends, subreddit lookup), request parameters, response schemas, and error codes, with no research-workflow framing. Use when the user wants raw endpoint documentation, is debugging a reddapi.dev integration, needs exact request/response field names, or asks for 'reddapi API reference', 'reddapi.dev endpoints', or 'reddapi error codes'. For guided research workflows and query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query documents and conversations stored in cognee to retrieve answers, supporting passages, or context for an AI model. This skill guides search method selection, source filtering, result interpretation, and troubleshooting empty or unexpected results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate software errors, version conflicts, and API questions across official documentation, GitHub, technical Q&A, and Chinese developer communities. Results distinguish matching errors, source authority, and reported environments, giving you documented leads and next checks for debugging.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Multi-AI research using available external providers (Double Diamond Discover phase) - Questions about best practices, patterns, or ecosystem research PRIORITY TRIGGERS (always invoke): "octo research", "octo discover", "co-research", "co-discover" DO NOT use for: simple file searches (use Read/Grep), questions Claude can answer directly, debugging issues (use skill-debug), or "what are my options" for decision support.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation. Triggers on "deep research", "comprehensive analysis", "research report", "compare X vs Y", "analyze trends", or "state of the art". Not for simple lookups, debugging, or questions answerable with 1-2 searches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide a researcher step by step into an unfamiliar research field, or decode a paper, abstract, figure caption, or referee comment they cannot parse. Builds understanding in rungs (motivation, vocabulary, core framework, methods, frontier), anchored to what the user already knows, with a checkpoint before each advance. Use when the user says they are new to a field, asks what a research area or method is, says an explanation was too technical, asks to be walked through something step by step, asks for a reading path, or supplies dense research text. Trigger even when the user only names an unfamiliar field or pastes an abstract without asking to be taught. Do not trigger for a one-line summary, a short overview request, or a direct factual answer; do not use it for translation, editing, search, debugging, or specialist questions inside the user's own field. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides debugging through reproduction, comparison with working examples, hypothesis testing, and a focused fix. It starts with a repeatable check for the exact symptom and uses regression tests to verify the result.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage Obsidian notes from the command line: read, create, search, update properties, and review tasks. Also supports plugin and theme development through reload commands, error checks, screenshots, and inspection of page elements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use OpenViking through OpenClaw to manage long-term memories, search archived conversations, and find imported resources or Agent Skills. Inspect recall traces to understand search results and recover full tool outputs stored outside the conversation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use OpenViking MCP tools to retrieve relevant knowledge before substantial tasks and save lasting preferences, decisions, and lessons during or after work. Import documents as searchable resources so later tasks can draw on previous findings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Conduct enterprise-grade research with multi-source synthesis, citation tracking, and verification. Use when user needs comprehensive analysis requiring 10+ sources, verified claims, or comparison of approaches. Triggers include "deep research", "comprehensive analysis", "research report", "compare X vs Y", or "analyze trends". Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs, reviews, and debugs DynamoDB data layers from design axioms — enumerates access patterns, chooses partition/sort keys and GSIs, decides single-table vs. multi-table, configures Streams, Global Tables, TTL, vector indexes for similarity search, and zero-ETL integrations to OpenSearch/Redshift/SageMaker Lakehouse, and produces a defensible data-layer design with a monthly cost estimate and optional live validation. Applies whenever a user is designing, reviewing, or refactoring anything backed by DynamoDB — schemas, access patterns, GSIs, single- vs. multi-table choices, Streams consumers, transactional outboxes, Global Tables, zero-ETL pipelines, or storing embeddings and running semantic/vector similarity search with SearchVectors on items already in DynamoDB — even when they don't say "axioms" or "design review." Also applies when debugging hot partitions, throttling, unbounded Scans, LWW conflicts, or surprise bills on DynamoDB workloads.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation. Triggers on "deep research", "comprehensive analysis", "research report", "compare X vs Y", "analyze trends", or "state of the art". Not for simple lookups, debugging, or questions answerable with 1-2 searches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research existing code, documents, and relevant sources before producing a practical plan for implementation, migration, debugging, or evaluation. The plan explains key decisions, ordered steps, and validation checks, giving users something concrete to review before execution.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Support authorized hardware security research by locating debug interfaces, recording pin assignments and voltage levels, and collecting boot logs. Assess interface locks and firmware extraction options, then hand extracted images to firmware analysis tools.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Identify software protections that hinder inspection, such as debugger detection and obfuscation that makes code harder to understand. Support authorized binary analysis and CTF security challenges with protection findings, bypass strategies, reports, and analysis scripts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compose compact, structured prompts for coding, debugging, review, and research with Codex or GPT-5.4. This internal skill defines task scope, completion criteria, output format, verification steps, and evidence requirements using consistent XML tags.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.