'knowledge' 검색 결과

Query the Precision Medicine Knowledge Graph (PrimeKG) for multiscale biological relationships across genes and proteins, drugs, diseases, phenotypes, pathways, biological processes, exposures and anatomy. Use this skill to search entities by name, pull direct neighbours and their evidence types, summarise the local network around a disease, and find direct or two-hop drug-disease connections for repurposing hypotheses. Also trigger on PrimeKG, kg.csv, Harvard Dataverse knowledge graph, disease_protein, drug_protein, indication and contraindication edges, or network pharmacology over a biomedical knowledge graph.

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

Entity and relation tracking skill using MCP memory server patterns and local knowledge graph storage. Build persistent knowledge graphs of entities, relationships, and observations across agent sessions. Covers the MCP memory server (@modelcontextprotocol/server-memory), local JSON-based graphs, and entity-relation querying patterns for long-running agents.

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

Initialise a project for knowledge base use. Appends the [Knowledge Base] section to the project's CLAUDE.md, creates the library/ directory structure, optionally seeds with three example library files from the Agentic SDLC research, and reports next steps. Run once after installing sdlc-knowledge-base.

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

Rebalances context across Memory, Custom Instructions, knowledge files, and User Preferences in Claude Projects. Audits Memory for redundancy, staleness, and misplacement; prescribes optimization including Codification of stable Memory patterns into explicit User Preferences or Project CI rules. Use when user says "optimize my memory," "what should be in my memory," "trim my knowledge files," "reduce my context usage," "rebalance my project," "what should be in my preferences vs memory," or asks whether something belongs in Memory, a knowledge file, or User Preferences. Also trigger on symptom-phrased: "my project feels bloated," "Claude keeps forgetting things," "my context window keeps hitting limits." Activate whenever Memory-layer balance is the primary concern. Do NOT use for full Project audits (use rootnode-project-audit if available), single-prompt evaluation (use rootnode-prompt-validation if available), or global-layer audits that don't touch Project Memory (use rootnode-global-audit if available).

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

Analyzes Claude Project context budget under the automatic-RAG-by-window model: knowledge files vs. threshold-exempt overhead (Skills, MCPs, CI, Memory). Two modes: Quick Diagnostic and Full Budget Audit. Use when user says "check my context budget," "how much context am I using," "is my project too big," "optimize my token usage," "tier my files," "optimize for RAG," "improve retrieval quality," "should I keep compressing," "am I over-compressing," "should I accept RAG mode." Also trigger on context pressure symptoms: "Claude forgets my instructions," "responses getting generic," "content not found in my knowledge files." Also use when a project audit scores Knowledge Architecture ≤ 3. Do NOT use for content placement decisions (use rootnode-memory-optimization if available), full project audits (use rootnode-project-audit if available), or behavioral tuning (use rootnode-behavioral-tuning if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

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

Use when capturing research artifacts to a vault or knowledge base, formatting source citations, saving synthesized connections from a writing project, or enriching a knowledge base with produced content.

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

Build AI knowledge base creation systems. TRIGGERS - Use when user needs help with ai-knowledge-base-builder related tasks.

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

Design AI knowledge management systems. TRIGGERS - Use when user needs help with ai-knowledge-management related tasks.

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

Efficiently accumulate and retrieve competition knowledge in the knowledge/ stock layer (atomic pages + INDEX). Distill reusable insights from the daily-report flow and promote them, deduplicating and keeping things current. Use when an insight emerges, for weekly cleanup, or to recall past knowledge.

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

Manage knowledge graph for autonomous coding. Use when storing relationships, querying connected knowledge, building project understanding, or maintaining semantic memory.

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

Reusable learnings: セッション中の再利用知見を構造化し、ドメイン別（microsoft / copilot など）に振り分けて出力。Use when: knowledge, lessons learned, 知見化。作業ログは export-session-log、対話再現は export-copilot-session-dialogue を使う

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

Study unfamiliar codebases and produce evidence-backed knowledge artifacts. Use for repository orientation, architecture mapping, subsystem tracing, onboarding, or codebase documentation.

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

Test Retrieval-Augmented Generation (RAG) systems for data poisoning, prompt injection via retrieved documents, and data exfiltration through manipulated context windows. Use this skill when assessing RAG-based chatbots, knowledge bases, enterprise AI assistants, or any system that augments LLM responses with external document retrieval. Covers document injection, embedding manipulation, knowledge base poisoning, and cross-document inference attacks.

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

Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.

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

Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and Iceberg), establishing metadata governance with Knowledge Catalog aspect types, or grounding agentic IDEs (VS Code, Antigravity) by using the Google Cloud Data Agent Kit. Don't use for provisioning borderless data lakehouse infrastructure (use google-cloud-solution-agentic-ai-borderless-data-lakehouse instead).

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

