archiving-databases

Process use when you need to archive historical database records to reduce primary database size. This skill automates moving old data to archive tables or cold storage (S3, Azure Blob, GCS). Trigger with phrases like "archive old database records", "implement data retention policy", "move historical data to cold storage", or "reduce database size with archival".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

A highly actionable, well-sequenced archival workflow with strong validation checkpoints for a destructive operation; its weaknesses are moderate verbosity in the Examples and a monolithic structure that ignores the existing bundle files.

Suggestions

Wire the body to the bundle files: reference scripts/archival/database_archival.py, assets/archival_template.sql, etc. instead of inlining all SQL, turning the stubs into real referenced material.

Trim the three narrative Examples to concise before/after specs (table size, row count, batch size) to reduce verbosity while keeping the illustrative value.

Move the extended SQL DDL and cloud-upload snippets into reference files and keep SKILL.md as an overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete SQL/CLI with no concept-explanation fluff, but the lengthy narrative Examples and inline SQL that duplicates the (stub) bundle scripts could be tightened or offloaded, so it is not fully lean.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout (CREATE TABLE ... LIKE ... INCLUDING ALL, INSERT ... SELECT *, NOW(), batch_id, COPY ... TO ... WITH CSV HEADER, aws s3 cp ... --sse aws:kms), with placeholders only where flexibility is justified.	3 / 3
Workflow Clarity	Ten clearly sequenced steps with explicit validation for a destructive batch operation ('Verify row counts match', 'Delete from source only after verification', transaction wrapping, batch_id-based restart), plus an error-handling table for recovery.	3 / 3
Progressive Disclosure	The body is well-sectioned but monolithic, and the bundle directories (references/, scripts/, assets/) contain only README stubs that are never referenced or signaled from the body, so content that could be split remains inline.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 description with explicit trigger guidance, natural trigger phrases, and a clear niche; the main weakness is the second-person 'you need to' voice, which lowers specificity per the rubric's voice rule.

Suggestions

Rewrite in third person to avoid the voice penalty, e.g. 'Archives historical database records to reduce primary database size. Use when the user wants to archive old records, implement a retention policy, or move historical data to cold storage.'

Fix the garbled opener 'Process use when' (likely a truncation of 'Processes' or 'Use when') so the lead reads cleanly.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('archive historical database records', 'moving old data to archive tables or cold storage (S3, Azure Blob, GCS)') matching the level-3 anchor, but the second-person phrasing 'you need to archive' incurs the voice penalty, reducing it to 2.	2 / 3
Completeness	Clearly states what it does (archive historical records to reduce primary DB size, move to archive tables or cold storage) and gives explicit when-guidance via 'Trigger with phrases like...', satisfying both what and when.	3 / 3
Trigger Term Quality	Provides four natural user phrases ('archive old database records', 'implement data retention policy', 'move historical data to cold storage', 'reduce database size with archival') giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (database archival to archive tables / S3 / Azure Blob / GCS) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 607d11b

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