pgfaq
Answer PostgreSQL core database questions by researching the local postgres source tree, PostgreSQL documentation under doc/src/sgml, relevant source code, and DeepWiki repository knowledge for postgres/postgres; use when the user asks any PostgreSQL database behavior, internals, SQL, configuration, administration, performance, storage, planner, executor, replication, or documentation question and wants a sourced Markdown answer saved to the current project's markdown directory. Refuse questions about non-PostgreSQL-core projects, including PostgreSQL ecosystem plugins, extensions maintained outside postgres/postgres, external tools, drivers, cloud services, forks, or third-party products.
Best for PostgreSQL developersWorks with GitHub
⌘source
- author
@digoal- repo
- digoal/blog
- language
- HTML
★8.5kstars
1.9kforks
Apr 21, 2026
✦overview.md
Key Features
- ·Answers PostgreSQL core database questions
- ·Researches local PostgreSQL source tree
- ·Searches PostgreSQL documentation in doc/src/sgml
- ·References DeepWiki repository knowledge
- ·Saves sourced Markdown answers to project directory
Use Cases
- →Getting detailed answers about PostgreSQL database behavior and internals
- →Researching SQL, configuration, or administration questions
- →Investigating performance, storage, planner, or executor topics
- →Finding documentation on replication or PostgreSQL core features
Best for
- ✓PostgreSQL developers
- ✓Database administrators researching core features
Not ideal for
- !Questions about third-party extensions or plugins
- !Cloud PostgreSQL services
- !External tools or drivers
- !Non-PostgreSQL-core projects
FAQs
name
pgfaq
description
Answer PostgreSQL core database questions by researching the local postgres source tree, PostgreSQL documentation under doc/src/sgml, relevant source code, and DeepWiki repository knowledge for postgres/postgres; use when the user asks any PostgreSQL database behavior, internals, SQL, configuration, administration, performance, storage, planner, executor, replication, or documentation question and wants a sourced Markdown answer saved to the current project's markdown directory. Refuse questions about non-PostgreSQL-core projects, including PostgreSQL ecosystem plugins, extensions maintained outside postgres/postgres, external tools, drivers, cloud services, forks, or third-party products.
pgfaq
Scope
Use this skill only for questions about the PostgreSQL core open-source project in postgres/postgres.
Refuse the request if it is about a project outside PostgreSQL core, including third-party extensions, plugins, tools, drivers, cloud products, forks, wrappers, or ecosystem projects. State briefly that pgfaq only answers PostgreSQL core questions.
Required Workflow
-
Confirm the current working directory is a PostgreSQL source checkout.
- Verify expected paths exist, especially
doc/src/sgml. - Prefer
git remote -v,git rev-parse --show-toplevel, and directory checks when needed. - If the current directory is not a PostgreSQL source tree, stop and ask the user to run from a postgres source checkout or provide the correct path.
- Verify expected paths exist, especially
-
Classify the question before researching.
- Confirm it is within PostgreSQL core scope.
- Identify likely documentation areas under
doc/src/sgml. - Identify likely source areas, such as
src/backend,src/include,src/bin,src/test, orcontribonly when the topic is a PostgreSQL core/contrib module shipped in the postgres repository.
-
Search local documentation and code first.
$install
1-click copynpx skills add digoal/blog --skill pgfaqSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
2/ 5
lowSome hints are present, but an agent still has to guess many steps.