Enforce Edgion observability and safety rules for Rust code changes.
npx skills add https://github.com/Pandaala/Edgion --skill coding-standards-pandaala
Please help me install this Agent Skill. Skill: coding-standards Source: https://github.com/Pandaala/Edgion/tree/main/skills/03-coding Command: npx skills add https://github.com/Pandaala/Edgion --skill coding-standards-pandaala
It standardizes how Edgion writes tracing logs, access logs, metrics, and resource sync identifiers so engineers avoid secret/config leakage and keep control-plane and data-plane observability properly separated.
push_err) without leaking dynamic secrets.Use the coding-standards skill during code review or implementation work that touches logging, tracing IDs, access logs, metrics, or shared observability rules in Edgion.
High-intent search queries and answers about installing and using this skill.
Prevent sensitive data leakage in Rust tracing logs by enforcing strict log safety boundaries that prohibit config and dynamic secret exposure across all HTTP, gRPC, and TLS execution paths. This standardizes PluginLog error classification and access-log field semantics to ensure secrets remain isolated.
Separate control-plane and data-plane observability by prohibiting tracing macros on the data-plane hot path and enforcing disciplined Rust coding patterns for long-running paths. This ensures tracing and logging remain strictly isolated to control-plane operations.
Correlate control-plane and data-plane logs when requests fail by propagating standardized rv, sv, and key_name identifiers across all tracing and access log records. This ensures synchronized correlation IDs across HTTP, gRPC, and stream paths for accurate failure tracking.
Add metrics counters and gauges selectively in Rust observability by practicing metrics restraint to avoid histogram and label explosions. Unified metrics management guides when to introduce new counters versus avoiding high-cardinality labels that degrade system performance.
Rust coding rules for graceful degradation in long-running paths require disciplined unwrap and expect avoidance, strict clone usage limitations, and actionable error messages. These patterns ensure long-running execution paths degrade safely without panicking or leaking sensitive configuration data.
PluginLog error classification prohibits dynamic secret exposure to maintain strict log safety boundaries during plugin execution summaries. By enforcing push_err rules without leaking secrets, it standardizes how plugin decisions are recorded across all observability paths.
majiayu000Configure Prometheus metrics, OpenTelemetry traces, and JSON logs for LiteLLM gateway.
Canhada-LabsOrchestrate real-time market data systems with Python for order books and VWAP calculations.
louloulinAutomate logging, metrics, and tracing collection for distributed systems.
peancharoenRun static analysis tools to detect linting, type, and security issues across source code.