Content
86%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.
The body is an excellent example of a lean lookup skill: three clearly separated query paths, executable code, and hard-won gotchas (path expansion, backend interface mismatch, pip extras) that only real experience provides. The only notable gaps are placeholder arguments in the Neo4j example and no guidance on how to pick the right backend.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and every token carries non-obvious information ('load_from_file does not expand ~', 'QueryEngine needs an object exposing execute_sparql()'), with no explanations of concepts Claude already knows — matching the 'every token earns its place' anchor rather than the 4 anchor's minor over-explanation. | 5 / 5 |
Actionability | Mostly executable, concrete code ('graph.query("vendor selection", skip=0, limit=20)') plus real dependency/gotcha notes ('needs semantica[tripletstore-oxigraph]'). It falls short of the 5 anchor because the Neo4j example uses ellipsis placeholders ('Neo4jStore(uri=..., user=..., password=...)') and 'store.execute_query(sparql)' references an undefined variable, though it is well above the pseudocode-level 3 anchor. | 4 / 5 |
Workflow Clarity | The routing cue 'Which API you want depends on where the graph lives' plus three cleanly separated per-backend sections makes each query path unambiguous, and read-only queries need no destructive-operation validation. It is not a 5 because the skill never explains how to determine where the graph lives (e.g. checking ~/.semantica/kg.json vs. a running endpoint), leaving a minor gap in selection logic. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the ~80-line body is well-organized into one section per backend with everything needed at the top level, no nested references, and no content that clearly belongs in a separate file — matching the simple-skill case of a clear, well-organized single file. | 5 / 5 |
Total | 18 / 20 Passed |