Create and maintain the shared knowledge/ context files that every other marketing skill reads - brand voice, ICP personas, positioning, KPIs, and the learnings log. Run this once per company or client before using any other marketing skill. Use when the user says "set up brand context", "onboard my brand", "set up the marketing knowledge base", "the skills don't know my brand", "update our positioning", "our voice has changed", "add a new persona", or when any marketing skill reports that a knowledge/ file is missing. Also use when output sounds generic or off-brand. For writing a positioning statement as a standalone document, see positioning-doc. For deep persona research from raw sources, see customer-research.

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

Analyze competitors using Blue Ocean Strategy's ERRC Grid and Strategy Canvas (W. Chan Kim and Renee Mauborgne) to identify uncontested market space, not just who is better on the same axes. Produces an ERRC Grid, Strategy Canvas, positioning matrix, messaging comparison, and differentiation map. Use when the user asks for competitive analysis, competitor research, "how do we compare to X", positioning vs competitors, market landscape, "analyze our competition", "where is the blue ocean", or wants to update competitor docs. Writes to knowledge/markets/competitors.md. For a lightweight competitor summary in the knowledge base, see brand-context. For positioning against them, see positioning-doc. For a product or feature-level comparison outside the marketing knowledge base, see competitive-analysis.

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

Use this skill when designing the UX and content strategy for a Salesforce-powered self-service portal or help center — pre-deflection article surfacing, Help Center search UX, friction-calibrated case submission forms, community peer support layers, and deflection measurement. Trigger keywords: design self-service portal, case deflection strategy, help center UX design, reduce support volume with self-service, knowledge base search experience. NOT for picking which contact reasons to deflect and through which channel — use architect/case-deflection-strategy. NOT for building the Experience Cloud site itself — use admin/experience-cloud-site-setup. More trigger keywords: article visibility matrix IsVisibleInCsp IsVisibleInPkb, which articles show in the customer portal, case visibility for portal users, CaseComment IsPublished customer visible comment, self-registration profile and account for a portal, Help Center template does not support login, deflection metrics SOQL KnowledgeArticleViewStat, self-service journey map, moderation policy for a support community.

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

Use when planning, sequencing, or troubleshooting an org-wide migration from Salesforce Classic to Lightning Experience. Covers the LEX Transition Assistant Readiness Check, asset triage matrix (Visualforce, JavaScript buttons, page layouts, Knowledge, email templates, list views, AppExchange), pilot/wave rollout sequencing, end-user adoption telemetry, and cutover criteria. Triggers: 'lightning experience transition', 'classic to lightning migration plan', 'LEX readiness check', 'why are some users still on Classic', 'turning on Lightning for everyone'. NOT for individual asset migrations like a single VF page (use lwc/visualforce-to-lwc-migration), a single JavaScript button (use admin/custom-button-to-action-migration), or Knowledge article migration (use admin/knowledge-classic-to-lightning) — this skill orchestrates the program. NOT for Lightning App Builder page design (use admin/lightning-app-builder-advanced).

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

Capture and organize knowledge in Notion—research findings, best practices, reference materials. Build searchable knowledge base for your team and future self.

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

Deep analysis of knowledge distillation techniques for compressing large models into smaller efficient ones

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

Search, read, create, edit, and maintain knowledge in a Memex KB via the `mx` CLI. Use when the user asks to search the KB, find documentation, check project or organizational docs, add or update knowledge-base entries, audit KB quality, or when reusable knowledge should be captured for future agents.

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

Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.

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

Render a wiki into ONE self-contained HTML snapshot (pages + provenance) that opens offline — no CDN, no remote assets, page content HTML-escaped. Use to share or review accumulated wiki knowledge as a static page. NOT for capturing/approving knowledge (see mk:wiki); NOT for generic code/diagram visuals (see mk:preview).

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