115건 · 관련도순
Set up Acontext so Claude Code or OpenClaw can retain conversations and turn them into reusable skills. Covers CLI installation, login, project selection, plugin configuration, and checks that the configured service is reachable.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automatic init the first time Claude acts in an incident or alerts channel — one named like #inc-…, #incident-…, #sev0-…/#sev1-…, or whose recent messages are pages or alerts from PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or relayed by people (talk about being paged is not an alert) — that isn't already a team's oncall / monitoring channel. Run once per channel, on first contact (just invited, first @-mention, channel just created), before doing what was asked: load the oncall memory oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / code tools Claude can reach and which are missing, post one short zero-context message, note findings in this channel's memory, then hand off to `incident-investigate` if something was asked — or immediately, unasked, when the channel was plainly opened for a live outage. Works with no oncall memory (offers setup once). Also on "load the oncall setup here" / "init this incident".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up Claude Tag for oncall for a team, from that team's standing (public) oncall / monitoring channel. Two things: it sets the channel up for monitoring, so alerts and incident posts here (from a person or another Slack bot) get triaged and acted on automatically, and it finds and sets up the connectors, plugins and skills Claude uses for oncall. A workspace can have several such channels; run once in each, by anyone, and every run adds or updates that team's section in the one oncall memory in shared workspace memory. Use on "set up oncall", "init oncall", "configure Claude for on-call". Surveys the agent connectors an admin configured for Claude, proves one with a read-only pull so access is verified, explores tools, Slack, repos and docs to learn how oncall works here, then recommends what's missing and walks the team through setup. The result goes into the indexed oncall memory every channel reuses; the other skills (incident init, investigation, handoff) pick it up automatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user explicitly says to save something to memory or scan this session for memories. Not for auditing memory: use memory-clean.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose slow loading, high memory use, and low frame rates in USD 3D scenes. Coordinate scene structure checks, validation, optimization, and before-and-after performance comparisons, then produce a report documenting findings and changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Capture and analyze iOS memory snapshots to find objects that remain allocated unexpectedly. Trace the references keeping them alive, identify a targeted fix, and compare the same app flow before and after to document evidence.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Host-side DOCA UROM library (doca_urom_*): offload an HPC / UCX / MPI application's remote memory operations (puts, gets, atomics, collectives) from the host CPU onto a BlueField DPU. Trigger on "MPI all-reduce burning host CPU", "push UCX traffic onto the BlueField", "first doca_urom call returns NOT_PERMITTED", or "host library and DPU service look out of sync", even without naming DOCA UROM. An offload needs both halves: this host library and the UROM Service on the DPU (doca-urom-svc), which owns deploying that container. Covers creating UROM Service contexts (doca_urom_service_*) and Worker contexts (doca_urom_worker_*) that run plugins on the DPU, discovering plugins via doca_urom_service_get_plugins_list, progressing completions, and DOCA_ERROR_* from doca_urom_* calls. Route elsewhere for UROM Service deployment on the DPU side, MPI / UCX collective algorithm design, and RDMA / RoCE / IB substrate bring-up.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal. Triggers: "add memory", "remember across sessions", "call agent from app", "invoke agent from code", "agent auth", "streaming", "VPC", "VPC connectivity", "can't reach from VPC", "multi-agent", "A2A", "A2A auth", "orchestrator not delegating", "specialist not called", "migrate Bedrock Agent", "migration issue", "change model", "browser tool", "code interpreter", "delete agent", "tear down", "agentcore remove", "cross-account memory", "add payments capability to my agent", "wire payments plugin", "integrate x402 payments with the agent I'm building", "add MPP payments", "Machine Payments Protocol". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI/dev-server errors: use agents-debug. Runtime x402/MPP payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cross-agent self-inspection of your AI-agent stack. Audits skills, MCP servers, hooks, plugins, commands, credentials, and memory files across Claude Code, Codex, OpenClaw, and NanoClaw. Produces a structured inventory and narrative briefing with cross-ecosystem risk analysis. Use when the user asks to audit their own setup, check what they have installed, review their agent stack security posture, or understand cross-tool interactions. Use when a user has accumulated skills/plugins/MCP servers over time and wants visibility into their attack surface. Use after installing new skills or plugins. Do NOT use for vetting external code before install (that is repo-forensics). Do NOT use for incident response during active attacks. Do NOT use for fixing or patching vulnerabilities (forensify is read-only).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Seed a fresh (greenfield) repository with the PRD-Driven Context Engineering scaffold — PRD.md, SoT/ knowledge files, EPIC templates, domain-profile config, and agent MEMORY starters. Invoked as /prd-ce:init when the plugin is installed. The framework itself (skills, agents, hooks, scripts) ships LIVE in the plugin; this skill only plants the consumer-owned files the plugin cannot carry as behavior. Triggers on "/prd-ce:init", "set up PRD lifecycle here", "scaffold a new PRD-CE project", "initialize the methodology". Outputs a seeded scaffold + a verification report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI knowledge engine - a memory system in 6 lines of code. remember/recall/forget/improve loop, vector + graph search, OpenClaw plugin supported.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when modifying agentic contextual building blocks like skills (SKILL.md), slash commands, agents, hooks, plugins, marketplaces, and instruction files (CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md, Cursor, Copilot, Cline, or Kiro rules), tool configuration such as an OpenCode `opencode.json`, Muse Code hooks (`.muse/hooks.json`), a Grok Build `.grok/` project layer or a Google Antigravity customization root (`.agents/`, `.agent/`, `_agents/`, `_agent/` — hooks, MCP config, rules, registries and plugins), and committed project memory (`.agents/memory/`). Run skillsaw on the files you touched, apply autofixes, resolve remaining violations with `skillsaw explain` guidance, and re-lint until clean before considering the work complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
xUnit, Moq/NSubstitute, FluentAssertions, and coverlet patterns for any .NET project. Covers test structure ([Fact]/[Theory]/[InlineData]), mocking discipline, fluent assertions, integration test setup with WebApplicationFactory, and coverage measurement. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write clear, maintainable unit tests with xUnit [Fact] and [Theory]. - Mock dependencies with Moq or NSubstitute without overusing mocks. - Write expressive assertions with FluentAssertions. - Measure coverage with coverlet and enforce a minimum threshold. Do NOT use this skill for: - ASP.NET Core-specific integration tests (WebApplicationFactory, HttpClient — those are in aspnet-core-plugin:aspnet-conventions). - EF Core in-memory or SQL Server LocalDB test patterns (aspnet-core-plugin:efcore-patterns). - C# language idioms — see csharp-foundation:csharp-conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when analyzing warp divergence, memory coalescing, shared memory bank conflicts, cache behavior, atomics, or occupancy tradeoffs on NVIDIA and AMD GPUs. Not for tool commands: use cuda-profiling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a human asks to audit memory, find stale or duplicate memories, or needs tidy's ICM-state audit. Not for writing new memories: use memory-update.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search, inspect, and record SIPS-owned Memory Fabric lessons. Use when a task needs prior lessons, recurring-fix memory, recall health, scoped historical context, or when a just-fixed bump or error should be recorded.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Authors reproducible bioinformatics pipelines with Snakemake - rules wired by output-file pattern, wildcards and expand() for sample fan-out, checkpoints for runtime-unknown outputs, resource/retry escalation, and conda/container software deployment on HPC and cloud. Use when deciding rule-based (Snakemake) vs channel/dataflow (Nextflow) authoring; wiring rules by OUTPUT-file pattern rather than imperative order; using wildcards + expand() for sample fan-out and constraining them to stop silent mis-routing; adding checkpoints when the set of outputs is unknown until a step runs (dynamic DAG); diagnosing why a job reran (or did not) under the mtime-plus-provenance trigger set; escalating memory on retry for OOM-killed jobs; and porting a Snakemake 7 `--cluster`/remote-provider command to the Snakemake 8+ executor-plugin and storage-plugin model (snakemake-executor-plugin-slurm) with `--software-deployment-method`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenViking long-term memory plugin guide. Once installed, the plugin automatically remembers important facts from conversations and recalls relevant context before responding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The barber for your coding agents' config. Weighs everything every agent on this machine loads (instruction files, memory, MCP servers, hooks, skills, commands, subagents, plugins, leftovers), prices each item in tokens from your own transcripts, and parks the dead weight with a receipt and an undo. Use this skill whenever the user mentions config bloat, a heavy or slow session start, tokens burned before the first word, too many MCP servers, hooks that are slow or fire on every prompt, skills or commands or plugins nobody invokes, cleaning up or auditing CLAUDE.md or AGENTS.md, Codex config, or asks what does my agent actually load, why is my context full before I type, which of these servers can I turn off, or what is this plugin costing me. Use it even when they only say the session feels bloated or startup got slow, and even when they mention /context, /doctor or /skill-doctor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
지정한 주소나 기본 USB Ethernet 주소로 Cognitum Seed 기기를 등록합니다. 식별 정보 조회, 초기 신뢰 수준 설정, 선택적 페어링, 상태 확인과 기록 저장을 수행합니다.
Creates a new domain-specific skin for reskinnable-demo, combining branding, layouts, pages, data, tools, and an agent. Structures live sales demonstrations around visible AI interactions, including generated interfaces, shared state, confirmations, and memory features.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Tune adaptive behavior in an instrumented NeMo Relay application using runtime data. Configure tool parallelism, prompt caching, and state storage, then compare changes against a baseline to check latency, correctness, and failure rates.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Routes Claude Code: plugin/Skill repair, marketplace, statusline, model profiles/source sync, 1M/[1m] context, usage/quota reset ping, memory→docs, .txt repair, turning auto memory off. Reads one bundled specialist; history, hooks, and Lark keep their own entries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install and use GrayMatter as an OpenClaw skill that provides primary durable memory, shared object-graph state, and authenticated access to the live api-docs schema via api-0. Use when the agent should persist durable memory, inspect organizational data models, and operate inside the business domain through RBAC-scoped API access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.