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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured workflow skill with concrete tool/path guidance and an explicit validation loop that earns top workflow-clarity marks. Minor conciseness redundancy and the absence of copy-paste code examples keep actionability and conciseness at 4.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's knowledge of PostgreSQL, but the refusal policy and some research-discipline points are restated across the description, Scope, and Research Discipline sections, leaving minor trim opportunities.	4 / 5
Actionability	Concrete, specific guidance with real tool names and paths (git remote -v, rg in doc/src/sgml, mcp__deepwiki__ask_question with repoName 'postgres/postgres', src/backend etc.) and a copyable answer-format template, but no full executable code/SQL examples.	4 / 5
Workflow Clarity	A clear 7-step sequence with an explicit validation feedback loop in step 6 (DeepWiki correctness check, re-check against local docs, revise, repeat until no material issues) and a stop-checkpoint in step 1 for non-postgres directories.	5 / 5
Progressive Disclosure	Well-organized into Scope, Required Workflow, Answer Format, and Research Discipline sections with no external bundle files needed; slightly over the simple-skill 50-line threshold so it does not fully qualify for the 5-anchor exception.	4 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit what/when structure, comprehensive natural trigger terms, and clear boundary/refusal guidance. The only minor weakness is that the core capability is one action (answer via research) supported by several sources rather than multiple distinct actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions—researching the local source tree, doc/src/sgml docs, source code, and DeepWiki, plus saving a Markdown answer and refusing out-of-scope topics—but the core verb is a single 'answer by researching' with multiple sources rather than fully distinct actions.	4 / 5
Completeness	Explicitly answers both what ('Answer PostgreSQL core database questions by researching...') and when ('use when the user asks any PostgreSQL database behavior, internals, SQL... question'), with concrete trigger phrases and a stated output destination.	5 / 5
Trigger Term Quality	Comprehensive natural keyword list users would actually say: 'SQL', 'configuration', 'administration', 'performance', 'storage', 'planner', 'executor', 'replication', and 'documentation question', covering synonyms and sub-domains.	5 / 5
Distinctiveness Conflict Risk	Clear niche scoped to PostgreSQL core in postgres/postgres with an explicit refusal clause for extensions, drivers, cloud services, forks, and third-party products, minimizing wrong-skill triggering.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: digoal/blog
Path: skills/pgfaq/SKILL.md
Commit: 3b9c83d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.