Name: netalertx-database-patterns
Rating: 70.39999999999999 (1 reviews)
Author: netalertx

netalertx-database-patterns

NetAlertX database architecture patterns. Use this when designing features that write to the Devices table, implementing audit/history logging, or choosing between trigger-based vs Python-hook approaches.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

83%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent, dense reference skill with executable SQL and concrete attribution rules that assumes Claude's competence. Its main weakness is structure as a pattern catalog rather than a sequenced workflow, so it lacks the validation checkpoints the rubric expects for database/batch operations.

Suggestions

Add an explicit sequenced workflow (e.g., 1. audit write paths against the table, 2. choose trigger vs hook, 3. implement and test against a known write path) with a validation/verification checkpoint before deploying trigger logic.

Consider moving the DevicesHistory reference schema and FIELD_SOURCE_MAP into a references/ file so SKILL.md stays a tighter overview pointing one level deep.

Add a brief verification step for trigger features, such as confirming the AFTER UPDATE trigger fires across an executemany() bulk scan path before considering the feature done.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout — write-path inventory table, FIELD_SOURCE_MAP, attribution rules, and executable SQL all assume Claude's competence with no padding about what SQLite/triggers are; even the storage math ('≈ 280 MB/day vs <1 MB/day') earns its place as concrete justification.	5 / 5
Actionability	Fully executable guidance: real FIELD_SOURCE_MAP, COALESCE/NULLIF attribution expressions, a copy-paste trigger template, and a complete DevicesHistory schema with indexes; placeholders (SomeTable, TRACKED_FIELDS) are explicitly signaled as template slots.	5 / 5
Workflow Clarity	The body presents patterns and decision rules ('always use event-sourced', 'prefer triggers', 'audit ALL write paths') rather than a sequenced multi-step workflow with validation checkpoints; per the destructive/batch cap, database/batch operations without explicit validate-fix-retry feedback loops cannot score above 3.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Devices write paths, attribution, triggers vs hooks, audit logging, reference schema) with no nested references and no bundle files present; not a 5 because the reference schema and FIELD_SOURCE_MAP could live in separate reference files to keep SKILL.md a tighter overview.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capability and trigger conditions with concrete, domain-accurate language. The only minor gap is that the 'what' is framed as use-case scenarios rather than a fuller enumerated capability set.

Dimension	Reasoning	Score
Specificity	Names the domain ('NetAlertX database architecture patterns') plus three concrete action areas ('designing features that write to the Devices table', 'implementing audit/history logging', 'choosing between trigger-based vs Python-hook approaches'); falls short of 5 only because the actions are framed as scenarios rather than an exhaustive enumerated capability list.	4 / 5
Completeness	Explicitly answers both what ('NetAlertX database architecture patterns') and when ('Use this when designing features that write to the Devices table, implementing audit/history logging, or choosing between trigger-based vs Python-hook approaches') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural terms a NetAlertX contributor would actually say ('Devices table', 'audit/history logging', 'trigger-based vs Python-hook'); not a 5 because it omits common synonyms/variations a user might phrase differently.	4 / 5
Distinctiveness Conflict Risk	Highly specific niche (NetAlertX Devices table write paths, attribution, trigger-vs-hook choice) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: netalertx/NetAlertX
Path: .github/skills/database-patterns/SKILL.md
Commit: 014b960

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.