foryourhealth111-pixel/Vibe-Skills / bundled/skills/structured-content-storage
structured-content-storage
VerifiedEnforces structured, highly documented storage for code and data projects. Use when working on machine learning scripts, data processing, code creation, or script modification that should preserve clear structure and documentation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| assets/templates/CHANGELOG-template.md | markdown | 3.3 KB |
| assets/templates/DATA_DICTIONARY-template.md | markdown | 6.0 KB |
| assets/templates/PROCESS-template.md | markdown | 7.9 KB |
| assets/templates/data-processing-README.md | markdown | 3.5 KB |
| assets/templates/ml-project-README.md | markdown | 2.4 KB |
| references/comment-guidelines.md | markdown | 16.2 KB |
| references/directory-templates.md | markdown | 9.9 KB |
| references/documentation-standards.md | markdown | 6.9 KB |
| references/index.md | markdown | 1.3 KB |
assets/templates/DATA_DICTIONARY-template.md
View on GitHub# DATA_DICTIONARY Template
Comprehensive documentation of all data fields and schemas.
## Overview
- **Dataset Name**: [Name of dataset]
- **Source**: [Where the data comes from]
- **Update Frequency**: [How often data is updated]
- **Date Range**: [Start date] to [End date]
- **Total Records**: [Number of records]
---
## Raw Data
### File: [filename.csv]
**Location**: `data/raw/[filename.csv]`
**Description**: [Brief description of what this file contains]
**Schema**:
| Field Name | Type | Description | Valid Range / Values | Constraints | Notes |
|------------|------|-------------|---------------------|-------------|-------|
| id | string | Unique identifier | UUID format | NOT NULL, PRIMARY KEY | Auto-generated |
| timestamp | datetime | Record timestamp | 2020-01-01 to present | NOT NULL | ISO 8601 format |
| value | float | Measurement value | -999.99 to 999.99 | NOT NULL | Rounded to 2 decimals |
| category | string | Category label | ['A', 'B', 'C'] | NOT NULL | Enum type |
| status | string | Record status | ['active', 'inactive'] | NOT NULL | Default: 'active' |
| metadata | json | Additional metadata | Valid JSON | NULLABLE | Optional field |
**Example Record**:
```json
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"timestamp": "2026-01-19T10:30:00Z",
"value": 123.45,
"category": "A",
"status": "active",
"metadata": {"source": "sensor_01", "quality": "high"}
}
```
**Data Quality**:
- Completeness: 98.5%
- Missing values: 1.5% (primarily in metadata field)
- Duplicates: 0.2% (based on id field)
---
## Processed Data
### File: [filename_processed.csv]
**Location**: `data/processed/[filename_processed.csv]`
**Description**: [Brief description of processed data]
**Schema**:
| Field Name | Type | Description | Valid Range / Values | Constraints | Notes |
|------------|------|-------------|---------------------|-------------|-------|
| id | string | Unique identifier | UUID format | NOT NULL, PRIMARY KEY | From raw data |
| timestamp | datetime | Record timestamp | 2020-01-01 to present | NOT NULL | ISO 8601 format |
| value | float | Measurement value | -999.99 to 999.99 | NOT NULL | From raw data |
| value_normalized | float | Normalized value | 0.0 to 1.0 | NOT NULL | **NEW**: Min-max normalized |
| category | string | Category label | ['A', 'B', 'C'] | NOT NULL | From raw data |
| category_encoded | int | Encoded category | 0, 1, 2 | NOT NULL | **NEW**: Label encoded |
| status | string | Record status | ['active', 'inactive'] | NOT NULL | From raw data |
| is_outlier | boolean | Outlier flag | true/false | NOT NULL | **NEW**: IQR-based detection |
**Transformations Applied**:
1. **value_normalized**: Min-max normalization
- Formula: `(value - min) / (max - min)`
- Min: -999.99
- Max: 999.99
2. **category_encoded**: Label encoding
- 'A' → 0
- 'B' → 1
- 'C' → 2
3. **is_outlier**: Outlier detection using IQR method
- Threshold: 1.5 * IQR
- Outliers flagged but not removed
**Data Quality**:
- Completeness: 100% (missing values handled)
- Records removed: 1,234 (duplicates and invalid entries)
- Outliers detected: 567 (0.5%)
---
## Field Definitions
### Common Fields
**id (Identifier)**
- **Purpose**: Unique identifier for each record
- **Format**: UUID v4 (e.g., 550e8400-e29b-41d4-a716-446655440000)
- **Generation**: Auto-generated at data collection
- **Uniqueness**: Guaranteed unique across all records
**timestamp (Datetime)**
- **Purpose**: When the record was created or event occurred
- **Format**: ISO 8601 (YYYY-MM-DDTHH:MM:SSZ)
- **Timezone**: UTC
- **Precision**: Seconds
- **Example**: 2026-01-19T10:30:00Z
**value (Numeric)**
- **Purpose**: Primary measurement or metric
- **Unit**: [Specify unit, e.g., USD, meters, etc.]
- **Precision**: 2 decimal places
- **Range**: -999.99 to 999.99
- **Special values**: None (no NaN or Inf)
**category (Categorical)**
- **Purpose**: Classification or grouping
- **Type**: Enum
- **Values**:
- 'A': [Description of category A]
- 'B': [Description of category B]
- 'C': [Description of category C]
- **Default**: None (must be specified)
---
## Data Sources
### Source 1: [Source Name]
- **Type**: [Database, API, File, etc.]
- **Location**: [URL or path]
- **Access**: [How to access]
- **Update frequency**: [Daily, hourly, etc.]
- **Reliability**: [High, medium, low]
### Source 2: [Source Name]
- **Type**: [Database, API, File, etc.]
- **Location**: [URL or path]
- **Access**: [How to access]
- **Update frequency**: [Daily, hourly, etc.]
- **Reliability**: [High, medium, low]
---
## Data Collection Process
1. **Extraction**: [How data is extracted from source]
2. **Validation**: [What validation checks are performed]
3. **Storage**: [Where and how data is stored]
4. **Update**: [How and when data is updated]
---
## Data Quality Rules
### Completeness
- All NOT NULL fields must have values
- Missing values in optional fields are acceptable
### Validity
- Numeric fields must be within specified ranges
- Categorical fields must match allowed values
- Datetime fields must be valid ISO 8601 format
### Consistency
- id must be unique across all records
- timestamp must be chronologically valid
- Related fields must be logically consistent
### Accuracy
- Values must match source data
- Transformations must be correctly applied
- No data corruption during processing
---
## Known Issues and Limitations
1. **Issue**: [Description of known data quality issue]
- **Impact**: [How it affects analysis]
- **Workaround**: [How to handle it]
2. **Limitation**: [Description of data limitation]
- **Impact**: [What analyses are not possible]
- **Future**: [Plans to address]
---
## Change History
### 2026-01-19
- Added `value_normalized` field to processed data
- Added `is_outlier` flag for outlier detection
- Updated data quality metrics
### 2026-01-15
- Initial data dictionary created
- Documented raw and processed schemas
---
## Contact
For questions about this data dictionary:
- **Maintainer**: [Name]
- **Email**: [Email]
- **Last Updated**: [Date]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |