eBPF BCC Tools Kernel & System Performance Tracing
Verified SecureCreated by IO Visor Project•devops Workflow
Diagnose elusive Linux performance bottlenecks, disk latency spikes, and socket drops using BCC.
mkdir -p ~/.agents/skills/ebpf-bcc-kernel-troubleshooting && curl -fsSL https://askills.dev/api/skills/ebpf-bcc-kernel-troubleshooting/raw -o ~/.agents/skills/ebpf-bcc-kernel-troubleshooting/SKILL.md
Client Trigger & Invocation Simulator
$ebpf-bcc-kernel-troubleshooting <your task>Type `$ebpf-bcc-kernel-troubleshooting` in the chat or invoke via natural language. Codex automatically identifies the skill from ~/.agents/skills or project .skills, mounts bundled scripts, and executes inside the workspace sandbox.
$ebpf-bcc-kernel-troubleshooting Trace runaway CPU spikes caused by frequent short-lived child processes using execsnoop.
Overview & Problem Solved
When modern frontier LLMs (like Claude 3.7, GPT-4o, or deep reasoning agents) execute complex domain tasks without standard operating procedures, they frequently suffer from context drift, incorrect CLI arguments, or non-standard file hierarchies. eBPF BCC Tools Kernel & System Performance Tracing eliminates probabilistic guessing by supplying the Agent with an authoritative, sandboxed execution specification.
By packaging verified workflows into a structured SKILL.md manifest, this skill establishes deterministic boundaries, verifies dependencies, and executes tasks using proven engineering conventions.
Operational Impact: Without Skill vs. With Skill
Raw frontier models possess deep knowledge, but probabilistic prompting lacks rigid engineering guardrails. Packaging eBPF BCC Tools Kernel & System Performance Tracing into a verified SKILL.md transforms speculative model behavior into reproducible, deterministic delivery.
- Speculative CLI Flags: Model guesses experimental command arguments or deprecated API endpoints.
- Lazy Placeholder Code: Outputs
// TODO: implement error handlingor skips critical verification phases. - Directory Pollution: Generates non-standard file structures that break existing project linters and monorepo roots.
- Extraneous Context Bloat: Wastes thousands of output tokens on narrative pleasantries rather than verified deliverables.
function process() {
// TODO: Connect database here
console.log("Done");
}- Codified Workflow Stages: Follows strict step-by-step algorithms explicitly codified in SKILL.md.
- Zero-Placeholder Delivery: Every deliverable is 100% implemented, with complete error boundaries and types.
- Automatic Pre-Flight Check: Agent inspects environment dependencies (Python/Node/Docker) before modifying files.
- Self-Healing Verification: Runs automated linting, test suites, or syntax parsers before concluding the turn.
export async function execute() {
const validated = schema.parse(input);
return await auditAndPersist(validated);
}Core Capabilities & Guarantees
Follows pre-tested instructions and step-by-step algorithms, avoiding experimental or hallucinated flags.
Runs with identical behavioral fidelity across OpenAI Codex, Claude Code, Cursor IDE, and Windsurf Cascade.
Enforces workspace-scoped file mutations and shields environment secrets against accidental prompt leakage.
Automates test verification, linter checks, and syntax validation before completing any user turn.
Agent Execution Pipeline
Intent Matching & Context Ingestion
The agent scans the user request against the skill's YAML frontmatter triggers and loads the verified instructions into active working memory.
Toolchain & Dependency Validation
The runtime verifies that necessary tools, interpreters, and environment configurations exist within the workspace sandbox before proceeding.
Deterministic Execution & Delivery
The agent executes the codified SOP, runs verification checks, and outputs high-fidelity deliverables without extraneous narration.
Validated Prompt Templates
(Click to copy)“Trace runaway CPU spikes caused by frequent short-lived child processes using execsnoop.”
“Generate an I/O latency distribution histogram to diagnose slow NVMe writes using biolatency.”
“Identify which PID is consuming 10Gbps network bandwidth in real time using tcptop.”
Automated Security & Audit Report
Workspace Scoped
Cannot escape workspace rootInstruction Only
Zero system subprocessesOffline Sandbox
No internet egressNone Required
Runs fully standaloneEnterprise & Production Use Cases
Frequently Asked Questions
Q: What makes eBPF BCC Tools Kernel & System Performance Tracing different from a standard MCP server?
MCP (Model Context Protocol) provides external protocol connections to databases or APIs. In contrast, eBPF BCC Tools Kernel & System Performance Tracing is a high-level operational skill (SKILL.md) that teaches AI Agents procedural intelligence, deterministic step-by-step SOPs, parameter constraints, and self-correction workflows.
Q: Is eBPF BCC Tools Kernel & System Performance Tracing compatible with frontier models like Claude 3.7 Sonnet, GPT-4o, and DeepSeek-R1?
Yes. The skill is packaged with standard markdown instructions (SKILL.md) and YAML frontmatter, adhering to the universal agent skill standard natively supported across Codex, Claude Code, Cursor, and Windsurf.
Q: What permissions does eBPF BCC Tools Kernel & System Performance Tracing require in agent mode?
Every listed skill undergoes automated static analysis scoring 98/100. It strictly adheres to workspace-scoped filesystem boundaries and does not execute untrusted remote code.
Q: Can our team customize or extend the rules in this SKILL.md?
Yes. Once installed in your project root (.skills/ebpf-bcc-kernel-troubleshooting/SKILL.md or ~/.agents/skills/ebpf-bcc-kernel-troubleshooting/), you can customize the instructions to include internal team guidelines, custom linters, or proprietary APIs.
SKILL.md Source Specification
---
name: "ebpf-bcc-kernel-troubleshooting"
description: "Diagnose elusive Linux performance bottlenecks, disk latency spikes, and socket drops using BCC."
metadata:
author: "IO Visor Project"
version: "1.0.0"
runtime_compatibility:
- "codex"
- "claude-code"
- "cursor"
- "windsurf"
triggers:
- "run bcc execsnoop"
- "measure disk latency biolatency bcc"
- "trace tcp connections tcptop"
permissions:
fs_read: true
fs_write: "workspace"
shell_exec: false
net_access: false
---
# eBPF BCC Tools Kernel & System Performance Tracing
Troubleshoots production Linux with eBPF BCC (BPF Compiler Collection): biolatency (disk I/O histograms), execsnoop (short-lived process spikes), tcptop (network throughput per process), and opensnoop.
## When to Invoke
Invoke this skill whenever you need to:
- run bcc execsnoop
- measure disk latency biolatency bcc
- trace tcp connections tcptop
## Execution SOP & Rules
1. Install bpfcc-tools package on Linux server matching running kernel headers.
2. Run execsnoop-bpfcc -T to monitor new process execution timestamps, arguments, and return codes.
3. Run biolatency-bpfcc -m 10 to measure disk latency distribution in milliseconds.
4. Run tcpretrans-bpfcc to locate TCP retransmissions and identify network congestion bottlenecks.
## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.
Related Devops Skills
Guarantee minimum pod availability during voluntary node drains and cluster upgrades.
Distribute pods evenly across availability zones, nodes, and regions to prevent outage blast radius.
Monitor per-second Linux system metrics, containers, and hardware performance via Netdata.