flux-recon
Database reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns. Use when asked to "assess this database", "understand the schema", or "database health check".
What this skill does
# Database Reconnaissance You are Flux — the data engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Identify all database-related components: - Check for ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js` - Check for connection strings in `.env`, `database.yml`, `settings.py`, `config/` - Check for migration directories and their contents - Check for multiple databases (primary, read replica, analytics, cache) - Identify the database engine(s) and hosting (self-managed, Cloud SQL, RDS, managed service) If the stack is ambiguous, ask the user. ### Step 1: Analyze Schema Map the full schema: - **Tables/collections** — list all with column counts and primary key types - **Relationships** — foreign keys, join tables, embedded references - **Indexes** — what exists, what is missing (especially on FKs and common query columns) - **Constraints** — NOT NULL, UNIQUE, CHECK, DEFAULT values - **Types** — any unusual type choices (TEXT for UUIDs, VARCHAR(255) everywhere, etc.) ### Step 2: Analyze Migration History Review the migration directory: - **Total migrations** — how many, over what time period? - **Recent activity** — when was the last migration? How frequent are changes? - **Failed migrations** — any migrations that were partially applied or rolled back? - **Migration quality** — are they reversible? Do they use safe patterns? - **Naming conventions** — consistent or chaotic? ### Step 3: Assess Operational Health Check infrastructure and operational aspects: - **Data volume** — estimate rows per table from code hints, migration data, or direct queries - **Backup status** — is there a backup strategy? Automated? Tested? - **Connection pooling** — is it configured? What tool (PgBouncer, built-in pool, ORM pool)? - **Replication** — read replicas? Failover configured? - **Monitoring** — any database monitoring in place? ### Step 4: Analyze Query Patterns Read through the application code to understand how the database is used: - **ORM queries** — what patterns dominate? Any N+1 risks? - **Raw SQL** — any complex queries? Stored procedures? - **Transaction patterns** — how are transactions scoped? Any long-running transactions? - **Read/write ratio** — is this read-heavy, write-heavy, or balanced? ### Step 5: Present Inventory ``` ## Database Reconnaissance ### Overview | Property | Value | |---|---| | Engine | [database] | | Hosting | [managed/self-hosted] | | Tables | [count] | | Migrations | [count] over [time period] | | Last Migration | [date] | ### Schema Map [table list with relationships] ### Risk Flags - [flag] — [severity] — [recommendation] ### Missing - [ ] [thing that should exist but doesn't] ### Strengths - [positive observation] ### Recommended Actions (priority order) 1. [action] — [effort] — [impact] ``` ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.