Diagnose unreachable or unhealthy OpenShell gateways and sandbox startup failures. Identify the underlying execution platform, then examine logs, authentication, certificates, and configuration with the matching tools to narrow down the cause.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Investigate gateway connection and health check failures
- Find why a sandbox remains pending or fails to start
- Check Docker or Podman runtime and image problems
NVIDIA/OpenShell☆ 1.7만2026년 10월 19일 업데이트
Identify and analyze unused or redundant code including unused functions/methods, unused variables/imports, unreachable code, and redundant conditions. Use when cleaning up codebases, improving maintainability, reducing technical debt, or conducting code quality audits. Analyzes Python code using AST analysis and produces markdown reports listing dead code locations with line numbers, severity ratings, and recommendations. Triggers when users ask to find dead code, remove unused code, identify unused imports, find unreachable code, or clean up redundant logic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ArabelaTso/Skills-4-SE☆ 2552026년 8월 21일 업데이트
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
swaylq/master-skill☆ 1612026년 9월 6일 업데이트
Use when testing unreachable skills
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ComeOnOliver/skillshub☆ 642026년 6월 24일 업데이트
Send a single request to DeepSeek for summarization, information extraction, or simple classification. Receive the response and token usage as JSON for further processing, with structured status information when the API is unavailable.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Summarizing text in a single request
- Extracting information from text
- Classifying text into simple categories
ruvnet/ruflo☆ 7.7만2026년 10월 19일 업데이트
Send proofs, planning questions, or difficult debugging tasks to DeepSeek's reasoning model. Receive the final answer and model-provided reasoning text in separate fields, with token usage reported for reviewing responses and costs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Requesting a mathematical proof
- Planning work that requires several reasoning steps
- Investigating root causes of difficult bugs
ruvnet/ruflo☆ 7.7만2026년 10월 19일 업데이트
Manage Jira issues, build JQL searches, and design project workflows and reports. Use bundled scripts to generate search queries and check workflow designs, with guidance on which operations require Jira’s interface or API.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Finding overdue or stale Jira issues
- Creating issues and updating their status
- Checking workflow designs for unreachable states
alirezarezvani/claude-skills☆ 2.8만2026년 8월 30일 업데이트
Diagnose why GKE Pods cannot authenticate to Google Cloud APIs. Inspect cluster settings, service account bindings, resource permissions, and metadata server health, then provide evidence and concrete fixes for a human to apply.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Investigate Pod authentication failures and 403 errors
- Check Kubernetes service account identity bindings
- Diagnose metadata server connectivity problems
google/skills☆ 2.1만2026년 10월 17일 업데이트
Inventory feature flags, switches that control feature availability, and remove eligible flags with their unused code branches. Leave ongoing rollouts and experiments untouched, run verification checks, and prepare a pull request for human review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Removing flags after a feature has fully rolled out
- Cleaning up unused flags and unreachable code branches
- Listing ongoing rollouts and experiments for human review
kortix-ai/suna☆ 2만2026년 10월 19일 업데이트
Diagnose failed model requests from OpenShell sandboxes to hosted APIs or local servers such as Ollama and vLLM. Check provider attachment, access rules, credentials, network layout, and client settings to identify the narrowest configuration change needed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Diagnose failed requests to hosted model APIs
- Troubleshoot connections to Ollama or LM Studio
- Investigate credential and endpoint mismatch errors
NVIDIA/OpenShell☆ 1.7만2026년 10월 19일 업데이트
Checks a local CARLA checkout for missing API documentation, outdated references, broken links, and pages absent from navigation. Produces a grouped Markdown report without building the project or running the simulator.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Reviewing documentation before a release
- Finding missing or outdated API references
- Checking broken links and navigation gaps
carla-simulator/carla☆ 1.5만2026년 10월 18일 업데이트
Measure which code fuzzing reaches as it tries many generated inputs. Use coverage reports to find unreachable areas, compare progress, and guide improvements to test harnesses, starting inputs, or dictionaries of useful input values.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
- Establish initial coverage for a fuzzing run
- Investigate why fuzzing stops reaching new code
- Compare coverage before and after harness changes
trailofbits/skills☆ 7.6천2026년 10월 16일 업데이트
Audits .NET test mock usage by tracing each mock setup through the production code's execution path to find dead, unreachable, redundant, or replaceable mocks. Use when the user asks to audit mock usage, find unused or unnecessary mock setups, check if mocks are needed, reduce mock duplication or over-mocking, simplify test setup, or review whether mock configurations like ILogger/IOptions should use real implementations instead. Supports Moq, NSubstitute, and FakeItEasy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
dotnet/skills☆ 5.7천2026년 10월 18일 업데이트
Find unused functions and dead code in the codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
parcadei/Continuous-Claude-v3☆ 3.9천2026년 1월 27일 업데이트
Monitors task execution for skill improvement opportunities: logs patterns, user corrections and methodology worth preserving to the workspace, turns them into skill updates in a weekly review, and flags repeating work as new skills. Use during ANY multi-step task, agentic workflow, or work session. Also triggers in post-task feedback discussions and when the user mentions skill observations, the observation log, or skill taxonomy. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: invoke this skill before the FIRST tool call of any session and before writing or proposing a plan — any turn that will involve a tool call counts. This sentence is the session-start trigger and the only activation layer that survives an unreachable config file; pair it with a CLAUDE.md instruction or a session-start hook (references/environments.md). A subagent dispatched by a session already running it does not run it: it writes nothing and puts its findings in its report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
rebelytics/one-skill-to-rule-them-all☆ 3.4천2026년 10월 17일 업데이트
Verify that every interactive control on a page can take keyboard focus and that its primary action fires from the keyboard rather than only the mouse, and say plainly that Tab order cannot be verified today. Use when a component was hand-tested with a mouse, a custom dropdown/modal/combobox was added, or an accessibility report flags an unreachable control.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
reticlehq/reticle☆ 1.3천2026년 10월 19일 업데이트
Use when auditing or recalibrating game balance: build a source-driven Monte Carlo balance lab (Rust + rayon) that extracts live game data, simulates human playstyles (AFK→pro), emits win-rate/economy verdicts with confidence intervals, and bruteforce-tunes parameters. Trigger on unfair levels, unreachable shops, farm exploits, interest-curve cliffs, post-content recalibration, or CI balance JSON diffs. Keywords: balance lab, Monte Carlo, win rate, difficulty curve, economy career, playstyle simulation, Resource extraction, GDScript parser, bruteforce tuning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
thedivergentai/Game-Dev-Agentic-Skills☆ 8692026년 10월 17일 업데이트
Use when auditing or recalibrating game balance: build a source-driven Monte Carlo balance lab (Rust + rayon) that extracts live game data, simulates human playstyles (AFK→pro), emits win-rate/economy verdicts with confidence intervals, and bruteforce-tunes parameters. Trigger on unfair levels, unreachable shops, farm exploits, interest-curve cliffs, post-content recalibration, or CI balance JSON diffs. Keywords: balance lab, Monte Carlo, win rate, difficulty curve, economy career, playstyle simulation, Resource extraction, GDScript parser, bruteforce tuning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
thedivergentai/Game-Design-Agentic-Skills☆ 8502026년 10월 13일 업데이트
Find and remove unreachable/unused code safely. Use during cleanup or before a refactor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive228/loopkit☆ 7552026년 7월 15일 업데이트
Find unused functions and dead code in the codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
vibeeval/vibecosystem☆ 5382026년 8월 9일 업데이트
Audits .NET test mock usage by tracing each mock setup through the production code's execution path to find dead, unreachable, redundant, or replaceable mocks. Use when the user asks to audit mock usage, find unused or unnecessary mock setups, check if mocks are needed, reduce mock duplication or over-mocking, simplify test setup, or review whether mock configurations like ILogger/IOptions should use real implementations instead. Supports Moq, NSubstitute, and FakeItEasy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
managedcode/dotnet-skills☆ 4902026년 10월 17일 업데이트
Check agent-produced plans, tests, or code against the owner's actual intent. Find missing meaning, unrequested work, stale truth, unreachable decisions, unsupported completion claims, and implementation debt. Use before approval or merge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
sno-ai/sno-station-skills☆ 4592026년 10월 18일 업데이트
This skill should be used when the user asks to "write a branching story", "interactive fiction", "choose your own adventure", "plan the branches", "choice graph", "add a choice", "gamebook", "Twine", "Ink", "draft a branch", "where the branches rejoin", "add an ending", "unreachable chapter", "path continuity", "state-differs-by-path", or wants to plan, draft, or revise a story project whose chapters carry `choices`. NOT for turning a finished linear book into an interactive edition in Ink or Twine (use adaptation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
danjdewhurst/story-skills☆ 3282026년 10월 15일 업데이트
Design natural vertical street-interview and walk-and-talk video prompts for MiniMax H3 or Seedance 2.0. Use when a user wants spontaneous documentary energy, a referenced recurring person, first-person handheld follow, concise dialogue, moving daylight, believable street parallax, or a consent-led interaction that must fit 4–15 seconds without unreachable beats.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
T8mars/minimax-h3-prompt-skill-T8☆ 2902026년 10월 18일 업데이트