Device Class Review
Use when reviewing an SNMP::Info pull request or branch that adds or changes a device class, detection in device_type(), or a shared role such as Bridge, LLDP or Entity, including a self-review before opening the pull request.
Install
npx skills add netdisco/snmp-info --skill device-class-reviewgit clone --depth 1 https://github.com/netdisco/snmp-info.git /tmp/snmp-info
mkdir -p ~/.claude/skills
cp -r /tmp/snmp-info/.claude/skills/device-class-review ~/.claude/skills/device-class-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Reviewing SNMP::Info device class changes Compare the branch with its merge base. Read the PR description, the linked issues, `AGENTS.md`, and `.claude/skills/device-class-authoring/SKILL.md`; the authoring skill is the standard the change is held to. ## Mechanical checks Run the CI command from `AGENTS.md` and report each failing test by name. Then check the `AGENTS.md` pull request checklist item by item: test class, SUBCLASSES POD entry, MANIFEST, Changes placement and form, generated files and `$VERSION` untouched, no committed walks or assets, MIBs available in a netdisco-mibs release. ## Behavior checks - **Run it.** A claim about what a method returns is verified by running the class against a walk: the mocked test session, or the walk served by an SNMP simulator on a private port. Reading the code is not evidence. Resolve every leaf to its numeric OID before searching a walk; vendor subtrees look alike. - **Detection.** Every sample routes to the new class, neighboring products still reach their own classes, and the change adds no GET for devices outside the target branch. Count the GETs a plain device of the same enterprise now receives, across repeated `device_type()` calls and with `Offline` set. Check the vendor's MIBs for other product lines under the matched branch; a whole-enterprise match needs a reason. - **Merge order.** For each hash a class merges, the parents appear in
Details
- Skill name
device-class-review- Repository
- netdisco/snmp-info
- Path
.claude/skills/device-class-review/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Device Class Review skill do?
Use when reviewing an SNMP::Info pull request or branch that adds or changes a device class, detection in device_type(), or a shared role such as Bridge, LLDP or Entity, including a self-review before opening the pull request.
How do I install the Device Class Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add netdisco/snmp-info --skill device-class-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Device Class Review popular?
It lives in netdisco/snmp-info, which has 44 GitHub stars and 48 forks.
Related skills
Device Class Authoring
44netdisco/snmp-info
Use when adding or changing an SNMP::Info device class (lib/SNMP/Info/Layer*/Vendor.pm), its detection in device_type(), its tests or its POD, or when choosing between a standard MIB and a vendor MIB for a method.
Building Devsecops Pipeline with Gitlab CI
100adriannoes/awesome-agentic-ai
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
Repo Scan
80KerberosClaw/kc_ai_skills
Use when the user wants to evaluate a GitHub repository before installing, running, forking, or depending on it. Takes a GitHub repo URL, cleans tracking params, shallow-clones to /tmp, inspects dependency/supply-chain risk, static vulnerability patterns, issue-reported security problems, maintainer health, and produces a risk summary. NOT for reviewing the user's own PR diff or for running untrusted code.
Changelog Updates
88jonathimer/devmarketing-skills
Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: "changelog", "release notes", "product updates", "version communication", "breaking changes", "deprecation notice", "what's new", "release communication", "developer updates", "API versioning", "migration announcement
Keeping Git Repos Clean
115wdm0006/python-skills
Prevents, detects, and remediates files that should never be committed — secrets (.env, API tokens, hardcoded credentials) and dev artifacts (build output, scratch databases, editor/OS files). Covers .gitignore (and why it does not untrack), git rm --cached, auditing tracked files, history scrubbing, and credential rotation. Use when a repo has committed secrets or junk, when setting up a new repo's ignore rules, or when reviewing what a repo actually tracks.
Github Presence
88jonathimer/devmarketing-skills
When the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include "GitHub README," "README optimization," "GitHub profile," "GitHub stars," "GitHub discoverability," "awesome lists," or "GitHub marketing.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.