Content
83%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An exemplary lean quick-reference: dense tables and executable SQL with no filler. The only substantive gap is the lack of validation or rollback guidance around the destructive configuration statements, which caps workflow clarity; structure and disclosure are otherwise strong.
Suggestions
Add validation/rollback notes to the 設定範本 section, e.g. a check query to verify connections/timeouts after pg_reload_conf(), and guidance to revert REVOKE/ALTER SYSTEM changes if issues arise.
Move the anti-pattern detection queries and configuration templates into a references/ file (e.g. references/detection.sql, references/config.sql) to keep SKILL.md as a tighter overview.
Briefly note prerequisites for the monitoring and detection queries (e.g. pg_stat_statements must be enabled) so they fail loudly rather than silently for users on default configurations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean tables and copy-paste SQL where every token earns its place (e.g. "O(1) vs OFFSET 是 O(n)", "用 SELECT 包裝!"), with zero explanation of concepts Claude already knows. It matches the lean-and-efficient anchor exactly; nothing to trim for a 4. | 5 / 5 |
Actionability | All guidance is fully executable, copy-paste-ready SQL covering the common cases: composite/covering/partial indexes, RLS policy, UPSERT, cursor pagination, FOR UPDATE SKIP LOCKED queue processing, anti-pattern detection queries, and config templates. Specific examples span the whole skill's stated scope. | 5 / 5 |
Workflow Clarity | As a reference skill it is well organized with per-pattern applicability notes, but the 設定範本 section prescribes destructive system-wide statements ("REVOKE ALL ON SCHEMA public FROM public", "ALTER SYSTEM SET max_connections...", "statement_timeout") with no validation or rollback guidance, which the rubric caps at 3. Not 2 because content is clearly organized and each pattern states when it applies. | 3 / 5 |
Progressive Disclosure | Clean section structure with clear headers, tables, and an appropriate pointer to the database-reviewer agent for deeper guidance. Not 5 because at ~140 lines with no bundle files, the config templates and anti-pattern detection queries could live in a references/ file; not 3 because nothing is buried and all content fits the quick-reference purpose. | 4 / 5 |
Total | 17 / 20 Passed |