4.8만건 · 관련도순
Manage which n8n instance an MCP session targets when working across production, staging, teams, or clients. Guides instance switching, checks before credential changes, and recovery from unexpected missing data or ambiguous credential writes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Train sentence-transformers models for search, similarity, and reranking, which reorders search results by relevance. Choose a model type, prepare data, configure training, compare results against a baseline, and publish the trained model to Hugging Face Hub.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check an OpenClaw environment for risky settings, unsafe skills, known software vulnerabilities, and privacy exposure. It combines local checks with optional online threat lookups and also supports reviewing individual skills before installation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication, deadlock avoidance, virtual threads, structured concurrency, scoped values, backpressure, cancellation discipline, and observability for concurrent systems. This should trigger for requests such as Review Java code for concurrency; Review Java code for thread safety; Fix race conditions in Java concurrency code; Choose ExecutorService or virtual threads in Java; Improve synchronization and shared mutable state handling; Apply structured concurrency for related Java subtasks. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenClaw 베타·안정·장기 유지보수 버전의 준비, 배포, 복구, 검증을 진행합니다. 승인된 수정의 이식과 검증 기록, 배포 후 확인까지 다룹니다.
macOS의 OpenClaw를 main 최신 상태로 업데이트하고 Gateway와 앱을 확인합니다. 자동 검사 실패 수정과 실제 배포 없는 전체 릴리스 검증도 수행합니다.
OpenClaw CI의 대기와 실행 환경 부족 원인을 조사합니다. 측정 결과에 따라 실행기 등록 수, 병렬 실행 수, 테스트 분할과 작업 배치를 조정합니다.
Build Python applications that handle other work while waiting for network or database operations. Use asyncio and async/await to run tasks concurrently, manage errors and timeouts, and handle cancellation with appropriate cleanup.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review C# asynchronous code and get suggestions for method names, return types, exception handling, concurrent tasks, and cancellation. Identify blocking calls and missing awaits, and choose patterns for long operations or sequences processed asynchronously.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and check Git branch names using Conventional Branch rules. Choose a prefix for the task, normalize the description, detect the repository’s base branch, and create and switch to the new branch.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan a product or feature launch from preparation through launch day and 30 days of follow-up. Create channel plans, assigned tasks, checklists, and Product Hunt briefs, with a readiness score to identify preparation gaps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Improve MNN inference on OpenCL by measuring bottlenecks and refining GPU kernels, the code that performs calculations. The skill guides baseline measurements, correctness checks, Android device benchmarks, and integration of new OpenCL features with compatibility fallbacks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Train sentence-transformers models for search, similarity, and reranking, which reorders search results by relevance. Choose a model type, prepare data, configure training, compare results against a baseline, and publish the trained model to Hugging Face Hub.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Choose the right OpenClaw design guidance for brand identity, application interfaces, public pages, or audits. It directs agents to focused instructions and shared rules for consistent styling, reusable components, and browser checks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan a product launch across discovery sites, social media, and communities. Select channels for the intended audience, build a waitlist, prepare launch materials, coordinate launch-day activities, and organize follow-up promotion and measurement.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Launch a new OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw using the local CLI. Configure the agent type, deployment name, model, and Telegram settings according to the supported launch options and requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Orientação completa sobre conformidade com regulamentações do Banco Central do Brasil: Resolução CMN nº 4.893/2021 (Política de Segurança Cibernética), Resolução BCB nº 85/2021 (GRSIC), Open Finance Brasil (Resoluções BCB nº 32/2020 e atualizações), e demais normas prudenciais do BACEN. Cobre elaboração e revisão de Política de Segurança Cibernética, Plano de Ação e Resposta a Incidentes (PARI), Gestão de Riscos de Serviços de Informação e Comunicação (GRSIC), consentimento e compartilhamento de dados no Open Finance, requisitos de API, gestão de terceiros (outsourcing) e sanções do BACEN. Triggers: Bacen, Banco Central, CMN 4.893, Resolução 4.893, segurança cibernética bancária, PARI, GRSIC, Open Finance, Open Banking, compartilhamento de dados financeiros, consentimento Open Finance, API financeira, outsourcing bancário, risco cibernético, incidente cibernético banco, LGPD financeira, fintech compliance, instituição financeira, DICT, Pix segurança.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles. **Defaults to dev tools / OSS / B2B SaaS; for 2C products (education, apps, games) the launch channels & metrics differ — see gingiris-seo-geo/references/2c-adaptation.md.** 🇨🇳 AI 产品 / SaaS 企业出海完整 SOP — 从竞品调研到 Launch 到商业化的全流程操作手册。覆盖 Phase 0-5（市场验证、定位、前100用户、用户访谈、Beta转增长）+ 开源发布、Product Hunt、Reddit、SEO/GEO、转化与组织原则。**默认面向开发者工具/开源/B2B SaaS；2C 产品（教育/应用/游戏）的启动渠道与指标不同，见 gingiris-seo-geo/references/2c-adaptation.md。** 🇯🇵 AI製品/SaaS海外展開フルサイクルSOP — 競合調査からローンチ、マネタイズまで。Phase 0-5（市場検証、ポジショニング、最初の100ユーザー、ユーザーインタビュー、ベータから成長）＋オープンソース、Product Hunt、Reddit、SEO/GEO、コンバージョン、組織原則。 🇰🇷 AI 제품/SaaS 글로벌 진출 완전 SOP — 경쟁사 조사부터 런칭, 수익화까지 전 주기 플레이북. Phase 0-5(시장 검증, 포지셔닝, 첫 100명 사용자, 사용자 인터뷰, 베타→성장) + 오픈소스 런칭, Product Hunt, Reddit, SEO/GEO, 전환, 조직 원칙. Triggers: "go global" | "出海" | "overseas expansion" | "GTM" | "cold start" | "launch strategy" | "international expansion" | "海外增长" | "出海SOP" | "product launch overseas" | "海外进出" | "グローバル展開" | "글로벌 진출" | "go-to-market" | "出海打法"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve Swift concurrency compiler errors, adopt approachable concurrency (SE-0466), and write data-race-safe async code. Use when fixing Sendable conformance errors, actor isolation warnings, or strict concurrency diagnostics; when adopting default MainActor isolation, @concurrent, nonisolated(nonsending), or Task.immediate; when designing actor-based architectures, structured concurrency with TaskGroup, or background work offloading; or when migrating from @preconcurrency to full Swift 6 strict concurrency.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, and guide Swift 6 migration. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenClaw 출시 후보의 CI를 실행하고 감시하며 실제 서비스 제공자 연결과 설치·업데이트를 검증합니다. 실패 원인과 검증 결과를 정리합니다.
현재 소스와 테스트 결과를 바탕으로 OpenClaw 이슈와 풀 리퀘스트를 조사하고 검토합니다. 허용된 범위에서 수정부터 합병 완료 확인까지 진행합니다.