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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/database-patterns/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

A highly actionable, information-dense reference with complete executable SQL and project-specific rationale. Its main gaps are the absence of validation checkpoints for database/batch operations and no progressive disclosure into separate reference files.

Suggestions

Add a short verification workflow for trigger/audit changes (e.g., run a test UPDATE, confirm the DevicesHistory row and changedBy attribution, then clean up) so database operations have explicit validation checkpoints.

Move the time-sensitive write-path inventory (and its 2026-07-04 date) into a references file or a clearly marked 'as-of' section so SKILL.md stays lean and staleness is signaled by structure rather than an inline date.

Split the DevicesHistory schema and FIELD_SOURCE_MAP into a reference file (e.g., references/schema.md) linked from the body to enable one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no generic concept explanations), but it carries an inline time-sensitive date ("as of 2026-07-04") outside any deprecated/old-patterns section, which the guidelines penalize, so it sits at the mostly-efficient-but-could-be-tightened anchor rather than 3.	2 / 3
Actionability	Provides fully executable, copy-paste-ready artifacts — a complete CREATE TRIGGER with guards, the FIELD_SOURCE_MAP dict, COALESCE attribution expressions, and a full DevicesHistory schema with indexes — matching the executable-and-specific anchor.	3 / 3
Workflow Clarity	Decision guidance is clear (prefer triggers, when hooks are appropriate) but there is no sequenced multi-step workflow, and database/batch operations (executemany, triggers) lack validation/verification checkpoints, which caps this dimension at 2 per the feedback-loop guidance.	2 / 3
Progressive Disclosure	Content is well-sectioned but entirely inline in a ~137-line SKILL.md with no bundle files and no one-level-deep references; the write-path inventory and schema are candidates for separate reference files, fitting the structure-present-but-content-should-be-separate anchor rather than the under-50-line simple-skill exception.	2 / 3
	Total	9 / 12 Passed

Description

85%Weight 40%Scale 1-3

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 tightly scoped, well-structured description that answers both what and when with an explicit Use-when clause and concrete, distinguishable triggers. The only weakness is trigger-term breadth — the keywords are correct but technical and lack common variations.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "designing features that write to the Devices table", "implementing audit/history logging", "choosing between trigger-based vs Python-hook approaches" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly states what ("NetAlertX database architecture patterns") and when via a clear "Use this when..." clause with concrete triggers, matching the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Relevant domain terms (audit/history logging, trigger-based vs Python-hook, Devices table) are natural for a NetAlertX contributor, but coverage is narrow and technical with no common variations, fitting the some-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped to a specific codebase (NetAlertX, Devices table) with niche triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 12 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: 20ddf48

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