Audit YAML, model paths, OpenVINO device selection, camera and serial settings, and camera/gimbal calibration values for this repository. Use when parameters appear ignored, deployment differs between machines, or pose and model behavior are suspicious.
HNUST-Dust/Dust_infantry_vision
SkillsMP has collected 14 skills from HNUST-Dust/Dust_infantry_vision. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 14
- GitHub stars
- 4
- GitHub forks
- 1
Skills in this repository
Showing 14 of 14 collected skills.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews…
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module…
Diagnose HikRobot, MindVision, or USB camera discovery, SDK, streaming, frame, and frame-rate failures in this repository. Use when camera initialization fails, frames are empty, FPS is wrong, or exposure/gain/VID-PID settings look suspect.
Safely diagnose this repository's gimbal and cboard serial links, packet framing, CRC, timing, quaternion interpolation, and reconnect behavior. Use for /dev/gimbal failures, stale state, CRC errors, dropped packets, or incorrect control data.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Reproduce and isolate auto-aim detection, tracking, solving, aiming, and planning issues from recorded video in this repository. Use for false positives, missed armors, tracker state changes, aim jitter, fire decisions, or latency regressions.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.