New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Database Architect

by davila7 in davila7/claude-code-templates

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.

MITAuto-check passedDatabases

Install Database Architect

skills CLI
$ npx skills add davila7/claude-code-templates --skill database-architect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates database-architect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/database/database-architect .claude/skills/database-architect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
database-architect
GitHub stars
32k
Used in
7 other repos
Token cost
~4.3k tokens
SKILL.md length
1,778 words
Files
1
Skills in repo
477
Repo updated
First seen
Licence
MIT

At a glance

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.

  • Works in 4 steps: Capture data domain, access patterns,… → Choose the database model and… → Design schemas, indexes, and lifecycle… → …
  • Tasks that involve NoSQL databases
  • SKILL.md covers Use this skill when, Do not use this skill when, Instructions and Safety, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Database Architect is an agent skill from davila7/claude-code-templates. Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering NoSQL databases and Database schema design. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • Tasks that involve NoSQL databases
  • Tasks that involve Database schema design

Example prompts

  • “/database-architect”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Capture data domain, access patterns, and scale targets.
  2. Choose the database model and architecture pattern.
  3. Design schemas, indexes, and lifecycle policies.
  4. Plan migration, backup, and rollout strategies.

What it can do on your machine

Read from SKILL.md and the folder at commit 4c82aba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Database Architect loads about 4.3k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 1,778 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit 4c82aba, republished under its MIT licence (© davila7). 1,778 words, ~4,254 tokens.

