415건 · 관련도순
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate abstract Control Flow Graph (CFG) representations of programs showing loops, branches, and function calls for static analysis or verification. Use when users need to: (1) Visualize program control flow structure, (2) Generate CFGs for static analysis tools, (3) Create control flow abstractions for formal verification, (4) Analyze program paths and reachability, (5) Document program structure. Supports both function-level (intraprocedural) and program-level (interprocedural) analysis with multiple output formats (textual, DOT/Graphviz, JSON).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Hepatologist. Use when a task calls for Hepatologist judgment. Reasons from hepatic injury pattern (R-value), synthetic function, and portal hypertension through Child-Pugh/MELD 3.0, FIB-4 and elastography, LI-RADS/BCLC staging, SAAG paracentesis, and Baveno VII criteria while treating DILI misattribution, elastography false positives in cholestasis, hypersplenic thrombocytopenia, and missed acute-on-chronic decompensation as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provider-independent production workflow for recutting long talking-head, podcast, interview, webinar, panel, lecture, livestream, founder call, or customer-call footage into short clips, highlight reels, trailers, audiograms, captioned vertical videos, and social cutdowns. Use when an agent must ingest source recordings, transcribe and diarize speakers, select quotes without misrepresentation, preserve context, handle consent/rights/disclosures, clean jump cuts and audio, add captions, graphics, lower thirds, b-roll, platform variants, synthetic-media boundaries, review packets, delivery specs, and recut QA.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create polished HTML technical reports and multi-page documents for consulting deliverables. Features a professional design system with dark cover pages, warm cream content pages, Switzer + Cartograph CF typography, and a curated component library (KPI cards, data tables, callout boxes, recommendation cards, priority banners). Outputs standalone HTML that prints cleanly to PDF.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test REST and GraphQL API endpoints with structured assertions and reporting. Use when a user asks to test an API, hit an endpoint, check if an API works, validate a response, debug an API call, test authentication flows, or verify API contracts. Supports GET, POST, PUT, PATCH, DELETE with headers, body, auth, and response validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in entertainment industry concept art workflows, from initial ideation through final production-ready deliverables. Combines traditional art fundamentals with modern digital workflows used at AAA studios and film production houses. Draws from methodologies of industry masters: Feng Zhu's efficient design process, Scott Robertson's perspective and vehicle design systems, Sparth's graphic shape language, and Syd Mead's industrial design thinking. Use when "concept art, visual development, vis dev, keyframe, color script, production design, mood board, thumbnail sketch, environment concept, character concept, prop design, callout sheet, orthographic views, design exploration, photobash, speedpaint, concept-art, visual-development, game-art, film-art, pre-production, ideation, design" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Mastery of AI image generation across the full spectrum: Midjourney for aesthetic perfection, Flux for prompt adherence, DALL-E 3 for concept clarity, Stable Diffusion for control, and Imagen 3 for photorealism. This skill transforms text into visual reality at the speed of thought. We've moved beyond "AI can make pictures" to "AI is the fastest concept artist, product photographer, and visual designer ever created." The skill isn't just prompting—it's understanding how each model thinks, what makes images work, and how to systematically produce exactly what you envision. The best AI image generators have internalized composition, lighting, color theory, and style—not by studying art, but by generating thousands of images and learning what works. They're visual directors who happen to work in text. Use when "AI image, generate image, Midjourney, DALL-E, Flux, Stable Diffusion, Imagen, text to image, AI art, AI photo, AI illustration, AI visual, AI graphics, generate picture, ai-image, midjourney, dall-e, flux, stable-diffusion, imagen, generation, text-to-image, visual, art" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract, suggest, and sync tags and categories for blog posts across all major CMS platforms. Supports WordPress REST API, Shopify GraphQL, Ghost Content API, Strapi REST/GraphQL, and Sanity GROQ. Generates tag suggestions from content analysis (keyword frequency, heading extraction, semantic grouping), enforces minimum post-count thresholds to prevent thin tag archives, and syncs taxonomy via authenticated API calls. Use when user says "tags", "categories", "taxonomy", "tag suggestions", "sync tags", "WordPress tags", "Shopify tags".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Programmatic security management in Neo4j — RBAC/ABAC, user lifecycle (CREATE/ALTER/DROP USER), role lifecycle (CREATE/GRANT ROLE/DROP ROLE), privilege grants and denies (GRANT/DENY/REVOKE on graph, database, DBMS), property-level access control, sub-graph access control, SHOW PRIVILEGES inspection, and auth provider config reference (LDAP, OIDC/SSO). Use when an agent needs to manage users, roles, or privileges programmatically via Cypher on the system database. Does NOT handle Cypher query writing — use neo4j-cypher-skill. Does NOT handle cluster ops or backups — use neo4j-cli-tools-skill. Property-level security and ABAC require Enterprise Edition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI knowledge engine - a memory system in 6 lines of code. remember/recall/forget/improve loop, vector + graph search, OpenClaw plugin supported.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatic graph layout using dagre with React Flow (@xyflow/react). Use when implementing auto-layout, hierarchical layouts, tree structures, or arranging nodes programmatically. Triggers on dagre, auto-layout, automatic layout, getLayoutedElements, rankdir, hierarchical graph.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compose polished charts (timeseries, bar, line, area, pie, scatter, or anything else the data calls for) from tabular data using the chartkit primitives, producing PNG, SVG, or self-contained interactive HTML. Use when the user asks to chart, graph, plot, or visualize data and wants something better than raw matplotlib defaults.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a question is about *structure* rather than text - who calls or launches a symbol, where it is defined, what a change would reach, whether something is dead, how a request gets from the API to a kernel. Triggers on "who calls", "who launches this kernel", "where is X defined", "what breaks if I change", "is this still used", "is this dead", "trace the path from X to Y", "blast radius", "what depends on this header". Do NOT use for free-text search (`rg` is better and cheaper) or to open a file whose path you already know.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prismatic API access patterns and GraphQL reference. Covers the two-tier access hierarchy (MCP tools → Prism CLI), CLI usage rules, GraphQL query patterns, pagination, authentication, and managing platform resources programmatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Diagnostic Medical Sonographer — deciding whether a duplex, compression, or graded-compression ultrasound study is diagnostic versus technically limited, choosing when to interrupt a scanning protocol to escalate a real-time critical finding, setting scan technique and ALARA (TI/MI) parameters for a given exam type, or drafting the technical worksheet and preliminary findings a physician will interpret and sign.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Traces and documents signal paths, bus/aux architecture, and sidechain connections in audio systems. Surfaces hidden coupling between audio components. Use when the user asks to trace a signal chain, explain audio routing, understand an audio graph, locate sidechain sources, or describe how audio flows through a plugin or engine. Trigger on phrases like "trace this signal chain", "explain this audio routing", "what calls what in this audio graph", "where does the sidechain come from", "how does audio flow through this plugin".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for Backend.AI distributed computing platform. Automatically activates when users ask about: - Backend.AI architecture, components (Manager, Agent, Storage Proxy, Webserver, App Proxy) - Features (session scheduling, Sokovan orchestrator, multi-tenancy, resource allocation) - APIs (REST, GraphQL), authentication, RBAC authorization - Container runtime (kernels, jail sandbox, hook library, virtual folders) - Accelerator support (CUDA, ROCm, TPU, NPU, Graphcore IPU) - Client SDKs (Python, Java, JavaScript, PHP) - Setup, requirements (Python 3.13+, Docker, PostgreSQL, Redis, etcd) - How WebUI connects to/interacts with Backend.AI backend - Plugin interfaces, development setup, infrastructure Use when user mentions "Backend.AI", "backend.ai", "Sokovan", component names, or asks about the backend platform this WebUI connects to. allowed-tools: WebFetch, Read
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, `main`) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep, whenever the user asks "where does X come from?", "what API/data populates Y?", "what renders or wraps the Z panel?", "which file for feature F?", "how is this wired up?", or any code-navigation question mapping a UI element, route, or feature concept to source files. Also reverse queries ("what uses /api/foo?", "who consumes this service?"). Keyword search routinely picks up unrelated flows sharing a domain word and produces wrong answers; the walk follows the actual graph. The JS/TS `walk.mjs`/`discover.mjs` are an optional accelerator, not required — the walk is language-agnostic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.