Results for “counters”

Use this skill when the user is invoking the DOCA PCC Counters tool — the `pcc_counters.sh` bash script under the DOCA tools directory — to arm and read the fixed firmware/hardware PCC (Programmable Congestion Control) diagnostic counters (CNP, RTT, WRED-drop, etc.) on a ConnectX / BlueField device via mst + the mlx5 debugfs `diag_cnt` interface. The script takes two positional args — `set | query` and an mst device path — with no `--help` or subcommands. Trigger even without "pcc_counters.sh" or "PCC counters": "how do I read the CNP / RTT / WRED-drop counters", "PCC counter stuck at zero", "the script says Bad Device", or "is congestion control dropping packets on this port?". Route elsewhere for writing a custom PCC algorithm (doca-pcc), factory firmware PCC config, DOCA install, or fleet-wide CC tuning.

The English summary is being prepared. Showing the original description.

Use this skill to read DOCA hardware-counter events from a `doca_dev` through the per-domain Telemetry reader libraries: `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, and `_pci`. It covers capability checks, context creation, startup, and per-domain reads or samples. Trigger for implicit requests such as "read PCC counters from my BlueField app", "sample DPA counter exports", or "expose PHY, PCI, or DIAG counters from this doca_dev". This is the counter-reader surface, not a NetFlow, IPFIX, or local-socket collector. Route publishing and export to `doca-telemetry-exporter`; route the deployed DOCA Telemetry Service to `doca-dts`, and collectors and plain stdout logging elsewhere.

The English summary is being prepared. Showing the original description.

Implement distributed data synchronization with CRDTs, data structures designed to merge concurrent updates. Covers counters, sets, shared values, and sequences, with incremental updates and tracking of dependencies between operations.

• Implementing shared counters across multiple nodes
• Merging concurrent additions and removals in shared sets
• Sending only changes during data synchronization

Inspect local AGNTCY integration settings and summarize endpoint configuration, the optional SLIM package, transport status, and session counters in a short table. Distinguish available components from unimplemented features without making network calls or changing settings.

• Check whether AGNTCY is configured
• Review SLIM package and endpoint settings
• Inspect mod counters for the current project

Design, implement, tune, or test Three.js action-game encounters. Use for arena layout, enemy composition, spawn pacing, objectives, boss phases, reward cadence, encounter fixtures, and difficulty validation.

The English summary is being prepared. Showing the original description.

doca_telemetry_utils command line on a host with DOCA: discover the diagnostic-counter schema, translate counter names to binary Data IDs and back, and check per-device counter support before committing a DOCA Telemetry exporter config. Start here when telemetry counters vanish between the exporter and the collector: "my exporter ships but the collector sees nothing", "this metric silently drops downstream", "which counters does this BlueField expose", "translate this 0x... back to a counter name", "what do node / pcie_index / depth mean here", or "is this counter supported on this device", even without naming the tool. Writing exporter or collector code belongs to doca-telemetry-exporter / doca-telemetry; DTS deployment to doca-dts; DOCA install or repair to doca-setup.

The English summary is being prepared. Showing the original description.

Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {ship counters to Fluent Bit from the DPU}, {daemon starts but no schema rows appear}. This skill owns the CollectX collection mechanism plus the operator's own doca-telemetry / doca-telemetry-exporter usage; it ROUTES the productized DOCA Telemetry Service (DTS) to public docs (AGENTS.md Non-goal #7), the reader API to doca-telemetry, and the publisher API to doca-telemetry-exporter. Refuse to invent clx symbols, provider names, schema fields, flags, or config paths — describe the class and route to the live source.

The English summary is being prepared. Showing the original description.

Use when you need to implement or improve Java metrics observability with Micrometer — including meter design, naming/tag conventions, cardinality control, timers/counters/gauges/distribution summaries, percentiles/histograms, Actuator/Prometheus integration, and metrics validation through tests. This should trigger for requests such as Improve metrics; Apply Micrometer; Add metrics observability; Refactor Micrometer instrumentation; Add Micrometer timers counters or gauges to Java services. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

Build sequential (stateful) logic circuits including latches, flip-flops, registers, counters, and finite state machines. Covers SR latch, D and JK flip-flops, binary/BCD/ring counters, and Mealy/Moore FSM design with clock signal and timing analysis. Use when a circuit must remember past inputs, count events, or implement a state-dependent control sequence.

The English summary is being prepared. Showing the original description.

Build interactive animations in React or Next.js, including draggable elements, swipe gestures, animated text, SVG line drawing, and loading indicators. Guides API selection and multi-step animation sequences, with touch testing and cleanup practices.

• Building draggable sheets and reorderable lists
• Adding word reveals and animated number counters
• Animating SVG lines and circular progress

Diagnose network errors and intermittent connections on routers, switches, and Linux hosts. Compare both ends of a link and changes in error counts to distinguish cable faults, congestion, and mismatched speed or communication settings.

• Investigating packet loss and intermittent connections
• Checking a switch port with rising CRC errors
• Comparing settings at both ends of a network link

Record concrete improvements in Paperclip when an agent encounters significant workflow friction. The skill turns observed problems with tools, permissions, environments, or documentation into brief internal feedback while keeping the main task moving.

• Suggesting fixes for inconsistent tool behavior
• Reporting missing context or confusing instructions
• Proposing improvements to repeated approval loops

Analyze recorded GPU frames from RenderDoc through command-line tools. Inspect drawing operations, textures, and shaders, compare rendering settings between events or captures, and export images and inspection bundles for reviewing graphics problems.

• Investigating drawing operations in a captured frame
• Exporting textures and shader code
• Comparing rendering settings between events

Create a browser board for daily tasks and numeric goals, then track progress alongside conversations with an AI partner. Includes focus mode, gentle task carryover, progress notes, and a recap you can save at the end of the day.

• Plan a manageable set of tasks for today
• Track reading pages or completed work sessions
• Focus on one task when getting started feels difficult

Apply consistent names to SGLang speculative decoding code, which verifies draft tokens to generate text. Distinguish tokens with or without the bonus token, counts, counters, and arrays when adding identifiers, renaming code, or reviewing changes.

• Naming variables in speculative decoding code
• Renaming identifiers to match their meaning
• Reviewing metric and counter names

Coordinate game area design from story, world context, and visual direction through layout, enemies, rewards, accessibility, and test planning. Compile the results into a level design document, with specialist participation determined by the configured team size.

• Designing a tutorial village or dungeon
• Aligning area layouts with story and visual direction
• Planning enemy encounters and reward placement

Review DXF and STEP/STP files before ordering from SendCutSend.com. Compare measured geometry with current official material and service specifications, then report upload issues, manufacturing constraints, missing information, and specific edits needed.

• Check a DXF before ordering laser cutting
• Review flange dimensions and bend radii
• Check material and secondary service compatibility

Set up credentials and a development environment for your first Google Ads API request to retrieve campaigns. Choose from six official client libraries or direct HTTP requests, with guidance for account IDs, developer tokens, and common authorization errors.

• Prepare credentials for a first Google Ads API integration
• Build an example that retrieves advertising campaigns
• Choose a client library or direct REST requests

Identifies custom Convex code that an existing component or built-in feature could handle. After the current task is complete, it suggests one matching option, explains the connection to the code, and provides installation guidance without installing automatically.

• Reviewing custom scheduled jobs for a suitable component
• Finding components for rate limits or shared counters
• Considering existing options for long-running workflows

Save large text files when write_file or shell_agent encounters payload size limits. Create the parent directory first, write the content with Python through run_shell, and verify the resulting file.

• Saving large source files after write errors
• Writing files into new nested directories
• Saving long JSON or Markdown content

Create a related Excel workbook, PNG diagram, and PDF report in one workflow. It allocates execution attempts across stages, checks output files, and provides retries or simpler versions when generation encounters errors.

• Preparing a comparison table, diagram, and report together
• Creating a PDF that references spreadsheet findings and diagrams
• Allocating execution attempts across several output formats

Handle failed video encoding by checking available encoders, testing a short clip, and trying alternatives. The workflow covers copying without re-encoding, switching codecs, which define video compression, and using MoviePy as another processing option.

• Processing uploaded videos with unknown codecs
• Handling video conversion in containers with limited encoder support
• Testing encoding before a large batch

Track every required output in a visible checklist, update progress as each is completed, and review the original requirements before finishing. When one output is blocked, try alternatives and continue work on the remaining deliverables.

• Tracking completion of several requested files
• Preparing separate email drafts for multiple recipients
• Checking that every required output is finished

Turn unstructured clinical encounter summaries into SOAP notes, a four-part format for medical records. Organize symptoms and findings, include diagnoses with ICD-10 classification codes, and document treatment steps, follow-up timing, and reasons to return for care.

• Converting unstructured clinical summaries into SOAP notes
• Documenting diagnoses with ICD-10 codes and supporting reasoning
• Organizing treatment details, dosages, and timelines