SKILLEMALL.ai
GitHub ↗ RU Sign in

AD postgres-job-queue

基于关系型数据库的作业队列,优先级/批量认领/进度跟踪。关系型数据库-based job queue with priority scheduling, batch claiming,。触发关键词: based, priority, 关系型数据库, job, queue, postgres。提供专业能力支持,覆盖多场景工作流,支持自动化处理。

ClawHub Hermes author: 天轰穿 v1.0.1 MIT-0 2 files body ≈ 1 642 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

基于关系型数据库的作业队列,优先级/批量认领/进度跟踪。关系型数据库-based job queue with priority scheduling, batch claiming,。触发关键词: based, priority, 关系型数据库, job, queue…

As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

ReferencePostgreSQLInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: postgres-job-queue (ClawHub)

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 172 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (postgres-job-queue) differs from the folder (pg-job-queue)
  • 50When it triggers. No condition that starts the skill
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 21 steps
  • 100Execution cost. Instruction body is 1642 tokens
  • low 16 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 172: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (5 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.

External checks

ClawHub: clean
This skill is a markdown guide for building a Postgres-backed job queue, with no hidden files or automatic execution behavior found.
LLM: benign (high) · VirusTotal: · 25 Aug 2026