Receber por email
← Voltar para o catálogo

openskills-runtime-debug

Diagnose openskills-runtime execution failures in sandboxed paths (Landlock, seatbelt, native script execution, wasm execution) and produce root-cause-first findings with minimal-risk remediation steps.

60estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add Geeksfino/openskills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/openskills-runtime-debug/svg)](https://www.skillteca.com.br/skills/openskills-runtime-debug)

Skills relacionadas

Ver todas de Dados e Análise →

Alerta por categoria

Receba novas skills de Dados e Análise toda segunda

1 email curto, só com as skills novas de Dados e Análise. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

OpenSkills Runtime Debug

Use this skill when debugging runtime failures in runtime/ and execution paths used by run_skill_target, native scripts, or sandbox enforcement.

Primary Targets

  • runtime/src/executor.rs
  • runtime/src/native_runner.rs
  • runtime/src/wasm_runner.rs
  • runtime/src/permissions.rs
  • runtime/tests/sandbox
  • runtime/tests/seatbelt_tests.rs

Workflow

  1. Reproduce with the smallest command that fails.
  2. Classify failure bucket:
  3. sandbox policy issue
  4. feature/config mismatch
  5. script/tool resolution issue
  6. wasm runtime issue
  7. Confirm behavior against tests and existing fallback logic.
  8. Propose the smallest safe fix that preserves security boundaries.
  9. Re-run focused tests, then broader runtime tests.

Recommended Commands

cargo check -p openskills-runtime
cargo test -p openskills-runtime
cargo test -p openskills-runtime seatbelt_tests -- --nocapture

Debug Heuristics

  • Treat silent degradation in sandbox setup as high risk.
  • Prefer explicit error propagation over ignored Result.
  • If fallback behavior is intentional, confirm it is visible in logs and tests.
  • Keep macOS and Linux behavior differences explicit in findings.

Output Format

Return:

  1. Root cause
  2. Impact surface
  3. Fix proposal
  4. Verification evidence
  5. Residual risks
Compartilhar X LinkedIn