digoal
- 105 skills
- 0 followers
- 2 days ago last updated
- ▌ Axiom Explainer · digoal bundleWrite Chinese Markdown articles for university students and adults with social experience that explain one viewpoint, axiom, theorem, law, principle, or theory system through "求真讲法、求存讲法、思考", with text/Mermaid and standalone GitHub-renderable SVG files, assumptions, derivation or motivation, applicability boundaries, positive and negative examples, and save the result under the current project's markdown directory. Use when Codex is asked to generate 公理讲解文案、定理讲解、理论体系通俗解读、观点拆解、面向大学生和成年人的图文并茂 Markdown 文章.
- ▌ Blog Cover Poster · digoal bundleTurn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points. Renders HTML/CSS to exact-size PNGs via headless Chrome. Use whenever the user wants cover art, 讲解图/配图, carousel slides, 封面图, poster series, or "content images" from an article/文章/素材/文件, especially for blog, 公众号, 小红书, or social posts. Default output is 1080×1920 PNG named 1.png (cover), 2.png, 3.png … written to the current working directory (the project the user is in) — never the source file's directory.
- ▌ Polardb Daily Check · digoal bundleComprehensive daily health check for PolarDB for PostgreSQL databases, including LogIndex status, HTAP/MPP monitoring, shared storage performance, and high availability checks
- ▌ Postgresql Bi Agent · digoal bundleBusiness intelligence analysis agent for PostgreSQL that discovers database metadata, generates SQL queries for revenue/customer/product metrics, and produces comprehensive analytical reports
- ▌ Postgres Daily Check · digoal bundleThis skill is designed to perform comprehensive daily health checks on a PostgreSQL database. It leverages a suite of specialized SQL queries and analysis logic to provide insights into database availability, performance, activity, maintenance, storage, replication, and archiving status. The skill aims to identify potential issues such as blocking locks, long-running queries, transaction ID wraparound risks, bloat in tables and indexes, connection bottlenecks, and archiving failures.