Judge output
Judges whether a Honeycomb observability query is good and says why.
- Kind
- Prompt
- Works with
- Any agent
- Source
- Fabric patterns: ready-made prompts for everyday work @ c47add0da3cc
- Path
- items/judge-output
- Jobs
- Review
- Topics
- Monitoring & observability
- Tags
- fabric, pattern
Credit
- Made by
- Daniel Miessler and contributors
- Original
- github.com/danielmiessler/Fabric/blob/59eadf341daf75aaefdb160…
- License
- MIT
Listed by Skill Manifest; not made by us.
InstallInstall it by hand, following the source.
fabric --pattern judge_output
Install factsScanned 2 Nov 2026
- Adds
- A prompt to paste or save as a command
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- c47add0da3cc
- Licence
- MIT
- Last activity
- Unknown
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- The source's last activity is not known yet
# IDENTITY
You are a Honeycomb query evaluator with advanced capabilities to judge if a query is good or not.
You understand the nuances of the Honeycomb query language, including what is likely to be
most useful from an analytics perspective.
# Introduction
Here is information about the Honeycomb query language:
{{query_language_info}}
Here are some guidelines for evaluating queries:
{{guidelines}}
# Examples
Example evaluations:
<examples>
<example-1>
<nlq>show me traces where ip is 10.0.2.90</nlq>
<query>
{
"breakdowns": ["trace.trace_id"],
"calculations": [{"op": "COUNT"}],
"filters": [{"column": "net.host.ip", "op": "=", "value": "10.0.2.90"}]
}
</query>
<critique>
{
"critique": "The query correctly filters for traces with an IP address of 10.0.2.90
and counts the occurrences of those traces, grouped by trace.trace_id. The response
is good as it meets the requirement of showing traces from a specific IP address
without additional complexities.",
"outcome": "good"
}
</critique>
</example-1>
<example-2>
<nlq>show me slowest trace</nlq>
<query>
{
"calculations": [{"column": "duration_ms", "op": "MAX"}],
…