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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill archiving-databases89
Quality
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific actions, excellent trigger term coverage with natural user phrases, clearly answers both what and when, and occupies a distinct niche. The only minor issue is the awkward phrasing 'Process use when' at the start, but this doesn't significantly impact functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'archive historical database records', 'moving old data to archive tables or cold storage', and names specific storage targets (S3, Azure Blob, GCS). | 3 / 3 |
Completeness | Clearly answers both what (automates moving old data to archive tables or cold storage) and when (explicit 'Use when' equivalent with 'Trigger with phrases like...' providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'archive old database records', 'data retention policy', 'move historical data to cold storage', 'reduce database size with archival'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on database archival and data retention - distinct triggers like 'archive old database records' and 'cold storage' are unlikely to conflict with general database or file management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and concrete executable examples. The main weakness is verbosity - the skill could be more concise by removing explanatory text and potentially splitting detailed procedures into separate files. The error handling table and examples section add significant value.
Suggestions
Trim the Prerequisites section - remove explanatory items like 'Understanding of data retention requirements' that Claude already knows
Consider moving cloud storage archival (step 6) and data retrieval procedures (step 9) to separate reference files to improve progressive disclosure
Remove redundant explanations like 'Focus on tables where historical data is rarely queried' - the examples already make this clear
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary context like explaining what archival candidates are and basic concepts Claude would know. The prerequisites section could be tightened, and some explanatory text could be removed while preserving the actionable content. | 2 / 3 |
Actionability | Excellent executable guidance throughout with specific SQL commands, CLI commands, and concrete examples. Every step includes copy-paste ready code snippets with actual syntax for PostgreSQL, AWS S3, and other tools. | 3 / 3 |
Workflow Clarity | Clear 10-step sequence with explicit validation checkpoints (verify row counts match, verify no active references, wrap in transaction for atomicity). Includes feedback loops for error recovery and batch processing with restart capability. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), but the skill is quite long (~100 lines of dense content) and could benefit from splitting detailed procedures (cloud storage archival, retrieval procedures) into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Reviewed
Table of Contents
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.