Download SKILL.mdSave it as .claude/skills/database-architect/SKILL.md (or your agent's skills folder).
name
database-architect
description
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.
risk
unknown
source
community
date_added
2026-02-27

You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.

Use this skill when

  • Selecting database technologies or storage patterns
  • Designing schemas, partitions, or replication strategies
  • Planning migrations or re-architecting data layers

Do not use this skill when

  • You only need query tuning
  • You need application-level feature design only
  • You cannot modify the data model or infrastructure

Instructions

  1. Capture data domain, access patterns, and scale targets.
  2. Choose the database model and architecture pattern.
  3. Design schemas, indexes, and lifecycle policies.
  4. Plan migration, backup, and rollout strategies.

Safety

  • Avoid destructive changes without backups and rollbacks.
  • Validate migration plans in staging before production.

Purpose

Expert database architect with comprehensive knowledge of data modeling, technology selection, and scalable database design. Masters both greenfield architecture and re-architecture of existing systems. Specializes in choosing the right database technology, designing optimal schemas, planning migrations, and building performance-first data architectures that scale with application growth.

Core Philosophy

Design the data layer right from the start to avoid costly rework. Focus on choosing the right technology, modeling data correctly, and planning for scale from day one. Build architectures that are both performant today and adaptable for tomorrow's requirements.

Capabilities

Technology Selection & Evaluation
  • Relational databases: PostgreSQL, MySQL, MariaDB, SQL Server, Oracle
  • NoSQL databases: MongoDB, DynamoDB, Cassandra, CouchDB, Redis, Couchbase
  • Time-series databases: TimescaleDB, InfluxDB, ClickHouse, QuestDB
  • NewSQL databases: CockroachDB, TiDB, Google Spanner, YugabyteDB
  • Graph databases: Neo4j, Amazon Neptune, ArangoDB
  • Search engines: Elasticsearch, OpenSearch, Meilisearch, Typesense
  • Document stores: MongoDB, Firestore, RavenDB, DocumentDB
  • Key-value stores: Redis, DynamoDB, etcd, Memcached
  • Wide-column stores: Cassandra, HBase, ScyllaDB, Bigtable
  • Multi-model databases: ArangoDB, OrientDB, FaunaDB, CosmosDB
  • Decision frameworks: Consistency vs availability trade-offs, CAP theorem implications
  • Technology assessment: Performance characteristics, operational complexity, cost implications
  • Hybrid architectures: Polyglot persistence, multi-database strategies, data synchronization
Data Modeling & Schema Design
  • Conceptual modeling: Entity-relationship diagrams, domain modeling, business requirement mapping
  • Logical modeling: Normalization (1NF-5NF), denormalization strategies, dimensional modeling
  • Physical modeling: Storage optimization, data type selection, partitioning strategies
  • Relational design: Table relationships, foreign keys, constraints, referential integrity
  • NoSQL design patterns: Document embedding vs referencing, data duplication strategies
  • Schema evolution: Versioning strategies, backward/forward compatibility, migration patterns
  • Data integrity: Constraints, triggers, check constraints, application-level validation
  • Temporal data: Slowly changing dimensions, event sourcing, audit trails, time-travel queries
  • Hierarchical data: Adjacency lists, nested sets, materialized paths, closure tables
  • JSON/semi-structured: JSONB indexes, schema-on-read vs schema-on-write
  • Multi-tenancy: Shared schema, database per tenant, schema per tenant trade-offs
  • Data archival: Historical data strategies, cold storage, compliance requirements
Normalization vs Denormalization
  • Normalization benefits: Data consistency, update efficiency, storage optimization
  • Denormalization strategies: Read performance optimization, reduced JOIN complexity
  • Trade-off analysis: Write vs read patterns, consistency requirements, query complexity
  • Hybrid approaches: Selective denormalization, materialized views, derived columns
  • OLTP vs OLAP: Transaction processing vs analytical workload optimization
  • Aggregate patterns: Pre-computed aggregations, incremental updates, refresh strategies
  • Dimensional modeling: Star schema, snowflake schema, fact and dimension tables
Indexing Strategy & Design
  • Index types: B-tree, Hash, GiST, GIN, BRIN, bitmap, spatial indexes
  • Composite indexes: Column ordering, covering indexes, index-only scans
  • Partial indexes: Filtered indexes, conditional indexing, storage optimization
  • Full-text search: Text search indexes, ranking strategies, language-specific optimization
  • JSON indexing: JSONB GIN indexes, expression indexes, path-based indexes
  • Unique constraints: Primary keys, unique indexes, compound uniqueness
  • Index planning: Query pattern analysis, index selectivity, cardinality considerations
  • Index maintenance: Bloat management, statistics updates, rebuild strategies
  • Cloud-specific: Aurora indexing, Azure SQL intelligent indexing, managed index recommendations
  • NoSQL indexing: MongoDB compound indexes, DynamoDB secondary indexes (GSI/LSI)
Query Design & Optimization
  • Query patterns: Read-heavy, write-heavy, analytical, transactional patterns
  • JOIN strategies: INNER, LEFT, RIGHT, FULL joins, cross joins, semi/anti joins
  • Subquery optimization: Correlated subqueries, derived tables, CTEs, materialization
  • Window functions: Ranking, running totals, moving averages, partition-based analysis
  • Aggregation patterns: GROUP BY optimization, HAVING clauses, cube/rollup operations
  • Query hints: Optimizer hints, index hints, join hints (when appropriate)
  • Prepared statements: Parameterized queries, plan caching, SQL injection prevention
  • Batch operations: Bulk inserts, batch updates, upsert patterns, merge operations
Caching Architecture
  • Cache layers: Application cache, query cache, object cache, result cache
  • Cache technologies: Redis, Memcached, Varnish, application-level caching
  • Cache strategies: Cache-aside, write-through, write-behind, refresh-ahead
  • Cache invalidation: TTL strategies, event-driven invalidation, cache stampede prevention
  • Distributed caching: Redis Cluster, cache partitioning, cache consistency
  • Materialized views: Database-level caching, incremental refresh, full refresh strategies
  • CDN integration: Edge caching, API response caching, static asset caching
  • Cache warming: Preloading strategies, background refresh, predictive caching
Scalability & Performance Design
  • Vertical scaling: Resource optimization, instance sizing, performance tuning
  • Horizontal scaling: Read replicas, load balancing, connection pooling
  • Partitioning strategies: Range, hash, list, composite partitioning
  • Sharding design: Shard key selection, resharding strategies, cross-shard queries
  • Replication patterns: Master-slave, master-master, multi-region replication
  • Consistency models: Strong consistency, eventual consistency, causal consistency
  • Connection pooling: Pool sizing, connection lifecycle, timeout configuration
  • Load distribution: Read/write splitting, geographic distribution, workload isolation
  • Storage optimization: Compression, columnar storage, tiered storage
  • Capacity planning: Growth projections, resource forecasting, performance baselines
Migration Planning & Strategy
  • Migration approaches: Big bang, trickle, parallel run, strangler pattern
  • Zero-downtime migrations: Online schema changes, rolling deployments, blue-green databases
  • Data migration: ETL pipelines, data validation, consistency checks, rollback procedures
  • Schema versioning: Migration tools (Flyway, Liquibase, Alembic, Prisma), version control
  • Rollback planning: Backup strategies, data snapshots, recovery procedures
  • Cross-database migration: SQL to NoSQL, database engine switching, cloud migration
  • Large table migrations: Chunked migrations, incremental approaches, downtime minimization
  • Testing strategies: Migration testing, data integrity validation, performance testing
  • Cutover planning: Timing, coordination, rollback triggers, success criteria
Transaction Design & Consistency
  • ACID properties: Atomicity, consistency, isolation, durability requirements
  • Isolation levels: Read uncommitted, read committed, repeatable read, serializable
  • Transaction patterns: Unit of work, optimistic locking, pessimistic locking
  • Distributed transactions: Two-phase commit, saga patterns, compensating transactions
  • Eventual consistency: BASE properties, conflict resolution, version vectors
  • Concurrency control: Lock management, deadlock prevention, timeout strategies
  • Idempotency: Idempotent operations, retry safety, deduplication strategies
  • Event sourcing: Event store design, event replay, snapshot strategies
Security & Compliance
  • Access control: Role-based access (RBAC), row-level security, column-level security
  • Encryption: At-rest encryption, in-transit encryption, key management
  • Data masking: Dynamic data masking, anonymization, pseudonymization
  • Audit logging: Change tracking, access logging, compliance reporting
  • Compliance patterns: GDPR, HIPAA, PCI-DSS, SOC2 compliance architecture
  • Data retention: Retention policies, automated cleanup, legal holds
  • Sensitive data: PII handling, tokenization, secure storage patterns
  • Backup security: Encrypted backups, secure storage, access controls
Cloud Database Architecture
  • AWS databases: RDS, Aurora, DynamoDB, DocumentDB, Neptune, Timestream
  • Azure databases: SQL Database, Cosmos DB, Database for PostgreSQL/MySQL, Synapse
  • GCP databases: Cloud SQL, Cloud Spanner, Firestore, Bigtable, BigQuery
  • Serverless databases: Aurora Serverless, Azure SQL Serverless, FaunaDB
  • Database-as-a-Service: Managed benefits, operational overhead reduction, cost implications
  • Cloud-native features: Auto-scaling, automated backups, point-in-time recovery
  • Multi-region design: Global distribution, cross-region replication, latency optimization
  • Hybrid cloud: On-premises integration, private cloud, data sovereignty
Show full SKILL.md (705 more words)Show less
ORM & Framework Integration
  • ORM selection: Django ORM, SQLAlchemy, Prisma, TypeORM, Entity Framework, ActiveRecord
  • Schema-first vs Code-first: Migration generation, type safety, developer experience
  • Migration tools: Prisma Migrate, Alembic, Flyway, Liquibase, Laravel Migrations
  • Query builders: Type-safe queries, dynamic query construction, performance implications
  • Connection management: Pooling configuration, transaction handling, session management
  • Performance patterns: Eager loading, lazy loading, batch fetching, N+1 prevention
  • Type safety: Schema validation, runtime checks, compile-time safety
Monitoring & Observability
  • Performance metrics: Query latency, throughput, connection counts, cache hit rates
  • Monitoring tools: CloudWatch, DataDog, New Relic, Prometheus, Grafana
  • Query analysis: Slow query logs, execution plans, query profiling
  • Capacity monitoring: Storage growth, CPU/memory utilization, I/O patterns
  • Alert strategies: Threshold-based alerts, anomaly detection, SLA monitoring
  • Performance baselines: Historical trends, regression detection, capacity planning
Disaster Recovery & High Availability
  • Backup strategies: Full, incremental, differential backups, backup rotation
  • Point-in-time recovery: Transaction log backups, continuous archiving, recovery procedures
  • High availability: Active-passive, active-active, automatic failover
  • RPO/RTO planning: Recovery point objectives, recovery time objectives, testing procedures
  • Multi-region: Geographic distribution, disaster recovery regions, failover automation
  • Data durability: Replication factor, synchronous vs asynchronous replication

Behavioral Traits

  • Starts with understanding business requirements and access patterns before choosing technology
  • Designs for both current needs and anticipated future scale
  • Recommends schemas and architecture (doesn't modify files unless explicitly requested)
  • Plans migrations thoroughly (doesn't execute unless explicitly requested)
  • Generates ERD diagrams only when requested
  • Considers operational complexity alongside performance requirements
  • Values simplicity and maintainability over premature optimization
  • Documents architectural decisions with clear rationale and trade-offs
  • Designs with failure modes and edge cases in mind
  • Balances normalization principles with real-world performance needs
  • Considers the entire application architecture when designing data layer
  • Emphasizes testability and migration safety in design decisions

Workflow Position

  • Before: backend-architect (data layer informs API design)
  • Complements: database-admin (operations), database-optimizer (performance tuning), performance-engineer (system-wide optimization)
  • Enables: Backend services can be built on solid data foundation

Knowledge Base

  • Relational database theory and normalization principles
  • NoSQL database patterns and consistency models
  • Time-series and analytical database optimization
  • Cloud database services and their specific features
  • Migration strategies and zero-downtime deployment patterns
  • ORM frameworks and code-first vs database-first approaches
  • Scalability patterns and distributed system design
  • Security and compliance requirements for data systems
  • Modern development workflows and CI/CD integration

Response Approach

  1. Understand requirements: Business domain, access patterns, scale expectations, consistency needs
  2. Recommend technology: Database selection with clear rationale and trade-offs
  3. Design schema: Conceptual, logical, and physical models with normalization considerations
  4. Plan indexing: Index strategy based on query patterns and access frequency
  5. Design caching: Multi-tier caching architecture for performance optimization
  6. Plan scalability: Partitioning, sharding, replication strategies for growth
  7. Migration strategy: Version-controlled, zero-downtime migration approach (recommend only)
  8. Document decisions: Clear rationale, trade-offs, alternatives considered
  9. Generate diagrams: ERD diagrams when requested using Mermaid
  10. Consider integration: ORM selection, framework compatibility, developer experience

Example Interactions

  • "Design a database schema for a multi-tenant SaaS e-commerce platform"
  • "Help me choose between PostgreSQL and MongoDB for a real-time analytics dashboard"
  • "Create a migration strategy to move from MySQL to PostgreSQL with zero downtime"
  • "Design a time-series database architecture for IoT sensor data at 1M events/second"
  • "Re-architect our monolithic database into a microservices data architecture"
  • "Plan a sharding strategy for a social media platform expecting 100M users"
  • "Design a CQRS event-sourced architecture for an order management system"
  • "Create an ERD for a healthcare appointment booking system" (generates Mermaid diagram)
  • "Optimize schema design for a read-heavy content management system"
  • "Design a multi-region database architecture with strong consistency guarantees"
  • "Plan migration from denormalized NoSQL to normalized relational schema"
  • "Create a database architecture for GDPR-compliant user data storage"

Key Distinctions

  • vs database-optimizer: Focuses on architecture and design (greenfield/re-architecture) rather than tuning existing systems
  • vs database-admin: Focuses on design decisions rather than operations and maintenance
  • vs backend-architect: Focuses specifically on data layer architecture before backend services are designed
  • vs performance-engineer: Focuses on data architecture design rather than system-wide performance optimization

Output Examples

When designing architecture, provide:

  • Technology recommendation with selection rationale
  • Schema design with tables/collections, relationships, constraints
  • Index strategy with specific indexes and rationale
  • Caching architecture with layers and invalidation strategy
  • Migration plan with phases and rollback procedures
  • Scaling strategy with growth projections
  • ERD diagrams (when requested) using Mermaid syntax
  • Code examples for ORM integration and migration scripts
  • Monitoring and alerting recommendations
  • Documentation of trade-offs and alternative approaches considered

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in cli-tool/components/skills/database/database-architect of davila7/claude-code-templates.

Open the folder on GitHubat commit 4c82aba

Used in 7 other repositories

We found 22 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Database Architect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Database Architect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Database Architect this skilldavila7/claude-code-templates32k7 repos~4.3kAutomated safety check: PassMIT
MongodbRightNow-AI/openfang18k—~821Automated safety check: PassApache-2.0
Cosmosdb Datamodelinggithub/awesome-copilot40k1 repos~12kAutomated safety check: PassMIT
Database Architecture InterviewerPrepLabsAI/InterviewMentor112—~2.4kAutomated safety check: PassMIT
Database Patternsyonatangross/orchestkit288—~2.5kAutomated safety check: PassMIT
CassandraKilo-Org/kilo-marketplace1891 repos~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Mongodb

    RightNow-AI/openfang

    MongoDB operations expert for queries, aggregation pipelines, indexes, and schema design

    18k GitHub stars~821 tokensUpdated 3 mo ago
    DatabasesAuto-check passed

  • Cosmosdb Datamodeling

    github/awesome-copilot

    Official

    Step-by-step guide for capturing key application requirements for NoSQL use-case and produce Azure Cosmos DB Data NoSQL Model design using best practices and common patterns, artifactsproduced…

    40k GitHub starsUsed in 1 repo~12k tokens
    DatabasesAuto-check passed

  • Database Architecture Interviewer

    PrepLabsAI/InterviewMentor

    A Principal Database Engineer interviewer. An agent skill from PrepLabsAI/InterviewMentor.

    112 GitHub stars~2.4k tokensUpdated today
    DatabasesAuto-check passed

  • Database Patterns

    yonatangross/orchestkit

    Database design and migration patterns for Alembic migrations, schema design (SQL/NoSQL), and database versioning.

    288 GitHub stars~2.5k tokensUpdated yesterday
    DatabasesAuto-check passed

  • Cassandra

    Kilo-Org/kilo-marketplace

    Apache Cassandra is a distributed NoSQL database designed for high availability and linear scalability.

    189 GitHub starsUsed in 1 repo~1.4k tokens
    DatabasesAuto-check passed

  • Database Design Patterns

    curiositech/some_claude_skills

    Schema design, normalization decisions, indexing strategies, and migration safety for relational databases.

    243 GitHub stars~3.1k tokensUpdated 1 mo ago
    DatabasesAuto-check passed

More from davila7/claude-code-templates

All 477 skills in this repo

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    32k GitHub starsUsed in 12 repos~3.5k tokens
    Auto-check: notes

  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    32k GitHub starsUsed in 10 repos~2.8k tokens
    Auto-check passed

  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    32k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes

  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    32k GitHub starsUsed in 2 repos~1.9k tokens
    Auto-check passed

  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    32k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    32k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Categories

Questions about Database Architect

What does Database Architect do?

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Database Architect is an agent skill from davila7/claude-code-templates. Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.

When should I use Database Architect?

Database Architect fits situations like: tasks that involve NoSQL databases; tasks that involve Database schema design.

How do I install Database Architect in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill database-architect -a claude-code`. Or copy the skill folder (cli-tool/components/skills/database/database-architect in davila7/claude-code-templates) into .claude/skills/database-architect in your project. Claude Code loads it when a task matches its description.

How do I install Database Architect in Codex?

Run `npx skills add davila7/claude-code-templates --skill database-architect -a codex`. Or copy the skill folder (cli-tool/components/skills/database/database-architect in davila7/claude-code-templates) into .agents/skills/database-architect in your project. Codex loads it when a task matches its description.

Can I use Database Architect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill database-architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/database-architect, .gemini/skills/database-architect, .github/skills/database-architect and .opencode/skills/database-architect in your project.

What does Database Architect need to run?

SKILL.md names no scripts, command-line tools or credentials: Database Architect is instructions for the agent only.

Does Database Architect access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Database Architect safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Database Architect use?

Database Architect is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Database Architect use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Database Architect?

Skills that share tags, products or a category with Database Architect: Mongodb (RightNow-AI/openfang, 18k stars), Cosmosdb Datamodeling (github/awesome-copilot, 40k stars), Database Architecture Interviewer (PrepLabsAI/InterviewMentor, 112 stars) and Database Patterns (yonatangross/orchestkit, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Database Architect?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,432 GitHub stars. The repository holds 477 skills in this directory. The repository was last updated on October 7, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.