Name: netalertx-database-patterns
Rating: 68 (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

81%

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

76%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 exceptionally dense, competent patterns reference with concrete SQL/Python and clear decision guidance. Its main weakness is the absence of validation/feedback steps for the database and batch operations it describes, which caps workflow clarity.

Suggestions

Add a short validation/feedback step to the trigger pattern, e.g. after creating the trigger, run a test UPDATE and confirm a DevicesHistory row is inserted only for tracked fields, then revert.

Add a verification note for the event-sourced logging section showing how to confirm retention (e.g. a DELETE-by-timestamp check) so the destructive pruning path has an explicit checkpoint.

Consider moving the dated write-path inventory table into a references/ file (e.g. WRITE_PATHS.md) and keeping a one-line pointer in SKILL.md, since it is rot-prone and the largest single block.

Dimension	Reasoning	Score
Conciseness	Dense and information-rich with no padding or basic-concept explanations; assumes Claude's competence and every section (write-path inventory, FIELD_SOURCE_MAP, attribution rules, trigger template, schema) earns its place.	5 / 5
Actionability	Provides copy-paste-ready SQL schema and a concrete FIELD_SOURCE_MAP plus actionable decision tables, but the trigger example is a template with placeholders ('SomeTable', 'TRACKED_FIELDS') and an ellipsis ('Repeat for each tracked field...'), leaving a minor gap from fully executable.	4 / 5
Workflow Clarity	The content is a pattern/decision catalog rather than a sequenced multi-step workflow, and because it governs database operations with batch (executemany) and destructive (DELETE) paths yet teaches no validation or verify-the-trigger feedback loop, workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clear headed sections with logical flow and no nested references; the minor gap is that the large dated write-path inventory ('as of 2026-07-04') and the DevicesHistory schema are inlined in SKILL.md rather than split into a reference file.	4 / 5
	Total	16 / 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, well-targeted description with an explicit 'Use when' clause and concrete, niche-specific triggers. The only soft spot is the 'what' statement being a domain label rather than an action list.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete use-cases ('designing features that write to the Devices table', 'implementing audit/history logging', 'choosing between trigger-based vs Python-hook approaches'), but the leading 'what' is a domain label ('NetAlertX database architecture patterns') rather than a list of concrete actions, leaving a minor coverage gap.	4 / 5
Completeness	Explicitly states both what ('NetAlertX database architecture patterns') and when ('Use 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	Good natural keyword coverage for the target audience ('Devices table', 'audit/history logging', 'trigger-based vs Python-hook'), though it lacks synonyms or file extensions that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clear, narrow niche (NetAlertX Devices-table write patterns) with distinct triggers that would not plausibly fire for an unrelated skill.	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: 257431b

Reviewed: 2 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.