skills.rest
Niller2005
Niller2005COMMUNITY
Explore all skills by this author →
Website𝕏@niller2005GitHub

database-analyzer

Sync production trades.db and analyze trade history, PnL, and balances.

18|3|Updated Jan 2, 2026
Search Tags:#database#audit#sqlite#pnl#anomaly-detection#trades
One-click install
npx skills add https://github.com/Niller2005/PolyFlup --skill database-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-analyzer
Source: https://github.com/Niller2005/PolyFlup/tree/main/.opencode/skill/database-analyzer
Command: npx skills add https://github.com/Niller2005/PolyFlup --skill database-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs production trades.db to keep data aligned, auditable, and ready for historical analysis of trades, balances, and market history.

Core Features & Use Cases

  • Syncs the production trades.db using the sync_db tool.
  • Queries the SQLite database for trade history, PnL, and position data.
  • Verifies database integrity and migration status.
  • Identifies trends or anomalies in the trading data.

Quick Start

Run sync_db to fetch the latest trades.db, then run check_db.py to verify integrity and prepare data for queries.

Frequently Asked Questions about database-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit production SQLite trades database for PnL and balance anomalies?▼

To audit a production SQLite trades database for PnL and balance anomalies, sync the latest trades.db using the sync_db tool, then run check_db.py to verify integrity before querying historical trade data to surface trends and detect anomalies across time and symbols.

What is the best way to sync a production trades database for historical analysis?▼

The best way to sync a production trades database for historical analysis is running the sync_db tool to fetch the latest trades.db, ensuring production data stays aligned and ready for querying trade history, PnL, and position data.

How does database integrity checking work for SQLite trade records?▼

Database integrity checking for SQLite trade records works by running the check_db.py script after syncing, which verifies the database structure, checks migration status, and prepares the data for reliable SQL queries and anomaly detection.

Can I run SQL queries directly against trades.db to identify market trends?▼

Yes, you can run SQL queries or Python scripts directly against trades.db to extract trade history and position data, enabling you to identify trends, analyze historical performance, and detect anomalies across different symbols and time periods.

Do I need to sync trades.db before checking database integrity and migration status?▼

Yes, you need to sync trades.db first to fetch the latest production data before running check_db.py, because integrity verification and migration status checks must run against the most current database state to ensure accurate auditing.

Related Skills

Explore More Data & Analytics Skills→
TrevorEdrisTrevorEdris
2

database-schema-designer

Design production-ready database schemas with normalization, indexing, and migrations.

Community
Basic
Arnutt-NArnutt-N

audit-dashboard

Consolidate real-time HR-IMS audit events into a unified monitoring dashboard.

Community
Advanced
mehdicmehdic

velocity-tracker

Analyze historical project data to compute velocity, cycle times, and trends.

Community
Advanced
tkerseytkersey
66

cron

Manage Codex automations in a local SQLite database via Python CLI.

Community
Intermediate