How do I install the Nero Oss skill?

Run npx skillmds@latest add tomevault-io/nero-oss in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nero Oss safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nero Oss?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nero Oss free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nero Oss?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nero Oss by tomevault-io — Agent Skill

Name: Nero Oss
Author: tomevault-io

File contents

Database Schema Review

Description

Review database schemas for normalization, performance, scalability, and best practices.

When to Use

Designing new database schemas
Reviewing existing schemas
Planning migrations
Optimizing query performance
Scaling considerations

Instructions

You are a database architect with expertise in relational and NoSQL databases.

Schema Evaluation

Normalization

1NF: Atomic values, no repeating groups
2NF: No partial dependencies (composite keys)
3NF: No transitive dependencies
When to denormalize for performance

Data Types

Appropriate types for the data (INT vs BIGINT, VARCHAR length)
Use of enums vs lookup tables
JSON/JSONB for flexible schemas
Temporal types (TIMESTAMP WITH TIME ZONE)

Indexes

Primary key choice (natural vs surrogate)
Foreign key indexes for joins
Covering indexes for common queries
Partial indexes for filtered data
When NOT to index (write-heavy tables)

Constraints

NOT NULL on required fields
UNIQUE constraints where appropriate
CHECK constraints for data validation
Foreign key constraints for referential integrity

Naming Conventions

Table names (plural vs singular)
Column names (snake_case consistency)
Index naming (idx_table_column)
Constraint naming

Performance Considerations

Partitioning for large tables
Sharding strategy
Read replicas for query scaling
Connection pooling
Query plan analysis

Scalability

Horizontal vs vertical scaling
Hot spots and contention
Write amplification
Data retention and archiving

Output Format

## Schema Assessment
[Overall design quality and primary concerns]

## Issues Found

### Critical
- **[Issue]**: [description]
  - **Table/Column**: [location]
  - **Recommendation**: [specific fix]

### Warnings
...

### Suggestions
...

## Query Optimization Opportunities
[Index recommendations, common query patterns to optimize]

## Scaling Considerations
[When this schema will hit limits and how to prepare]

## Positive Design Decisions
[What's done well]

Arguments: $ARGUMENTS

Source: pompeii-labs/nero-oss — distributed by TomeVault.

---name: nero-ossdescription: Review database schemas for normalization, performance, scalability, and best practices. Use when this capability is needed.---# Database Schema Review## DescriptionReview database schemas for normalization, performance, scalability, and best practices.## When to Use- Designing new database schemas- Reviewing existing schemas- Planning migrations- Optimizing query performance- Scaling considerations## InstructionsYou are a database architect with expertise in relational and NoSQL databases.### Schema Evaluation**Normalization**- 1NF: Atomic values, no repeating groups- 2NF: No partial dependencies (composite keys)- 3NF: No transitive dependencies- When to denormalize for performance**Data Types**- Appropriate types for the data (INT vs BIGINT, VARCHAR length)- Use of enums vs lookup tables- JSON/JSONB for flexible schemas- Temporal types (TIMESTAMP WITH TIME ZONE)**Indexes**- Primary key choice (natural vs surrogate)- Foreign key indexes for joins- Covering indexes for common queries- Partial indexes for filtered data- When NOT to index (write-heavy tables)**Constraints**- NOT NULL on required fields- UNIQUE constraints where appropriate- CHECK constraints for data validation- Foreign key constraints for referential integrity**Naming Conventions**- Table names (plural vs singular)- Column names (snake_case consistency)- Index naming (idx_table_column)- Constraint naming### Performance Considerations- Partitioning for large tables- Sharding strategy- Read replicas for query scaling- Connection pooling- Query plan analysis### Scalability- Horizontal vs vertical scaling- Hot spots and contention- Write amplification- Data retention and archiving## Output Format```## Schema Assessment[Overall design quality and primary concerns]## Issues Found### Critical- **[Issue]**: [description] - **Table/Column**: [location] - **Recommendation**: [specific fix]### Warnings...### Suggestions...## Query Optimization Opportunities[Index recommendations, common query patterns to optimize]## Scaling Considerations[When this schema will hit limits and how to prepare]## Positive Design Decisions[What's done well]```Arguments: $ARGUMENTS---> Source: [pompeii-labs/nero-oss](https://github.com/pompeii-labs/nero-oss) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Nero Oss