Skip to content
Back to skills

2625 Technical Patterns 0e516b8b

ASecurity

- [ ] New code uses `strcmp()`, not `matches()` for argument comparison - [ ] Proper use of `NEXT_ARG()`, `NEXT_ARG_OK()`, `PREV_ARG()` - [ ] Error helpers used correctly: `invarg()`, `duparg()`, `missarg()` - [ ] All output uses `print_XXX()` helpers, not raw `fprintf(fp, ...)` - [ ] Error messages go to stderr, not stdout - [ ] `open_json_object()` / `close_json_object()` properly paired - [ ] `open_json_array()` / `close_json_array()` properly paired - [ ] Uses `PRINT_ANY` where possible, ...

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
developmentgoapi

Works with

  • api

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2625-technical-patterns_0e516b8b --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2625 Technical Patterns 0e516b8b?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2625 Technical Patterns 0e516b8b
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2625-technical-patterns-0e516b8b/badge)](https://www.skillsdirectory.com/skills/tools-only-2625-technical-patterns-0e516b8b)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md


### 2. Argument Parsing
- [ ] New code uses `strcmp()`, not `matches()` for argument comparison
- [ ] Proper use of `NEXT_ARG()`, `NEXT_ARG_OK()`, `PREV_ARG()`
- [ ] Error helpers used correctly: `invarg()`, `duparg()`, `missarg()`

### 3. JSON Output
- [ ] All output uses `print_XXX()` helpers, not raw `fprintf(fp, ...)`
- [ ] Error messages go to stderr, not stdout
- [ ] `open_json_object()` / `close_json_object()` properly paired
- [ ] `open_json_array()` / `close_json_array()` properly paired
- [ ] Uses `PRINT_ANY` where possible, not separate JSON/text paths
- [ ] Rates/times use proper helpers for human-readable vs raw JSON values

### 4. Memory Safety
- [ ] All allocations checked for NULL
- [ ] No buffer overflows
- [ ] Memory freed on all error paths
- [ ] Use goto for centralized cleanup when appropriate

### 5. Netlink Handling
- [ ] Proper request structure initialization with designated initializers
- [ ] Correct use of `addattr_l()`, `addattr32()`, `addattr_nest()`
- [ ] Nested attributes properly closed with `addattr_nest_end()`
- [ ] Error return values checked

### 6. Kernel Compatibility
- [ ] uapi header updates in separate patch from functionality
- [ ] uapi changes reference upstream kernel commit
- [ ] Code handles older kernels gracefully
- [ ] Runtime feature detection where appropriate
- [ ] no #ifdef KERNEL_VERSION

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.