数据库探查
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "flux-recon":https://skillpi.com/zh/skills/deepskill-8da72df89c009ba57d66a34bf80a5029098ba1910ca5e74c9d77f06fba882880。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/flux-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/flux-recon --skill flux-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 数据库探查 的公开用途。DeepSkill 当前公开目录说明:“数据库探查 — 全面盘点数据库架构、迁移记录、数据量、备份情况、连接池配置及查询模式。适用于被要求“评估此数据库”、“理解数据库架构”或“数据库健康检查”的场景。” 适用场景包括写 SQL 取数、系统管理。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: flux-recon description: 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". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # 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.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供数据库架构、迁移记录、数据量、备份、连接池及查询模式的全面探查,解决数据库健康检查的核心痛点
评分依据
触发词精准覆盖数据库评估、架构理解、健康检查等典型场景,边界清晰
评分依据
步骤划分清晰(Step 0-5),输出格式规范,包含端到端示例和明确的交付机制
评分依据
工具来源明确,参数使用合理,覆盖主要异常场景,具备良好的执行可靠性
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。